If I get rid of attribute: event_object and to: human in the above Automation – i.e.SecuritySpy will send me a native notification when a human is detected with this camera, so the human detection is working as expected in SecuritySpy.
There are no Conditions, so I guess we can say those work. If I click Run Actions from the Automation detail page, the Actions work as expected (I get a notification on my phone with the specified image and notification actions). The Trigger is a direct copy of the example on the SecuritySpy for Home Assistant README (but with my entity_id).Īll the pieces seem to be working individually: For now (while testing) I just have it set up to send me a notification.Īutomation YAML alias: 'cam1 / Front Door: person detected – TEST'Įntity_id: binary_sensor.cam1_front_door_motionįilename: /config/www/cam_captures/frontdoor.jpg For example, someone walks up to the front door and it turns the porch light to 100%, sends me a notification, etc. SecuritySpy will detect if a human is present, and fire an event – I’d like to have Home Assistant do something when this happens. Here’s my Trigger config in SecuritySpy for this camera. SecuritySpy 5.4.1 on the same Mac, connected to Home Assistant via the SecuritySpy for Home Assistant integration. Home Assistant 2022.3.3 in Home Assistant OS via a VirtualBox VM on a Mac. This automation is trying to use the SecuritySpy for Home Assistant integration, but it’s not clear if that is where the problem lies. 
I can’t get an event to fire a trigger with an event_object Attribute change, but all the pieces seem to be working as expected.
0 kommentar(er)
