Restart only restarts the Hubitat process (so the underlying Linux OS is not restarted).
Reboot restarts the underlying Linux OS, so naturally the Hubitat process is also restarted.
1 Like
Why does your Watchdog report say "Zwav" after the delay time? Mine just says "null".
LJ
Wow, How did I miss THAT one! Is that new? or am i blind. (no need to answer that! 
)
LJ
Was this added in recent firmware versions? I didn't see anything in any release notes.
I'm still running versions from earlier this year hence my question above ..... I don't see a "restart" option anywhere, only reboot.
Doesn't appear on the docs site either at Hubitat Diagnostic Tool - Hubitat Documentation
Can't remember, but it has been there for at least a few months. It has never been documented. I believe someone at Hubitat brought it to @dman2306's attention, presumably with the goal of seeing whether restarts were as effective as reboots in resolving a slowdown.
Because, if only reboots resolved a slowdown, it would imply the issue lay outside of the JVM running the hubitat process.
1 Like
Didn't know about this. Thanks!
LJ
1 Like
Thanks @aaiyar didn't know about that ...... would have thought that with all the issues this would have been a good thing to officially announce!
1 Like
If folks have slowdown problems, stating what hub type may help in narrowing problems. The different hubs have different software configurations on them.
I do see improvement in 2.2.2 releases on my setup. I expect there are fixes in web sockets and eventstream methods (likely helping folks using hub connect, nst manager and the likes).
I have C4s, recently started using C5. On my busy C4 hubs, I had to restart every 36 hrs, now it goes many days. I do find doing many compiles shortens my restart interval. I subscribe to the onion theory mentioned above
As FYI, I use hub connect, nst manager, webCoRE (over 100 pistons), Rule Machine, weather apps, maker, Package manager, Intesis, tankUtility, Wemo, Alexa, etc.
2 Likes
I am running a C5, with new C7 on the way as soon they ship.
LJ
Thank you for pointing this out. We will add it to the docs. This existed for as long as /shutdown and /reboot existed, is just not commonly used, or included in the Diagnostic Tool, that's why is not there.
1 Like
Running on a C5. Before 2.2.2 I had to reboot the hub every 72 hours due to the hub slowing down. Running on 2.2.2.123 that time has extended 112 hours before the slowdown hits. So things have improved but the problem hasn't been solved.
Observing my hub's slowdown I do not experience a tapering off in performance. For me the hub performs consistently then within a short period of time (about an hours time) performance drops off significantly. If I don't reboot within another 24 hours the hub is almost crippled. Instead of the nightly system backup taking a minute or so, it sometimes just hangs never completing. The hub is still running but the lag is terrible.
Per the topic title you're still an update behind and don't have the "fix" yet.
Definitely better for me, but I too am just finding I need to reboot less frequently. Still slows down after a while.
OMG, What a difference a day makes. After about 36 hours with no slowdowns, the delays did start to come back at about 8PM. They rapidly increased to a constant state and stayed that way throughout the night. The hub restarted the Hubitat process at least twice in the night but the slowdowns continued constantly.
I then upgraded to 2.2.2.126 this morning, and the slowdowns continued in a constant state. I have fully rebooted at least twice, and Hub Watchdog has restarted the Hubitat process twice and the hub is still in a constant state of slowdown.
So now It appears worse than before. I am tempted to roll back to 2.2.2.125 for now and see if that gets better. This is strange. 
LJ
sad news that it's not fixed, I was hopeful and followed this forum for all those users having problems
On the plus side, they never advertised this release as "the fix" - just some things that directionally should have helped. More to come, as they say - maintain hope. 
4 Likes
It’s also never been clear (to me, at least) that there is one “problem” that leads to hub slowdowns or freezes. Meaning that it may not make sense to expect a single “fix” will resolve the issues that some of us have experienced.
1 Like
UPDATE: Before rolling back to 2.2.2.125 I chose to scour my logs to see if I could identify an offender. I noticed I was getting a lot of warning messages from Hubitat Dashboard app. I then went around to check all my panels and I found one that was stuck in some sort of loop or frozen. I reloaded the panel and now I am back to normal.
I am not sure I can identify the exact Dashboard because I am running the great app HubiPanel by a great young coder named @CordMaster. This app loads all the chosen Dashboards into a menu on the panel itself and then provides a rapid switching mechanism between dashboards which are kept up to date in the background. I have had no issues with this app at all, and not read of anyone else having any issues at all. This may have been a one off issue but reloading this panel has stopped the constant slowdown seen over the last 14 hours.
I will continue to observe and share.
LJ
2 Likes
Ok, looks like dashboard code is going to be getting some TLC over the next few days. Can't say what's broken since I haven't seen similar slowdowns, but it will go through some stress tests that will hopefully identify the problem.
9 Likes
