People have reported that if you have 'ghost z-wave devices', devices that you have forced removed that the hub still thinks exist, could cause issues. This is what @vjv had I believe.
I did mention in a post that it would be nice if someone has fixed this put an idiots guide together so that we can check for them and remove them.
It hasn't appeared yet from anyone so perhaps it hasn't been done by anyone yet.
HE staff doesn’t encourage just pulling plug to restart and suggest using then restart option in UI if possible. Otherwise power loss may cause database to corrupt. If possible VPN into network to restart.
Would be nice if RM could restart hub on a periodic basis.
Except that the administrative portal is unavailable when the hub has frozen or crashed. No choice here. I'm looking for a way to mitigate the fact that the hub is non-responsive, or I would otherwise employ the reboot option in the portal.
If we're looking for a way to automate the periodic reboot, we have bigger problems than missing functionality.
I totally agree with you, but needed that ability whilst working away too. For the sake of a few quid, kept my WAF where I need it to be. I went for one which would use the Magic Home app, as I already have one of their LED drivers. It’s a “break in case of emergency” approach.
Agree but there's not much choice when you have a frozen hub in the morning and have to leave the house. I have a Zigbee switch from Wink2 as a remote power cycle.