Skip to content

Zaptec v0.8.7 fails to load on Home Assistant Core 2026.11 due to pydantic version incompatibility #454

Closed

Description

@fmjensen

Description

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.

Activity

  1. kaffedrikkeren commented on Nov 5, 2026

    @kaffedrikkeren

    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.

  2. JohnnydeJong commented on Nov 5, 2026

    @JohnnydeJong

    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!

  3. b00tsie commented on Nov 5, 2026

    @b00tsie

    same here. hope a permanent fix will be released soon...

  4. JohnnydeJong commented on Nov 6, 2026

    @JohnnydeJong

    Changing "pydantic>=2.11.7,2.14" to "pydantic>=2.11.7", in the manifest.json worked as a work around.

  5. b00tsie commented on Nov 6, 2026

    @b00tsie
  6. sveinse commented on Nov 7, 2026

    @sveinse
    Collaborator

    v0.8.8 has been released. This should fix this issue. Please install and test.

  7. JohnnydeJong commented on Nov 7, 2026

    @JohnnydeJong

    Thanks!

  8. b00tsie commented on Nov 10, 2026

    @b00tsie

    i believe it is fixed again.

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