Skip to content

Error after updating to HA 2026.11.0b0 #448

Closed

Description

@wilfredktlr

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'].

Activity

  1. Bluhme1 commented on Oct 29, 2026

    @Bluhme1

    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.

  2. munklinde commented on Oct 29, 2026

    @munklinde

    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.

  3. rhammen commented on Nov 1, 2026

    @rhammen
    Contributor

    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?

  4. rhammen commented on Nov 1, 2026

    @rhammen
    Contributor

    @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.py has had full test coverage since #338.

    You suggested this yourself in #337:

    I think we should rather relax the upper bound on pydantic version. By having this restriction, we always need to follow suit when HA change version.

    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.

  5. sveinse commented on Nov 2, 2026

    @sveinse
    Collaborator

    Yes, please go ahead and propose a PR for fixing this and we'll get it included in 0.8.8

  6. TorbjornMohn commented on Nov 4, 2026

    @TorbjornMohn

    Error still present in the release verison ov core 2026.11.0 !!

  7. PsychoMnts commented on Nov 5, 2026

    @PsychoMnts

    Zaptec intergration stopped working here too after updating to 2026.11.0

  8. fredsluter commented on Nov 5, 2026

    @fredsluter

    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

  9. haakon88t-cell commented on Nov 5, 2026

    @haakon88t-cell

    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

    Same here

  10. costibenzen commented on Nov 5, 2026

    @costibenzen

    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. "

  11. fredsluter commented on Nov 5, 2026

    @fredsluter

    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

  12. haakon88t-cell commented on Nov 5, 2026

    @haakon88t-cell

    Thank you fredsluter! This solved it for me 😃 Great work

  13. sveinse commented on Nov 7, 2026

    @sveinse
    Collaborator

    v0.8.8 has been released. Please install and test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    verificationWaiting for verification

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions