Imou Life
user2684/imou_life · v1.0.16
Home Assistant custom component for controlling Imou devices
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 |
|---|---|---|
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) |
What people report
Cloud-polled Imou cameras work with a developer account limited to 5 controllable devices. Doorbells and some models lack events, streaming or API calls.
- Partly works2
- Won’t be supported2
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Imou Bullet 2C camera | Partly works Cloud | Motion push callback needs HTTP endpoint or TLS workaroundSaved copyI have followed the Option 3 described here in order to enable the HASS to receive callbacks from Imou Cloud for my Bullet 2C cameras motion alarm, but the callback url configured on the service was never triggered by them. I'm using the https://webhookrelay.com/ service, but tried to debug with https://requestbin.com/ also. Both services didn't receive any request from Imou cloud. Just to be clear, I received the push notifications on my iOS app as expected, just the Imou cloud isn't working. Here how was configured on Imou Cloud: I tried these and nothing worked for now: - Generate a … Excerpt saved from GitHub on 2026-10-23. | Issue #56 · 2023-03 | |
| Imou camera hitting DV1026 API error | Partly works Cloud | Function unsupported by some models after version 1.0.14Saved copyVersion of the custom_component 1.0.14 ## Configuration This error originated from a custom integration. Logger: custom_components.imou_life Source: custom_components/imou_life/coordinator.py:44 Integration: Imou Life (documentation, issues) First occurred: 13:57:23 (5 occurrences) Last logged: 14:57:23 APIError: DV1026: The device does not support the call of this function. Traceback (most recent call last): File "/config/custom_components/imou_life/coordinator.py", line 42, in _async_update_data return await self.device.async_get_data() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File … Excerpt saved from GitHub on 2026-10-23. | Issue #82 · 2023-12 | |
| Imou Cue 2 camera | Won’t be supported Local | Local ONVIF control not planned by maintainerSaved copyI have disabled to remote functionality of the camera by changing the gateway of the camera. Now I have control of the camera on my local network via the ONVIF protocol/RTSP streams. Can this addon be adapted to discover devices on the local network and have the same control? I have the Cue2 model btw. Excerpt saved from GitHub on 2026-10-23. | Issue #123 · 2024-11 | |
| Imou DB11/DB60/DB61 doorbells | Won’t be supported Cloud | Motion and doorbell button sensors not supported; cloud video stream failsSaved copyI am requesting support for the Imou/Dahua doorbell products (DB11/DB60/DB61) to provide motion detection and doorbell button binary sensors. The recent binary sensor enhancement for cameras is not working for doorbells. I think this is because it uses a different event classification `mobileDetect` whereas cameras are using `videoMotion` events. Ideally I want to know when someone actually presses the doorbell button, probably more important than the motion detection event. This should be possible through the `callBellEvent` Example JSON webhook response for `mobileDetect` event [code] … Excerpt saved from GitHub on 2026-10-23. | Issue #35 · 2022-11 |
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
Cloud polling
Goes through the maker’s cloud, asking it for updates every so often. Needs the internet and an account.
Details
| Installs (analytics) | 1,247 (0.18%) |
|---|---|
| GitHub stars | 163 |
| Latest version | 1.0.16 (2025-06-06) |
| Set up in the UI | Yes |
| Maintainers | @user2684 |
| License | MIT |
Limitations from the README
- The Imou API does not provide a stream of events, for this reason the integration periodically polls the devices to sync the configuration. So if you change anything from the Imou Life App, it could take a few minutes to be updated in HA. Use the "Refresh Data" button to refresh data for all the devices' sensors
- Imou limits up to 5 the number of devices which can be controlled through a developer account (e.g. the method used by this integration). Additional devices are added successfully but they will throw a "APIError: FL1001: Insufficient remaining available licenses" error message whenever you try to interact. As a …
- For every new device to be added, AppId and AppSecret are requested
- Advanced options can be changed only after having added the device
- Due to malformed requests sent by the Imou API server, in order for push notifications to work, Home Assistant must be behind a reverse proxy
Notable forks
Forks with stars, or with code pushed at least 90 days after the original’s last push. Useful when the original goes quiet.
| Fork | Stars | Last push | Description |
|---|---|---|---|
| maximunited/imou_life Newer code | ★ 2 | 2026-10-22 | Home Assistant custom component for controlling Imou devices |
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/user2684/imou_life
- Source code: https://github.com/user2684/imou_life
- Issues: https://github.com/user2684/imou_life/issues
- HACS: https://hacs.xyz