You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be a compatibility issue between luxtronik integration version 2024.10.5-Beta and Home Assistant Core version 2024.10.4. After the update most entities become unavailable and „no longer provided by the integration”. Only a few sensors are still working.
Restoring Home Assistant Core version 2024.10.3 fixes the problem and updating causes it again.
The update notes mention some changes to the yaml syntax but are supposed to be non breaking.
The text was updated successfully, but these errors were encountered:
I have observed the same problem. If the entities are no longer available, a restart is enough for me. However, it is probably the case that after each restart of HA the entities are not available, after each further restart they are available again. And again and again...
There seems to be a compatibility issue between luxtronik integration version 2024.10.5-Beta and Home Assistant Core version 2024.10.4. After the update most entities become unavailable and „no longer provided by the integration”. Only a few sensors are still working.
Restoring Home Assistant Core version 2024.10.3 fixes the problem and updating causes it again. The update notes mention some changes to the yaml syntax but are supposed to be non breaking.
Same but different here. My integration worked until HO Core 2024.11.1. With Core 2024.11.4 some entities became unvailable. Restoring to Core 2024.11.1 solved it for me.
There seems to be a compatibility issue between luxtronik integration version 2024.10.5-Beta and Home Assistant Core version 2024.10.4. After the update most entities become unavailable and „no longer provided by the integration”. Only a few sensors are still working.
Restoring Home Assistant Core version 2024.10.3 fixes the problem and updating causes it again.
The update notes mention some changes to the yaml syntax but are supposed to be non breaking.
The text was updated successfully, but these errors were encountered: