I have this config
sensor:
- platform: synologydsm
host: 192.168.178.130
username: !secret syn_user
password: !secret syn_pass
monitored_conditions:
- cpu_total_load
- memory_real_usage
which leads to the following 2 errors
This worked fine before 0.86. I see no error messages in the log pertaining to this component. Please advise, thanks.
Can you please format your code properly - take a look at the blue box at the top of the page for how to do this.
Well, apart from the fact that HA won’t properly work a lot of the time, this forum software apparently has its issues too. No matter how many times I hit the format button, this is the best I get - and I also miss documentation on how to manually format my code properly. Which is also right in tune with the rest of the documentation. Cheers.
sensor:
- platform: synologydsm
host: 192.168.178.130
username: !secret syn_user
password: !secret syn_pass
monitored_conditions:
- cpu_total_load
- memory_real_usage
Not that difficult
Great. Could you document what you did? So, Googlers and me alike can _learn from it?
I was saying its not that difficult to format code to its easy to read, it looks like your formatting is off
sensor:
- platform: synologydsm
host: 192.168.178.130
username: !secret syn_user
password: !secret syn_pass
monitored_conditions:
- cpu_total_load
- memory_real_usage
- network_upCopied & pasted the config straight from the documentation and it works fine for me on V0.80.3 as well as V0.88.0:
I am all of a sudden getting this error
Error doing job: Future exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/synologydsm/sensor.py", line 107, in run_setup
for volume in config.get(CONF_VOLUMES, api.storage.volumes):
TypeError: 'NoneType' object is not iterable
Anyone else having issues?
I get this issue sometimes, but other times it works, it’s very inconsistent.
Yes, I am getting the error as well.
It actually shows up as WARNING in my HA log, but I’ve set the logger now to hide warnings, but setting the default to ERROR.
However these WARNING message are still appearing in my log, has anyone manage to hide these warnings?
It still works for me even tho I get these warnings are it’s taking over 10 seconds
Hi,
I also got problems with DSM integration…was working fine before but now stopped i deleted integration I tried to added again but no luck… it seems that it can not find or connect to dsm… user should work i tested it on dsm.
the plex that is running on dsm connected great thru plex integration so IP should be ok.
Same problem here. It was working fine before and now the only that I see in the logs is:
[homeassistant.components.synology_dsm.config_flow] {'api': 'SYNO.DSM.Info', 'code': 119, 'reason': 'Unknown', 'details': None}
Same on my side too.
All entities are now “unavailable”
I uninstall the integration and try to add it again ==> Impossible also, the system return “Unexpected Error”
All the fields are filled properly
User & Password are OK (when connecting directly to DSM)
IP address is pingable
Port is 5001 (SSL) (this is also how I access my DSM)
Same error here
Still not possible to add it. Is someone has an idea how to solves this ?
i have all the time this Error:
WARNING (MainThread) [homeassistant.components.synology_dsm] async_update - connection error during update, fallback by reloading the entry
Has anyone come up with a solution to Synology being unavailable and then not being able to reinstall the integration. I keep getting “unexpected error” when I try to set it up.
