Would there be any reason to do this? Is there a cache or do things get bogged down or need to be periodically rebuilt?
3 Likes
Yea I'm working with support at the moment, but late at night when I try to set the home to night mode, the hubs riding the struggle bus to nowhere...
I need to test rebooting it before I do the nightly good night command and see if it improves...
Don't know what to say if it does.
Short answer, there is no need to do it. Longer answer...see this:
1 Like
Yea I remember that.
I've tried to always avoid rebooting and let it work out whatever it's thinking about.
But when idiots are rewarded with better performance after a reboot we keep doing it. 
I've got to see what I can remove from the system tonight.
I see we have some rather strong feelings about this.
A "need" to reboot to make things right suggests that ones effort should go towards finding what's wrong for which a reboot is the apparent cure. Symptomatic relief vs finding the real underlying cause.
1 Like
Good to know - I only use one custom app. The Circadian Daylight coordinator, which is probably safe. I try to stay native as much as possible for this exact reason. I don't have as much time to bug chase as I used to. @bravenel, so a reboot should be considered a major last-resort event, and should probably be reported, yes?
Assuming you have something to report is my take on the subject. You had to reboot. You report that. How could support help with that? You would need some log that points to the issue or at least helps guide toward it. If you're running a single custom app, you need regular reboots, and you have tried removing that custom app and still need regular reboots, then there's almost certainly a device attached to the system via Zigbee, Z-Wave or IP that is causing the need for a regular reboot.
I'm finally stable. The issues where I wasn't have been narrowed to devices connected via IP that were to blame. I've corrected this issues on those devices and I'm stable again. No reboots required.
My last reboot was 12/3 when I installed 2.0.1.117. Before that it was 11/30 when I installed 2.0.1.114
I keep thinking "I don't reboot ever, just for Firmware upgrades." When I look at the Hub Events Log I see it's true, BUT they release new firmware more often than I'd normally reboot.
I don't need a regularly scheduled reboot to fix mysterious things, Hubitat releases are my schedule 
4 Likes
Other than updates the only time I reboot is if I've played with a user app and decided to remove it. Just to make sure nothing is hanging around I'll do a reboot after removal of custom code..
Does that help clean up user app junk?
I feel like it garbage collects.
I make changes so frequently because I'm trying to nail everything down maybe that's why it helps me.
Actually, there is a nightly system job that cleans up the mess you've left behind, like abandoned apps. I make huge messes routinely, and never do anything more than simply removing unneeded app instances or virtual devices. It's quite rare for me to reboot, although I do platform updates much more frequently than any of you.
1 Like
That's good to know.
@bobbyD has revealed that it's at my bed time so I'm competing with it to turn my lights off.
More reason to go to sleep earlier and stop breaking Hubitat.
Nothing wrong with a three-fingered salute on occasion in my experience 
