snjoetw / py-synology Goto Github PK

The session parameter should be set to SurveillanceStation otherwise it will not be possible to authenticate with users only having access to SS. From docs:

User can assign “SurveillanceStation” to this parameter to login SurveilllanceStation. If not specified, default session is DSM, and SurveillanceStation is also available."

Hi,

I have come from the home-assistant community where we're having an issue around SIDs expiring and causing any instanced SurveillanceStation instances to become stale, requiring a full restart of the app.

What are your thoughts about your library silently re-establishing connections in cases like that? Meaning when you get an exception from Synology:
home-assistant/core#12037

Just recreate the API?

After looking at the most up-to-date doc on the API https://global.download.synology.com/download/Document/DeveloperGuide/Surveillance_Station_Web_API_v2.8.pdf

I think the Video and Audio stream that was being used was removed? Maybe it was replaced with something else, but I am not familiar with their API.

This is was is called out in the linked doc

Remove following methods
• SYNO.SurveillanceStation.AudioStream
◦ Stream
◦ Query
◦ Open
◦ Close
• SYNO.SurveillanceStation.VideoStream
◦ Stream
◦ Query
• SYNO.SurveillanceStation.Device
◦ ListVS
◦ ListCMS
◦ GetServiceSetting
• SYNO.SurveillanceStation.Streaming
◦ LiveStream
◦ EventStream
`

With the upcoming stream component (in 0.90) in Home Assistant that only supports RTSP streams without transcoding, I was wondering if we should consider providing an RTSP stream.

Surveillance Station supports RTSP stream and we should consider implementing that.

Looks like it might be possible to implement a switch for "home mode" in surveillance station. This would facilitate more complex operations to turn on/off the camera system based on home assistants automation. See:
https://community.home-assistant.io/t/synology-surveillance-station-ip-camera/3552/98