Hi,
I am using the Synology DSM Sensor component to grab stats from three Synology NAS devices on my home network.
I’m currently running HA v 0.63.1 (the latest revision at the time of this post).
Unfortunately, the details returned for two of the NAS devices are transposed. I’ve checked the configurations multiple times and compared the returned stats in HA vs those reported in the NAS DSM UI, and they’re definitely transposed.
Here’s a copy of the relevant section from my sensors.yaml file:
#### Synology NAS Devices
- platform: synologydsm
host: 192.168.0.250
name: 250 Synology DS214+
port: 5000
username: USERNAME
password: !secret PASSWORD
monitored_conditions:
- cpu_total_load
- memory_real_usage
- volume_size_total
- volume_size_used
- volume_percentage_used
- network_up
- network_down
- volume_disk_temp_avg
- platform: synologydsm
host: 192.168.0.251
name: 251 Synology DS212J
port: 5000
username: USERNAME
password: !secret PASSWORD
monitored_conditions:
- cpu_total_load
- memory_real_usage
- volume_size_total
- volume_size_used
- volume_percentage_used
- network_up
- network_down
- volume_disk_temp_avg
- platform: synologydsm
host: 192.168.0.252
name: 252 Synology DS214+
port: 5000
username: USERNAME
password: !secret PASSWORD
monitored_conditions:
- cpu_total_load
- memory_real_usage
- volume_size_total
- volume_size_used
- volume_percentage_used
- network_up
- network_down
- volume_disk_temp_avg
…and the relevant section from my groups.yaml file:
#### Synology NAS Devices
synologyNAS_250:
name: 250 Synology DS214+
entities:
- sensor.total_size_volume_1
- sensor.used_space_volume_1
- sensor.volume_used_volume_1
- sensor.network_up
- sensor.network_down
- sensor.cpu_load_total
- sensor.memory_usage_real
- sensor.average_disk_temp_volume_1
synologyNAS_251:
name: 251 Synology DS212J
entities:
- sensor.total_size_volume_1_2
- sensor.used_space_volume_1_2
- sensor.volume_used_volume_1_2
- sensor.network_up_2
- sensor.network_down_2
- sensor.cpu_load_total_2
- sensor.memory_usage_real_2
- sensor.average_disk_temp_volume_1_2
synologyNAS_252:
name: 252 Work NAS DS214+
entities:
- sensor.total_size_volume_1_3
- sensor.used_space_volume_1_3
- sensor.volume_used_volume_1_3
- sensor.network_up_3
- sensor.network_down_3
- sensor.cpu_load_total_3
- sensor.memory_usage_real_3
- sensor.average_disk_temp_volume_1_3
…and the relevant section from my customize.yaml file:
#### Synology NAS - 250
sensor.average_disk_temp_volume_1:
friendly_name: Disk Temp
icon: mdi:thermometer-lines
sensor.cpu_load_total:
friendly_name: CPU Load
icon: mdi:chip
sensor.memory_usage_real:
friendly_name: Memory Usage
icon: mdi:memory
sensor.total_size_volume_1:
friendly_name: Total Size
icon: mdi:harddisk
sensor.used_space_volume_1:
friendly_name: Used Space
icon: mdi:chart-pie
sensor.volume_used_volume_1:
friendly_name: Volume Used
icon: mdi:chart-pie
#### Synology NAS - 251
sensor.average_disk_temp_volume_1_2:
friendly_name: Disk Temp
icon: mdi:thermometer-lines
sensor.cpu_load_total_2:
friendly_name: CPU Load
icon: mdi:chip
sensor.memory_usage_real_2:
friendly_name: Memory Usage
icon: mdi:memory
sensor.total_size_volume_1_2:
friendly_name: Total Size
icon: mdi:harddisk
sensor.used_space_volume_1_2:
friendly_name: Used Space
icon: mdi:chart-pie
sensor.volume_used_volume_1_2:
friendly_name: Volume Used
icon: mdi:chart-pie
#### Synology NAS - 252
sensor.average_disk_temp_volume_1_3:
friendly_name: Disk Temp
icon: mdi:thermometer-lines
sensor.cpu_load_total_3:
friendly_name: CPU Load
icon: mdi:chip
sensor.memory_usage_real_3:
friendly_name: Memory Usage
icon: mdi:memory
sensor.total_size_volume_1_3:
friendly_name: Total Size
icon: mdi:harddisk
sensor.used_space_volume_1_3:
friendly_name: Used Space
icon: mdi:chart-pie
sensor.volume_used_volume_1_3:
friendly_name: Volume Used
icon: mdi:chart-pie
and these are grabs from the HA UI:
It’s the stats against the second and third NAS devices (192…251 & 192…252) that get transposed.
Has anyone else experienced this, or does anyone have any helpful suggestions, please?
Many thanks,
Colin