I just discovered with sub stream is, so I got it working but all the above still applies!!

You know you want to Ben..

I agree, from what I've seen on the web so far there would be a great demand for something like this. The NEST solution is Clould based and insanely expensive. I genuinely think that a home server solution which could integrate with Google Home and Homekit would be very popular.

Anyone else have any experience with integrating security spy with home assistant. I am close, but do not have it working successfully yet.

I'd like to get my SS install working with HA too. I'm curious about ben's aug 23rd post. Is this method known to work, or is this just speculation?

Has anyone made any more progress on this?

configuration.yaml (hass)
https://gist.github.com/boxgr0ve/a0dc40e954b5eb2b703dcda796aea098

automation.yaml (hass)
https://gist.github.com/boxgr0ve/b74699e680cf70f4e823c1501be1fd9d

trigger_motion_capture_scpt (Mac)
https://gist.github.com/boxgr0ve/81973b8b14df2609c8fecc1b5df75207

Hopefully self explanatory ....

Ben mentioned in an earlier post that using the "++video request" method would be the best approach for pulling live video into HA today. It seems to work well, but is there a way to get only the video feed, without the "live" title and links to "main page", "captured files" and "cant view?" ?

Thanks Ben, that's exactly what I was looking for. And you are correct, I was trying to use the new iFrame card in Home Assistant to display live video using the live request feature.

Has anyone had more luck integrating with Home Assistant?

So spending some time with Home Assistant (HA), as I need a better way to control automations vs spending additional$$ for expensive web relays, when I have existing relays in place. Over the years, I've collected switches from TP-Link, Leviton, Eco Plugs, EweLink, and now leaning more towards Shelly relays. I'm finding it hard to find good outdoor motion sensors that tie to HA, so I'm on a quest to learn Node-Red and incorporate SS into HA.

Thanks Boxgrove for the github files. I'm running my instance of HA on a Raspberry Pi, as I've got my Mac Pro running SS & Plex management, so I'm trying to reverse the thought process between the two platforms.

My primary goal is when a motion is detected by a camera, then I'd like to 1) Determine if it's night time and 2) If Yes, send a command to turn on the lights associated with that camera and potentially another. Basically, using my cameras a glorified Motion Sensors, but hoping over time the AI interface that Ben has written will help minimize false positives from the occasional wasp or other insect, and thereby scare off potential intruders. My secondary goal, I plan to dissect my alarm system panel, whereby an actual breach of an alarm contact will trigger All Cameras, All Lights (internal/external), and anything else that makes sense that my current alarm system doesn't cover or wants to gouge me on the cost of the service. My current alarm system is an IControl Hub that uses Z-Wave modules and already has a siren and central station monitoring. I'm hoping to figure out how to sniff out the Z-Wave messaging and use HA to drive the other switches/automations.

Any ideas or ways to simplify this would be appreciated. I agree with the others on this thread, that tying together existing IoT devices with SS is a good thing for Ben and the future of SS for all of us.

tlutrick I use combination of Apple scripts from SS to webhooks on the Pi running HASS

I’ll share config tomorrow but basically when motion is detected on SS, it sent a curl command to a URL on the Pi (the webhook) which acts as a trigger in an automation. You can then use a condition if it’s night (maybe using the sun sensor component) and then turn on the light as normal.


EDIT: right this will be very quick and dirty but hopefully you can follow... This is an automation I use to detect motion on a SS camera to flash a light an LED strip in my office. Formatting will probably be screwed up, but if you can't get it working give me a few days and I'll try and get it on GitHub or something.

make a security spy script: mine is called driveway_ss_trigger_1 - pay attention to that (remove square brackets below) and set that to be an action on motion detection.

[do shell script "curl -d \"\" \"http://HASS_IP:8123/api/webhook/driveway_ss_trigger_1\""]

Then my automation in Home Assistant looks like:

- alias: SS Trigger Driveway Desk Flash
id: ss_trigger_driveway_desk_flash
trigger:
- platform: webhook
webhook_id: driveway_ss_trigger_1. ### this needs to match up to what the curl command points to

condition: ### this just links to the occupancy sensor in my office to make sure it doesn't fire when I'm not there
condition: state
entity_id: binary_sensor.0x00158d0002c5888c_occupancy
state: 'on'

action:
- service: script.driveway_motion #this runs a script that flashes the LED's
- service: automation.turn_off
entity_id: automation.ss_trigger_driveway_desk_flash
- delay:
minutes: 1
- service: automation.turn_on
entity_id: automation.ss_trigger_driveway_desk_flash

Now you're probably wondering why I turn the automation off for a minute and then back on again... I have the driveway_motion script set up so it first captures the current state of the LED strips to a scene (I have a few different colour modes) flashes them red to indicate motion detected and then returns to it's previous state. So for example if I had them set to blue before motion is detected, they would flash red and then return to blue.

What I found is that if motion was detected a 2nd time when the red flashes were happening, the script would capture the red flashes as the previous state and keep them turned on. Having the automation turn off for a minute gives the LEDs an opportunity to return to their previous state.

If you're interested - script.drive_motion is....

driveway_motion:
sequence:
- service: scene.create
data_template:
scene_id: before
snapshot_entities:
- light.wled_desk
- service: light.turn_on
data:
entity_id: light.wled_desk
transition: 3
brightness: 127
rgb_color: [255, 0, 0]
effect: Solid ### just realise they don't actually flash here they just turn red, ha!
- delay:
seconds: 10
- service: scene.turn_on
data:
entity_id: scene.before

N.B you can also run multiple curl commands in one apple script - mine actually fires "driveway_ss_trigger_1" and "driveway_ss_trigger". One is a telegram notification with a capture screenshot, and the other is the desk flashing. I have them as two separate automations so I can turn them on and off independently.

Now this is all probably a lot easier with NodeRED.... but I've always used yaml and it works for me.

BoxGrove,

Been a terrible week. I've run into significant problems with my HA instance. AT&T had to replace my modem and the new BGW210-700 modem blocks port 443 and screwed up my access, so I spent most of the time troubleshooting the fiasco they created, but now I'm finally good...

Ok, so I'm working through your scripts (thank you btw) and not following the creation of the entities. I'm still working through this

Oh, and Ben you're AWESOME as well for the ability to push the webhook scripting and improved AI on motion detection. Makes for a very nice integration now. Much happier and full of ideas on how to better automate my home. Thanks

Boxgrove & Ben,

So I'm noticing that the curl commands aren't executing all the time. I'll test for example the command...

do shell script "curl -d \"\" \"http://192.168.1.79:8123/api/webhook/driveway_ss_trigger_1\""

which executes an automation in Home Asst and runs fine. I execute it again (from the script editor play button) and it doesn't work. I don't know how to verify that curl commands are going out and being received, but I'm trying to learn. Let me know if you guys can think of something off the top of your head for me to try.

I got so excited from the initial setup from Boxgrove, that I started adding some more Shelly 1 switches to control more lights to tie to Motion from the cameras. I started noticing that one of my automations related to the garage cameras were really slow. I could walk 20' before the routine would run. That's when I started testing and finding that some routines aren't running all the time.

Let me know if you have some ideas where/how to test this? Thanks again

Just a side note, you may not need to escape all the quotes from your example. Mine looks like this in an Apple Script and it works ok (those are two single quotes after -d):

do shell script "curl -d '' http://192.168.1.10:8123/api/webhook/kiosk_doorcam_motion"

So I went into Terminal on Mac and entered the curl command, and it executed. Went back into File Editor on HA and found this line in the debug for the appropriate time stamp...

2020-07-15 00:46:20 DEBUG (MainThread) [homeassistant.components.webhook] Handling webhook POST payload for driveway_ss_trigger_1

So if I'm thinking about this correctly, the curl command is getting to HA. HA is recognizing the webhook, but it is not executing. I can manually execute the automation in the Configuration and it works. here is the excerpt from the automations.yaml file...
```
- id: '1593209500332'
alias: ss_driveway_motion
description: Activate lights on SS driveway camera motion
trigger:
- platform: webhook
webhook_id: driveway_ss_trigger_1
condition:
- after: sunset
before: sunrise
condition: sun
- condition: state
entity_id: switch.shelly_shsw_1_115f00
state: 'off'
action:
- device_id: e6629ba0af684d6890b50f41079b5a4d
domain: switch
entity_id: switch.shelly_shsw_1_115f00
type: turn_on
- delay: 00:10:00
- device_id: e6629ba0af684d6890b50f41079b5a4d
domain: switch
entity_id: switch.shelly_shsw_1_115f00
type: turn_off
```

What am I missing?

Ok, another update. The activity is working (Yeah Baby!!!!), but I'm noticing that the amount of time to recognize the motion and then activate the lights is longer than I hoped. I observed that I walked almost 25 feet on my driveway before the light switched on. I thought it was still HA, but I confirmed that the signaling to the Shelly 1 switch is staying local and really quick. When I execute the Apple Script manually on the Mac Pro that acts as the server for SS, it's really fast. So the time from the script activating to the lights turning on is less than 1-2 seconds

So it's the time from when the motion detection begins, the AI determines it's a person or vehicle (which works great and cuts down false positives enough to make this viable), and sends the Action script. For recording video, it works great. So without sounding ungrateful, how can I improve the timing on this for the switch relay? I like that the lights would not be set off by every insect that flies in front of the camera, but I also don't want to walk completely through the detection area before the lights turn on. Everything is currently set with defaults that Ben wrote.

Thoughts?