SynoAI aims to solve this problem by side-stepping the Synology notifications entirely by allowing other notification systems to be used. Due to the delay between fetching the snapshot, processing the image using the AI and requesting the alert, it means that the image attached to the Synology notification is sometimes 5-10 seconds after the motion alert was originally triggered. While sssAI is a great solution, it is hamstrung by the Synology notification system to send motion alerts.

The aim of the solution is to reduce the noise generated by Synology Surveillance Station's motion detection by routing all motion events via a Deepstack docker image to look for particular objects, e.g. SynoAI Buy Me A Coffee! ☕ Versioning Table of Contents Features Config General Config Camera Config Camera API Development Config Supported AIs Deepstack Notifications Pushbullet Webhook Configuration Example POST data Telegram Email Gmail HomeAssistant Pushover Discord MQTT Configuration Example payload data Caveats Configuration 1) Configure Deepstack 2) Configure SynoAI 3) Create Action Rules Summary Updating Docker Images Docker Configuration Docker-Compose Example appsettings.json Problems/Debugging Logging Trouble Shooting Not receiving notifications when one should have been detected Image files are saved with a date/time different to the current local Snaphots taken in quick succession always return the same image Snapshots are slow to fetch from SSS Camera names with spaces in cause the error 'The camera with the name 'My Camera' was not found.' Logs show timeout exceptions and SynoAI fails to initialise or the logs show crashes when passing snapshot requests to the AI 'Failed due to Synology API error code X' Common Synology Error Codes DeepStack FAQ How do you set up a notification for each camera? README.mdĪ Synology Surveillance Station notification system utilising DeepStack AI, inspired by Christopher Adams' sssAI implementation.

Synology surveillance station patcher