Have you tried just waiting to see if the change is reflected after 30 secs-1minute?
It's not instant.
I am having an issue, I turn a light switch on via the dashboard, light turns on turn off via the dashboard, light turns off but the "button" gets stuck on sending. Then if I go into the device the switch still says "on" but the light is off.
It seems to be all the single switches. I have removed and added device back in Hubitat, flashed a newer version of Tasmota
So if you see above the switch says it is on and switch1 says it is off, no matter what I click on or off the one called "switch always stays on which must be the one the dashboard reads
1 Like
I think it didn't change. But I will confirm later today. 30sec- 1 min seem bit too much. So it is not Realtime for 2-way switch. My home assistant integration takes only 2-3 sec.
I have just uploaded version 1.3.3 and it is available via HPM. As far as I know it cleans up all of the known issues. A couple of notes.
In Tasmota switches are defined as Switch 1 - 8 in multi-relay devices. In Hubitat the first switch is "switch" and it is at the programmers discretion what subsequent switches are named, but most commonly the sequence goes switch, switch1, switch2 etc. or switch, switch2, switch3 etc.
To be consistent I have linked the attributes "switch" and "switch1". These should always be in the same state and you can elect to use either one in your rules. Use whatever makes the most logical sense to you. Likewise "On" (at default behavior) and "Power1 On" have the same outcome as does the equivalent off operation.
I have left a "test()" function enabled and you will see it is a command button. This toggles the state of the useChildDevices boolean. The only time you would need it is if you upgrade an existing single relay device in which case the useChildDevices value would be null. This command will be removed on the next release.
In a newly installed device this is set at install. In an existing multi-relay device this value is toggled be the create\delete child devices.
Sorry for the issues you have had. Hopefully this will put them to bed and that driver dev can go back to sleep.
7 Likes
Tested. Perfect, thank you.
1 Like
working my side as well, many thanks
1 Like
Thanks for this temporary easy fix. 
Minor nit-pik: It initializes to "true" which still generates errors on single-relay devices. Took me a little while to figure out I have to click it twice to get the errors to stop. 
1 Like
test() is a toggle for the useChildDevices state. useChildDevices is initialized by the install routine as false for all new installations.
I just flashed an interesting switch, a Tuya Milfra MFA05 Motion Switch (Milfra MFA05 / CloudFree SWM1 Motion Smart Switch | digiblurDIY), which could be an interesting addition to my home, but I just can´t make it work properly, and I´m not even sure I configured as it should.
I used @garyjmilne Hubitat-Tasmota/Universal_Multi_Sensor_Single_Relay.groovy at main · GaryMilne/Hubitat-Tasmota · GitHub. Is this the right driver?
So far, the only right behaviour is if I turn on/off the switch via HE virtual switch with the mentioned driver, but HE virtual switch does not reflect changes when the switch is turned on via Motion sensor, or Tasmota UI Toggle switch. Both options mentioned work properly, but they just do not show any change on HE virtual switch.
Any ideas?
Have a look at my documentation. Traditional power relays were expected to be configured at SW1 and SW2 if present. Sensor switches were expected to start at SW3 in Tasmota to be recognized in the driver correctly. If I remember correctly.
Remember to do a tasmotaInjectRule.
Yes I always do so.
Will look again at the documentation. I went through it some time ago.
I took a look and my memory was correct. It's under Advanced Topics \ Sensor Switches.
Sorry, no page numbers in that doc.
1 Like
Gary, I will appreciate some help from you.
First things first; am I using the right driver for this device? a single relay switch with PIR and Light sensor?
or maybe I should be using a different one?
Please do a "Status 8" at the console and send me the result.
O.K. You need to change the Tasmota config so that status 8 shows those two switches as Switch3 and Switch4. You might need to experiment a but two of those GPIO's should be Switch3 and Switch4. GPIO12 is one of them I think, the other is probably 14.
Repeat the Status 8 command until they should Switch3 and Switch4. Once you have that do a TasmotaInjectRule and it will configure the correct rule and should work after that.
Great! Thanks a lot.
Tomorrow morning is going to be a very interesting and busy morning.
I will report results after testing.
