Synology DSM Integration - Surveillance Station Camera do not show anymore

Configuration
1

Hi all,
running HA 2026.3.2, Synology DSM 7.3.2-86009 Update 1 and Surveillance station 9.2.5-11979.

I am not sure since I have this issue, but Synology Integration work fine for Disk and Station, but not for camera.

I tried to delete the integration and recreate but camera are not created anymore and in the logs I have this error:

Logger: homeassistant.components.synology_dsm.common
Source: components/synology_dsm/common.py:155
integration: Synology DSM ([documentation](https://www.home-assistant.io/integrations/synology_dsm), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+synology_dsm%22))
First occurred: 17:32:58 (7 occurrences)
Last logged: 18:14:38

Surveillance Station found, but disabled due to missing user permissions

I use admin user for the integration and admin have full control on DSM and Surveillance station. I also tried to create a specific user with all permission, but with no luck.

Any help would be appreciated.

Marco

2

Hi Marco, did you solved your issue ? I’m the same issue and behavior since 15 days.

3

Hi,
No issue is not solved even in 2026.4
For now I use ONVIF integration to show camera stream into Dashboard and a WebService call to Synology DSM to enable/disable home mode.

I hope this issue will be fixed in future release of DSM/Home Assistant

4

I have the same issue while it worked before.

5

Are you running CMS (to combine cameras across multiple NAS)? I had a similar problem (with DSM 6.4) - a permissions issue arose after a CMS update. 2 cameras, on a 2nd NAS, were no longer available in HA but also not available in the DS Cam app. My fix was to escalate permissions in CMS (for the HA user) to administrator.

6

I already tried giving the ha user administrator rights. When I use the ha account to login to DSM interactively I can just start surveillance station and view and edit all cameras. But when ha tries to connect, it gives the mentioned error in the log.