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
From this morning 11AM no connection anymore ... #452
Instellen mislukt, wordt opnieuw geprobeerd: Failed to validate data: 2 validation errors for list[ChargerFirmware] 0.AvailableVersion Field required [type=missing, input_value={'ChargerId': 'a82db78b-5...6.0.7', 'DeviceType': 4}, input_type=dict] For further information visit https://errors.pydantic.dev/2.13/v/missing 0.IsUpToDate Field required [type=missing, input_value={'ChargerId': 'a82db78b-5...6.0.7', 'DeviceType': 4}, input_type=dict] For further information visit https://errors.pydantic.dev/2.13/v/missing
This is what I have, a dependency problem. The version of the pedantic package seems to br too limited!?
Loggare: homeassistant.setup
Källa: setup.py:272
Inträffade först: 4 november 2026 kl. 23:49:27 (1 förekomst)
Senast loggat: 4 november 2026 kl. 23:49:27
Setup failed for custom integration 'zaptec': Requirements for zaptec not found: ['pydantic>=2.11.7,<2.14'].
Loggare: homeassistant.util.package
Källa: util/package.py:222
Inträffade först: 4 november 2026 kl. 23:49:25 (3 förekomster)
Senast loggat: 4 november 2026 kl. 23:49:27
Unable to install package pydantic>=2.11.7,<2.14: error: No solution found when resolving dependencies cause: Because you require pydantic>=2.11.7,<2.14 and pydantic==2.14.1, we can conclude that your requirements are unsatisfiable.
I think the pydantic error is because if the new 2026.11 version released today. Im still on 2026.10.4, and the error occured today, it references a firmware version field in the error. Also tried to change thr manifest file with no luck.
Logger: homeassistant.setup
Bron: setup.py:272
Eerst voorgekomen: 4 november 2026 om 22:12:08 (1 gebeurtenis)
Laatst gelogd: 4 november 2026 om 22:12:08
Setup failed for custom integration 'zaptec': Requirements for zaptec not found: ['pydantic>=2.11.7,<2.14'].
Temporary workaround that works for me until a new release is out: edit /config/custom_components/zaptec/manifest.json and change the pydantic requirement to
"pydantic>=2.11.7,<3"
then restart Home Assistant. This matches what #451 proposes. The change will be overwritten by the next HACS update, which is fine once the fix is released.
Temporary workaround that works for me until a new release is out: edit /config/custom_components/zaptec/manifest.json and change the pydantic requirement to
"pydantic>=2.11.7,<3"
then restart Home Assistant. This matches what #451 proposes. The change will be overwritten by the next HACS update, which is fine once the fix is released.
My Zaptec stopped working yesterday and are still 2026.10.4, msnifest fix does nothing, seems like the firmware value returned by API contains something not accepted. What formware are ypu using?
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.<charger>_charge_power to exclude the charger load. With the sensor unavailable, that exclusion is skipped and the home battery would discharge into the car.
Temporary workaround that works for me until a new release is out: edit /config/custom_components/zaptec/manifest.json and change the pydantic requirement to
"pydantic>=2.11.7,<3"
then restart Home Assistant. This matches what #451 proposes. The change will be overwritten by the next HACS update, which is fine once the fix is released.
Temporary workaround that works for me until a new release is out: edit /config/custom_components/zaptec/manifest.json and change the pydantic requirement to
"pydantic>=2.11.7,<3"
then restart Home Assistant. This matches what #451 proposes. The change will be overwritten by the next HACS update, which is fine once the fix is released.
Activity
phillipelauwych commentedon Nov 4, 2026
Version 0.8.7 Zaptec is used en EV charger-firmware 6.0.7
jonare77 commentedon Nov 4, 2026
Same problem her:
GrasshopperNL commentedon Nov 4, 2026
Same here
thuben commentedon Nov 4, 2026
This is what I have, a dependency problem. The version of the pedantic package seems to br too limited!?
Loggare: homeassistant.setup
Källa: setup.py:272
Inträffade först: 4 november 2026 kl. 23:49:27 (1 förekomst)
Senast loggat: 4 november 2026 kl. 23:49:27
Setup failed for custom integration 'zaptec': Requirements for zaptec not found: ['pydantic>=2.11.7,<2.14'].
Loggare: homeassistant.util.package
Källa: util/package.py:222
Inträffade först: 4 november 2026 kl. 23:49:25 (3 förekomster)
Senast loggat: 4 november 2026 kl. 23:49:27
Unable to install package pydantic>=2.11.7,<2.14: error: No solution found when resolving dependencies cause: Because you require pydantic>=2.11.7,<2.14 and pydantic==2.14.1, we can conclude that your requirements are unsatisfiable.
jonare77 commentedon Nov 4, 2026
I think the pydantic error is because if the new 2026.11 version released today. Im still on 2026.10.4, and the error occured today, it references a firmware version field in the error. Also tried to change thr manifest file with no luck.
EenerNL commentedon Nov 5, 2026
Same problem here since updating to 2026.11.
GrasshopperNL commentedon Nov 5, 2026
Temporary workaround that works for me until a new release is out: edit
/config/custom_components/zaptec/manifest.jsonand change the pydantic requirement to"pydantic>=2.11.7,<3"
then restart Home Assistant. This matches what #451 proposes. The change will be overwritten by the next HACS update, which is fine once the fix is released.
+1 for merging #451 and tagging a release.
jonare77 commentedon Nov 5, 2026
My Zaptec stopped working yesterday and are still 2026.10.4, msnifest fix does nothing, seems like the firmware value returned by API contains something not accepted. What formware are ypu using?
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
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.<charger>_charge_powerto 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!
StevetheV commentedon Nov 7, 2026
This fixed it for me! Bedankt @GrasshopperNL
jonare77 commentedon Nov 7, 2026
Didny work for me, i needed to change validate.py to get the firmware error resolved. Started the same day, but on version 2026.10.4 for me.
sveinse commentedon Nov 7, 2026
v0.8.8 has been released. Please install and test.
thuben commentedon Nov 7, 2026
V0.8.8 works for me! Thanks for the update!!!