Synology Surveillance Station Smart-Home-Integration, kostenlos und Open Source
Synology Surveillance Station, locally: camera images, motion, cameras on/off, Home Mode.
Veröffentlicht von LM1LC3N7
- Geräte
- Version 0.1.1
- Erfordert Gladys >=5.1.0
- ★ 0
Die Dokumentation dieser Integration wird von ihrem Autor geschrieben und ist bisher nur auf Englisch verfügbar.
Your Synology Surveillance Station cameras in Gladys, locally, through the Web API of DSM (no cloud, no QuickConnect):
- each camera becomes a Gladys camera: its image on the dashboard, a fresh snapshot in the live view;
- its enabled state in Surveillance Station (the camera on/off control of Gladys);
- a motion sensor per camera, and the Motion detected scene trigger (motion detection or video analytics events);
- the Home Mode of Surveillance Station: read, switched, and the Home Mode changed scene trigger.
Never tested on a real NAS. This first version was written from the Surveillance Station Web API guide and from py-synologydsm-api, and tested against a fake NAS only. Please report what works and what does not on the Gladys forum.
Unofficial integration, not affiliated with Synology.
Before you start: a dedicated account
- In DSM, Control Panel → User & Group, create a user
gladyswith a strong password. It needs no shared folder and no other application. - In Surveillance Station → Privilege settings (Privilege profiles),
give it a profile:
- read only (spectator) is enough for the images, the motion sensors and reading Home Mode;
- to enable / disable cameras or switch Home Mode from Gladys, the profile must allow it (manager, or a custom profile with these rights).
- 2-step verification: prefer an account without it (the account is used by a machine). If DSM enforces it for every account, see below.
Configuration
- NAS address:
https://192.168.1.10:5001. A bare address is read as https on port 5001. Avoidhttp://192.168.1.10:5000: the password and the session would cross your network in clear. - DSM user name / password: the dedicated account. The password is kept by Gladys in its database, never shown again, sent only to your NAS.
- 2-step verification code: only for an account with 2-step
verification. Type a fresh 6-digit code of your authenticator app and save
at once (a code lasts 30 s). Gladys then keeps the device token DSM gives
(in its
/datavolume) and never needs a code again. A code is sent only once; the field is masked like the password. - Accept the self-signed certificate of the NAS: off by default, the certificate must then come from a known authority (Let's Encrypt…). On: the certificate seen at the first connection is trusted and remembered; a different one later is refused (someone may be impersonating your NAS) until you press Trust the new certificate.
- Allow reducing the surveillance: off by default (see Commands).
- Motion events read: every 5 s to 1 min (10 s by default).
- Dashboard image refresh: none, or every 30 s to 10 min.
Then open the Discovery tab and create the cameras and the Surveillance Station device (Home Mode) you want.
Commands
- Enabling a camera and leaving Home Mode add surveillance: always possible.
- Disabling a camera and turning Home Mode on reduce the surveillance (fewer recordings, fewer alerts): Gladys refuses both unless you tick Allow reducing the surveillance. Keep it off if a scene or another user should not be able to blind your cameras.
- Commands run one at a time. Just before acting, Gladys reads the current state from the NAS: if it cannot (or the NAS does not say), nothing is sent; if the NAS is already in the asked state, nothing is sent either. When the NAS is too slow to answer within 3.5 s, nothing is sent and Gladys shows a failure (never an action after a failure was shown). If you untick Allow reducing the surveillance or change the configuration while a command waits, it is not sent.
- A failure says whether the command was not sent (it could not reach the NAS) or sent without confirmation (the state is then read again).
Motion
Surveillance Station does not push its events to Gladys: Gladys reads the
recent events at the chosen pace. A motion or video analytics event fires
Motion detected once (with the camera, its name and motion or
analytics) and sets the motion sensor of the camera; the sensor goes back
to "no motion" once the event is over.
In normal running, every new event fires, whatever the clocks say. Only the
reading that catches up (after a start of the integration, a reconnection to
Gladys or a NAS outage) is limited to the events that ended (or still run)
less than 2 minutes ago: the old events of an outage are marked as seen
without a burst of triggers. Gladys keeps in its /data volume the last
events it processed, so none fires twice after a restart. The 2 minutes are
measured in NAS time (Gladys reads the clock of the NAS in its answers), but
keep both clocks synchronized (NTP, in DSM: Control Panel → Regional
Options → Time) for this catch-up to be exact. Motion
detection must be enabled on the camera in Surveillance Station (event
detection settings).
Connection problems
- Wrong password, locked or expired account: Gladys does not try again by itself, because DSM blocks an address after a few failed logins (auto block). Fix the configuration and save it, or press Test the connection.
- NAS unreachable: retried after 30 s, then up to every 10 min; the cameras show as unreachable meanwhile.
- Lost session (DSM restarted, session expired): renewed once, never in a loop (at most one login every 30 s).
- NAS busy (HTTP 429): every request pauses for 1 minute to 6 hours, as long as the NAS asks (Retry-After), even across a restart; saving the configuration or pressing Test the connection lifts it. Server error (HTTP 5xx, DSM restarting or updating): retried like an unreachable NAS.
Limits
- One NAS per integration. Images are snapshots (no live video stream in Gladys); a snapshot larger than Gladys accepts (150 KB) is asked again in the "low bandwidth" profile, else it is not shown. The dashboard image aims at 60 KB and goes up to 150 KB for a camera whose snapshots never fit.
- The motion sensor and the trigger lag by up to the chosen pace.
- Only motion (event reason 2) and video analytics (7) events are motion; other recordings (continuous, manual, alarm input) are ignored. These reason codes are taken from the API guide and are not checked yet.
- Not tested with Surveillance Station on a Synology VisualStation, CMS recording servers or C2 Surveillance.
Konfigurationseinstellungen
Diese Einstellungen fragt Synology Surveillance Station in seinem Konfigurationsbildschirm in Gladys ab.
| Einstellung | Typ | Pflichtfeld | Beschreibung |
|---|---|---|---|
| How it works | section | Nein | Gladys talks to Surveillance Station on your Synology NAS, on your network, through the Web API of DSM. Each camera of Surveillance Station becomes a Gladys camera (Discovery tab) with its image, its enabled state and a motion sensor; the Home Mode of Surveillance Station becomes a switch. Create a DSM account dedicated to Gladys, without 2-step verification, with access to Surveillance Station only (see the documentation). Unofficial integration, not affiliated with Synology. |
| NAS address | string | Ja | The address of DSM on your network: https://<IP>:5001. A bare address is read as https on port 5001. Avoid http://<IP>:5000: the password and the session would cross your network in clear. |
| DSM user name | string | Ja | |
| DSM password | secret | Ja | Kept by Gladys in its database, never shown again, sent only to your NAS. |
| 2-step verification code | secret | Nein | Only if the account uses 2-step verification: a fresh 6-digit code of your authenticator app, saved at once. Gladys then keeps a device token and never asks again; the code is used once. |
| Accept the self-signed certificate of the NAS | boolean | Nein | Off: the certificate must come from a known authority. On: the certificate seen at the first connection is trusted and remembered; a different one later is refused until you press "Trust the new certificate". |
| Commands | section | Nein | Enabling a camera and leaving Home Mode are always possible from Gladys. Disabling a camera or turning Home Mode on reduces the surveillance (fewer recordings, fewer alerts): Gladys refuses both unless you allow them below. The account then needs a Surveillance Station privilege profile that can change cameras and Home Mode. |
| Allow reducing the surveillance (disable a camera, turn Home Mode on) | boolean | Nein | |
| Refresh | section | Nein | Surveillance Station does not push its events to Gladys: Gladys reads the recent events at the pace below (motion sensors and the "Motion detected" trigger), and the cameras and Home Mode every minute. |
| Motion events read | select | Ja | |
| Dashboard image refresh | select | Ja |
So installierst du Synology Surveillance Station in Gladys
- Öffne in Gladys Integrationen: Synology Surveillance Station erscheint im Katalog neben den nativen Integrationen, mit einem Community-Badge.
- Klicke auf Installieren. Gladys lädt das Docker-Image (
ghcr.io/lm1lc3n7/gladys-synology-surveillance:0.1.1) herunter, startet es in einer vom Kern isolierten Sandbox und erzeugt die Oberfläche der Integration (Geräte, Erkennung und Konfiguration). - Öffne den Bildschirm Konfiguration der Integration, fülle die Einstellungen aus und speichere.
- Du kannst sie auch direkt über die URL ihres Repositorys installieren: https://github.com/LM1LC3N7/gladys-synology-surveillance.
Synology Surveillance Station benötigt Gladys >=5.1.0. Der Katalog in Gladys wird stündlich aktualisiert, eine neue Version ist also spätestens eine Stunde nach ihrer Veröffentlichung verfügbar.
Du nutzt Gladys noch nicht? Es ist kostenlos und Open Source: folge der Installationsanleitung, um loszulegen.
Über externe Integrationen
Synology Surveillance Station ist eine externe Integration: eine Community-Integration, die als Docker-Container verpackt und auf GitHub veröffentlicht wird. Gladys installiert sie mit einem Klick und führt sie in einer vom Kern isolierten Sandbox aus. Sie wird von LM1LC3N7 veröffentlicht und gepflegt, nicht vom Gladys-Kernteam.
- Alle Integrationen durchsuchen, native und aus der Community
- Deine eigene externe Integration bauen und veröffentlichen
- Quellcode auf GitHub — Quelle dieser Dokumentation