AD410 button pressed stopped working in latest 0.9.47

rroller / dahua

Dahua Camera and Doorbell Home Assistant Integration

MIT License

382 stars 73 forks source link

AD410 button pressed stopped working in latest 0.9.47 #295

Open barrymossel opened 1 year ago

barrymossel commented 1 year ago

Last week the button pressed for my AD410 stopped working. Removed the doorbell and added it again. No button pressed binary sensor is added. Downgraded to 0.9.46 and added the doorbell again, and it works again.

michaeloldaker commented 1 year ago

i have the same issue, how do i downgrade so i can get this feature back? this is the main door everyone uses and i use this binary sensor to alert over google speakers that someone is at the door

shred86 commented 1 year ago

Out of curiosity, do any of you also have the AD410 integrated through Scrypted?

I use this integration with Home Assistant for my wall mounted tablets and the Amcrest integration with Scrypted for HomeKit support. It works fine for a period of time but at some point, I have the same issue where doorbell press events are no longer registered. If I restart both integrations, everything will work fine again for some period of time before having issues. Everything else works though (e.g. motion events, streaming video, etc.).

My initial thought was maybe something was going on where the AD410 didn't like being connected to both integration, and when I disabled this integration via HA, the Scrypted one worked fine for several days. I'm not sure if that is actually true but if you guys are having the same issue with only being integrated through HA, then I suspect what I thought is not the case.

kenno7 commented 11 months ago

I also have this issue with 0.9.47 and have since downgraded to 0.9.46 I can see that 0.9.48 is out now but no mention of a fix to this issue.

I have intermittant issues with the entire integration going offline in 0.9.46 but have done a bandaid fix for it with the following automations which triggers several times a day (motion is just one of the sensors that go offline when there is an issue .. ) :

alias: Reload Dahua for Amcrest Doorbell Ring Issue description: "" trigger:

platform: state entity_id:
- switch.amcrest_ad410_doorbell_motion_detection to: unavailable from: null condition: [] action:
service: homeassistant.reload_config_entry data: {} target: device_id: e48912e9797cc4a6dbfd121b0983dea7 mode: single

thornygravy commented 11 months ago

I haven't tried 0.9.48 yet, but I'm on firmware 1.000.0000000.7.R,build:2021-02-20, and 0.9.44 is pretty stable for me. Every once in a while all the cameras will become unavailable for a second but it's super short. Just hoping to help someone out. Cheers.

NoNaMoe commented 11 months ago

I also noticed my AD410 button was not working at all! Downgraded to 0.9.46 and it works again now, but only if I don't have the feed open (using WebRTC on my HA dashboard). I've seen Frigate users say when the doorbell is "In Call" the button doesnt work (WebRTC attempting 2way audio would cause this). They are able to fix it by putting #backchannel=0 to the end of the stream url. We don't have that option as this addon exposes the camera as an entity?

https://github.com/blakeblackshear/frigate/issues/7093 https://github.com/blakeblackshear/frigate/discussions/5342

razulian commented 11 months ago

I have v0.9.48 installed together with AD410 firmware V1.000.00AC002.0.R.230810. It didn't work for me initially but after removing the camera, updating to the latest firmware and re-configuring it I could receive sensor updates again. I did not have to do anything special other than that. My automation is triggered when the Alarm Local-sensor becomes unsafe.