Nå har HA endret strukturen på custom components så man må ha med de filene man bruker i samme mappe. Jeg klarer ikke helt å skjønne hva som skal med hvor eller om noen filer må endres. Har prøvd å ta noen filer over fra climate-componenten, men får det ikke til å fungere. Har du mulighet til å se på det?
Custom Components file structure change: A significant change in how the “under the hood” of Home Assistant works has led to forcing platforms to be resolved based off the component path, if it exists.
Today, if you want, you can override the Hue light platform, but not the other parts of the Hue integration. If a future update evolves the Hue component, removing or changing internal methods that the custom platform relied upon, the custom platform will start failing (like this report).
To avoid this, we’re going to no longer allow custom components to be partial overlays (just a platform). Instead, if you want to override a built-in platform, you will need to override the whole component.
This is enforced by first resolving the platform as a component, and if it exists, limiting the lookup path to the component path.
Example: if I look up the hue component, and it is provided by a custom component, then all platform lookups will also be looked up in the custom component dir. The same works the other way around, if a user would only try to override hue/light.py but nothue/__init__.py, the custom platform will be ignored.
Paulus has written some detailed information about this change on the developers’ blog, if you’d like more information. The Great Migration by Paulus