SynologyDSM Sensor not in Developer Tools > States

Configuration
1

I have installed the new SynologyDSM Sensor but I cannot see any related entries under Developer Tools > States. I am using DSM 5.0. This is what I have in my configuration file:

- platform: synologydsm
  host: 192.168.1.123
  port: 123
  username: !secret synology_username
  password: !secret synology_password
  monitored_conditions:
    - cpu_total_load
    - memory_real_usage
    - network_up
2

I have the same problem, and DSM version 5.2.

Found this error in the log:

16-11-06 12:47:24 homeassistant.core: BusHandler:Exception doing job
Traceback (most recent call last):
  File "/usr/local/lib/python3.4/dist-packages/homeassistant/core.py", line 1210, in job_handler
    func(*args)
  File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/sensor/synologydsm.py", line 112, in run_setup
    for volume in volumes:
TypeError: 'NoneType' object is not iterable
3

that’s the same error i got.

4

I am seeing the same error.

16-11-09 18:51:05 ERROR (ThreadPool Worker 5) [homeassistant.core] BusHandler:Exception doing job
Traceback (most recent call last):
File “/usr/src/app/homeassistant/core.py”, line 1210, in job_handler
func(*args)
File “/usr/src/app/homeassistant/components/sensor/synologydsm.py”, line 112, in run_setup
for volume in volumes:
TypeError: ‘NoneType’ object is not iterable

I have not specified a port

5

My Synology Sensor is working. I didn’t specify a port and the username I used has admin rights. Not sure if this makes a difference but I’m using DSM 6.0.

6

I’m having the same issue.

I tested it with my NAS and Router (Have a Synology too) and I can’t make it work.

Tested with and without port, admin and no admin user … little out of ideas right now but very interested on this one.

anyone with ideas to test?

thanks!

7

Anyone else having this working.

Can you share your config (not very complicated conf though, but better double-checking).

Thanks!!!

8

Do you have multiple volumes on your Synology?

9

I’m only using one volume but it should see each sensor for each volume\disk.

10

I am wondering if my error about not seeing ‘volume in volumes’ is related to me having multiple volumes on my synology setup

11

I have multiple Volumes here … is that the reason for the error ??

12

Same error for me… :frowning2:
16-11-09 18:51:05 ERROR (ThreadPool Worker 5) [homeassistant.core] BusHandler:Exception doing job
Traceback (most recent call last):
File “/usr/src/app/homeassistant/core.py”, line 1210, in job_handler
func(*args)
File “/usr/src/app/homeassistant/components/sensor/synologydsm.py”, line 112, in run_setup
for volume in volumes:
TypeError: ‘NoneType’ object is not iterable

13

Make sure that you have the right port setup as default it will be 5000 as port as per synology default config.

I had the same problem until I added the right port to the yaml and it all started working as I changed my default port.

14

I have sensor working but cannot work out how to have 2 NAS’s monitored. Basically when it creates the sensors, there is nothing in the sensor name that differentiates 1 NAS to another. For example I have sensor.volume_used_volume_1. If I try and setup another NAS it will just be the same. Am I doing something wrong? Can anyone shed some light on this because it almost seems like it works with 1 NAS only.

15

Upgraded to 0.34.3 from 0.34.0 and Synology sensors are gone.

Actually just saw log.

16-12-06 22:40:30 homeassistant.core: Error doing job: Future exception was never retrieved
Traceback (most recent call last):
File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/sensor/synologydsm.py", line 110, in run_setup
volumes = api.storage().volumes
TypeError: 'SynoStorage' object is not callable

Yeah as I said, it’s broken.

16

Yes after the update to 34.2 it doesn’t work anymore

17

Yep, same here on latest version 0.34.4.
Just wanted to share that I have the exact same error as KmanOz.

Seems to be a common problem, so let’s hope they get it fixed.

18

any update on this? it appears to still be an issue in 0.36.1

19

Working here… make sure you configured the right port on in HASS as if you changed your default port on the synology you need to configure that in HASS

  - platform: synologydsm
    host: 192.168.2.20
    port: 8080
    username: ......
    password: .....
    monitored_conditions:
      - volume_percentage_used
      - volume_status
      - disk_smart_status
      - disk_status
      - cpu_total_load
      - memory_real_usage
      - network_up
1 Like
20

so apparently I need to pay attention the port (3000 vs 3001) . oops.

thanks