hi there, i started using HA this week, built my first automations and added HACS and localtuya integration, my localtuya integration is broken after HA update to 2025.12. I had added some lamps already, if i now try to add more after the update of HA i get Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble. Any help much appreciated, as said new to HA, also not very familiar with discord. Thanks a lot in advance
#localtuya shows Config flow could not be loaded after update to HA 2025.12
austere canopy
austere canopy
also reported at localtuya github repository, seems it's not just me https://github.com/rospogrigio/localtuya/issues/2124
novel magnet
also getting this trying to configure the moonraker addon so it's not limited to localtuya
daring field
i noticed that, if you want to add something using the tuya api option it will fail when using ipv6
so maybe try to temp disable ipv6 in ha and reboot, then try again
novel magnet
so maybe try to temp disable ipv6 in ha and reboot, then try again
no dice, disabled via the network section in settings
daring field
hmm, then wait for other users to hop in. 😉
novel magnet
that it seems to be more than one addon seems to me more like it's a home assistant issue
daring field
difficult to say. checking ha issues atm
novel magnet
apparently this fixed it for the localtuya guys
but I don't even know what that means
doesn't help it isn't english I guess
@austere canopy that should fix it for you though apparently
it's there in the moonraker one as well, so HA is now expecting a _ in there apparently for some reason
so instead of self.config it needs to be self._config
yup that fixed it
that's dumb
it'll break again when they fix it and need to be changed back but it fixes it for now
austere canopy
i have seen the "fix", but in many other places it still depends on the self.config_entry property, so by just assigning to a different property might avoid the error, but i would assume, it would break things in other places
austere canopy
and how is that config_entry set then if the line that sets it self.config_entry = config_entry is changed to self._config_entry = config_entry, or in the PR someone else created even completely omitted https://github.com/rospogrigio/localtuya/pull/2127/files#diff-a5dd22b1a6a018159bb4f0ecf2c57118535dd94c44bc018c7647d51eb75e21d8R398
obsidian berry
it's set in the super object
austere canopy
<@525645207711252490> that should fix it for you though apparently
yes, it will fix it, if i change it locally, but the localtuya project seems no longer to be actively maintained, so PR might not be merged and tagged as new release, so it will remain broken for new users or anyone that does not change that line manually. also future breaking changes from core might not get fixed quickly when things are marked as deprecated
austere canopy
it's set in the super object
thanks, im not super familiar with python
so, i moved to using toya-local now, it was only my second day of using HA and immediately ran into this issue. glad it wasnt me. now on to discover the world of HA
thanks all for the help
mortal meadow