Send Synology Surveillance motion events to HA switch

xbmcnut · September 28, 2018, 4:04am

Are you sending a POST request to a HA service? Not sure what the ‘events’ is you’re sending to. Try sending an API request to a service like I have /api/services/script/xxxx

w1ll1am23 · September 28, 2018, 12:04pm

Not sure what I did wrong but I was able to get it working by posting to the events API.

Thanks.

J_IO_B · November 22, 2018, 12:59pm

Interested to know if this method is still working for you or if you now use an alternative?

xbmcnut · November 24, 2018, 1:09am

Still working for me by firing a script using the following:
http://ha_ip_address:8123/api/services/script/trigger_ss_entrance_boolean

xbmcnut · November 30, 2018, 9:34pm

This has now broken in 0.83.x. I’m assuming I’ll now need to use a webhooks link to my script. Anyone help with how to do that?

xbmcnut · November 30, 2018, 10:50pm

Wow. It is actually super simple now. Just create an automation that defines a webhook ID thus:

automation:
  - alias: 'Webhook endpoint to entry motion' ## http://hassio_ip:8123/api/webhook/motion_entrance ##
    hide_entity: true
    trigger:
      - platform: webhook
        webhook_id: motion_entrance
    action:
      - service: script.turn_on
        entity_id: script.trigger_ss_entrance_boolean
      - service: notify.hass_synochat
        data:
          message: "Entry motion webhook fired"

Mine is then calling this script which in turn fires an input boolean for 5s. I also have a notifier in my automation purely for testing purposes.

script:
  trigger_ss_entrance_boolean:
    alias: Trigger input boolean for motion from API
    sequence:
      - service: input_boolean.turn_on
        entity_id: input_boolean.motion_entrance
      - delay: 00:00:05
      - service: input_boolean.turn_off
        entity_id: input_boolean.motion_entrance

xbmcnut · November 30, 2018, 11:16pm

Buggar. Seems all is not well in Synology. Although I can fire that webhook event using Postman or the Android HTTP app using a POST request, it does not work as a SS action rule. Back to the drawing board. Looks like I’m going to have to break out Wireshark again.

J_IO_B · December 1, 2018, 5:56am

This is as far as I got, Postman works great for both the webhook and the event trigger. Unfourtuently SS doesn’t and I struggled to find any further information on what SS does with the action URL. I’ll keep my fingers crossed you can sniff something with Wireshark.

WhichWayWazzit · December 2, 2018, 6:10pm

I’ve had the same issue with webhooks not working from SS. I came to find out that SS only sends a GET request and does not set the content-type in header appropriately (HA expect application/json). As such, I created a Node-red flow to proxy the request to HA in the proper format.

So route the information takes is:
SS via the motion action sends HTTP GET request towards node-red listening on url. I used /synology_flows/:webhook, eg http://node.red.host/synology_flows/WEBHOOKID-devicename

Node red maps the provided webhook parameter towards the new POST request towards HASS and sets the content-type in header and also provides an empty (but defined) payload, eg, “{}”

This gets the motion events from synology into HA triggers, where you can do whatever you would want to set input_boolean, etc to act as a switch. I also have all my webhook IDs in this case start with a randomly generated string but also end with a “-devicename” so it can be referenced in automations.

- id: security_motion_events
  alias: Surveillance Motion event
  trigger:
    - platform: webhook
      webhook_id: !secret ss_camera_front_door_motion
    - platform: webhook
      webhook_id: !secret ss_camera_back_door_motion
    - platform: webhook
      webhook_id: !secret ss_camera_driveway_motion
    - platform: webhook
      webhook_id: !secret ss_camera_house_front_motion

  action:
  - service: notify.hass_notify_group
  data_template: >
    message: "Device {{ trigger.webhook_id.split('-')[1] }} just registered motion"

J_IO_B · December 2, 2018, 6:32pm

Amazing! Don’t suppose you’d mind sharing your Node-Red flow? What kind of latency do you get from this?

WhichWayWazzit · December 2, 2018, 6:46pm

It’s pretty much instant as far as I can tell. Obviously limited by how quickly your camera signals the event and how loaded your system is, etc but it comes through very fast in my testing.

Here’s my node flow: click

J_IO_B · December 2, 2018, 7:16pm

Thanks! You’ve just saved me heaps of headaches!

outlander4000 · December 3, 2018, 7:59pm

would you mind to explain in more details what a node.red is? Is this a service I need to install on the Synology?
How does it need to be configured?
This solution currently is not within my skills.
thx in advance

ErMejoo · December 16, 2018, 3:26am

Hi All! +1 for this - not sure what a node.red is…can you please expand on this?

Thanks a lot

w1ll1am23 · December 16, 2018, 3:28am

I don’t use it, but Home Assistant Community Add-on: Node-RED all the details are here.

xbmcnut · February 12, 2019, 12:16am

Pleased to advise that the latest update of Surveillance Station (8.2.3-5828) fixes the Action Rules ability to send events to a webhoook URL in HA!! How to do that is here Send Synology Surveillance motion events to HA switch

ashscott · July 7, 2019, 11:45am

Is this still working for you? It’s recently broken for me.

I’ve done my best to document my findings here.

pergola.fabio · October 20, 2019, 6:44pm

guys interesting thread, but i am also unable to fire a webhook from SS
as some screenshots above, where you create the action, i dont have “external device” i can choose only webhook
so i enter my nabucasa url there
but tried with post/get , nothing works, always test failed
if i test from SSH and the CURL - X POST https://xxx , then it works…

any idea?

xbmcnut · October 21, 2019, 12:59am

Webhook is the correct action. ‘External Device’ is if you want to receive a request from HA to do something on your SS. I use this for PTZ control.

For Webhooks, you need to create a receiving automation inside HA though otherwise the request goes nowhere. Below is my SS action and part of the HA automation that receives the request. Use the LAN IP of your HA instance if both devices are on the same network.

  - alias: 'Webhook endpoint to entry motion' ## http://internal_ip-address-of-HA:8123/api/webhook/motion_entrance ##
    hide_entity: true
    trigger:
      - platform: webhook
        webhook_id: motion_entrance ## this is the only place you create the webhook ID ##
    action:
      - service: camera.snapshot
        data:
            entity_id: camera.proxy_entry
            filename: '/config/www/images/entry_cropped.jpg'
      - service: script.turn_on
        entity_id: script.trigger_ss_entrance_boolean

You can use the SS ‘Test Send’ button to see if it’s working.

pergola.fabio · October 21, 2019, 6:31am

Strange , I have the exact same thing… It also created a webhook url for nabucasa … That one is working when I do it with curl, but not with ss…

You are using the internal IP, that’s my goal also, and not the nabucasa one…

Strange that it works for you without authentication in that ss screenshot??? Or how did you configure that local ip addresses don’t need authentication?