![]() ![]() The solution there worked for me as well:Īdded a Template Sensor to configuration.yaml: sensor:įriendly_name: Person detected at front door In case anyone else runs across this: I found an Issue on the integration’s Github repo that seemed related. I’m new to Home Assistant and very new to YAML, so apologies for any mistakes regarding terminology. I enabled Debug Logging for SecuritySpy for Home Assistant, but I don’t see anything useful there. ![]() In contrast, notifications directly from SecuritySpy and the motion-only test Automation in Home Assistant (without event_object: human) both trigger / notify much faster (less than a second). Also of note, it takes about 4 seconds for the notification to show up when I manually set the State like this. If I manually set the state to on with event_object: human via Developer Tools > States > Set State, it will trigger the Automation.I suspect this might be the root of the issue? But I don’t have a for: setup for the Trigger, so I’d expect it to trigger regardless of the event_length? Out of desperation I did try setting for: to 0 seconds, but that had no effect so I removed it. Of note, event_object rapidly changes between human and None and the event_length never goes above 0 when it’s at human. If I look at the binary_sensor.cam1_front_door_motion Entity in Developer Tools > States I can see the event_object Attribute change to human as expected when I walk in front of the camera as seen in this video screen capture.So the binary_sensor.cam1_front_door_motion created by SecuritySpy for Home Assistant does work: regular motion is detected and the corresponding event will fire. In fact it fires a ton of them in quick succession. just use regular motion detection without checking for a human – it fires the trigger as expected. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |