You can trigger a shut down from an endpoint, I think the Hub Info Driver v3 exposes it as a command you can call from RM. But you would need a way to power cycle it. If you had a Wifi plug that could integrate into something external like Node-Red, you could start a flow on NR with a delay, that once time has been given for the shut down, power cycles the plug, thus rebooting the hub.
1 Like
It's not a cumulative event that leads to data corruption, is cutting the power at inopportune time that does it, so every time you cut the power is like playing the lottery. Would that be the event that breaks the camel's back?
That's what I was (poorly) trying to say - over time I will "win" that lottery 
It's really a shame because my z-wave mesh has never worked as flawlessly and quickly as it does lately (other than this new problem). I have scenes that run at sunset / sunrise which command dozens of devices. With a little bit of metering, these work very well. You'd think the radio crash would be more likely to happen during one of these events due to all of the extra traffic, but that hasn't been the case in any of the crashes yet. Seems to happen a few hours after the nightly reboot (which I have disabled). Maybe I'll get lucky and this will have fixed the current issue. I will try and report back once I know.
Well, then start by checking those 3 devices reporting 9.6kbps. One is a repeater, but misbehaving sensors can choke the radio too. Normally a Z-Wave Plus device that hits 9.6kbps is indicative of a device with problems. Maybe the solution is far easier than rebuilding everything.
Two of those are sensors yes - not sure why they are misbehaving - they are near to the hub. I will power cycle them. The third device is outside and at the very edge of the mesh. Somehow it works well despite the poor signal. hmmm you do have me thinking though.
Proximity to the hub is irrelevant to the naked eye. The waves can hit obstacles that can minimize their radio strength. Also the boost of your external antennas can trick a device to think the signal is stronger when in reality may not be as strong as going through a repeater.
1 Like
I do consider this. The two sensors are not obstructed by more than 2 wood walls. The outdoor device is repeating through another outdoor device and is quite the uh... path. There are trees, a hill, and a small pond involved that otherwise block the signal I have routing around those obstacles and then through a basement window 
That was very difficult to read. But you have a ton of S0 paired Fibaro sensors. All the extra S0 traffic is going to tie-up the z-wave mesh. I would use a secondary controller to pair those all with no security.
3 Likes
If you download the second PDF file instead of viewing in Google Docs it is crystal clear. I am sorry it is frustrating.
Screenshots are easier to view these details from ..... which is why they are so widely used. And you can edit a screenshot to black out device names.
There are Chrome plugins that can capture an entire page as a single PNG.
1 Like
I downloaded two such Chrome plugins and neither worked. They tried to scroll the page but did not scroll the iframe which has all of the devices listed. I even tried taking a scrolling screenshot in Chrome developer options, and ran into the same problem.
ShareX has a scrolling capture which works on that page. For Future reference.
1 Like
You're going to think I'm being difficult on purpose here, but I just downloaded this, followed this guide - How to Take a Scrolling Screenshot of a Website in Chrome (ShareX is demonstrated further down the page) and it still does not work. I imagine if I carefully modified its settings it would. What a pain! Thank you for trying though. The output I get now is a partial screenshot - it scrolls and captures maybe half of it.
What works for me on Google Chrome and Hubitat web pages is this plugin :
4 Likes
We have a winner. This extension worked - I'll hang onto it for next time - thank you.
Right click and open image in new tab to view
4 Likes
Wow...17 SO devices (at least that was my count), that is a lot!
Was this screenshot just after a reboot?
Don't worry, we only ever think that of @rlithgow1. 
2 Likes
Yes, a few hours after a reboot.
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
