I tried a lot of things to fix this. Wasted about 6h and the fix was to remove the plug from the tuya app, remove it from local tuya in HA and add it again.
I hope i will not need to do this every time i have a power outage… so like 2-3 times a week.
This is weirder than i thought. When my pc is off the plugs work normally.
I don’t have time for more tinkering. Just flashed Tasmota and duck tuya integration.
Does anyone had luck fixing this? It seemed that with TuyaV2 1.5 everything is OK, but with 1.6 the issue is back again. A Core restart polls the sensors, but after that nothing…
I had similar when adding the integration, I already use Local Tuya for most of my Tuya devices but it didn’t support a new air con unit we had installed so I had to install the official cloud app. I found that although the unit could be controlled by HA through the official integration, the sensors for the unit weren’t updating when it was turned on etc, the only time it would refresh is if I restarted HA then it would stick again at whatever status it updated to at the time.
The reason mine was doing it was because although I was subscribed to the Device Status Notification module in Tuya IOT Platform, I hadn’t authorised to the project my HA Tuya integration is using to control things. Once I authorised it to that project everything started working as expected.
Sorry to revive this old thread, but I have the exact same issue you guys were experiencing. But unlike you, I double-checked everything in the Tuya IOT platform and confirmed that my HA project is already listed in the authorization list. I also revoked it and added it again for good measure, but to no avail .
Maybe there is something I missed, would you mind to explain a little bit more what were the steps you followed to resolve this ennoying issue?
I have the same problems, but found this workaround: Disable IPv6 in Supervisor → Host → Ip-Adress .
When setting the logger for tuya/tuya_iot to DEBUG you will notice, that there is often missing the PUBLISH answer from tuya after a POST of the switch-command. When IPv6 is disabled this happens nearly never.
I have the exact same issue. It seems that the data refresh was working for a week or so, then it stopped. Now I need to have the app open on a phone for it to work properly…