Symptom
After updating Home Assistant, all LocalTuya devices are unavailable and the integration shows "not loaded" or "config flow could not be loaded". Nothing changed on the devices.
Why
LocalTuya is a custom integration. It uses Home Assistant internals that Home Assistant deprecates and removes over time. Its GitHub tracker shows this repeatedly:
| Home Assistant | Reported LocalTuya problem |
|---|---|
| 2025.1 | issues when updating (widely reacted issue) |
| 2025.5 | failed to load: 'HomeAssistant' object has no attribute 'helpers' from a hass.helpers.service.async_register_admin_service() call |
| 2025.12 | "Config flow could not be loaded" |
| 2026.3 | color temperature control broken (mired → kelvin migration) |
For 2025.5, a fix was committed (9f4405a) and many users confirmed it worked, but it reached HACS as an update only afterwards, so users either patched the file by hand or waited.
What to do
- Before each Home Assistant update, open the LocalTuya issue tracker and look for issues mentioning the new version.
- Create a backup before updating. Home Assistant can do this automatically before updates, which lets you restore the previous state if the integration no longer loads.
- If it breaks: check the tracker for a confirmed fix or release. Hand-patching
custom_components/localtuyaworks, but it is overwritten by the next update, and Python indentation errors are a common mistake. - Consider the alternatives described in the Tuya-in-Home-Assistant comparison (official Tuya integration, Tuya Local). Choose based on your devices and on how quickly each project follows Home Assistant releases.