jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-11 19:36:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update category

Browse Source
This commit is contained in:
Fabian Affolter 2017-08-05 17:03:07 +02:00
parent 69f06bc8e2
commit 6d88986c55
No known key found for this signature in database
GPG Key ID: DDF3D6F44AAB1336
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
source/_components/sensor.synologydsm.markdown
View File

@ -8,9 +8,9 @@ comments: false
sharing: true
footer: true
logo: synology.png
ha_category: Sensor
ha_category: System Monitor
ha_release: 0.32
ha_iot_class: depends
ha_iot_class: "Local Polling"
---
@ -31,14 +31,6 @@ sensor:
- network_up
```
<p class='note'>
After booting Home Assistant it can take up to 15 minutes for the sensors to show up. This is due to the fact that sensors are created after Home Assistant has fully been initialized.
</p>
<p class='note warning'>
This sensor will wake up your Synology NAS if it's in hibernation mode.
</p>
Configuration variables:
- **host** (*Required*): The IP address of the Synology NAS to monitor
@ -79,7 +71,15 @@ Configuration variables:
- **volume_disk_temp_avg**: Displays the average temperature of all disks in the volume (creates a new entry for each volume).
- **volume_disk_temp_max**: Displays the maximum temperature of all disks in the volume (creates a new entry for each volume).
Separate User Configuration:
<p class='note'>
After booting Home Assistant it can take up to 15 minutes for the sensors to show up. This is due to the fact that sensors are created after Home Assistant has fully been initialized.
</p>
<p class='note warning'>
This sensor will wake up your Synology NAS if it's in hibernation mode.
</p>
## {% linkable_title Separate User Configuration %}
Due to the nature of the Synology DSM API it is required to grant the user admin rights. This is related to the fact that utilization information is stored in the core module.