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
When updating to the latest beta release of Home Assistant 2026.11.0b0 I get the error below.
Logger: homeassistant.setup
Source: setup.py:272
First occurred: 17:39:09 (1 occurrence)
Last logged: 17:39:09
Setup failed for custom integration 'zaptec': Requirements for zaptec not found: ['pydantic>=2.11.7,<2.14'].
Reacted by Lars, Patrik Andersson, raunimi2 and FrederikGN
I did the change suggested by Bluhme1 and it works - Thanks
At my system the file is located here: /config/custom_components/zaptec/manifest.json
After the change - then reboot the system to reload changes.
HA 2026.11 pins pydantic==2.14.1, but v0.8.7 requires pydantic<2.14, so the requirement can't be met.
This is already fixed on master by #445, which changed the requirement to pydantic>=2.11.7,<2.15. It just hasn't been released yet.
Until there's a release, change that line in /config/custom_components/zaptec/manifest.json to "pydantic>=2.11.7,<2.15" and restart HA. This keeps the upper cap, unlike removing it completely.
@sveinse@steinmn: HA 2026.11.0 final is due around Nov 4. Could a release with #445 go out before then?
Each time, the fix was only a change to the cap. Our code didn't need to change for pydantic itself, and validate.py has had full test coverage since #338.
Until there's a release, change that line in /config/custom_components/zaptec/manifest.json to "pydantic>=2.11.7,<2.15" and restart HA. This keeps the upper cap, unlike removing it completely.
But does not work
Failed setup, will retry: Failed to validate data: 2 validation errors for list[ChargerFirmware] 0.AvailableVersion Field required [type=missing, input_value={'ChargerId': 'xxxxxxx', 'DeviceType': 4}, input_type=dict] For further information visit https://errors.pydantic.dev/2.14/v/missing 0.IsUpToDate Field required [type=missing, input_value={'ChargerId': 'xxxxxxxx', 'DeviceType': 4}, input_type=dict] For further information visit https://errors.pydantic.dev/2.14/v/missing
Until there's a release, change that line in /config/custom_components/zaptec/manifest.json to "pydantic>=2.11.7,<2.15" and restart HA. This keeps the upper cap, unlike removing it completely.
But does not work
Failed setup, will retry: Failed to validate data: 2 validation errors for list[ChargerFirmware] 0.AvailableVersion Field required [type=missing, input_value={'ChargerId': 'xxxxxxx', 'DeviceType': 4}, input_type=dict] For further information visit https://errors.pydantic.dev/2.14/v/missing 0.IsUpToDate Field required [type=missing, input_value={'ChargerId': 'xxxxxxxx', 'DeviceType': 4}, input_type=dict] For further information visit https://errors.pydantic.dev/2.14/v/missing
"Cause: Home Assistant 2026.11 includes a newer version of pydantic, a library Zaptec depends on. Zaptec 0.8.7 is still the latest release, and it only accepts versions below 2.14, so Home Assistant refused to load it.
Fix: I changed that one limit in the Zaptec files to "below 2.15", the same change the Zaptec developers have already made for their next release. "
Activity
Bluhme1 commentedon Oct 29, 2026
I ran into the same issue.
The problem appears to be the Pydantic version constraint in manifest.json:
pydantic>=2.11.7,<2.14
Removing the upper version constraint fixed the issue for me. I changed it to:
pydantic>=2.11.7
After making this change and restarting Home Assistant, the integration loaded successfully again.
So it looks like the <2.14 constraint is no longer compatible with the current Home Assistant environment.
munklinde commentedon Oct 29, 2026
I did the change suggested by Bluhme1 and it works - Thanks
At my system the file is located here: /config/custom_components/zaptec/manifest.json
After the change - then reboot the system to reload changes.
rhammen commentedon Nov 1, 2026
HA 2026.11 pins
pydantic==2.14.1, but v0.8.7 requirespydantic<2.14, so the requirement can't be met.This is already fixed on
masterby #445, which changed the requirement topydantic>=2.11.7,<2.15. It just hasn't been released yet.Until there's a release, change that line in
/config/custom_components/zaptec/manifest.jsonto"pydantic>=2.11.7,<2.15"and restart HA. This keeps the upper cap, unlike removing it completely.@sveinse @steinmn: HA 2026.11.0 final is due around Nov 4. Could a release with #445 go out before then?
rhammen commentedon Nov 1, 2026
@sveinse, shouldn't we relax the pydantic cap to
<3?This is the third time a pydantic minor bump in HA has broken a released version:
Each time, the fix was only a change to the cap. Our code didn't need to change for pydantic itself, and
validate.pyhas had full test coverage since #338.You suggested this yourself in #337:
If a future minor version does break something, we'd fix it when it happens. That's the same work we do now, but only when there's an actual breakage.
sveinse commentedon Nov 2, 2026
Yes, please go ahead and propose a PR for fixing this and we'll get it included in 0.8.8
TorbjornMohn commentedon Nov 4, 2026
Error still present in the release verison ov core 2026.11.0 !!
PsychoMnts commentedon Nov 5, 2026
Zaptec intergration stopped working here too after updating to 2026.11.0
fredsluter commentedon Nov 5, 2026
Tried this
Until there's a release, change that line in /config/custom_components/zaptec/manifest.json to "pydantic>=2.11.7,<2.15" and restart HA. This keeps the upper cap, unlike removing it completely.
But does not work
Failed setup, will retry: Failed to validate data: 2 validation errors for list[ChargerFirmware] 0.AvailableVersion Field required [type=missing, input_value={'ChargerId': 'xxxxxxx', 'DeviceType': 4}, input_type=dict] For further information visit https://errors.pydantic.dev/2.14/v/missing 0.IsUpToDate Field required [type=missing, input_value={'ChargerId': 'xxxxxxxx', 'DeviceType': 4}, input_type=dict] For further information visit https://errors.pydantic.dev/2.14/v/missing
haakon88t-cell commentedon Nov 5, 2026
Same here
costibenzen commentedon Nov 5, 2026
had the same .
Claude MCP fixed quite fast
"Cause: Home Assistant 2026.11 includes a newer version of pydantic, a library Zaptec depends on. Zaptec 0.8.7 is still the latest release, and it only accepts versions below 2.14, so Home Assistant refused to load it.
Fix: I changed that one limit in the Zaptec files to "below 2.15", the same change the Zaptec developers have already made for their next release. "
fredsluter commentedon Nov 5, 2026
I have now made some extra changes
/config/custom_components/zaptec/zaptec/validate.py
changed these lines
ChargerId: str
DeviceType: int
IsOnline: bool
CurrentVersion: str
AvailableVersion: str
IsUpToDate: bool
into
ChargerId: str
DeviceType: int | None = None
IsOnline: bool | None = None
CurrentVersion: str | None = None
AvailableVersion: str | None = None
IsUpToDate: bool | None = None
This allows the Zaptec API response to omit those firmware properties without Pydantic rejecting the entire response.
After this I have made a complete reboot. This fixed it for me
haakon88t-cell commentedon Nov 5, 2026
Thank you fredsluter! This solved it for me 😃 Great work
sveinse commentedon Nov 7, 2026
v0.8.8 has been released. Please install and test.