Describe what’s not working. Any errors in the log? The core Amcrest integration has supported RTSP streaming on both the AD110 and AD410 since they’ve been released. Human detection/doorbell press detection requires event handling.
Previously I’d seen URL errors in my logs, but for some reason I’m not seeing them now. When I add in the camera all I get is a single entity for the camera (camera.amcrest_camera) and I can get what looks like some sort of stream, but nothing else. No events, no other entities other than a single camera entity. I’ve been running the amcrest2mqtt but would really prefer to have it all in HA
Ok…it took me re-reading the doc to see the ‘binary_sensors’ section in amcrest. Did a ‘listen to events’ and saw the amcrest event show up. Of course, now I have even more questions.
If I do a ‘enable_recording’ where does the video get stored?
Can you share some of your example configs and/or automations? Specifically around triggering something when someone rings the doorbell
If you are using the core Amcrest integration, the provided binary sensors aren’t of much use for the AD410/AD110 doorbells. The custom Dahua integration does a better job of creating useful sensors, but I prefer to stick with triggering on events as it’s more flexible since the event payload is exposed.
Here’s the automation for triggering on the doorbell press event.
trigger:
- platform: event
event_type: amcrest # Note: for the custom Dahua integration, use "dahua_event_received" here
id: doorbell button pressed
event_data:
event: CallNoAnswered
payload:
action: Start
Here’s the AD410 human detection motion trigger. On the SmartHome app, I recommend configuring human detection ONLY, and turn off general motion detection. If you must check for both types of motion, then you will need to add the VideoMotion event.
trigger:
- platform: event
event_type: amcrest
id: Human Motion
event_data:
event: CrossRegionDetection
payload:
action: Start
data:
ObjectType: Human
For you AD110 users out there, the core Amcrest integration motion binary sensor triggers on raw pixel changes within the grid (VideoMotion event). That creates a lot of false triggers. The AD110 has a PIR that creates motion events on heat signatures, but the Amcrest motion binary sensor ignores it. Here’s what you need to use instead:
trigger:
- platform: event
event_type: amcrest
id: AD110 Object Motion (from PIR sensor)
event_data:
event: AlarmLocal # or ProfileAlarmTransmit can be used
payload:
action: Start
9 Likes
Perfect! I’m going to stick with the Amcrest integration now that I understand it better! Thanks for those configs. And yes, I really like the fact it does ‘human’ detection instead of just motion detection that is usually a false positive.
Just a note for people that want to go fully offline regarding the two-way audio feature, I suggest looking into Amcrests View Pro app for android and Amcrest View Lite for apple devices. It uses ONVIF to connect to the doorbell and supports the two-way audio.
I have two devices: an old Nook HD with LineageOS installed, running Amcrest View Pro and iPad 1 with a Amcrest View Lite from the AppStore. Both of them along with the AD110 are on my IoT VLAN with no internet access and working fine.
As a precaution, I would if you are using the apps, do NOT modify any of the doorbell properties using them. Just use them to view and have two way talk audio.
Has anyone had any luck being able to trigger some of the “Doorbell Quick Responses” on AD410 via Home Assistant?
Not that I’ve heard, and I’ve had no luck. When listening to ALL amcrest/ad410 events and sending a quick response via the SH app, no events are detected. The API extensions for SmartHome communications haven’t been publicly documented either.
So it’s a mystery for now what the mechanism is.
1 Like
Thanks for the response @GaryOkie, appreciated! Hopefully it can be figured out, would be a handy feature! Trying all I can to avoid having to use the awful Amcrest app 
Sorry, less HA and more just doorbell, but do you guys get a snapshot in the event list in the Smart Home app when someone rings the doorbell? We don’t really use this doorbell often it’s more just for the camera POV… so I kinda ignored it for awhile… but was curious if it was worth looking into. I’m pretty sure I have occasionally got an image, but not at all recently.
My Android SH app (for AD410) is showing thumbnails in the event list just fine. Don’t think it matters, but I do have “push notification thumbnail” turned off. (I’m also sending snapshots with a link to recorded video via Telegram to our phones so my reliance on the SH app is mainly limited to answering the doorbell, which is quite rare).
How are you sending the snapshots? I’d like to include that in my HA!
You will need an integration that can provide push notifications with the ability to include pictures. I’m using Telegram. There are several other integrations that can do this - PushBullet and the HASS Companion to name a few.
Creating local snapshots is simply done with the camera.snapshot service.
Until we can send quick responses via home assistant I’ll need to use the app on my iphone,
Has anyone been able to change the orientation when getting a ‘call’ on the ios app? for some ridiculous reason when I answer it forces landscape mode and stretches the picture distorting it, truly rubbish.
I wonder about that too, any success?
Afraid not! Hopefully someone can figure that piece out, it’d be really useful!
is it possible to detect the button press in HA for this doorbell?
welcome to the bottom of the thread. Several posts earlier…
1 Like
It seems the latest Amcrest integration now exposes this, but I haven’t upgraded yet. This is what I currently use:
- trigger:
- platform: event
event_type: amcrest
event_data:
event: CallNoAnswered
payload:
action: Start
- platform: state
entity_id: binary_sensor.doorbell_rang
to: "off"
binary_sensor:
name: Doorbell Rang
icon: "{{ (trigger.platform == 'event') | iif('mdi:bell-ring-outline', 'mdi:bell-outline') }}"
state: "{{ trigger.platform == 'event' }}"
auto_off:
seconds: 5
Otherwise, use the Dahua integration as suggested.
1 Like
It seems the latest Amcrest integration now exposes this (button press).
Well, it did very briefly. The PR to expose the doorbell press event (edit: as a binary_sensor) was initially approved and merged. However, it was then noticed by a different reviewer that it violated a rule that no integration that require NEW YAML config updates can be implemented, so this update was quickly reverted. See: New amcrest binary sensor to monitor doorbell button by PanicRide · Pull Request #66302 · home-assistant/core · GitHub
Incidentally, a previous update to add the crossline detection event as a binary_sensor with a corresponding YAML requirement did get approved. Apparently the reviewer wasn’t aware of this rule and it snuck by.
Thanks for posting how the doorbell event can be transformed to a binary_sensor via a template. I would point out that instead of using a binary_sensor, the relatively new “Button” integration would be a bit better since it doesn’t need to be turned on, then off.