A simple guide to move Sonoff / Tasmota / http devices to Edge driver

I was using the devices with firmware and device handler from ecrocm1231, Tasmota firmware with device handler from argiope then hongtat, and even developed a simple http button device handler for zmote IR blaster, during the groovy era.

So now it’s time to move, it took me a while to figure out how & which driver to migrate in Edge era, eventually I migrated all my devices using ST Edge driver from TAustin, so I decided to share the steps below:

This guide will cover 3 types of devices:

  1. SONOFF with firmware from ecrocm1231 (figure 1)
  2. Tasmota firmware
  3. Zmote IR Bluster (http)

Prerequisite (please install):

  1. Web Requestor from TAustin
  2. vEdge Creator from TAustin

Sonoff with firmware from ecrocm1231

Step to migrate:

  1. After install the web requestor, you will have the “Web Req Multi Master” in your ST App dashboard (usually under “No room assigned”).
  2. Click on the button point by the cursor (Figure 4 below) to create an instance of Web Requestor, you will find another device created with the name “Web Req Multi #” appear in your ST App.
  3. Open the newly created device, click on the 3 dots at the top right corner, Settings, setup the value for the Web Request #1 and #2 (refer Figure 5 for example).
  4. Open vEdge Creator V2, enter the “Quantity to Create”, select “Switch” for the type of Virtual Device to be created.
  5. A virtual switch will be created in ST App with the name “vEdge Switch #”
  6. Open the newly created device, click on “Routines”, “+” to add a new routine, see Figure 6 & 7 below for sample to setup on and off action.


(Figure 1)


(Figure 2, showing how to turn on a SONOFF device using http command)


(Figure 3, showing how to turn off a SONOFF device using http command)


(Figure 4, click on the button to create an instance of Web Req device)


(Figure 5)


(Figure 6)


(Figure 7)

1 Like

This is a sample setup screen for a Tuya power strips (4 individual controls), with Tasmota Firware.

Showing how to configure the virtual switch

1 Like

Sample of Zmote setup

Showing how to configure the virtual momentary button (suitable for IR device):

2 Likes

I experimented with this method a few weeks ago but was only able send commands to outputs, have you figured out how to change the vSwitch states based on inputs?

First of all, can you execute the action you want via http? If yes then you can use this approach

I had no problem with outputs using vSwitch and Web Req, it works great but I was unable to get inputs from the device to change the vSwitch state.

I have since changed to using MQTT which does everything I need but does require a broker.

What you want is the active callback / http hook to update the vswitch, I don’t think this solution will work for you.

Just thought that you’d be interested in the Tasmota Edge driver.

It’s probably simpler, and covers all you need. :grinning:

Your driver was the first I tested but could not get it to work for inputs. I then tested the method described here but had the same problem so ended up using Mosquitto. If your Edge driver would work for inputs (contact sensors) then it would be an ideal solution.

Yes, it will cover that soon.

1 Like

The purpose of this post is to show people what can be done with the simple yet flexible edge driver from TAustin, beyond just Tasmota support

Related to TAustin’s excellent drivers, you can also use the virtual device to post the http directly rather than setting it up in the main creator tool and referencing the pre-configured request. I found this easier when I was experimenting with these driver.

Do share the steps if possible, I can’t figure out how you do it.

It is the same method but instead of selecting a pre-configured request (in the routine) you select post or get and enter the http there.

Ok, that’s done within the web requestor right?

My approach of create virtual switch is to facilitate control using Alexa, individual switch make it easy.

No, it’s done with the virtual switch and works with Alexa control. It is the same as your process above except don’t select the pre-configured entry but instead just enter the post or get request. It bypasses needing to save (pre-configure) entries in the multi master so with multuple devices I thought it was easier to manage but your method works.

1 Like

I get what you trying to do, yes keep the url calling in virtual switch will be neater.

For scenario that need to add header and with extra body payload, can only preconfigure in the web requestor like my 3rd example above