Problem is solved!
For some reason the ip adress of my Homey was set on the blacklist on my NAS.
Removed the ip adress from the blacklist and added it to the Whitelist and all is working again.
Can’t check the script now because my NAS is set to off (at work right now). So on/off setting is working again.
Because of many DOS attacks lately I have set it to go to the blacklist after one wrong password. Must be related to this but can’t happen no more, I think/hope.
I still notice that the CPU usage (14 days old value) and disk usage (7 months old value) don’t get updated. When I check my NAS, the disk usage has a different value that the app is showing. Any idea?
I created a flow to turn off my NAS in the night, and back on in the morning. The off-flow works without any issues, but not the on-flow. And I cannot turn it on using the button in the app neither.
It reports I have to wait up to 10 minutes, before the NAS is shown as ON. But before it gets to that, it shows as OFF again, and nothing else happens.
@martijnpoppen , may I ask, is the REBOOT button really REBOOT or it’s Shutdown ? I realized already twice that I had to send “Wake-up” (via ON - works fine) call to my Synology to get again operational… I think in both cases I was waiting like 5 or 10 min. Would debug logs make any sense next time ? Not sure…
Thank you Martijn, it’s weird, because in log under given Homey user, I see it initiated shutdown… ?
Now I tested again - I wait 5min, then I had to do WOL.
Hi @martijnpoppen what I’ve noticed for a while when I turn my nas on or off is the double notifications and illogical notifications.
When I turn it on, I see that the nas is turned on and turned off again a minute later, after which it is turned on again.
Same thing when powering off but off on off.
In practice this is not the case at all so the question is why does the log see it differently?
Hmm only thing what i can think of. Homey can’t really see if the NAS is booting or not. There’s a timer which checks every now and then if it is up again.
I think that’s why it flashes. For Reboot I have some logic in place, but for turning on not really.