[DEPRECATED] Tasmota 7.x/8.x firmware for Hubitat + Tuya, Sonoff and other drivers

🚧 Developers
,
618

Not seeing a way to PM you, potentially as I am a new user. I have a Tuya garage door opener I'd like to try out that has Tasmota flashed, and it sounds like your beta driver is more appropriate when attempting to support non-standard devices.

619

OK will post it on a diff thread. And yes, I won't be using the IR anyway. Cheers bud.

620

Yes, since you're new you can't PM, I'll add you to the Closed Beta thread, the only thing missing for the version of the driver is good documentation, please read through the thread to get a good understanding on how it works.
Also, post a link to your device in the Closed Beta thread, most informative would be if you can find it here:

Ok, please post in the Closed Beta thread

622

Ditto that markus :wink:

624

I have 2 KMC 4 Power Monitor Plugs. I flashed Tasmota Hubitat v8.1.0 (followed the guidelines so flashed the official tasmota first, then minimal and then the hubitat version). The plugs are connected to my WiFi and the hub recognized them successfully. However, I can no longer control the plugs even manually.

When I send a command via Hubitat, the LED blinks blue and the WebUI console displays "RSL: stat/tasmota/RESULT = {"Command":"Error"}". Trying to turn the power on manually does nothing.

Please any idea how I can get this working?

Thanks

625

Ok, really weird; I did a "reset 5" and I can now control only the middle plug via Hubitat and the WebUI. However, the other 2 plugs can't be controlled.

Also, manual control still doesn't work and the switch is inverted both in the WebUI and in HE (says "on" when the middle relay is "off" and "off" when middle relay is "on"). Any ideas how to fix pls?

P.S.
Hitting configure did the trick! Working fine now. Thanks much for this driver!

1 Like
626

So it is all working?

One thing I didn't realize when I setup my first device is that I had to update the template from the Tasmota web site.

Also note - after moving to Tasmota, the power monitoring feature needs to be re-calibrated! Otherwise, it will be off - I found this with my Costco power monitor plugs. It's pretty easy to do with a 60W bulb and a volt meter.

I am curious about that plug - does it monitor the power going to each outlet, or it does a total of all power use?

.

1 Like
627

Yup, all working.

It monitors the total power to the 3 outlets that can be controlled (not to each). Also, I don't believe it monitors power to the "Always On" outlet.

2 Likes
628

I flashed some Feit WiFi RGBW color bulbs and they work fine. However, if I turn off the bulbs using HE, the color temperature changes to a default of 3003 when I turn it back on. If I use the WebUI or the switch, I don't have that same problem. I'm guessing this issue is because of the white temperature scale but not sure (it's 153-500 in Tasmota).

Please help look into this. I'm using the Generic RGB/RGBW Controller/Bulb/Dimmer driver.

Thanks!

629

Found the issue... Line 122 is
cmds << setColorTemperature(colorTemperature ? 'colorTemperature : 3000)

Should be:
cmds << setColorTemperature(device.currentValue('colorTemperature') ? device.currentValue('colorTemperature') : 3000)

Else, colorTemperature would always be null and the color temperature when turned on would always change back to 3000

630

@yototogblo the best solution is to just use the Closed Beta drivers, they have all this sorted properly.

1 Like
631

Hi Markus,
I have flashed the 8.1 version of your tasmota firmware and my hubitat is running 2.2.0.121, but the state does not get updated even though I have Hubitat enabled and hubitat IP/Port is configured in the UI. Any ideas ?

632

What does the HE logs say? What does the device logs say? What device is it? What does work? Can you control it from HE? Can you control it from the device Tasmota webpage?

633

I set the HE in insane verbosity mode, but i don't see anything coming back from the device to HE. I can control from both HE and Device Tasmota Webpage. The device is Avatar Wifi Light Switch. This One
The issue is that I can control it from Device Webpage, HE and MQTT , but it does not update the HE with the status. Is there any issue enabling both mqtt and Hubitat feature ?

Here is the device log: (Nothing on HE)

15:40:49 MQT: stat/office_light/RESULT = {"POWER":"ON"}
15:40:49 MQT: stat/office_light/POWER = ON
15:40:50 CFG: Saved to flash at FB, Count 65, Bytes 4096
15:41:09 WIF: Checking connection...
15:41:09 WIF: Connected
634

I don't think so, but I've also never tried both at the same time. Try to deactivate MQTT and only activate Hubitat connection and see if that works separately. Then we take it from there.

635

I did try that without factory reset. But let me factory reset the device and try again and get back to you.

636

"Reset 5" is the reset you need

637

Thanks , tried upgrading firmware to 8.2 and back to 8.1 (hubitat) , did the reset 5 , and still hubitat doesn't update with the status from webpage.

The following log has power on from HE as well as power off from the device webpage. I wonder if below log lines(Exceptions) explains something :

[app:222](http://192.168.23.251/logs#app222)2020-04-22 09:58:18.000 am [error](http://192.168.23.251/installedapp/configure/222)java.lang.NullPointerException: Cannot invoke method off() on null object on line 5322 (delayedActCancel)

[app:222](http://192.168.23.251/logs#app222)2020-04-22 09:57:59.860 am [error](http://192.168.23.251/installedapp/configure/222)java.lang.NullPointerException: Cannot invoke method off() on null object on line 5322 (delayedActCancel)

[app:222](http://192.168.23.251/logs#app222)2020-04-22 09:57:30.064 am [error](http://192.168.23.251/installedapp/configure/222)java.lang.NullPointerException: Cannot invoke method off() on null object on line 5322 (delayedActCancel)

[dev:528](http://192.168.23.251/logs#dev528)2020-04-22 09:57:20.586 am [debug](http://192.168.23.251/device/edit/528)result: [POWER:ON]

[dev:528](http://192.168.23.251/logs#dev528)2020-04-22 09:57:20.440 am [debug](http://192.168.23.251/device/edit/528)Using getAction for '/cm?cmnd=Power%20On'...

[dev:528](http://192.168.23.251/logs#dev528)2020-04-22 09:57:20.434 am [debug](http://192.168.23.251/device/edit/528)on()

[dev:528](http://192.168.23.251/logs#dev528)2020-04-22 09:57:17.068 am [debug](http://192.168.23.251/device/edit/528)result: [POWER:OFF]

[dev:528](http://192.168.23.251/logs#dev528)2020-04-22 09:57:16.930 am [debug](http://192.168.23.251/device/edit/528)Using getAction for '/cm?cmnd=Power%20Off'...

[dev:528](http://192.168.23.251/logs#dev528)2020-04-22 09:57:16.924 am [debug](http://192.168.23.251/device/edit/528)off()

[app:222](http://192.168.23.251/logs#app222)2020-04-22 09:57:00.694 am [error](http://192.168.23.251/installedapp/configure/222)java.lang.NullPointerException: Cannot invoke method off() on null object on line 5322 (delayedActCancel)

[app:222](http://192.168.23.251/logs#app222)2020-04-22 09:56:57.073 am [error](http://192.168.23.251/installedapp/configure/222)java.lang.NullPointerException: Cannot invoke method off() on null object on line 5322 (delayedActCancel)
638

Type "setoption113" in the Tasmota Console, what do you see? On or off?
If it is off, type "setoption113 1" and see if you get updates now. If it is on... Then to eliminate as many issues as possible I'd say you should change to my Closed Beta driver, PM me about that.

What's the app with id 222? That does not look related at all to your issue, but best to be sure.

639

setoption113 is On, and app 222 is apparently an rule in the rule machine and the device does not exist. seems unrelated.