[RELEASE] Tasmota (Connect) for Sonoff, Tuya, SmartLife & other ESP8266 devices)

Could it be not adding the child device because I don’t have the temp & humidity sensor? I have the DS18B20, which is only a temp sensor.

Hi Dave, I have a very similar module but when I opened it up I could see no gpio pins exposed to flash it with Tasmotizer. How did you flash it please?

@hongtat, here are some Live Logging messages. What do the NullPointerExceptions mean in the logs? I used the switch’s button to turn it off followed by using the App to turn it “On”. This did close the switch. Again, no update at the App, only a message saying, *“A network error occurred. Try again later.”

I will check my network as you requested. Note, for this connection, the LAN element is a wireless access point with an embedded ethernet switch. This is wire connected to the Smartthings hub and wirelessly connected to the Tasmota switch.
.

Live Logging output with a few working Z-Wave motion sensor logs (…dcd4)

8915d8df-2212-4cd2-9de0-efe44b02baa7 10:18:13 AM: error java.lang.NullPointerException @line 129 (parseEvents)

50e661df-182e-4def-8258-495106a6b25c 10:18:13 AM: debug Humidity Switch (192.168.1.39) called: POWER1 1

6320d8eb-e611-4737-b676-a019b2bbdcd4 10:17:57 AM: debug Motion is active

6320d8eb-e611-4737-b676-a019b2bbdcd4 10:16:46 AM: debug Motion is inactive

8edd8a27-2be9-4d58-9cd5-f20a5577cd5f 10:16:32 AM: info Node Applet Bridge Status: Not Accessible

8915d8df-2212-4cd2-9de0-efe44b02baa7 10:15:09 AM: error java.lang.NullPointerException @line 129 (parseEvents)

8915d8df-2212-4cd2-9de0-efe44b02baa7 10:15:09 AM: error java.lang.NullPointerException @line 129 (parseEvents)

8915d8df-2212-4cd2-9de0-efe44b02baa7 10:15:09 AM: error java.lang.NullPointerException @line 129 (parseEvents)

8915d8df-2212-4cd2-9de0-efe44b02baa7 10:15:09 AM: error java.lang.NullPointerException @line 129 (parseEvents)

50e661df-182e-4def-8258-495106a6b25c 10:15:09 AM: debug Humidity Switch (192.168.1.39) called: Status 11

50e661df-182e-4def-8258-495106a6b25c 10:15:09 AM: debug Humidity Switch (192.168.1.39) called: Status 8

50e661df-182e-4def-8258-495106a6b25c 10:15:09 AM: debug Humidity Switch (192.168.1.39) called: Status 5

50e661df-182e-4def-8258-495106a6b25c 10:15:09 AM: debug Humidity Switch (192.168.1.39) called: Status 2

8915d8df-2212-4cd2-9de0-efe44b02baa7 10:13:08 AM: error java.lang.NullPointerException @line 129 (parseEvents)

50e661df-182e-4def-8258-495106a6b25c 10:13:06 AM: debug Humidity Switch (192.168.1.39) called: POWER1 1

6320d8eb-e611-4737-b676-a019b2bbdcd4 10:11:58 AM: debug Motion is active

10:11:40 AM: info Waiting on events…

10:11:40 AM: info For past logs for individual things go to the My Devices section, find the device and click on the Events link on the device information page.

10:11:40 AM: info This console provides live logging of your SmartThings.
.

Thanks!

Here is a link to the page I used - https://github.com/arendst/Tasmota/issues/5737

Tasmotizer couldn’t flash it for me, but using esptool I managed to get it flashed. My tip is to connect 3V, GND, Tx, Rx - power up with GPIO0 connected to GND and then briefly connect the RST pin to GND - that gets it into programming mode. Erase the flash and then program tasmota - all good.

@BartschLabs I think i might be having the same problem. When I try to add a new Tasmoto Device in the Tasmota (Connect) Smart App, the switch isn’t showing up in my list of devices even though it is listed under “Installed Devices”.

I am probably doing something wrong because I am having the exact same problem with @erocm1231 Sonoff-Connect Smart App. It must be some nuance on how the new iOS app functions that i am not understanding.

I think i found the issue here:

https://community.smartthings.com/t/smartthings-new-app-not-showing-all-devices-vs-classic-app-40-missing/193111?u=daniel_paulsen

@Daniel_Paulsen, do you mean the device gets created for you and shows up in the IDE but doesn’t show up in the new app?

For me, the child device just doesn’t get created. I think the smartapp isn’t recognizing that I have a sensor on my TH16 while it’s creating my TH16 device. My TH16 device gets created just fine and shows up in all three places: IDE, classic app, & new app.

Hi @hongtat, by the way very happy with the virtual switch on the IR blaster turning on and off the air conditioner (even with a fixed temp).

I was wondering I could use one of your DHs to a Standard Sonoff switch, with the tasmota-sensors.bin version and using the Tem/Humd sensors or a light sensor or a PIR sensor.

Does it supports?

Did you create it as “Sonoff TH” device? And any errors in the IDE “Live logging”?

@hongtat Thank you so much for your hard work and skill bringing this integration to us all!

I have my Sonoff Pow R2 successfully connected, and it toggles on and off correctly, but I can’t get any power meter readings.

I’ve installed the app and all the device handlers via GitHub. The Sonoff is flashed to Tasmota 9.1.0 and the power information all shows correctly in the web interface.

Have tried adding the device via Tasmota Connect as both a Pow R2 and also a Generic Metering Switch (1ch) but neither seems to provide power information. The only info I get in SmartThings (using the v2 app btw) other than the state of the relay is the wifi signal strength.

Any pointers gratefully accepted!

ps if it helps here is the log information that seemed relveant:

45780ed7-56ec-44a0-a11b-91c3185d8fee 18:37:26: debug Iron (192.168.3.196) called: Backlog Rule3 ON Tele-Energy#Power DO WebSend [192.168.2.79:39500] /?json={“StatusSNS”:{“ENERGY”:{“Power”:"%value%"}}} ENDON ON Tele-Energy#Total DO WebSend [192.168.2.79:39500] /?json={“StatusSNS”:{“ENERGY”:{“Total”:"%value%"}}} ENDON ON Tele-Energy#Voltage DO WebSend [192.168.2.79:39500] /?json={“StatusSNS”:{“ENERGY”:{“Voltage”:"%value%"}}} ENDON ON Tele-Energy#Current DO WebSend [192.168.2.79:39500] /?json={“StatusSNS”:{“ENERGY”:{“Current”:"%value%"}}} ENDON;Rule3 1;TelePeriod 10
45780ed7-56ec-44a0-a11b-91c3185d8fee 18:37:26: debug Iron (192.168.3.196) called: Backlog Rule2 ON Power5#state DO WebSend [192.168.2.79:39500] /?json={“StatusSTS”:{“POWER5”:"%value%"}} ENDON ON Power6#state DO WebSend [192.168.2.79:39500] /?json={“StatusSTS”:{“POWER6”:"%value%"}} ENDON ON Power7#state DO WebSend [192.168.2.79:39500] /?json={“StatusSTS”:{“POWER7”:"%value%"}} ENDON ON Power8#state DO WebSend [192.168.2.79:39500] /?json={“StatusSTS”:{“POWER8”:"%value%"}} ENDON;Rule2 1
45780ed7-56ec-44a0-a11b-91c3185d8fee 18:37:26: debug Iron (192.168.3.196) called: Backlog Rule1 ON Power#state DO WebSend [192.168.2.79:39500] /?json={“StatusSTS”:{“POWER”:"%value%"}} ENDON ON Power1#state DO WebSend [192.168.2.79:39500] /?json={“StatusSTS”:{“POWER1”:"%value%"}} ENDON ON Power2#state DO WebSend [192.168.2.79:39500] /?json={“StatusSTS”:{“POWER2”:"%value%"}} ENDON ON Power3#state DO WebSend [192.168.2.79:39500] /?json={“StatusSTS”:{“POWER3”:"%value%"}} ENDON ON Power4#state DO WebSend [192.168.2.79:39500] /?json={“StatusSTS”:{“POWER4”:"%value%"}} ENDON;Rule1 1
45780ed7-56ec-44a0-a11b-91c3185d8fee 18:37:26: debug Iron (192.168.3.196) called: Status 5
db8bd051-59be-48b3-9702-464003f4aa9a 18:37:26: debug MAC: ‘84:F3:EB:8D:61:19’, DNI: ‘84F3EB8D6119’
45780ed7-56ec-44a0-a11b-91c3185d8fee 18:37:26: debug Iron (192.168.3.196) called: Backlog Rule3 ON Tele-Energy#Power DO WebSend [192.168.2.79:39500] /?json={“StatusSNS”:{“ENERGY”:{“Power”:"%value%"}}} ENDON ON Tele-Energy#Total DO WebSend [192.168.2.79:39500] /?json={“StatusSNS”:{“ENERGY”:{“Total”:"%value%"}}} ENDON ON Tele-Energy#Voltage DO WebSend [192.168.2.79:39500] /?json={“StatusSNS”:{“ENERGY”:{“Voltage”:"%value%"}}} ENDON ON Tele-Energy#Current DO WebSend [192.168.2.79:39500] /?json={“StatusSNS”:{“ENERGY”:{“Current”:"%value%"}}} ENDON;Rule3 1;TelePeriod 10
45780ed7-56ec-44a0-a11b-91c3185d8fee 18:37:26: debug Iron (192.168.3.196) called: Backlog Rule2 ON Power5#state DO WebSend [192.168.2.79:39500] /?json={“StatusSTS”:{“POWER5”:"%value%"}} ENDON ON Power6#state DO WebSend [192.168.2.79:39500] /?json={“StatusSTS”:{“POWER6”:"%value%"}} ENDON ON Power7#state DO WebSend [192.168.2.79:39500] /?json={“StatusSTS”:{“POWER7”:"%value%"}} ENDON ON Power8#state DO WebSend [192.168.2.79:39500] /?json={“StatusSTS”:{“POWER8”:"%value%"}} ENDON;Rule2 1
45780ed7-56ec-44a0-a11b-91c3185d8fee 18:37:26: debug Iron (192.168.3.196) called: Backlog Rule1 ON Power#state DO WebSend [192.168.2.79:39500] /?json={“StatusSTS”:{“POWER”:"%value%"}} ENDON ON Power1#state DO WebSend [192.168.2.79:39500] /?json={“StatusSTS”:{“POWER1”:"%value%"}} ENDON ON Power2#state DO WebSend [192.168.2.79:39500] /?json={“StatusSTS”:{“POWER2”:"%value%"}} ENDON ON Power3#state DO WebSend [192.168.2.79:39500] /?json={“StatusSTS”:{“POWER3”:"%value%"}} ENDON ON Power4#state DO WebSend [192.168.2.79:39500] /?json={“StatusSTS”:{“POWER4”:"%value%"}} ENDON;Rule1 1

1 Like

@hongtat, yes I created the device as a “Sonoff TH” device.

Initially it showed up with !!!, but a couple of minutes later the !!! went away.

Here is an abridged log:

10:41:26 AM: debug Freezer Thermometer (192.168.x.x) called: Status 11
10:41:26 AM: debug Freezer Thermometer (192.168.x.x) called: Status 8
10:41:26 AM: debug Freezer Thermometer (192.168.x.x) called: Status 8
10:41:26 AM: debug Freezer Thermometer (192.168.x.x) called: Backlog Rule2 ON Power5#state DO WebSend [192.168.x.x:39500] /?json={“StatusSTS”:{“POWER5”:"%value%"}} ENDON ON Power6#state DO WebSend [192.168.x.x:39500] /?json={“StatusSTS”:{“POWER6”:"%value%"}} ENDON ON Power7#state DO WebSend [192.168.x.x:39500] /?json={“StatusSTS”:{“POWER7”:"%value%"}} ENDON ON Power8#state DO WebSend [192.168.x.x:39500] /?json={“StatusSTS”:{“POWER8”:"%value%"}} ENDON;Rule2 1
10:41:26 AM: debug Freezer Thermometer (192.168.x.x) called: Backlog Rule1 ON Power#state DO WebSend [192.168.x.x:39500] /?json={“StatusSTS”:{“POWER”:"%value%"}} ENDON ON Power1#state DO WebSend [192.168.x.x:39500] /?json={“StatusSTS”:{“POWER1”:"%value%"}} ENDON ON Power2#state DO WebSend [192.168.x.x:39500] /?json={“StatusSTS”:{“POWER2”:"%value%"}} ENDON ON Power3#state DO WebSend [192.168.x.x:39500] /?json={“StatusSTS”:{“POWER3”:"%value%"}} ENDON ON Power4#state DO WebSend [192.168.x.x:39500] /?json={“StatusSTS”:{“POWER4”:"%value%"}} ENDON;Rule1 1
10:41:26 AM: debug Freezer Thermometer (192.168.x.x) called: Status 5
10:40:32 AM: debug getChildDevices(false), children=3
10:40:22 AM: debug Created ‘Freezer Thermometer’ - 2ch
10:40:22 AM: debug channel: 2
10:39:35 AM: debug getChildDevices(false), children=2

Did you get a chance to look at this. I’m wondering if it might be better to keep the device as a single channel dimmer with the option to select which tasmota channel to use. Thoughts?

can someone put a video of what they can control with the Virtual Air Conditioner (HVAC)?

I have Blitzwolf IR (https://templates.blakadder.com/blitzwolf_BW-RC1.html)

do I need to make any changes or just flash and use the Virtual Air Conditioner (HVAC)?

Anyone got any ideas how to modify the existing single channel dimmer device to support dual channel? Looks like the device responds to standrd tuya commands for power1 power2 channel1 channel2:

20:49:21 CMD: tele/tasmota_57CF7C/STATE
20:49:21 SRC: WebConsole from 192.168.0.6
20:49:21 CMD: Group 0, Index 1, Command “STATE”, Data “”
20:49:21 RSL: stat/tasmota_57CF7C/RESULT = {“Time”:“2020-12-14T20:49:21”,“Uptime”:“7T21:09:32”,“UptimeSec”:680972,“Heap”:26,“SleepMode”:“Dynamic”,“Sleep”:10,“LoadAvg”:99,“MqttCount”:0,“POWER1”:“ON”,“Channel1”:100,“POWER2”:“ON”,“Channel2”:100,“Color”:“FFFF”,“Wifi”:{“AP”:1,“SSId”:“indigo-priv”,“BSSId”:“AC:86:74:EC:66:A3”,“Channel”:11,“RSSI”:62,“Signal”:-69,“LinkCount”:7,“Downtime”:“0T00:04:34”}}
20:49:22 TYA: Send “55aa00000000ff”

It looks like it is possible, however I don’t have any ETA for this.

I just encountered the child device creation issue. It appears ST broke the child device creation. I’ll look into it.

1 Like

Hi, did you ever manage to get any power readings?

I’m having similar issues with an esp8266 set as a generic metering switch,
thanks

Could you update & publish the latest codes? Remove and create the device again. I think it should fix the child device creation issue.

@Scott_Mitchell

Under http://[Your Tasmota Device IP]/cm?cmnd=status 0
Do you see something similar like this?

Then under http://[Your Tasmota Device IP]/cs?

Do you get similar to this?

I’m not getting similar to that no?

I am using a wemos D1 mini, as Generic (18) with a CT coil on the A0 pin.
Screenshot 2020-12-18 155846

The device was getting created and showing up as a hub child device but they were not showing up on home page.

After working with ST support I ended up resolving this issue by deleting my Samsung account and then creating a new one and setting everything up from scratch. Now everything is working correctly.