Franck Nijhof
Franck Nijhof
Right, but those don't take part in the migration process. It simply aren't using Pydantic at all anymore.
`pydantic` has been fully removed from `pvo` (PVOutput integration) and thus no longer taking part in this issue.
`pydantic` has been fully removed from `open-meteo` and thus no longer taking part in this issue. PR @ Core:
`pydantic` has been fully removed from `radios` (Radio Browser integration) and thus no longer taking part in this issue. PR @ Core: https://github.com/home-assistant/core/pull/103614
Man, what a liberating feeling! I should have learned about other options before using Pydantic in the first place. It would have saved me from many headaches now and in...
This sentences are the same?
Sorry, this seems to be working fine This action does: Home Assistant Core Integration: List all orphaned database entities 👻 It does not clean up orphaned entities, it cleans up...
This issue is mixing up the state machine/registries and database. Those are different things. If you don't understand the difference between these two methods, you probably shouldn't use them. ../Frenck
This is, unfortunately, not an problem with Spook, but a limitation of Home Assistant. The service call / action would remain the same / working, but the UI elements currently...
I'm going to close this, as per above :( Unfortunately, this is an upstream issue. ../Frenck