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
{{ message }}
Repository navigation
Zaptec v0.8.7 fails to load on Home Assistant Core 2026.11 due to pydantic version incompatibility #454
After upgrading Home Assistant Core from 2026.10.4 to 2026.11.0, the Zaptec custom integration fails to load with the following error:
Setup failed for custom integration 'zaptec': Requirements for zaptec not found: 'pydantic>=2.11.7,<2.14'
Root cause
Zaptec integration v0.8.7's manifest.json pins pydantic to >=2.11.7,<2.14. Home Assistant Core 2026.11 ships with a newer version of pydantic (>= 2.14), which does not satisfy this requirement, causing the integration to fail during setup.
Environment
Home Assistant Core: 2026.11.0
Home Assistant OS: 18.4
Zaptec integration: v0.8.7 (custom component)
Installation method: HACS/Marketplace (migrated from HACS on 2026.11 upgrade)
Expected behavior
Zaptec should load successfully on Home Assistant Core 2026.11.0.
Actual behavior
The integration fails to set up. No Zaptec entities are created. Zaptec devices still appear in the device registry but no entities are available.
Additional context
No relevant errors found in the supervisor resolution or device registry beyond the pydantic requirement failure.
Reacted by staal, André Paiusco, Oliver Weinitschke, Anteus, JP101000, C-son, Ronald R, jfkarrin and TobbeOnGit
Faced the same trouble. Changed require pydantic>=2.11.7,<2.14 to require pydantic>=2.11.7 in the manifest.json, restarted Home Assistant, and got it working again.
That's a temporary fix, of course.
Reacted by Anteus, C-son, bobhund, jfkarrin and bafl1971
Title: v0.8.7 fails to load on Home Assistant 2026.11.0 (pydantic 2.14.1) – please release the pydantic bump from #445
Environment
Home Assistant OS 18.4, Core 2026.11.0 (Python 3.14.10)
Zaptec integration v0.8.7 (HACS)
What happens
After updating Home Assistant from 2026.10.4 to 2026.11.0, the integration no longer loads. HA shows "Invalid config: the following integrations and platforms could not be set up: zaptec". All Zaptec entities are unavailable.
Log
Cause
HA 2026.11.0 ships pydantic 2.14.1. The v0.8.7 manifest pins pydantic>=2.11.7,<2.14.
Fix already on master
Commit 2c8a7ea "Bump pydantic, azure-servicebus and aiolimiter (#445)" (2026-10-20) changes the pin to pydantic>=2.11.7,<2.15. That change has not been released yet; v0.8.7 (2026-04-24) is still the latest release.
Request
Could you publish a release (v0.8.8) that includes #445, so users on HA 2026.11 can load the integration again without switching HACS to the master branch?
Side effect worth noting
Other integrations that rely on Zaptec sensors lose them silently. In my case a battery manager uses sensor._charge_power to exclude the charger load. With the sensor unavailable, that exclusion is skipped and the home battery would discharge into the car.
Tnx read some about that, rather wait for the official update for now…Warm regards / Groet, Ronald BootsmanOn 6 Nov 2026, at 18:20, Johnny de Jong ***@***.***> wrote:JohnnydeJong left a comment (custom-components/zaptec#454)
Changing "pydantic>=2.11.7,2.14" to "pydantic>=2.11.7", in the manifest.json worked as a work around.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
Activity
kaffedrikkeren commentedon Nov 5, 2026
Faced the same trouble. Changed
require pydantic>=2.11.7,<2.14torequire pydantic>=2.11.7in themanifest.json, restarted Home Assistant, and got it working again.That's a temporary fix, of course.
JohnnydeJong commentedon Nov 5, 2026
Title: v0.8.7 fails to load on Home Assistant 2026.11.0 (pydantic 2.14.1) – please release the pydantic bump from #445
Environment
Home Assistant OS 18.4, Core 2026.11.0 (Python 3.14.10)
Zaptec integration v0.8.7 (HACS)
What happens
After updating Home Assistant from 2026.10.4 to 2026.11.0, the integration no longer loads. HA shows "Invalid config: the following integrations and platforms could not be set up: zaptec". All Zaptec entities are unavailable.
Log
Cause
HA 2026.11.0 ships pydantic 2.14.1. The v0.8.7 manifest pins pydantic>=2.11.7,<2.14.
Fix already on master
Commit 2c8a7ea "Bump pydantic, azure-servicebus and aiolimiter (#445)" (2026-10-20) changes the pin to pydantic>=2.11.7,<2.15. That change has not been released yet; v0.8.7 (2026-04-24) is still the latest release.
Request
Could you publish a release (v0.8.8) that includes #445, so users on HA 2026.11 can load the integration again without switching HACS to the master branch?
Side effect worth noting
Other integrations that rely on Zaptec sensors lose them silently. In my case a battery manager uses sensor._charge_power to exclude the charger load. With the sensor unavailable, that exclusion is skipped and the home battery would discharge into the car.
Thanks for maintaining this integration!
b00tsie commentedon Nov 5, 2026
same here. hope a permanent fix will be released soon...
JohnnydeJong commentedon Nov 6, 2026
Changing "pydantic>=2.11.7,2.14" to "pydantic>=2.11.7", in the manifest.json worked as a work around.
b00tsie commentedon Nov 6, 2026
sveinse commentedon Nov 7, 2026
v0.8.8 has been released. This should fix this issue. Please install and test.
JohnnydeJong commentedon Nov 7, 2026
Thanks!
b00tsie commentedon Nov 10, 2026
i believe it is fixed again.