Hi everyone,
After upgrading to Home Assistant 2025.5.2 , the custom integration myPyllant
no longer works due to a version conflict with the pydantic
library.
What’s happening:
myPyllant==0.9.1
requires pydantic >=2.10.4, <2.11.dev0
Home Assistant 2025.5.2 now uses pydantic==2.11.3
This causes a dependency conflict and prevents the integration from being installed or working
Additional context:
My questions:
Is anyone else experiencing this issue?
What’s the recommended approach when a custom integration breaks due to a core library update and there’s no way to contact the maintainer?
Thanks in advance!
I’m happy to help test or report more info if needed.
Nick4
(Nick)
May 17, 2025, 3:05pm
2
Hi, welcome to the forum!
Steineich:
The GH page for this component doesn’t exist anymore and apparently other versions are facing issues as well.
Update regarding the original issue (myPyllant not working after Home Assistant 2025.5.2):
Just to clarify: While the myPyllant
library itself is maintained at kellerza/myPyllant , the Home Assistant integration comes from a separate repository: signalkraft/mypyllant-component , which wraps the library for HA.
The issue has been resolved in the latest versions:
myPyllant==0.9.0
(library)
mypyllant-component v0.9.2b0
(HA custom integration)
These updates fix the Pydantic 2 compatibility issue and restore functionality under Home Assistant 2025.5.2.
Thanks to everyone who helped track this down!
Nick4
(Nick)
May 17, 2025, 9:11pm
4
Hi, please take the time to mark the solution as the answer, you do that by selecting the three dots under the post:
Then select the check box:
By doing so:
this thread can be useful to other users as well (this thread comes up as solution when starting a thread which is similar to yours).
this prevents that someone else steps in trying to help
Thanks for giving back to the community!