Send Synology Surveillance motion events to HA switch

[Aaron_Toulmin]

I’ve been trying to get this working, where do i find the correct “ID:” to enter? Also in the automations.yaml should the first line be

-alias: 'Porch Camera Motion" 192.168.0.133

As an example?

[Aaron_Toulmin]

Disregard, i got it working. Thanks for you guys working this out. I have it working well with my Synology Surveillance Station and reolink cameras. Well Done.

[xbmcnut]

Glad you got it working.

[mdg4486]

@FlyersPh9 I am getting stuck on the “edited” version of the blueprint. I can change the value but but then it’s showing I have “unknown tag !<!input>” errors throughout the blueprint. Did you change any thing else on this blueprint?

Anyway someone can share the entire .yaml for this?

[xbmcnut]

Did you download the original version of the blueprint, create a renamed copy and edit that one line?

[mdg4486]

I think my issue may have been the auth_providers line where I placed my Synology as a trusted user. I’ve never set up auth_providers before this and I believe that line ended up locking me out of my Home Assistant when I rebooted.

[mdg4486]

@xbmcnut @FlyersPh9 is there a way to make these notifications clickable to where they take you directly to a Lovelace Camera dashboard?

[mdg4486]

Nevermind I was able to figure it out! Thanks for everyone’s help on this!

[pafftis (Maxim)]

please help me!

test send - test no connect

[xbmcnut]

As it’s an internal IP, try using HTTP?

[RedWheiler]

Thank you all for getting me in the right direction.

I’ve one weird problem…

I’m sending snapshots from two of my Synology camera’s to HA when motion is detected, without any problem.

But from that moment on I can’t access my internal ha anymore at http://192.168.0.5:8123 from my PC.

I still can get in my instance with the app, but for sure I need to be able to use my PC…

I must say, I didn’t made a boolean. But I can’t see how this would change my problem.

Thanks in advance.

[xbmcnut]

Probably need a lot more info but have you tried from a mobile browser after the lock-out? Is it possible your PC’s IP address is being auto-blocked by HA?

[RedWheiler]

Thanks for pointing me in the right direction.

I could still login with my mobile brower on the same network. Also nothing about a blocked IP. But I had some error in my logfile (didn’t copy it…) that pointed me to: Authentication Providers - Home Assistant

I did some small edit in my config file:

# configuration.yaml
homeassistant:
  auth_providers:
      - type: trusted_networks
        trusted_networks:
          - 192.168.0.0/24
        allow_bypass_login: true
      - type: homeassistant

And this seems to work for me.

[Johanvh (Johan Van Hoorde)]

Hi, spend some time to copy/paste and setup this very useful feature, based on the ‘tutorial’ above (many thanks by the way) but so far I couldn’t succeed.

Here is my complete setup:

homeassistant:
  auth_providers:
    - type: trusted_networks
      trusted_networks:
        - 192.168.100.250 # Synology NAS

I made an input boolean in the GUI (Configuration - Helpers):

Automations.yaml:

- id: '125477Z527526275'
  alias: 'Beweging tuin via Synology NAS'
  trigger:
    - platform: webhook
      webhook_id: https://192.168.100.146:8123/api/webhook/beweging_tuin
  action:
    - service: input_boolean.turn_on
      entity_id: input_boolean.beweging_tuin
    - delay: 00:00:05
    - service: input_boolean.turn_off
      entity_id: input_boolean.beweging_tuin
  mode: single

This is my Synology Surveillance Station setup:

When I hit ‘Test Send’ I get the green confirmation and no error.
The HA log shows:

But unluckely the automation is never triggered by the webhook.
When I manually run the actions of the automation the input_boolean.beweging_tuin changes to on for 5 seconds so the automation and the input_boolean are working.
Can someone tell me why the automation is not triggered from the webhook?
Thanks in advance!!!

P.S.: I just noticed that after the change in configuraton.yaml I cannot use my HA application. I got an authentication error from my router. I removed the changes in configuration.yaml and my Synology NAS can still send a webhook without errors.
I don’t know if it makes sense to tell that my Synology NAS and HA are in the same local network. HA is using Let’s Encrypt for SSL.

[xbmcnut]

Try sending to http instead of https in your action. That’s what I have. You’re using an internal address and unless you’ve gone through the faff of adding local certs for SSL, you’re fine just using http.

[Johanvh (Johan Van Hoorde)]

Thanks to take the time to read my issue and to answer.
When I’m at home I also have to use https to access HA. If I use http it doesn’t work.
I’m not a specialist in this things.
This is my setup:

homeassistant:
  external_url: https://casaxxxx.duckdns.org
  internal_url: https://casaxxxx.duckdns.org

I tried to change the internal_url to http://192.168.100.146:8123 and restarted HA completely but always get an error.

Off cours for external access I’d like to have a secured connection but internally it’s not required.
Maybe this problem can also be sorted out…

[xbmcnut]

What happens if you do a test send to the external URL? You can also use Postman to do a test from your PC/Mac to make sure HA is responding to GET requests.

[Johanvh (Johan Van Hoorde)]

If I use the external URL and use my DuckDNS name, it works! So that’s nice but it also means without internet, it won’t work. I was heard that I need NGINX proxy manager if I want SSL security on external side and no security on internal side.

[xbmcnut]

Do you own a Synology NAS? A proxy is super easy with that. Or better still, support HA by moving to Nabu Casa and then you can have both. SSL outside and non-SSL internally without a proxy. That’s what I have although I did use a reverse proxy on my Synology in the early days.

[overflywingo]

Hello
It is super easy to send a Synology Surveillance motion event via a Homebridge plugin ( Homebridge Sss Platform) and “Accessory Homekit” HA intergration.