I bought an Amcrest ASH47-W I’m trying to get into HA. Apprently this cam doesn’t play with the Dahua HACS integration. ONVIF only exposes the camera (which won’t stream) and “reboot”. I tried setting up the HA Amcrest integration and I got:
This entity (‘binary_sensor.amcrest_driveway_cam_motion_detected’) does not have a unique ID, therefore its settings cannot be managed from the UI. See the documentation for more detail
and the sensors don’t show anything.
I deleted the Amcrest integration out of my config.yaml but now I’m left with these inop sensors that I can’t delete. If I readd the Amcrest YAML to my config I still can’t delete them. I’m assuming this camera just isn’t compatible with the HA integration, because it appears to be compatible with almost nothing aside from its own app, even though it’s advertised as an ONVIF IP cam.
At this point I’d like to just remove these entities because I’ve already started the return and I will put my tail between my legs and reinstall my Ring floodlight cam.
Mine works fine on AD410. When you remove the integration, you can restart HA and then they will be gone. Make sure you close and repoen your browser or it’ll be cached.
That being said… I use events to for the sensors mostly instead of the inbuilt sensors. Works awesome. Obviously that wont help if the cam won’t stream. Any errors in your logs???
- host: !secret doorbell_ip
username: admin
password: !secret amcrest_frontdoor_password
name: Front Door Bell
resolution: high
stream_source: rtsp
binary_sensors:
- online
switches:
- privacy_mode
- host: !secret doorbell_ip
username: admin
password: !secret amcrest_frontdoor_password
name: Front Door Bell Sub
resolution: low
stream_source: rtsp
template:
- trigger:
- platform: event
event_type: amcrest
id: start
event_data:
camera: "Front Door Bell"
event: CrossRegionDetection
payload:
code: CrossRegionDetection
action: Start
data:
Action: Appear
object:
ObjectType: Human
- platform: event
event_type: amcrest
id: stop
event_data:
camera: "Front Door Bell"
event: CrossRegionDetection
payload:
code: CrossRegionDetection
action: Stop
data:
Action: Appear
object:
ObjectType: Human
binary_sensor:
- name: Front Door Bell Human
icon: mdi:motion-sensor
device_class: motion
state: >-
{{ 'on' if trigger.id == 'start' else 'off' }}
- trigger:
- platform: event
event_type: amcrest
id: start
event_data:
camera: "Front Door Bell"
event: CallNoAnswered
payload:
code: CallNoAnswered
action: Start
- platform: event
event_type: amcrest
id: stop
event_data:
camera: "Front Door Bell"
event: CallNoAnswered
payload:
code: CallNoAnswered
action: Stop
binary_sensor:
- name: Front Door Bell Ring
device_class: motion
icon: mdi:doorbell-video
state: >-
{{ 'on' if trigger.id == 'start' else 'off' }}
- trigger:
- platform: event
event_type: amcrest
id: start
event_data:
camera: "Front Door Bell"
event: VideoMotion
payload:
code: VideoMotion
action: Start
data:
Action: Appear
object:
- platform: event
event_type: amcrest
id: stop
event_data:
camera: "Front Door Bell"
event: VideoMotion
payload:
code: VideoMotion
action: Stop
data:
Action: Appear
binary_sensor:
- name: Front Door Bell Motion
device_class: motion
icon: mdi:motion
state: >-
{{ 'on' if trigger.id == 'start' else 'off' }}
I can’t get it to stream or anything with the Amcrest integration. The Dahua integration just says wrong username/password (Dahua works fine on my AD410). ONVIF exposes nothing and won’t stream either. I could get it into Frigate I suppose since you can view the stream in VLC, but the only thing I need is a binary sensor for motion (any motion) so it can turn on my outdoor lights at night. I don’t want to rely on Frigate because it only has sensors for objects (person, dog, cat, etc.) and I want the lights to turn on during any motion.
Apparently Amcrest really handicapped this camera, which is a shame because it has great picture quality, decent motion tracking, human detection, 24/7 recording to SD card, outdoor rated and WiFi.