⚠️ BREAKING CHANGES — ACTION REQUIRED BEFORE UPGRADING
No new breaking changes compared with 2.0.0. The migration 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; a registry conflict or backup failure causes setup to retry instead of building duplicate entities.
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.
Second release candidate for 2.0.1. Requires Home Assistant 2026.8.0 or newer. Stable users remain on 2.0.0 unless they select prereleases.
Since 2.0.1-rc.1
- Improve serial-migration conflict messages to identify both sides and distinguish duplicate legacy rows from an already-held destination. Messages name the affected entities, devices or config entry. Existing collision checks, registry backups and refusal-before-mutation behavior remain active. (#1144)
Included in 2.0.1-rc.1
- Fix
dahua.play_audioon devices that challenge the audio POST with HTTP 401. The push answers the fresh challenge and retries once with the complete clip, using fresh per-attempt state under the same speaker lock. A second 401 is reported rather than retried again. Devices that do not challenge still receive one POST. The contributor reports owner verification on the affected Empiretech Color4M. (#1137) - Update the development formatter dependency from Black 26.10.0 to 26.10.1. This tooling dependency is not part of the HACS integration ZIP. (#1142)
Validation
The combined merged code passed 5,470 tests, including all three real-ffmpeg conversion cases. All 353 Python files pass formatting with Black 26.10.1. The release HACS ZIP is verified against the tagged source and manifest version.
Hardware confirmation for the audio fix was reported by the contributor; automated tests cover fresh challenges, replaying the complete clip, a second refusal and the unchanged single-POST path.
2.0.0 release notes and upgrade instructions
Full changelog: 2.0.0...2.0.1-rc.2
Changes since the previous RC: 2.0.1-rc.1...2.0.1-rc.2