⚠️ BREAKING CHANGES — ACTION REQUIRED BEFORE UPGRADING
No new breaking changes compared with 2.1.0. The migration and removal notices below apply when upgrading from older releases.
CAMERA IDENTITY MIGRATION: Take a Home Assistant backup before upgrading. Cameras whose normal identity call fails but whose alternate CGI reports a serial now adopt that serial. Migration preserves entity IDs; unresolved collisions stop setup and require review through a repair or manual guidance. After adopting a serial, a temporarily unavailable serial read causes setup to retry rather than rebuilding entities under a generated identity.
No automatic entity removals or entity-ID renames are introduced compared with 2.0.0. The additional removal notices below apply when upgrading from 1.x.
Warning
Illuminator entities removed on affected channels: Channels that explicitly report a white emitter without a supported brightness bank no longer get an Illuminator light entity. Check automations and dashboards that reference it and remove or update affected references before upgrading.
Indoor monitors with no camera: Affected VTH monitors that do not describe a local camera and explicitly refuse the VideoInput table no longer get camera-related entities. Existing registry rows can remain unavailable. Review automations and dashboards that reference them.
Take a Home Assistant backup before upgrading. Existing HTTP indoor monitors now migrate their registry identities to their reported serial. Entity IDs are preserved. An unresolved registry conflict stops setup and raises repair or manual guidance; a backup failure retries without mutating the registries.
Affected recorder automations and dashboards need updating. This release removes the old per-camera Alarm Local sensors on recorders with the new terminal sensors and consolidates duplicate per-channel relay switches on the recorder.
- Illuminator entities: A named white-light row without a MiddleLight, NearLight or FarLight brightness bank no longer creates an Illuminator entity. This removes controls whose writes target a nonexistent brightness field and are refused. Review affected automation/dashboard references.
- VTH camera-related entities: A monitor with no Local0 camera declaration and an explicitly refused VideoInput table loses the nonworking camera-related entities, including motion controls. Retire affected dashboard and automation references. Session failures leave the capability undecided.
- HTTP indoor monitors: This release migrates generated identities to the real serial. The log names a private directory containing copies of the three persisted registries. Keep your Home Assistant backup; resolve any logged identity conflict or backup failure before retrying setup.
- Alarm inputs: Retarget automations and dashboards from the old per-camera Alarm Local sensors to the corresponding recorder terminal sensors. The old sensors become unavailable; their registry entries remain for reference.
- Relay outputs: Update automations and dashboards that used duplicate per-channel relay switches to use the recorder's relay switches.
Release candidate for 2.1.1. Requires Home Assistant 2026.8.0 or newer. The latest stable release remains 2.1.0.
The installed integration is unchanged from 2.1.0 apart from its version number. This candidate accompanies a repository documentation update; AGENTS.md is not included in the HACS integration ZIP.
New in 2.1.1-rc.1
- Refresh the repository map: Correct AGENTS.md to describe 38 integration modules, about 35,000 lines, 32 services, 320 Python files under tests and about 5,700 tests. Independent collection confirms 5,735 tests.
- Add the missing audio.py and late.py entries, describing audio preparation and late capability discovery. (#1167)
Validation
The PR’s GitHub checks pass. Its documentation counts were independently checked against the tracked tree, parsed service registrations and services.yaml. The release CI validates HACS, Hassfest, formatting, the full 5,735-test suite, tag/manifest agreement, ZIP layout and HACS visibility. The 59-file downloadable ZIP is verified byte for byte against the tagged integration files and matches 2.1.0 except for the manifest version.
Hardware and channel-search limitations remain as documented in the 2.1.0 release notes.
Full changelog: 2.1.0...2.1.1-rc.1