Using a Sonoff with ESPEasy and a Vera home controller

Description

This post is to describe how I used Sonoff modules with my Vera Plus automation controller.  I'll explain the configuration and setup of the Sonoff, as well as the modifications needed to an existing plugin to make the whole setup work.

Details

Sonoff modules are cheap Wi-fi controllable relay modules that are based off of the ESP8266 chip.  Here I will describe how to control these with a vera home controller. The procedures described here should work for nearly any ESP8266 based relay module and are not exclusive to the Sonoff modules.

The basic outline of the procedures are as follows:

  1. Flash new firmware to the Sonoff or other ESP8266
  2. Set up and configuration
  3. Testing the device
  4. Installing the necessary plugin on your Vera
  5. The configuration settings
  6. Adding local control using the button
  7. Updating your Vera device based on the local button press

DISCLAIMER: I take NO responsibility for issues or problems that may arise from using the procedures outlined here. I am merely giving the information on what worked for me on the devices that I have. The procedures may be different for other ESP8266 modules. Please consult documentation on the modules that you have for more information. It should also be noted that this will wipe out the existing firmware on the device and it will no longer be able to be used as originally sold.

 

Flashing firmware to the Sonoff or other ESP8266

The first step in this process is to make sure we have the correct firmware loaded on your device.  The firmware that we will be using for this project is the ESPEasy firmware which is an open source firmware for ESP8266 modules. There are a few ways to flash the firmware to the device, but the procedures I will outline here for flashing this firmware to the device involve the use of the Arduino IDE.  One thing you will need to do the programming is an FTDI USB to serial adapter.  These can be purchased on ebay cheap. Lets get started.

The first thing you will need, if you don't have it already, is the Arduino IDE which can be downloaded from this link: https://www.arduino.cc/en/Guide/HomePage. Follow the installation procedures outlined on that page to complete the install.

Once you have the IDE installed, you will need to add the ability for it to flash the ESP8266 modules. To do this, got to File > Preferences, and just up from the bottom of the Window you will see a text box labeled "Additional Boards Manager URLS". In the box, paste this URL "http://arduino.esp8266.com/stable/package_esp8266com_index.json". You should now see some new entries in the list of available modules. The one we are concerned about for this post is the "Generic ESP8266 Module". Select that and the com port that you have your FTDI adapter attached to.

Next you will need to connect the FTDI adapter to the Sonoff module or other ESP8266 device. For the purposes of this post, I will only outline the connection to the Sonoff.  It is easies to solder a header connector on to the Sonoff on the center row of holes as shown below.  If you plan on flashing a lot of modules, you may want to make yourself an adapter cable to connect the FTDI adapter to the Sonoff.  The cable should be wired like the diagram below.

Next you will need the firmware to flash.  This can be downloaded from the SourceForge websit using this link: https://sourceforge.net/projects/espeasy/. In order to flash the firmware, you will need to put the Sonoff into programming mode. To do this, unplug the USB cable to the FTDI adapter, hold down the reset button (labeled GPIO0 in the image above) on the Sonoff module, then plug the USB cable in again. Now click the upload button in the Arduino IDE. The firmware should flash to the device. If for some reason it does not, chances are that you didn't get it into programming mode. Repeat the steps above and try again.

Set up and configuration

After flashing the firmware to the device, you need to do the initial configuration to get it to connect to your WiFi router. When a device with ESPEasy firmware starts for the first time, it will present itself as an access point. For the initial configuration you will need a tablet, smart phone, laptop or other wireless capable device. On your chosen device, go to your configuration screen for setting up WiFi. In your list of available access points to connect to, you should see one called ESP_0.  When you try to connect to it, it will ask for a password.  The default password is configesp.  After connecting to the device, go to a web browser and navigate to 192.168.4.1.  This should bring you to the new device wifi setup page.  This is where you will set the device up to connect to your access point.  Select your access point from the list, and if your wifi is encrypted and requires a password, type that in and click connect.  You should then see a page showing a countdown.  At this point the controller is attempting to connect to your access point.  If successful, your laptop, tablet or phone should automatically switch back to connecting to your regular wireless access point and navigate you to the IP address that the device picked up from your router's DHCP server.

You are now ready to perform the device specific configuration to define how you will connect to the device to your Vera.  For my setup, I picked a range of IP addesses that I would use for my Sonoff devices.  I made a list of my Sonoff devices and assigned them each an IP address. I left room in the pool of IP addresses I chose to have more room if I decided to add more of these to my setup.  You can judge this based on your configuration.

Now, in the menu at the top, click on "Config".  This will take you to the main device configuration page to define how you will connect to the device.  Here we will start by selecting a protocol to use.  I am not sure of the specifics for each protocol, but for my setup I chose the ThingSpeak protocol.  You can ignore the Controller IP and Controller Port for now.  Next we will set up the IP address for the device from the list that we made earlier.  You will set this at the bottom of the page under "Optional Settings".  All of these settings should be set as appropriate for your home network setup, but here is how I set mine up.  Type the IP address in the box labeled ESP IP.  Next you will need the IP address of your wireless access point which in most cases can be typed in for the ESP GW and ESP DNS settings.  And last would be setting your subnet mask in ESP Subnet, which again in most cases can be left at the default of 255.255.255.0.

The last thing that you need to configure is how the device will operate.  Since the ESPEasy firmware can be used on amy number of different ESP8266 devices, the firmware is highly configurable for many different types of devices.  For the HTTP Switch plugin that we will be setting up with Vera, we are only concerned about configuring a relay for now.

In the top menu, click on Devices.  On initial setup, the devices page should look like this.  Some things you will want to know prior to setting up the relay.  The standard Sonoffs have the relay connected to GPIO 12.  If you are configuring this for some other type of ESP8266 device you will need to consult any available documentation to find out which GPIO port the relay is configured on.  Start by clicking the Edit button for device number 1.  On the next page you will be given an option to select a device. For this select "Switch Input" since we will be controlling a relay.  Once selected, you will be given a list of configuration options.  The options we are concerned with for now are 1st GPIO, Pull UpSwitch Type, Switch Button Type, Send Boot State and Send Data.  For the 1st GPIO, select GPIO-12 for the Sonoff relay.  If you are using another ESP8266 device, select the GPIO that your relay is connected to.  For the Switch Type, simply select "Switch" as this is a relay controller.  Last is selecting the Switch Button Type which will be "Normal Switch".  You should also make sure to check the box next to Pull Up since we will be using the ESP8266 internal pull up resistors.  For my setup I have also checked the boxes for Send Boot State and Send Data.  All other settings for now can be left at their defaults.  Now click on Submit to save the new device configuration.

Now we will reboot the Sonoff by clicking Tools in the top menu and selecting Reboot.  This will cause any changes to be loaded.  If you made changes to the IP address on the Config page, you will most likely need to type the new IP address into your browser's address bar to access the newly configured device.

Testing the device

Prior to doing anything on the Vera side of things we will want to make sure that all of the work we did configuring the device is going to work.  The ESPEasy firmware uses GET based control commands that can be typed into your browsers address bar.  For testing we are going to use the command for turning on and off the device.  You will want to have something connected to your Sonoff or other 8266 device to be able to see if the commands work.  For me, I connected a small night light for this.  The command format that you will use is this:
http://{your device IP addess}/control?cmd=GPIO,{GPIO pin},{1 or 0}
In the command above, replace {GPIO pin} with the GPIO pin of the relay, in our case 12, and replace {1 or 0} depending if you want to turn on (1) or off (0) the device. When sent a command like this:
http://{your device IP addess}/control?cmd=GPIO,12,1
The device should give a JSON response that looks like this:

{
"log": "GPIO 12 Set to 1",
"plugin": 1,
"pin": 12,
"mode": "output",
"state": 1
}

If you can successfully turn on and off your Sonoff, you are ready to move on to configuring your device(s) in Vera.

Installing the necessary plugin on your Vera

In my setup I am using a Vera Plus controller running UI7.  This plugin should work on any Vera controller though running UI7.  I cannot verify, nor do I make any claims, that this will work on devices running UI5, though it may, so test it at your own risk.

The plugin that I modified to make all of this work is called "HTTP Switch (WiFi Switch)".  You must install this prior to uploading the modified files listed in the next section. 

Next, there are 3 files that you should upload to your Vera; D_HttpSwitch1.json, D_HttpSwitch1.xml and L_HttpSwitch1.lua.  A .zip file containing these 3 files can be downloded by clicking on this link. Once downloded, extract the files from the archive to a temporary folder on your computer. In your web browser, navigate to your Vera controller and in the left menu, click on Apps > Develop apps > Luup files. Drag and drop the 3 files into the Upload box or click the Upload button and select them. Once the files are uploaded, rebot you Vera controller by clicking on Settings > Net & Wi-fi and clicking on Reboot at the top. Once the Vera has rebooted, you should be ready to configure your first device.

The configuration settings

After installing the HTTP Switch plugin, it should have created one device for you. Navigate to Apps > My apps and click on the Details button for the HTTP Switch plugin. The newly created device should be listed under "This plugin has created the following devices:", click on the device.  To configure the device, click on Advanced and navigate to the Variables tab.  Your settings should look similar to this:

The first steps in configuring the device is knowing the devices IP address and the GPIO pin that you set up earlier. When setting the IP address or GPIO pin number in settings, you MUST check the box underneath that says "switch to input type text". If this is not done, it will not work. Set these two values and once set, reload the luup engine. Once the luup engine reloads, return to the advanced tab for the device. For the LinkStatus, you should see "Online!" and for PingStatus you should see "UP". If you see something like "Set IP!" for the LinkStatus, it is possible that you didn't check the box for "switch to input type text". Double check your IP address setting and fix as necessary. If the IP address is set, you may want to try restarting you Vera by clicking on Settings > Net & Wi-fi > Reboot. Once you see the status of the device as "online!", you should be able to control your device. If by chance you cannot, double check to see that you have the correct GPIO pin value set.

Adding local control using the button

So I had a request to explain how to use the ESP Easy rules scripting to make use of the local button and the LED on the Sonoff.   This will also allow control via a 433MHz remote or other controller if you are using a Sonoff RF device since the 433MHz receiver is connected to GPIO 0 which is the same GPIO port as the local switch.  Because of this, a 433MHz trigger is the equivalent to pushing the local button.  In this example, we will use the button to locally toggle the Sonoff module on or off.  Also, when the device is turned on or off, we will use the LED on the module to indicate the on/off state of the device.   Lets get started.

By default, the ESP Easy firmware has rules scripting disabled, so in order to use scripting, we need to enable it.  In the top menu, click on Tools and then click on the Advanced button.  Near the bottom, just above the Experimental Settings section, check the box next to "Rules:".  This will give you a new selection in your top menu called "Rules".

Before creating our Rules script, we need to create an additional device to be able to use the button.  Click on your Devices link in the top menu.  You should already have a device listed under Task 1 for your relay.  We will now add the onboard switch to Task 2.  Click on the Edit button for Task 2.  Chang the device settings to match the image to the left.  The two values from this screen that we will be using in the script are "Name", and "Value Name 1".  We will also use these same two values from the relay device that we created earlier.

Now lets write a simple script.  When you click on the Rules link, you will simply see a blamk box.  This is the script window where your script  will be placed.  First I will give you the rules script code, and then I will explain how it works.  Here is the script:

on Relay#Switch do
    if [Relay#Switch]=0
        gpio,13,1
    else
        gpio,13,0
    endif
endon

on Button#Switch do
    if [Relay#Switch]=0
        gpio,13,1
        gpio,12,1
    else
        gpio,13,0
        gpio,12,0
    endif
endon

So, there are two sections to the script, the first starts with "on Relay#Switch do", and the second starts with "on Button#Switch do".  In both sections you will notice the "Relay#Switch" and "Button#Switch".  These are the values from the devices that I mentioned earlier would be used in the script, and as can be seen, they are written in the format {Device Name}#{Device Value Name 1}.

The first part of the script deals with incoming HTTP requests and handles any change in the relay state with "on Relay#Switch do". Next, "if [Relay#Switch]=0" checks the status of the relay to see if it is "0", and if it is, turn the LED on which is on GPIO 13.  I am speculating that the check of the relay state happens before the relay is turned on or off, so when checking "if [Relay#Switch]=0" is true, we are about to turn it on, and vice versa.

The second part of the script deals with the button press using "on Button#Switch do". It again checks the state of the relay, but here we need to perform two actions; first turn the LED on (or off), and then turn the relay on (or off).  Seems simple enough.

One thing that I noticed in my testing of the script is that the response time was a bit slow.  When I would press the button, the device would come on, and then 5 to 7 seconds later the LED would come on.  I also had to wait a few seconds after turning it on/off before I could turn it off/on again.  When sending an HTTP request, the LED would come on at the exact second that the device turned on.  Maybe you will have different luck with yours.
EDIT:  Thanks to Patrick (from the comments below) it was said that if you edit any devices that you have in your devices list and uncheck the "Send Data" box, this will fix that issue.  I tested this on my units and the response time is very fast now.  Thank you Patrick.

I have only given you the basics of what the ESP Easy firmware can do.  With rules, you can perform actions such as sending HTTP or MQTT requests back to your controller and much more.  If you want to perform more complex actions with your rules, check out the rules tutorial on the Let's Control It website: https://www.letscontrolit.com/wiki/index.php/Tutorial_Rules

Updating your Vera device based on the local button press

So, now you have your Vera controlling your Sonoff devices.  You even have local control of those devices from the button on the Sonoff itself.  But you may notice that when you control your device locally with the button, the status of your device does not change on the Vera controller.  How can we fix this?  Luckily, the Vera controllers, at least for UI7, have the ability to receive LUUP action requests through HTTP requests on port 3480.  A typical HTTP request for a light switch looks like this:
http://{your-vera-ip}:3480/data_request?id=action&output_format=json&DeviceNum=122&serviceId=urn:upnp-org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=X

So let's analyze what is going on here.   First, we are making a data request, and based on id=action, we are telling Vera that we want to perform some kind of action.  Next, we are going to tell what the output format of the response to that action should be.  In this case, it will be a JSON response based on output_format=json.  The two most common formats are JSON and XML.  Since we are not going to be doing anything with the response in this example, we'll just leave it set to json.  The next thing is important.  It is the device number.  In the example we have DeviceNum=122.  The device number will be the device number of the Sonoff as it is defined on your Vera controller.  There are a few ways to find your device number.  One way is to look up your device from your "Devices" list, clicking the Vera device options arrow icon next to your device and then clicking on "Advanced".   The device number will show at the top of the page:
Vera device number
The next part is defining the service ID for the device which is  serviceId=urn:upnp-org:serviceId:SwitchPower1.  Since the Sonoff is a switch type device, this is what we'll use.  The next part defines the action we want to take, action=SetTarget, which is setting a value for a target device.  And last we'll set the value for that device with newTargetValue=X, where X is a boolean on (1) or off (0) value.

WHEW, you made it through that part, and hopefully you have some understanding of what is going on with the HTTP request.  Now we need to translate this to an ESP Easy's rules engine command.  Let's look back at the rules engine script that we created earlier.  Since our goal here is to relay back to Vera when the button is pressed, the specific part in the script that we want to look at is the "on Button#Switch do" section of the script.  In this part of the script we want to make two HTTP calls.  The ESP Easy rules script command that we will use is "SendToHTTP".  To use this command we need to break apart our HTTP request that we defined above into parts.  The parts will be separated by commas in this format without spaces between the commas:
SendToHTTP {Your Vera IP} , {Port #} , {Your HTTP call}
So using this format, our request above would translate to:
SendToHTTP {your-vera-ip},3480,/data_request?id=action&output_format=json&DeviceNum={your-device-number}&serviceId=urn:upnp-org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=X
Replace the parts in green with your values.  Here is the full script for my device.
on Relay#Switch do
    if [Relay#Switch]=0
       gpio,13,1
    else
       gpio,13,0
    endif
endon

on Button#Switch do
    if [Relay#Switch]=0
       gpio,13,1
       gpio,12,1
       SendToHTTP 192.168.1.123,3480,/data_request?id=action&output_format=json&DeviceNum=122&serviceId=urn:upnp-org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=1
    else
       gpio,13,0
       gpio,12,0
       SendToHTTP 192.168.1.123,3480,/data_request?id=action&output_format=json&DeviceNum=122&serviceId=urn:upnp-org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=0
    endif
endon
Immediately after we tell GPIO 12 (the Sonoff relay) to turn on or off, we send the appropriate call back to the Vera controller to update the device status.  That's all there is to it.

Conclusion

I hope that this tutorial was helpful.  If you have problems or find errors, leave a comment and I will try to help.

Happy automating.

Related Images:

80 Replies to “Using a Sonoff with ESPEasy and a Vera home controller”

  1. I don’t have a Vera, but it’s probably the controller I’ll be getting for my new house, so I’m researching my options.

    Now wouldn’t it be easier to just add a virtual switch with a Luup code that sends an HTTP request to the Sonoff?

    As per documentation:

    http://wiki.micasaverde.com/index.php/Luup_Scenes_Events#Access_the_web

    Now ESP Easy has a great feature that’s not available in other ESP firmwares out there. It can be scripted to send HTTP requests itself based on events or timers and Vera can receive those on port 3480.

    Here’s the docs:

    http://wiki.micasaverde.com/index.php/Luup_Requests

    So let’s say you have a Sonoff relay with a physical switch connected to GPIO14. When switched, the Sonoff would send an HTTP request to the Vera to update the state of the virtual switch in the UI.

    Or you can use a thermometer hooked up to the Sonoff and pass the temperature value to the Vera every X seconds. Or whatever. There seem to be endless possibilities.

    Another thing I’d configure on a Sonoff relay is sending its state to the Vera every X minutes. Say there is a power outage and all your devices reboot. In this scenario, virtual switch created for the Sonoff in the Vera UI would probably not reflect the real state of the relay, but would self-update after the Sonoff sent its state to the Vera.

    Now again, I don’t have a Vera, so my idea is based on what I can read in the docs and on forums, but that should integrate nicely, at least in theory.

    1. I guess I had never thought of or even looked into how to use virtual switches.   I hadn’t even really looked on the Vera wiki pages.  I ended up finding the HTTP Switch plugin while browsing available plugins and found that it was close to what I wanted, so I just made the few modifications to make it work.  

      My primary automation platform for hardware and things that I connect to my Vera is based on MySensors.  The switches I use are MySensors based switches and everything is controlled using scenes on my Vera. 

      I have not even looked into the scripting capabilities of the ESP Easy firmware. I may have to look at some of this further.  

      Thanks for the post and hope you enjoy the website. 

  2. Hi this tutorial is great!! I setup a Sonoff relay and it is working perfectly except for that I can’t control the relay with the button on the sonoff itself. Is that normal or not? is there a way to be able to switch it with this button?

    Thanks for the great work!

    Jonathan

    1. Jonathan,  

      Thanks for the compliment, glad you like the tutorial.  The button on the sonoff controllers is not an on/off button.  It is a reset button which is connected to the reset line of the ESP8266.  There is however an extra exposed GPIO line.  GPIO 14 to be exact, which is on the header connector used for programming.  You could potentially connect an external button to that.  I have not looked into it, but as I understand it, the ESP Easy firmware allows some scripting in the module itself which should allow you to watch for the button press on GPIO 14 and toggle the relay which is on GPIO 12. 

      1. Okay, but when you use the original firmware which the sonoff comes with the button can be used to turn the relay on and off, so I think that’s weird :/

        1. My appologies, you are correct.  I have never used the original firmware, but I looked again and the button is actually NOT connected to the reset pin.  It is actually connected to GPIO 0, so you could technically script that to toggle the relay.  I will do some research on the script code needed to do that and add it to the article.

          Thanks for the posts 

          1. That would be awsome! And maybe you can use the led on the board as status light? If it’s possible ofcoarse. 🙂 But thanks for checking it out! 😉

          2. Jonathan,

            I have updated the tutorial to show how to use scripting/rules with the Sonoff and ESP Easy.  I have added it at the end just before my conclusion.  In my research, I have found that the Rules engine is pretty powerful.  Hope it works for you.

          3. Hi Dan,

            Thanks for adding the button script to the tutorial, it works really well! 😉
            But do you maybe know how I can write some code in the script so that the status off the relay is updated on the vera controller?

            Thanks!

            Jonathan Caes

    1. Tomasz,

      You don’t need to do this in Vera. You can do this directly from the Sonoff. Go to your Sonoff device IP address/web page and click on the devices tab in the top menu. For the switch input device you have under task 1, click the edit button on the left. From the edit screen, look for “Inversed” in the middle of the screen and check the box next to it. That will cause the device to act inverted.Inverting the sonoff relay

      1. Hi Dan,
        This is a fantastic run down…and I’m so glad I found this page.. it’s exactly what I was looking for, I managed to set up the whole thing perfectly… The only hickup I had was that after adding the script, the button and the LED wasn’t working as expected. These were the symtoms I was experiencing….
        – when i power up the sonoff unit, the LED is off, when i press the button, only the LED turns on, the lamp does not.
        – When i press the button again, nothing happens. LED stays on, and the lamp stays off.
        Using Vera, i can turn the Lamp on and Off, but the LED stays off either way.
        – If the Lamp is on, the local button will turn lamp off, and the LED will turn on – after this point i can not turn the LED off, unless i power the unit down.

        After various test of the script I found that the statement
        if [Relay#Switch]=0
        gpio,13,1

        Was always being skipped.. turns out that under the 1st device you have to set the Name to be “Relay”. Initially mine was blank, as soon as I made this update everting started work as expected.

        If anyone is thinking about putting this up into the celling rose and wants to have their wall toggle switch working with it too….. You have to connect gpio 14 an gnd to the wires going to the switch..and you also have to change device 2, switch button type to ‘Normal Switch’.

        Now….let order some more 🙂

        Sups

        1. Thank you, I enjoy helping people with things like this. You mention about using GPIO 14 for adding a switch when ceiling mounting it. What if you just soldered wires to the onboard button that runs on GPIO 0? GPIO 14 can also be used, but you would have to update the rules script which wouldn’t be hard.

  3. To anyone that has used this with their setups, Thanks to a Russian forum site, I found an error in this plugin. The main part of this hack uses an HTTP Switch plugin that I found on the Vera plugins page. I simply modified what the original creator had done, so this means that the person who originally posted the plugin got it wrong.

    The problem has to do with the device_type that is created when adding a new switch device. The person that created the original plugin had the default device type for a new device at “urn:upnp-org:serviceId:SwitchPower1”. The correct device type should be “urn: schemas-upnp-org: device: BinaryLight: 1”. The difference is that one is a service and the other is a device. Because of this, the device was switchable on the Vera side of things from the main controller, but it wouldn’t work if you used something like ImperiHome. For that matter, I don’t even think ImperiHome would see the device to be able to add it to things because if this. I have uploaded an updated .zip file with the changed file. Really the only file that changed is the D_HttpSwitch1.xml file, but I uploaded the new zip file with all 3 files for anyone new that drops in.

    Hope that helps.

  4. Hi there,

    Great work thank you. This is awesome but is there any (quick) way to make it work with UI5? I tried uploading your files but no device is created. The app store version installs but of course, it does not work with ESPEasy.

    Pete

    1. I wish I could help, but I have never used UI5, only UI7, so I don’t even know what changes would be necessary. you may want to check with the original creator of the plugin that I modified to see if he knows. Here is a thread on the micasaverde forums for that plugin. http://forum.micasaverde.com/index.php/topic,33337html If you figure it out and can let me know, I will add the necessary changes to my blog post.

      1. Looks like no development for some time so not much point posting but I got it working anyway. Install the app in UI5 through the app store so the HTTP switch device is created then overwrite the LUA files with yours using the Upload File option. GPIO pin now configurable! This is great stuff, thank you.

        I’ve now created two switches controlling a dual Electrodragon relay.

        1. Here is my blog post quote that actually says to do that.

          The plugin that I modified to make all of this work is called “HTTP Switch (WiFi Switch)”. You must install this prior to uploading the modified files listed in the next section.

          Maybe you missed that. Anyways, glad to see that you got it working.

          I don’t know if you were aware, but this should work with any ESP8266 based module controlling a relay, not just a Sonoff. One of these days I may do some more mods to the plugin and actually release it as a new plugin advertised specifically for ESP8266 devices running the ESP Easy firmware. The ESP Easy firmware can be set up to handle all kinds of different sensors, so maybe I will look into adding support for some other basic sensors like temp and humidity sensors and the like.

          1. I am guessing then that that is an issue with UI5. Everything works fine in UI7. If you feel like looking, I believe that the icons are defined in the D_HttpSwitch1.json file. Maybe look to compare that with a light switch .json file from another type of light switch that you have working in UI5.

          1. Thanks Dan. I really appreciate your help and know how frustrating this is when your running blind. That fixed the icons but sadly the light bulb still not does change state on action.

            I also noted that there is no device selection available when selecting notifications unlike other entities so maybe that is related (no state change, no icon change) even though the Sonoff relay does pole?

            Screenshot here https://1drv.ms/i/s!AjRs7Xpm-jMMhuN9WqZNppFrnousxA

          2. Yes, I know what you are saying. Almost wish I knew more about plugin development, but then again, it seems that UI5 is quite different from UI7. Have you ever thought of switching to UI7?

  5. Thanks Dan. I tried a Vera Edge with UI7 (awful UI!) but I have a IO module that brings in my garage door reed and rain sensor and UI7 did not work with that and it got too hard.

    I like to solve problems but my strength is hardware not software. Would’ve been great to get this working in UI5 but I understand the constraints.

    1. I have my VeraPlus box that I got about a year and a half ago and it came with UI7, so I have never even used UI5. I have only seen pictures and some short videos.

      I do both hardware and software. I am a computer tech for our local school district. One of my biggest software projects has been a web based software package That takes care of inventory and work order tracking, software license management and manages our 1 to 1 laptop program that manages the laptops that we hand out to students. I completely designed the framework and the UI for it.

      I am mainly a hardware guy though. For my Home automation stuff I have converted much of it to sensors that use the MySensors framework. I have built many of my own sensors and switches/scene controllers. The switches that I use with Vera to control my Sonoff devices are of my own creation. I have made custom PCBs for the project and have them in a few places around my house. Check out my thread in the MySensors forum https://forum.mysensors.org/topic/4317/us-decora-style-wall-switch/34.

      Everything that I work with, be it hardware or software requires some bit of understanding of what I am working on. That is true for anyone. If there is anything else I can help with, hardware or software wise, I am always glad to share my knowledge. Don’t hesitate to ask.

  6. Thanks for the work Dan! Got everything working.

    Do you know if it’s possible to update the status in Vera when you use the local push button?

    1. I’ll look up how to do that and add it to the blog post tonight. My guess is that there is some sort of HTTP request that you can send to the Vera to do that. I would just then have to figure out the scripting end of ESP Easy to make it work.

    2. Patrick,
      I have updated the blog post to show how to update the Vera status based on a local button press. Try it out and let me know if you have any issues with it.

      1. Thanks Dan! Will try that and let you know how it goes.

        I had another problem: the device didn’t show up in Imperihome. I checked the advanced settings and under device_type it had the right type but had some spaces in the syntax. Removing them from the advanced screen didn’t work offcourse as the luup reload put back the old one. I then checked the D_HttpSwitch1.xml and removed the spaces from the device_type section. After a luup restart the device was visible in Imperihome. Maybe you can correct this in your file on the site.
        Thanks again for the effort!

        1. Patrick,

          I had run into that same issue. I thought I had uploaded the updated file that corrected that issue, but it appears that I didn’t. I will get that fixed right away. Thanks for pointing it out. Let me know how the local button status updates work out for you. I always like hearing the success stories.

  7. It’s working nicely Dan! Updates to the Vera are usually quite fast as well.

    I experienced the same delay as you discribed in your original post. Sometimes it took a couple of seconds for the LED to turn on after pushing the local button.
    I checked the log and they were some: “HTTP : connection failed” errors and after a few of those errors the device would reboot.
    I found out that the device tried to connect to a controller to update the devices status. Offcourse it can’t because in this case we don’t use the controller in that way. I unchecked the “send data” option in the devices section and that fixed it. No more errors in the log and the response is fast.
    Also set the log levels to 0 to free up some up RAM. Now see how the device performs for a longer time.

    1. Patrick,

      I just unchecked the “Send Data” option for my test unit and you are correct, the response time now is really fast. I am going to edit and add that to the article and mention you. Heck, I can’t take all the credit.

        1. Hi Dave,

          I unchecked the send data option and changed the log levels to 0 and the delay for led is still 7 seconds and the status update delay is about 1 minute.. Are these similar to the results you have are is there a way to improve this?
          Thanks by the way for the other improvements!!

          Jonathan

          1. Jonathan,

            My name is Dan BTW.
            First, go to Tools and click on Log. See if the device shows any ConnectFailures. Then, reboot the device. Once rebooted, check your log for ConnectFailures again. If you are continually getting ConnectFailures, you may want to check the distance to your wifi router and anything that may obstruct the signal in between. That could be your problem.

            Do you have it scripted to update your Vera controller? If so, make sure it is doing that. If that is not working, that could be another problem. The Sonoff may be trying to contact your Vera controller to send the update and if it can’t reach it, there will be a significant delay. If that is all working, can you post your rules script?

          2. When I look into log it gives me this:
            86738 : SW : GPIO 12 Set to 1
            86739 : ACT : SendToHTTP 192.168.0.142,3480,/data_request?
            92851 : ACT : id=action&output_format=json&DeviceNum=180&serviceId=urn:upnp-
            92856 : ACT : org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=1
            92871 : SW : State 1
            92872 : EVENT: Relay#Switch=1.00
            92876 : ACT : gpio,13,1
            92878 : SW : GPIO 13 Set to 1
            96919 : WD : Uptime 1 ConnectFailures 0 FreeMem 29024
            126920 : WD : Uptime 2 ConnectFailures 0 FreeMem 29024

            And this is my rules script:
            on Relay#Switch do
            if [Relay#Switch]=0
            gpio,13,0
            else
            gpio,13,1
            endif
            endon

            on Button#Switch do
            if [Relay#Switch]=0
            gpio,13,0
            gpio,12,1
            SendToHTTP 192.168.0.142,3480,/data_request?
            id=action&output_format=json&DeviceNum=180&serviceId=urn:upnp-
            org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=1
            else
            gpio,13,1
            gpio,12,0
            SendToHTTP 192.168.0.142,3480,/data_request?
            id=action&output_format=json&DeviceNum=122&serviceId=urn:upnp-
            org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=0
            endif
            endon

            Everything works well, the led comes on and goes off, the status in vera gets updated, the only problem is that the delay is very long.
            I also unchecked the “send data” line like mentioned in the blog.

          3. Everything looks to be right with what you posted. Do you have send data unchecked for both the relay and the button in devices?

          4. No should be 180. Thanks for the call. The led has a delay of about 6 seconds and the status to the vera now has a delay of about 10-15 seconds.

    1. Jonathan,

      One thing i can see in your script is that you use two device numbers (180 and 122). Is that correct?
      What is delayed? The status to the Vera, relay or LED??

      1. oh yeah, that is fixed.
        now the delay of the LED on the ESP is about 6 seconds.
        and to update the status in vera the delay is about 10-30 seconds.
        the relay changes state immediatly.

        1. Hi Jonathan,

          Strange! Although the updates to my Vera sometimes take a while, the LED goes on immediately when i push the button.
          Did you name your devices correctly (name and Value Name 1)??

  8. I checked everything and it all matches your description.
    The settings of relay device and button device are exactly the same as yours. So can’t figure out what is wrong with it.
    Do you have the logging feature enabled or set to 0?
    And the message delay, is it set to 0 or something else on yours?
    Weird :p

    1. Jonathan,

      So just to be sure: you named the first device mentioned in Dan’s post: Relay? Because in Dan’s example the name field is not filled in. Second device should be named: Button. Later these two devices are reffered to in the script.
      At the moment i have set log level to 0 which is ok if everything is good. Maybe you should change it to level 3 or 4 so you can see what is is no going on.
      The whole web interface (including the different log levels) is described here:
      https://www.letscontrolit.com/wiki/index.php/ESP_Easy_web_interface

      My delay is set to 1000ms

      1. Yes, all the names are correct.
        And when I look into the loggings there is no error when I push the button or when toggled by vera.
        And that delay was set to 1000 before and gave the same result so that’s not the problem.
        I think I have to let it go. :/

        1. Hi Jonathan,

          I checked your script again you posted in a previous message. If i compare it with Dan’s script and my script i can a see difference in the starting GPIO states. Maybe you can copy-paste Dan’s script one more and see if that helps? In that case you should have the exact same configuration as us.

          1. Is it the gpio 13 you mean? For the LED? For that it’s on when the relay is off and vice versa. This way it is easier to see where I need to push in the dark :p
            But I’ll try that one more time and see if that helps.

  9. I already thought that was the idea 🙂

    If i have some time this weekend i will try your script as well. In the device options i have seen an “inversed” option. Maybe that will work in your case.

  10. I’m truly enjoying the design and layout ᧐f your website.

    It’s a very easy on the eyes ᴡhich makes it much moгe pleasant for me to come hеre and
    visit more often. Diɗ you hire out a developer to create your theme?

    Fantaѕtic work!

    1. The theme is actually a free one called “Twenty Seventeen”. I did the home page video background myself piecing together a couple free tech intro clips that I found on youtube. The other images are just some free desktop background pics I found on a google search.

  11. For those that want to register as a user on my site, you can click the register button at the bottom of the page.

    For those that want to just subscribe to my blog to be notified of new blog posts, add your email address under the “Subscribe to my Blog via Email” section in the right menu. I do not share email addresses with ANYONE. Your email will ONLY be used for the purposes of blog notifications.

  12. Good morning,

    I bought the devices you reported, followed the procedures but I have problems installing the “http switch” app. After several attempts he installed it, I imported his files but still can not create any devices. Do you have any advice? I have a veraplus with firmware UI7. Thank you so much for your work.

      1. Hello Dan Bemowski,

        sorry if I did not answer you first but I had problems with my real no longer available and now I’ve solved it. The problem I find is that once I install the plugin I do not see any new device, even if I try to create another plugin interface, so the whole process stops there. Another problem is that I installed the new firmware on the Sonoff and despite the procedure being successful, the device does not start the hotspot, so I can not see it to configure it. Greetings and thanks for your work.

        1. Have you checked to see that after the install you see it in Apps > My apps in the menu? If you do, click on the [Details] button next to “HTTP Switch (WiFi Switch)”. Once in there, do you see any devices listed under “This plugin has created the following devices:”? If there is nothing listed, that would be why you don’t see anything under Devices in the menu. Are you able to click on the [Create another] button at the bottom? If so, try to create a device from there and let us know how it goes.

          1. Thanks for the answer, I had already done all the tests you told me but without any positive results. I do not know what to do. Greetings.

  13. Hi, I was able to install the plugin, and create the device, the problem was due to my true. Now it remains only as the problem on the flash module sonoff, it will not create the hotspot. Good work and thank you very much.

    1. How are you flashing the Sonoff module? Are you using the arduino IDE or some other method? Are you sure the Sonoff flashed correctly? Did you hold the reset button on power up to put it in programming mode?

  14. Hello, I have used is the Arduino IDE is .bat present in the firmware project espeasy r120. The writing from the IDE response is completed, but after the cre not reset the hotspot. I bought a FTDI module for programming which allows you to select both 5V and 3.3V is it possible that the transmission signal will remain at 5V and burn the ESP8266? Even if i put the jumper 3.3V. Thanks and good job.

  15. Thanks Dan, with your suggestion I managed to flash the device. As soon as I get home I try to handle it from the file. Greetings.

  16. Hi Dan,

    Thanks to your help I did everything. One problem remains, I can not create new devices from the app. I wanted to use more than one jest but I do not really create the devices. How did you solve the problem? Thanks and good work.

    1. To create a new device, go to Apps > My apps in the menu and click on the [details] button next to the HTTP SWitch (WiFi Switch) plugin. Under there, click the [Create Another] button at the bottom. That should let you create new devices.

  17. Thanks Dan for your fantastic job,

    in the end the problems are from my central but control the devices through scenes that send the following command:

    http = require “socket.http”
    result, statuscode, content = http.request (“http://192.168.1.40/control?cmd=GPIO,12,1”)

    and everything works to perfection.

    The only problem is that the SONOFFs turn off automatically after two hours and are no longer reachable via web browsers so I have to restart it by disabling the input and re-energizing it. Do you think it is a function to be modified on SONOFF?

    Good job.

    1. Did you change any settings in the hardware tab of your Sonoff? I had changed some settings on a couple of mine and they would hang and stop responding. Mine would stop responding within a minute or two, not two hours? I have also heard from some that if you have “Send Data” checked under your devices, that that can cause some trouble in certain situations. I myself have not seen that though. How far is the thing from your wireless router? See if you can ping the IP address from your computer. Outside of that I am not sure what to tell you. Maybe someone else reading this may have more suggestions.

Leave a Reply

Your email address will not be published. Required fields are marked *