Dahua
rroller/dahua · v1.3.1
Dahua Camera and Doorbell Home Assistant Integration
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
light | Light | |
switch | Switch or outlet | |
camera | Camera | Needs its own HomeKit Bridge in accessory mode |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) | |
button | Button (as a switch) | |
select | Mode picker (as switches) |
3 reports below say how a device from this integration behaves in the Home app.
What people report
Dahua, Amcrest, Lorex, Imou and Intelbras cameras and doorbells work locally, with OEM firmware differences. Newer Imou DB6x firmware drops local API, and H.265 streams never paint in Apple Home.
- Works7
- Partly works7
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Amcrest NV5232E-16P NVR | Works | Channel diagnostic sensors fixed to show camera, not recorder, valuesSaved copyReported by @billjes in #1043, on an Amcrest NV5232E-16P running 1.3.0-rc.1: > on both channels the Diagnostic firmware/serial sensors show the recorder's values (4.000.00AC000.0.R, AMR044032F4F06B33E), while Device info shows each camera's own firmware (2.460.AC01.0.R) and serial. Two answers to one question, a few centimetres apart on the same page. The page was right. #1044 made a recorder channel's device page describe the camera in that slot, and #1054 gave the box a page of its own to be described on. These two sensors were never moved with it. ### One rule, not two copies The condition … Excerpt saved from GitHub on 2026-10-23. | PR #1058 · 2026-10 | |
| Dahua NVR4108-8P-4KS2 | Works | Could not be added over HTTPS on 2021 firmware; fixedSaved copyFixes #947. An NVR4108-8P-4KS2 on 2021 firmware could not be added over HTTPS. The reporter had already checked the same credentials against the same CGI endpoint in a browser and got an answer back. What they were told was: > The camera rejected that username and password Every 401 that reaches a caller is reported that way, and nothing recorded what the device had actually asked for, so a refused password and an unreadable challenge were indistinguishable. I probed the committed module with challenges real firmware sends. Three of them produce that message with the password being right: | … Excerpt saved from GitHub on 2026-10-23. | PR #954 · 2026-10 | |
| Dahua video doorbell | Works | Works in Home Works as video doorbell once bell and motion entities are linked | HomeKit video doorbell configured via HomeKit Bridge with bell and motion entitiesSaved copyYes, and it is configured on the HomeKit side rather than here. Home Assistant's HomeKit Bridge supports a video doorbell, and it needs to be told which entity is the bell and which is the motion sensor, because it cannot infer either: [code] With `linked_doorbell_sensor` set, a press produces a HomeKit doorbell notification with a snapshot. Answering the call is not possible. HomeKit two-way Excerpt saved from GitHub on 2026-10-23. | Issue #388 · 2024-09 |
| EmpireTech IPC-Color4M-TZ camera | Works Local | Tested on hardware and added to README supported tableSaved copySummary Add two EmpireTech-branded Dahua OEM cameras tested on physical hardware to the README’s known-supported-camera table: - `IPC-Color4M-TZ` in the 4 MP column. - `PTZ3E10X-T180` in the 8 MP column, with its separate 4 MP PTZ channel noted below the table. ## Validation - Two physical `IPC-Color4M-TZ` cameras were tested on firmware `3.140.0000000.21.R`, build `2025-12-06`. - One physical `PTZ3E10X-T180` was tested on firmware `3.211.0000003.1.R`, build `2025-11-11`. - Both model families have been configured as direct cameras in Home Assistant and exercised for camera entities, events, … Excerpt saved from GitHub on 2026-10-23. | PR #892 · 2026-09 | |
| EmpireTech PTZ3E10X-T180 PTZ camera | Works Local | Security light support completed for dual-sensor modelSaved copySummary Complete Security Light support for the dual-sensor `PTZ3E10X-T180`. Current capability probing correctly discovers this model’s shared red/blue deterrence output. Its runtime mapping differs from the generic direct-camera path, however: RPC2 state is reported on channel 1 rather than channel 0, and IO 0 is required to turn the output off. ## Changes - Select the verified RPC2 status channel and off encoding for the `PTZ3E10X-T180` family. - Retain the verified legacy CGI mapping as a fallback when RPC2 capability probing is unavailable. - Keep the two sensor-channel aliases … Excerpt saved from GitHub on 2026-10-23. | PR #893 · 2026-09 | |
| Intelbras VIPW-1300 camera | Works Local | Illuminator turn-on HTTP 400 fixed with fallback pathSaved copyFixes #994. ## The problem On some OEM/rebranded Dahua cameras (reported by @aridiojr on an Intelbras VIPW-1300, Dahua OEM), `light. _illuminator` turning on fails with HTTP 400. That firmware refuses every CGI `setConfig` on `Lighting_V2`, including no-op writes, so the plain illuminator path cannot drive the white light: [code] The same camera accepts the two-table `LightingScheme` + `Lighting_V2` write over RPC2 (`async_set_lighting_scheme_illuminator`), which is the path already used for `IPC-COLOR4M-TZ`. It is gated on that model name, so this camera never reaches it. @aridiojr confirmed … Excerpt saved from GitHub on 2026-10-23. | PR #999 · 2026-10 | |
| Lorex E893DD camera | Works | Added to README compatibility listSaved copyAdded Lorex E893DD camera model to the compatibility list in the README. Excerpt saved from GitHub on 2026-10-23. | PR #962 · 2026-10 | |
| Amcrest AD410 / Lorex 2K doorbell (DB61) | Partly works Local | Rebrands of Dahua DB61 with inconsistent features; some firmware shows as Generic RTSPSaved copyWhich firmware version are you using? There is a new firmware for the AD410: https://github.com/rroller/dahua/issues/282#issuecomment-1732595571 There were firmware versions from 2022 that caused problems with newer Home Assistant versions. I've been using an Imou DB61i for a few days now, which is basically identical to the Amcrest AD410. - Firmware from 2021 is working. - Firmware from 2022 is not working. - New Firmware from 2023 (1.000.0000002.1.R,build:2023-08-19) is working. My active Home Assistant installation is version 2023.8.4 with Dahua Addon 0.9.44 = The Imou DB61i works without … Excerpt saved from GitHub on 2026-10-23. | Issue #304 · 2023-09 | |
| Amcrest doorbell camera | Partly works Cloud | Free cloud needed for person detection and doorbell eventsSaved copyI'm shocked Amcrest hasn't done this with their older doorbell cameras yet. Personally I use a commercial grade NVR and pull the RTSP from the camera directly. But if they ever do kill the free cloud service I'll lose person detection, and doorbell event integration. It's the only thing left in my house that needs cloud for any functionality. I use Ecobee thermostats, but I've moved them to Homekit integration for full local control. Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23. | Reddit comment · 2026-07 | |
| Amcrest video doorbell | Partly works Cloud | Works with chime; doorbell events go out to cloud; ONVIF to NVR works locallySaved copyi have an Amcrest and while it detects people well in camera for notifications, and works on my original chime transformer, it is still cloud based for the integration. I am able to feed the onvif output to my nvr directly though, which is then integrated with HA locally. But doorbell events literally go out to the cloud and back. Also no way with HA that I found for talking to visitors through it, you need their app which is crap. And the issue with the IR nightvision bulbs reflecting off the lens so you cant see at night. I added 2 strips of black tape to mine to mitigate that. And the … Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23. | Reddit comment · 2026-06 | |
| Dahua camera with H.265 stream | Partly works | Broken in Home H.265 stream loads forever in Home app; use H.264 | Camera works in Home Assistant; HomeKit needs H.264 sub streamSaved copy@Tornadoalley constantly loading in HomeKit while working in the Home Assistant app is almost always the codec. HomeKit needs H.264. If the stream it is handed is H.265 or HEVC, nothing errors, it just never paints, which matches your screenshot and your clean logs. Worth checking on the camera itself, under Encode, for whichever stream HomeKit is using. If Main is H.265, either switch it to H.264 or point HomeKit at the sub stream and set that to H.264. I hit the same thing from the other direction on a video wall here: H.265 negotiated audio only and showed nothing, and moving the sub … Excerpt saved from GitHub on 2026-10-23. | Issue #576 · 2026-05 |
| Dahua NVR cameras | Partly works | Broken in Home Live view black when camera encodes H.265 | Cameras appear in HomeKit but live video stays black unless encoded as H.264Saved copyI have a problem with my Dahua NVR cameras. I can see all my camera on Home Assistant and Home Kit but using Home Kit I can't see live video. Someone could help me? Excerpt saved from GitHub on 2026-10-23. | Issue #244 · 2022-12 |
| Imou DB61i doorbell | Partly works Local | Video, motion, human detection work; newer firmware removes local API and breaks eventsSaved copyI can confirm that doorbell IMOU DB61i works, with video, motion detection, and human detection, is normal. The button press is detected as a local alarm. Thank you for this! Excerpt saved from GitHub on 2026-10-23. | Issue #261 · 2023-02 | |
| Imou IPC-TA42-B camera | Partly works Local | Local connection works again on firmware 2.800.0000000.15.R after earlier firmware broke itSaved copyNot a doorbell, but wow, I have two Imou's and I can connect to them locally again. There was an earlier firmware that broke local connections: * https://www.amazon.com/gp/product/B08RD2C67R (IPC-TA42-B) - Firmware v2.800.0000000.15.R * https://www.amazon.com/gp/product/B09W24KP3V (IPC-A43) - Firmware v2.800.0000000.16.R Excerpt saved from GitHub on 2026-10-23. | Issue #282 · 2023-06 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local polling
Talks to the device on your network, asking it for updates every so often.
Found automatically over
- DHCP
Details
| Installs (analytics) | 4,715 (0.67%) |
|---|---|
| GitHub stars | 572 |
| Latest version | 1.3.1 (2026-10-23) |
| Set up in the UI | Yes |
| Maintainers | @rroller |
| License | MIT |
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
Sources
- Documentation: https://github.com/rroller/dahua
- Source code: https://github.com/rroller/dahua
- Issues: https://github.com/rroller/dahua/issues
- HACS: https://hacs.xyz