[ST Edge] •• Tasmota Edge •• for Sonoff, Tuya & many other ESP WiFi & HTTP devices - over 2000 Tasmota supported devices

Was on 8.1 or maybe 9.1 the whole time through tasmota connect, Went to 12.3.1 for edge, so yes, currently 12.3.1.

Just now rolled one back to 11.1.0, fiddled with sleep commands, same behaviour as with 12.3.1.

I was on a mix of 10.0, 10.1, and 11.1 before the edge driver. Then I standardized on 12.1.1, then 12.3.1.

My early results with downgrading to 9.1 are not successful in solving the problem.

I’m finding it’s not simply an offline problem.

Sometimes the device is shown as offline, but most of the time they’re showing as online but the on off buttons do nothing. Or the buttons show as if they’re doing something but the device does not turn on and off to follow. Or get this, yesterday on a Sonoff POWR2 when the latter was happening, the power statistics were still updating.

When controlling on off doesn’t work with this driver, I’ll jump over to the Tasmota web UI for the device, TasmoAdmin, or Home Assistant (using MQTT) and on off works. For that reason, I’m thinking I might test the SmartThings MQTT edge driver to see if just Tasmota Edge is exhibiting the problem or if the problem is related to SmartThings in general.

I have a switch, a contact sensor, and a DS18B20 on a ESP8266. The sensor discovery keeps adding duplicates. When I go delete the duplicate it automatically adds it back in.
In the Edge portal… I see it listed twice, once in the Sensor section and again in the switch section.
image

Also is it possible to detect the ADC Range value?

I’m investigating.

Can I have the output of http://<IP address>/cm?cmnd=status 0?

Does “pull to refresh” the offline tasmota devices in ST app set the device to online again (assuming they are still accessible via tasmota web UI) ?

Are the Tasmota devices and ST hub on the same subnet; e.g. 192.168.1.XX ?

Tasmota Edge doesn’t use rule3, you can combine the 3 rules into a single rule under rule3. Would that work for you?

{“Status”:{“Module”:18,“DeviceName”:“Tasmota173”,“FriendlyName”:[“Tasmota173”],“Topic”:“tasmota_xxx”,“ButtonTopic”:“0”,“Power”:0,“PowerOnState”:3,“LedState”:1,“LedMask”:“FFFF”,“SaveData”:1,“SaveState”:1,“SwitchTopic”:“”,“SwitchMode”:[1,0,0,0,0,0,0,0],“ButtonRetain”:0,“SwitchRetain”:0,“SensorRetain”:0,“PowerRetain”:0,“InfoRetain”:0,“StateRetain”:0,“StatusRetain”:0},“StatusPRM”:{“Baudrate”:115200,“SerialConfig”:“8N1”,“GroupTopic”:“tasmotas”,“OtaUrl”:“http://ota.tasmota.com/tasmota/release/tasmota.bin.gz",“RestartReason”:"External System”,“Uptime”:“0T05:59:09”,“StartupUTC”:“2023-01-12T23:45:11”,“Sleep”:50,“CfgHolder”:4617,“BootCount”:27,“BCResetTime”:“2022-11-20T20:34:22”,“SaveCount”:248,“SaveAddress”:“F4000”},“StatusFWR”:{“Version”:“12.2.0(tasmota)”,“BuildDateTime”:“2022-10-17T08:39:23”,“Boot”:31,“Core”:“2_7_4_9”,“SDK”:“2.2.2-dev(38a443e)”,“CpuFrequency”:80,“Hardware”:“ESP8266EX”,“CR”:“443/699”},“StatusLOG”:{“SerialLog”:2,“WebLog”:2,“MqttLog”:0,“SysLog”:0,“LogHost”:“”,“LogPort”:514,“SSId”:[“Indigo-IOT”,“”],“TelePeriod”:300,“Resolution”:“558180C0”,“SetOption”:[“00008109”,“2805C80001000600003C5A0A192800000000”,“01008080”,“00006000”,“00004000”,“00000000”]},“StatusMEM”:{“ProgramSize”:626,“Free”:376,“Heap”:24,“ProgramFlashSize”:1024,“FlashSize”:4096,“FlashChipId”:“1640D8”,“FlashFrequency”:40,“FlashMode”:“DOUT”,“Features”:[“00000809”,“8F9AC787”,“04368001”,“000000CF”,“010013C0”,“C000F981”,“00004004”,“00001000”,“54000020”,“00000000”],“Drivers”:“1,2,3,4,5,6,7,8,9,10,12,16,18,19,20,21,22,24,26,27,29,30,35,37,45,62”,“Sensors”:“1,2,3,4,5,6”},“StatusNET”:{“Hostname”:“tasmota-1946”,“IPAddress”:“192.168.1.173”,“Gateway”:“192.168.1.1”,“Subnetmask”:“255.255.255.0”,“DNSServer1”:“192.168.1.47”,“DNSServer2”:“8.8.8.8”,“Mac”:“xxx”,“Webserver”:2,“HTTP_API”:1,“WifiConfig”:4,“WifiPower”:17.0},“StatusMQT”:{“MqttHost”:“”,“MqttPort”:1883,“MqttClientMask”:“DVES_%06X”,“MqttClient”:“DVES_DD079A”,“MqttUser”:“DVES_USER”,“MqttCount”:0,“MAX_PACKET_SIZE”:1200,“KEEPALIVE”:30,“SOCKET_TIMEOUT”:4},“StatusTIM”:{“UTC”:“2023-01-13T05:44:20”,“Local”:“2023-01-13T06:44:20”,“StartDST”:“2023-03-26T02:00:00”,“EndDST”:“2023-10-29T03:00:00”,“Timezone”:“+01:00”,“Sunrise”:“08:39”,“Sunset”:“17:17”},“StatusSNS”:{“Time”:“2023-01-13T06:44:20”,“Switch1”:“OFF”,“ANALOG”:{“Range”:1266}},“StatusSTS”:{“Time”:“2023-01-13T06:44:20”,“Uptime”:“0T05:59:09”,“UptimeSec”:21549,“Heap”:24,“SleepMode”:“Dynamic”,“Sleep”:50,“LoadAvg”:19,“MqttCount”:0,“POWER”:“OFF”,“Wifi”:{“AP”:1,“SSId”:“Indigo-IOT”,“BSSId”:“xxx”,“Channel”:11,“Mode”:“11n”,“RSSI”:100,“Signal”:-46,“LinkCount”:1,“Downtime”:“0T00:00:05”}}}

I’m using the ADC range to monitor the voltage of a 12v battery. Trying to create rules around this ADC value.
thx

Hello I don’t understand well. Tasmota edge don’t support rule3 or not?

I found 2 workoround…

1st mode:
I modified the configuration of device, instead of 3 button i use 3 “virtual” relay used to trigger each rule.
In this way tasmota edge recognize the relay like switch and i can command them from smarthings.

2nd mode:
I used your http button to send command for the rule.

Hello, i’m stil investigating in sensors with tasmota edge…

I used a lot of sensors: (in red the data not imported in smartthings)

{“Status”:{“Module”:18,“DeviceName”:“Tasmota”,“FriendlyName”:[“Tasmota”],“Topic”:“tasmota_876C21”,“ButtonTopic”:“0”,“Power”:0,“PowerOnState”:3,“LedState”:1,“LedMask”:“FFFF”,“SaveData”:1,“SaveState”:1,“SwitchTopic”:“0”,“SwitchMode”:[0,0,0,0,0,0,0,0],“ButtonRetain”:0,“SwitchRetain”:0,“SensorRetain”:0,“PowerRetain”:0,“InfoRetain”:0,“StateRetain”:0,“StatusRetain”:0},“StatusPRM”:{“Baudrate”:115200,“SerialConfig”:“8N1”,“GroupTopic”:“tasmotas”,“OtaUrl”:“http://ota.tasmota.com/tasmota/release/tasmota.bin.gz",“RestartReason”:"Software/System restart”,“Uptime”:“0T00:36:47”,“StartupUTC”:“2023-01-15T10:40:19”,“Sleep”:50,“CfgHolder”:4617,“BootCount”:62,“BCResetTime”:“2023-01-10T18:01:17”,“SaveCount”:98,“SaveAddress”:“FA000”},“StatusFWR”:{“Version”:“12.3.1(sensors)”,“BuildDateTime”:“2022-12-16T10:28:17”,“Boot”:31,“Core”:“2_7_4_9”,“SDK”:“2.2.2-dev(38a443e)”,“CpuFrequency”:80,“Hardware”:“ESP8266EX”,“CR”:“413/699”},“StatusLOG”:{“SerialLog”:2,“WebLog”:2,“MqttLog”:0,“SysLog”:0,“LogHost”:“”,“LogPort”:514,“SSId”:[“ASUS”,“”],“TelePeriod”:300,“Resolution”:“558180C0”,“SetOption”:[“00008009”,“2805C80001000600003C5A0A192800000000”,“00000080”,“00006000”,“00004000”,“00000000”]},“StatusMEM”:{“ProgramSize”:689,“Free”:312,“Heap”:15,“ProgramFlashSize”:1024,“FlashSize”:4096,“FlashChipId”:“164020”,“FlashFrequency”:40,“FlashMode”:“DOUT”,“Features”:[“00000809”,“8F9A8787”,“0415A005”,“B7F7BFCF”,“05DA9BC4”,“64367CC7”,“00084052”,“20000000”,“54000020”,“00000081”],“Drivers”:“1,2,3,4,5,6,7,8,9,10,12,14,16,17,20,21,24,29,34,62”,“Sensors”:“1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,17,18,19,20,21,22,26,28,31,34,37,39,40,42,43,45,51,52,55,56,58,59,62,64,66,67,74,98”},“StatusNET”:{“Hostname”:“tasmota-876C21-3105”,“IPAddress”:“192.168.66.125”,“Gateway”:“192.168.66.254”,“Subnetmask”:“255.255.255.0”,“DNSServer1”:“192.168.66.254”,“DNSServer2”:“0.0.0.0”,“Mac”:“48:3F:DA:87:6C:21”,“Webserver”:2,“HTTP_API”:1,“WifiConfig”:4,“WifiPower”:17.0},“StatusMQT”:{“MqttHost”:“”,“MqttPort”:1883,“MqttClientMask”:“DVES_%06X”,“MqttClient”:“DVES_876C21”,“MqttUser”:“DVES_USER”,“MqttCount”:0,“MAX_PACKET_SIZE”:1200,“KEEPALIVE”:30,“SOCKET_TIMEOUT”:4},“StatusTIM”:{“UTC”:“2023-01-15T11:17:06”,“Local”:“2023-01-15T12:17:06”,“StartDST”:“2023-03-26T02:00:00”,“EndDST”:“2023-10-29T03:00:00”,“Timezone”:“+01:00”,“Sunrise”:“08:38”,“Sunset”:“17:20”},“StatusSNS”:{“Time”:“2023-01-15T12:17:06”,“HTU21”:{“Temperature”:17.7,“Humidity”:51.5,“DewPoint”:7.6},“BMP280-76”:{“Temperature”:18.5,“Pressure”:980.8},“BME680-77”:{“Temperature”:18.5,“Humidity”:48.8,“DewPoint”:7.5,“Pressure”:980.2,“Gas”:43.78},“SHT3X-44”:{“Temperature”:18.1,“Humidity”:57.1,“DewPoint”:9.4},“SHT3X-45”:{“Temperature”:18.7,“Humidity”:51.3,“DewPoint”:8.4},“SGP30”:{“eCO2”:471,“TVOC”:352,“aHumidity”:7.7964},“PressureUnit”:“hPa”,“TempUnit”:“C”},“StatusSTS”:{“Time”:“2023-01-15T12:17:06”,“Uptime”:“0T00:36:47”,“UptimeSec”:2207,“Heap”:15,“SleepMode”:“Dynamic”,“Sleep”:50,“LoadAvg”:19,“MqttCount”:0,“Wifi”:{“AP”:1,“SSId”:“ASUS”,“BSSId”:“16:94:AD:6D:0A:C6”,“Channel”:11,“Mode”:“11n”,“RSSI”:100,“Signal”:-48,“LinkCount”:1,“Downtime”:“0T00:00:09”}}}

It’s possible to add?

I’m still only seeing 8 max sensors.
How can I add more than 8 contact switches?
I got a new esp32 to replace all my Konnected esp8266. I need 20 contact sensors.
Thx

With some companies now moving away from ESP8266 to BK7231 based chips, are there any thoughts on support for OpenBeken?

Did you have any luck with this?

I’ve taken these types of plug out of the system. No good asking google to turn something on that’s not easily accessible when it’s offline all the time

Can you explain this? I set up my template to map my Konnected (esp8266) pins and have installed a few devices with the Tasmota edge driver but I don’t see anything “happening” when I open/close my doors.

I haven’t yet had time to try out the MQTT Edge driver. Will do it, though.

I hear ya. I just have too many of them in service (and they were so cheap) to be able to replace them

1 Like

in the Tasmota console, enter the commands
switchmode 1 * this sets your contact switches to follow mode.
image

enter setoption114 1 * this unlinks the switches to the relays
image

I was having lots of issues when I first converted from konnected.

what device is giving you issues? I have it running with no issues on the ESP8266

Thanks! I finally got one door sensor working end to end. Creating devices in ST is a little weird. It created a duplicate device each time I created a device. This “second” device seems to work while the first one does not. I’ll play around to see if this keeps happening.

@MagicMike @BartschLabs

Could you confirm whether you can still control (e.g. on/off) via the Tasmota device IP address when the device is marked as offline in SmartThings?

If can, I guess it’s probably an intermittent Wifi issue and the online/offline detection in the Tasmota Edge driver is too sensitive. It currently marks the device as offline after 1 “fail to connect” attempt. I can adjust the sensitivity level, so that it will only mark the device as offline when ST hub is unable to connect to the Tasmota device for more than 5 minutes.

The next upcoming update will have 20 contact sensors. However, I don’t know whether the real-time update will work for you or not. Because it requires rules for the 20 sensors, and the device may not have sufficient memory to store the rules.

@hongtat Is it possible to have a Smoke Detector device associated with a switch pin? This would allow the ST Home Monitor to work with my ESP8266 (konnected) that has a smoke detector relay signal feeding into the board.

Update: I created a virtual Smoke Detector device that’s triggered by the Tasmota open/close sensor to solve this, but it would still be nice to have a more direct configuration.

Hi Hongtat:

I am trying to move from Tasomta connect to Edge but not able to connect to Alexa

I installed Tasomta Edge in ST, Removed RF bridge from IDE and contact sensor. then create RF bridge from the Edge, then created contact sensor from RF bridge. However the contact sensor I created were not able to trigger Alexa like Tasomta Connect does.

And I try to added simulated Alexa into edit device for contact sensor under IDE but warning pop up says “Access Denied We’re sorry, but you are not authorized to perform the requested operation”

Can you give me some hints how to migirated to Alexa? (ALexa were able to discover the contact sensor but not able to trigger) and the Sonoff Console able to pick up the contact sensor signal but shown as unknown
“05:58:27 RUL: RFRECEIVED#RFKEY performs “WebQuery POST {“Mac”:”%MACADDR%”,“RfReceived”:{“RfKey”:“NONE”}}"
05:58:27 RSL: RESULT = {“Command”:“Unknown”}"

Thank You