Dahua doorbell features inconsistent across brands #282
Comments
|
Hey @jrb80 - I recognize that unattributed collection of doorbell images!
I agree that the electronics are all OEM'd from Dahua and are essentially the same, but the firmware is no longer anywhere near the same for some models. The Lorex for example has neutered the local Dahua API from day 1 and forces a cloud-centric interface. I understand that even the Dahua DB6I's latest firmware has done the same. The Amcrest AD110/AD410 has retained local access to the API but not without issues. Interim firmware releases had broken the API event handling, but Amcrest has rectified that in their latest releases. I'm sure there's no intentional filter restricting features. You can only develop for a known API. Some desirable features aren't documented in any API guide. And some devices like the Lorex don't adhere to the Dahua API whatsoever, and sadly, not even the Dahua DB6I if updated. |
Yes the picture sums up the situation nicely (taken from online forum). I gather the average end user doesn't appreciate all these doorbells (and other cameras) all come from the same manufacturer but why they choose to have so many different firmware variants is beyond me, particularly as most are not maintained. I am using Imou DB61i which has local API control (firmware v1.000.0000001.0.R Build: 2021-11-10) which is currently reported as the latest. Shame the firmware is a bit of mess as the hardware is pretty good. In theory, the Dahua/Imou DB61 should have the same feature level support as the Amcrest AD410. The question is why are some of the features missing, some further digging is required... |
Yep - I recognized it because it was a composite image I had created from scratch to show the differences in the case design. https://ipcamtalk.com/threads/a-new-doorbell.59558/page-7#post-634503 Your IMOU doorbell appears to be using the initial 2021 firmware release so be careful if a newer release comes out as it could completely disable use of this integration. See what other users have experienced when updating their DB6I's - https://ipcamtalk.com/threads/dh-db6i-doorbell-warning-do-not-upgrade-firmware.66508/#post-714024 Edit: I just now noticed you had posted a question to that same online forum/post I just referenced - asking if a newer dahua firmware still has disabled the local API. That would be good to know if corrected, but I doubt it. |
|
FYI: There is a new firmware version available for the Imou DB61i since yesterday. Firmware: 1.000.0000002.1.R,build:2023-08-19 https://ipcamtalk.com/threads/dh-db6i-doorbell-warning-do-not-upgrade-firmware.66508/#post-797703 ff. It works with the Dahua addon, except for "Smart Motion Human" and "Smart Motion Vehicle". So far I haven't encountered any errors or problems. |
|
Not 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:
|
|
After some tests some more info for the Imou DB61i In advance:
Human detection is woking over Cross Region Detection and not Smart Motion Human. You can turn off motion detection and human detection still works. You will receive a "Human Detected" notification about the Imou App and at the same time you can see a "Cross Region Detection" in the Dahua Log.
I can't yet judge how well and reliably the human detection function works. Next week I will mount the video/doorbell outside and test it there. |
|
For what it's worth, this new DB6I update now behaves identically to the Amcrest AD410, with original firmware. (Edit: not sure about the newest 8/2023 firmware). Only 1 interim iteration of the AD410 (and AD110) firmware broke the API event handling which has long been fixed. It's sure good to see Dahua revert from a cloud-centric API back to a far more useful local API control. Also confirming that the only motion detection AI implemented is the IVS-based logic for human detection via cross-region detection event. The more advanced Smart Motion Detection (SMD) was never implemented. In any case, the human detection works quite well for the most part in eliminating spurious movement (rain, sun, shadows, bugs, birds). as long as general "pixel change" motion is disabled. Oddly, I do get human detection events for small animals though, especially cats. |
|
Yes, there was also an update for the Amcrest AD410 a few days ago: Amcrest AD410 Change log: Lexus_SDB61i-Lexus2_Eng_N_32M_CA_V1.000.00AC002.0.R.20230810.bin The update incorporates the following enhancements:
I've only had the DB61i since Friday and want to use it to replace my Amcrest AD110. The Imou Smart Life app definitely has fewer setting options than I previously had with the Amcrest app for my AD110:
Unfortunately, the Amcrest AD410 is not available here in Germany and you cannot import it from the USA - for example via Amazon. In addition, the Imou DB61i was currently available on Aliexpress for € 75 and is therefore of course significantly cheaper than the Amcrest AD410, which is still said to cost $ 154.99 from Amcrest itself. I'm definitely curious to see how well the Imou DB61i works - or not. :-) |
The Dahua DB61 doorbell is resold through various partners under different names, i.e. Amcrest AD410, Lorex 2K. Dahua also use different end user direct brands for different markets, i.e. Imou DB61i, LincX2Pro. All models use the same hardware and electronics but perhaps with some minor adjustments to the firmware. However, the feature support with this HA integration is inconsistent, e.g. smartmotion switch, siren switch, call button binary sensor, etc are not available for the Dahua OEM version.
I wonder whether some filter is used in the integration which restricts features? Perhaps the integration should be designed in a generic way which supports all of the various brands.
The text was updated successfully, but these errors were encountered: