Hubitat crashes every night

[jp0550]

@jrau272

ns that seem to be having “recovery events” every few minutes and in hub events it looks like the hub restarted almost 30 minutes before my good morning piston was set to run.

Looking at the piston logs is mostly unrevealing to me. However, there are a bunch of events in one of the pistons like this:

The slowdown is coming before his piston code starts executing:

CS - Child Start - Event received in child and the event delay is logged (now() - event.date)
PS - Parent Start - Child calls parent to get runtime information (commands, colors, variables)
PE - Parent Exit - Runtime information gathered, return to child
CE - Child Exit - Child variables initialized. Right before piston execution

RunTime Analysis CS < 11571ms < PS < 10853ms < PE < 221730ms < CE

Normally the exchange above is supposed to happen in ideally around 150ms, but it varies in hubitat between 300ms and 600ms if the hub isn't too loaded down. When the hub is booting up, I see delays on mine, but not to the extent of 5 minutes. If his hub is crashing, it sounds like resources are low and is reflected in the logs for the piston execution time.

I've found that if I have a piston for refreshing zwave devices (~30 devices refreshed every 3 minutes (1 every 8 seconds or so)) the hub will run out of memory and become unresponsive in around a day before needing to reset.