Using smart life or tuya app?
Adding my name to the list of those affected, too. It seems the first time after a restart itāll be quick, but after that itās slow. The entity switch will toggle to the other state, but then toggle back. Sometimes itāll update eventually. Didnāt have this issue with 110.
This clip shows the behavior I am experiencing. The switches toggle back to the previous position, even though the physical switch stays in the requested state. Eventually the the Home Assistant animations do sync with the physical switch, but it can take up to 5 minutes. During that time, flipping them back and forth does nothing to the hardware.
Yep. Exactly the same behavior as me.
1 Like
Iām experiencing the same error. If I turn a socket on, the state turns on then after a few seconds off again. The actual socket stays on. To get it back to normal and turn the light off. I have to click it it quickly twice. (smart life)
Iām sure this only happened after I updated the other day also.
No problem with my flashed sockets (heed my warning though on someone whoās recently flashed them for the first time, while it was somewhat easy to do over the air, Iām having major problems on ghost switching at random times throughout the day. Garage keeps randomly opening)
Yeah, that was something i heard about flashing those as wellā¦ although i didnt know there was an over-the-air method.
As for the state of our Tuya lights and switches; they released a patch recently but it didnt address this issue with Tuya. I havenāt seen anything acknowledging it as an issue either. So for now Iām fully on a toggle Boolean system for all my switches and lights ā what a pain in the ass.
But at least now i have accurate āstatesā in my front end; and i can automate based on Boolean states as well. Took a while, but until i replace all these bulbs, itāll have to do.
All these wrong states were ruining my automations. Changing my automations to work with this issue was too much work. Flashing my devices using tuya convert was far easier and I did that. Just left out 4 devices out of 20 odd I have on stock firmware.
Out of the four, 2 are Sonoff like switches that I plan to open up and flash and if not replace with flashed Sonoff ones. One is a PIR sensor that I anyways use with HA and not tuya cloud and third is a plug that canāt be flashed.
I have also connected my HA with Alexa using haaska. So I can use my echo to control lights.
Everything works fine.
I really want to flash my devices, but i tried with this one
And didnĀ“t workedā¦
Same case with me. All my bulbs and couple plugs went fine. 2 of those type of switches had issues flashing. Might replace them with sonoff flashed ones later.
Iām afraid trying to flash my wall cover switches, because I canāt kill thoose during summer ahahah. But maybe I will tryā¦
Itās easier to integrate them using mqtt? Itās easier to configure each button?
MQTT is very easy. Just install the addon on HA. In integrations enable mqtt as integration. Enter mqtt host/user/password on device running tasmota. Run āsetoptions19 1ā on tasmota console to turn on autodiscovery. The device is automatically discovered by HA.
The important thing is the device template that needs to be used to configure the device. You can check blackadder templates and see if your device is listed.
1 Like
These days I will try to flash my cover switches and if everything goes well, I will replace the normal switches.
I know a few have said its ruining their automationās. Iāve been trying to figure out why a few of my node red flows were off then remembered back to this message. When trying to debug the sockets or switches i get no info from the tuya devices at all. Really hope tuya sort this soon, its no fun waking up in middle of the night nearly melting wondering why the electric blanket didnāt automatically shut off after 30 mins 
@atulalvenkar & @JorgeMaTeixeira you guys mentioned that a couple of your devices werenāt flashing, some of the newer products from tuya and others have been changing the esp chip to another, so messing up tasmota. In time im sure theyāll figure out ways around it. I also flashed two of my smart life wall switches, didnt have the option of flashing separate buttons but i feel its been worth it. It allowed me to link up some blinds i made and have them open and close instantly (when I tried it through tuya i was getting 30 second delays,)
Also been adding multiple secret button presses, so you can have different automation on 1,2,3 clicks etc.
1 Like
Does anyone know if the team is aware of the issue?
There are some topics in github about this situation, but donāt ask me if the right guy knows this. I donāt know that.
Itās nothing to do with the HA version, itās Tuyaās fault. They changed their api last week in a way that is causing this fault and several others reported here in separate threads (like wrong bulb colors).
Itās time to dump Tuya. This is the 2nd time in 6 months that they have broken Home Assistant, and they also broke IFTTT this month when they refused to pay their fee to IFTTT and got cut off.
Their response to customers has been āWhatās Home Assistant?ā, and to claim that you shouldnāt need anything more than the simple built-in automation in their app - as long as you have only Tuya-supported devices of course.
Hey @DougAmes I largely agree with you but there are a couple of things that Iāve discovered whilst tinkering that might help othersā¦
- Somehow, not all devices in my Tuya estate are affected. My older ones work flawlessly. I havenāt flashed any devices, itās all stock.
- I setup an automation in the Smart Life (Tuya) app, so that if one of the functioning devices turn off, then the others that have stopped working with HA, also turn off. This is useful for bedtime routines for my kids. The challenge is that even those automations in their own app are pretty much junk. The working devices turn off as expected, but nothing else happens.
I think Tuya are having serious issues across the board here, but I donāt see any viable replacements Iām afraid.
Make sense. I reverted to 110.X and noticed the same behavior.
So what happens now? Do we wait for an update from HA to support the changes in their API? Iām trying to hold off flashing these devices.
Same boat. I think I accidentally updated the firmware on one of my Tuya-supported devices a couple of months ago (silly me!), so it might not be flashable without soldering any more. Even for the others Iām concerned that a flashing failure will brick them.
For the moment Iām using a workaround in HA/Node Red - I tell Alexa to repeat the command to the device, and I had to create a separate Alexa routine for each command.
My unflashed Tuya lights are behaving again (turning on and off From HA dashboard with the same delay as asking google to do it).