When I restart my HA, my only Tuya wifi device fails to initialize, and I don't get prompted to re-scan the QR code. The only way to get it back working correctly is to remove the hub and re-add it, at which point the switch will (eventually) start working again, but is horribly laggy, on the order of several minutes before it turns off and on, after running for a while it will catch up and work "correctly" at least until I restart HA again. I have run HA for many months now, and this is the first time this has been an issue. switching to LocalTuya is more work than I really want to put into a single device when I do eventually plan to replace it... But has anyone else noticed this behavior? It's been happening since the last 2 or 3 updates.
#HA reboots seem to take down Tuya integration.
lost lion
lost lion
Logger: homeassistant.config_entries
Source: config_entries.py:749
First occurred: June 13, 2025 at 9:31:23 PM (2 occurrences)
Last logged: 7:23:05 PM
Error setting up entry ****@****.*** for tuya
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 749, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/tuya/__init__.py", line 138, in async_setup_entry
await hass.async_add_executor_job(manager.update_device_cache)
asyncio.exceptions.CancelledError: Global task timeout
ugh, looks like tuya and ipv6 dont get along, which is a shame since I use ipv6 to access my HA (ipv4 is cgnat, but with a public ipv6)
disabling ipv6 resolves it, but now I need to do something different for remote access, ugh