Hubitat Crashes Every Evening

🛎️ Get Help
1

Hubitat has been crashing every single evening since upgrading. There is NOTHING in the logs about what happened. It just....STOPS. I've been using Hubitat for over a year mostly without issue until these last series of updates. I desperately need to downgrade like right now. Can someone help me figure it out?
2.2.5.124
Rev C-5

I think it MIGHT have to do with duplicate logs 7X (septuplcate?) This type of logging happens throughout the day and by the evening I'm betting the logs are full.

dev:652021-01-29 08:13:30.404 pm infoDownstairs Thermostat thermostatSetpoint was set to 75°F

dev:652021-01-29 08:13:30.385 pm infoDownstairs Thermostat is pending heat

dev:652021-01-29 08:13:30.379 pm debugcmd:ThermostatOperatingStateReport(operatingState:4), desc:zw device: 05, command: 4203, payload: 04 , isMulticast: false

dev:652021-01-29 08:13:30.316 pm infoDownstairs Thermostat thermostatSetpoint was set to 75°F

dev:652021-01-29 08:13:30.295 pm infoDownstairs Thermostat is pending heat

dev:652021-01-29 08:13:30.291 pm debugcmd:ThermostatOperatingStateReport(operatingState:4), desc:zw device: 05, command: 4203, payload: 04 , isMulticast: false

dev:652021-01-29 08:13:30.092 pm infoDownstairs Thermostat thermostatSetpoint was set to 75°F

dev:652021-01-29 08:13:30.077 pm infoDownstairs Thermostat is pending heat

dev:652021-01-29 08:13:30.073 pm debugcmd:ThermostatOperatingStateReport(operatingState:4), desc:zw device: 05, command: 4203, payload: 04 , isMulticast: false

dev:652021-01-29 08:13:29.910 pm infoDownstairs Thermostat thermostatSetpoint was set to 75°F

dev:652021-01-29 08:13:29.859 pm infoDownstairs Thermostat is pending heat

dev:652021-01-29 08:13:29.854 pm debugcmd:ThermostatOperatingStateReport(operatingState:4), desc:zw device: 05, command: 4203, payload: 04 , isMulticast: false

dev:652021-01-29 08:13:29.829 pm infoDownstairs Thermostat thermostatSetpoint was set to 75°F

dev:652021-01-29 08:13:29.800 pm infoDownstairs Thermostat is pending heat

dev:652021-01-29 08:13:29.777 pm debugcmd:ThermostatOperatingStateReport(operatingState:4), desc:zw device: 05, command: 4203, payload: 04 , isMulticast: false

app:2912021-01-29 08:13:29.729 pm infohandleEvent(): Downstairs Thermostat(thermostatOperatingState:null) pending heat

dev:652021-01-29 08:13:29.667 pm infoDownstairs Thermostat thermostatSetpoint was set to 75°F

dev:652021-01-29 08:13:29.645 pm infoDownstairs Thermostat is pending heat

dev:652021-01-29 08:13:29.637 pm debugcmd:ThermostatOperatingStateReport(operatingState:4), desc:zw device: 05, command: 4203, payload: 04 , isMulticast: false

dev:4192021-01-29 08:13:29.085 pm infoKitchen Sensor: illuminance is 0lux

dev:4192021-01-29 08:13:29.031 pm infoKitchen Sensor: illuminance is 0lux

app:2912021-01-29 08:13:28.934 pm infohandleEvent(): Kitchen Sensor(temperature:°F) 69.08

dev:4192021-01-29 08:13:28.926 pm infoKitchen Sensor: humidity is 25%

dev:4192021-01-29 08:13:28.864 pm infoKitchen Sensor: temperature is 69.08°F

app:2912021-01-29 08:13:26.560 pm infohandleEvent(): Downstairs Thermostat(thermostatMode:null) off

dev:652021-01-29 08:13:26.490 pm infoDownstairs Thermostat mode is off

dev:652021-01-29 08:13:26.485 pm debugcmd:ThermostatModeReport(mode:0), desc:zw device: 05, command: 4003, payload: 00 , isMulticast: false

2

I found the Restore Previous Platform Version option so I'm running that now.
:crossed_fingers:

I'd be surprised if others aren't hitting something similar with the 2.2.5.* version. If not, feel free to ping me if you need more info. I don't know what I'm doing to cause the 7X logging but I'm certain that has something to do with the issue.

3

Those logs are hard to read in that format. Support will ask that you include screenshots instead of copy/paste.

I am not sure if I can do anything to help, but may be if you include the brand and model of these devices it would help someone to see what is going on. Are these Zwave by chance?

And are there rules associated with these, or a thermostat app? Maybe also screenshot any associated rules.

4

At a first look, the hub runs at a low load, and there's nothing obvious in the support logs (different from above) either. There are no straight up errors (which doesn't help in figuring the root cause).

Can you define the "crashing" part? Does web interface become inaccessible? Does it stop processing rules and/or device commands? Is diagnostics tool accessible even if main web interfaces isn't? The more information the better.

I'll examine the setup more closely.

5

Hi @gopher.ny,

By crashing I mean the UI is inaccessible and all rules appear to stop working and the API stopped responding.

I reverted back to 2.2.4 and all is well again. I DID notice I had debug logs enabled for a couple of devices so I disabled those. If it crashes again, I'll try to get more debug info but I'm staying on 2.2.4 for now. I use thermostats and sensors to control the heat in my toddler's room so I'd rather not experiment when we need the heating rule to be reliable at night.

1 Like
6

I turned off debug logging everywhere and upgraded to 2.2.5.128 again yesterday and it just crashed. Seems to crash after about 15 hours or so. I'm going to downgrade again.