C-7 freezes/hangs at least once per week

🎬 Get Started Using C-7
1

A couple of weeks ago my C-7 started freezing every now and then.
Before that it would typically run for at least a month or two without hanging.

This time I tried accessing the Diagnostic Tool at xxx.xxx.xxx.xxx:8081. No dice. Completely unresponsive. The firmware version is 2.3.7.146.

Besides the log portion below, is there anything else I could upload here that might help troubleshoot? As far as devices, I have about 10 Centralite smart outlets (all using the Iris Smart Plug driver), three Environment Sensor EX, and a Sinope Load Controller RM3250ZB with energy meter (all of these items are on Zigbee), and a Lutron hub with three Pico button units. A few simple Rule Machine automations to turn things on and off. That's it. My system was originally running on a C-5 [edit: C-4], and it would occasionally hang as well, but pretty rarely; maybe once every 3 months. I'm wondering if I should put in a rule that reboots the unit every night around midnight??

Here is the latest portion of the log (apparently hung right after 8:07 AM; I rebooted it at 5:09 PM):

dev:592024-02-10 17:09:13.558infoTelnet connection to Lutron interface established
dev:202024-02-10 17:09:13.199warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 4B3E 00 00 0000 00 00 00000A0109744A01744ADE6C01EBFF00000300000000030000EF5000F91E8C2C00F91EAD9300F91E00000300000000030000
dev:22024-02-10 17:09:12.995warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 6CDE 00 00 0000 00 00 00000A01094F18004F18CFDF00CFDF744A010000000003000000000300000000030000000003000000000300000000030000
dev:12024-02-10 17:09:12.980warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 CF0E 00 00 0000 00 00 00000A0109C4F800DE6CCFDF00CFDF4F1800CFDF744A01870C42FC0042FC0000030000000003000000000300000000030000
dev:162024-02-10 17:09:13.187warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 44B3 00 00 0000 00 00 00000A0109C4F8004F18744A013E4B4F18004F18CFDF00CFDF42FC0042FC0000030000000003000000000300000000030000
dev:32024-02-10 17:09:12.977warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 4A74 00 00 0000 00 00 00000A01094F1800CFDFCFDF00CFDF0000030000000003000000000300000000030000000003000000000300000000030000
dev:42024-02-10 17:09:12.985warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 34B4 00 00 0000 00 00 00000A0109D4F6003E4B4F18004F18CFDF00CFDF42FC0042FC744A010000DE6C01EBFF000003000000000300000000030000
dev:182024-02-10 17:09:12.981warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 FFEB 00 00 0000 00 00 00000A0109744A00744AEF5000F91E8C2C00F91EC0F300F91EAD9300F91ECFDF00CFDF000003000000000300000000030000
dev:592024-02-10 17:09:12.728infoLutron Telnet is still online
dev:572024-02-10 08:07:36.783infoGuestBathHWR button 3 was pushed
dev:592024-02-10 08:07:36.775inforcvd: DEVICE,3,3,3
dev:572024-02-10 08:07:34.671infoGuestBathHWR button 5 was released
dev:592024-02-10 08:07:34.662inforcvd: DEVICE,3,4,4
dev:572024-02-10 08:07:34.369infoGuestBathHWR button 5 was pushed
dev:592024-02-10 08:07:34.360inforcvd: DEVICE,3,4,3
dev:572024-02-10 08:07:33.669infoGuestBathHWR button 1 was released
dev:592024-02-10 08:07:33.611inforcvd: DEVICE,3,2,4
dev:572024-02-10 08:07:33.168infoGuestBathHWR button 1 was pushed
dev:592024-02-10 08:07:33.159inforcvd: DEVICE,3,2,3
dev:572024-02-10 08:07:33.018infoGuestBathHWR button 3 was released
dev:592024-02-10 08:07:33.010inforcvd: DEVICE,3,3,4
dev:572024-02-10 08:07:32.198infoGuestBathHWR button 3 was pushed
dev:592024-02-10 08:07:32.189inforcvd: DEVICE,3,3,3
dev:572024-02-10 08:07:30.273infoGuestBathHWR button 3 was released
dev:592024-02-10 08:07:30.265inforcvd: DEVICE,3,3,4
dev:572024-02-10 08:07:29.301infoGuestBathHWR button 3 was pushed
dev:592024-02-10 08:07:29.292inforcvd: DEVICE,3,3,3
dev:572024-02-10 08:07:27.629infoGuestBathHWR button 3 was released
dev:592024-02-10 08:07:27.620inforcvd: DEVICE,3,3,4
dev:572024-02-10 08:07:26.594infoGuestBathHWR button 3 was pushed
dev:592024-02-10 08:07:26.568inforcvd: DEVICE,3,3,3
dev:572024-02-10 02:05:18.861infoGuestBathHWR button 3 was pushed
dev:592024-02-10 02:05:18.830inforcvd: DEVICE,3,3,3

2

The freezes continue.
In the meantime I've installed Hubitat Package Manager, Hub Information driver, and the Rebooter app. I have the latter set to reboot at 00:05:00 every day. I have dashboard tiles set to show the Free Memory attribute from Hub Information, as well as the time since last boot.
So it ran for a little over 24 hours since doing that, but this morning at about a minute past midnight, it hung again, so that it didn't do the 00:05 AM reboot. I just discovered at about 16:20 this afternoon that it was frozen, and manually power cycled it.
Since my original post above, I've done a soft reset (restoration of a previous config).
I don't have anything on my LAN running Jumbo Frames.
For several years, my C-5 ran in the same environment with very infrequent hangs; maybe once every 3 months on average.
I don't see a way to attach a log file to this post (text), so I'll append it at the end of my message.
It shows that the last entry before the hang was Checking for updates for Zigbee Driver for Sinope device. And four minutes previously, the Free Memory was 606,952 KB.
What else should I be looking for that might indicate why this hub keeps freezing up?
And BTW, when it freezes, the Diagnostic Interface at port 8086 is also unresponsive; and the green light is still on at that point.

Log for 2024-02-18 to 2024-02-19 (a bunch of lines cut from the middle to shorten the message):

dev:542024-02-19 16:22:29.032warnDID NOT PARSE MESSAGE for description : catchall: 0000 0006 00 00 0040 00 1EF9 00 00 0000 00 00 0BFDFF040101190000
dev:32024-02-19 16:22:17.539warnDID NOT PARSE MESSAGE for description : catchall: 0000 0006 00 00 0040 00 4A74 00 00 0000 00 00 4AFDFF040101190000
dev:12024-02-19 16:21:37.947warnDID NOT PARSE MESSAGE for description : catchall: 0000 0006 00 00 0040 00 CF0E 00 00 0000 00 00 0AFDFF040101190000
dev:1222024-02-19 16:20:47.734infohubUpdateVersion : 2.3.8.119
dev:1222024-02-19 16:20:47.731infohubUpdateStatus : Update Available
dev:1222024-02-19 16:20:25.314infozigbeePower : 8
dev:1222024-02-19 16:20:25.311infozigbeeStatus : online
dev:1222024-02-19 16:20:25.309infofreeMemory : 682136KB
dev:1222024-02-19 16:20:25.003infoformattedUptime : 0d, 0h, 1m, 0s
dev:1222024-02-19 16:20:24.989infouptime : 60
dev:1222024-02-19 16:20:24.985infolastPoll : baseData
dev:1222024-02-19 16:20:24.982infolastPollTime : 1708384824980
dev:1222024-02-19 16:20:24.978infolocalIP : 192.168.21.144
dev:1222024-02-19 16:20:24.975infosunset : 18:16:00
dev:1222024-02-19 16:20:24.972infosunrise : 07:10:00
dev:1222024-02-19 16:20:24.939infocurrentHsmMode : null
dev:1222024-02-19 16:20:24.894infocurrentMode : Day
dev:1222024-02-19 16:20:21.924infolocationId : 1
dev:1222024-02-19 16:20:21.921infolocationName : AxleHub2
dev:1222024-02-19 16:20:21.917infozigbeeStatus : enabled
dev:1222024-02-19 16:20:21.912infozigbeeChannel : 0x19 (25)
dev:1222024-02-19 16:20:21.896infouptime : 57
dev:1222024-02-19 16:20:21.889infofirmwareVersionString : 2.3.7.146
dev:1222024-02-19 16:20:21.883infolocalSrvPortTCP : 39501
dev:1222024-02-19 16:20:21.878infolocalIP : 192.168.21.144
dev:1222024-02-19 16:20:21.867infotype : PHYSICAL
dev:1222024-02-19 16:20:21.849infohardwareID : 000D
dev:1222024-02-19 16:20:21.839infozigbeeEui : 000D6F0017403362
dev:1222024-02-19 16:20:21.833infozigbeeId : 000D6F0017403362
dev:1222024-02-19 16:20:21.790infoname : AxleHub2
dev:1222024-02-19 16:20:21.785infoid : 1
dev:1222024-02-19 16:20:21.772infotemperatureScale : F
dev:1222024-02-19 16:20:21.766infozipCode : 86315
dev:1222024-02-19 16:20:21.758infotimeZone : {"id":"America/Phoenix","offset":"-25200000","dstSavings":"0","useDaylight":"false","transitions":"12","lastRule":""}
dev:1222024-02-19 16:20:21.671infolongitude : -112.210916
dev:1222024-02-19 16:20:21.666infolatitude : 34.674293
dev:1222024-02-19 16:20:21.634infohubModel : C-7
dev:12024-02-19 16:20:16.705warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 CF0E 00 00 0000 00 00 00000A0109C4F800DE6CCFDF00CFDF4F1800CFDF000003000042FC0042FC0000030000000003000000000300000000030000
dev:592024-02-19 16:20:16.470infoTelnet connection to Lutron interface established
dev:592024-02-19 16:20:16.289infoLutron Telnet is still online
dev:202024-02-19 16:20:15.961warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 4B3E 00 00 0000 00 00 00000A01094F18004F18000003000042FC01F91E0000030000EF5000F91E8C2C00F91EAD9300F91E00000300000000030000
dev:182024-02-19 16:20:16.163warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 FFEB 00 00 0000 00 00 00000A01094F18004F18000003000042FC010000000003000000000300000000030000000003000000000300000000030000
dev:32024-02-19 16:20:15.961warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 4A74 00 00 0000 00 00 00000A0109000003000042FC013E4B4F18004F18000003000000000300000000030000000003000000000300000000030000
dev:162024-02-19 16:20:16.146warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 44B3 00 00 0000 00 00 00000A0109000003000000000300004F1800CFDFCFDF00CFDF42FC0042FC201F00201F000003000000000300000000030000
dev:22024-02-19 16:20:16.146warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 6CDE 00 00 0000 00 00 00000A01094F18004F18CFDF00CFDF42FC0042FC000003000000000300000000030000000003000000000300000000030000
dev:12024-02-19 16:20:16.142warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 CF0E 00 00 0000 00 00 00000A0109C4F800DE6CCFDF00CFDF4F1800CFDF000003000042FC0042FC0000030000000003000000000300000000030000
dev:42024-02-19 16:20:16.140warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 34B4 00 00 0000 00 00 00000A0109D4F6003E4B4F18004F18CFDF00CFDF42FC0042FC00000300000000030000000003000000000300000000030000
dev:1222024-02-19 16:20:14.887infolastHubRestartFormatted : 2024-02-19 16:19:24
dev:1222024-02-19 16:20:14.743infolastHubRestart : 1708384764607
app:1562024-02-19 00:00:14.992infoChecking for updates for Zigbee Driver for Sinope device
2024-02-19 23:20:14.594 INFO dev|122|HubInfo|Hub Information v3.0.36 initialized
app:1562024-02-19 00:00:14.789infoChecking for updates for Hub Rebooter
app:1562024-02-19 00:00:14.456infoChecking for updates for Hubitat Package Manager
app:1562024-02-19 00:00:14.055infoChecking for updates for Hub Information Driver v3
app:1562024-02-19 00:00:13.895infoA new repository was added, https://raw.githubusercontent.com/ady624/hubitat-hpm/master/repository.json
app:1562024-02-19 00:00:13.891infoA new repository was added, https://raw.githubusercontent.com/ljbotero/hubitat-flair-vents/main/repository.json
app:1562024-02-19 00:00:13.886infoA new repository was added, https://raw.githubusercontent.com/ShellyUSA/Hubitat-Drivers/master/repository.json
app:1562024-02-19 00:00:13.389infoRefreshing repository list
dev:212024-02-18 23:57:13.524infoWater Heater Switch : Load controller is on [physical]
dev:212024-02-18 23:57:09.526infoWater Heater Switch : Power is 0 W
dev:1222024-02-18 23:56:23.840infoformattedUptime : 0d, 23h, 51m, 7s
dev:1222024-02-18 23:56:23.835infouptime : 85867
dev:1222024-02-18 23:56:23.833infolastPoll : poll1
dev:1222024-02-18 23:56:23.831infolastPollTime : 1708325783830
dev:1222024-02-18 23:56:23.829infolocalIP : 192.168.21.144
dev:1222024-02-18 23:56:23.826infosunset : 18:15:00
dev:1222024-02-18 23:56:23.824infosunrise : 07:11:00
dev:1222024-02-18 23:56:23.815infotemperatureC : 37.0 °C
dev:1222024-02-18 23:56:23.813infocurrentHsmMode : null
dev:1222024-02-18 23:56:23.813infotemperatureF : 98.6 °F
dev:1222024-02-18 23:56:23.810infotemperature : 98.6°F
dev:1222024-02-18 23:56:23.810infocurrentMode : Day
dev:1222024-02-18 23:56:23.805infofreeMemory : 606952KB
dev:212024-02-18 23:55:40.790infoWater Heater Switch : Power is 4548 W
dev:212024-02-18 23:54:49.271infoWater Heater Switch : Power is 4578 W
dev:212024-02-18 23:47:11.078infoWater Heater Switch : Load controller is on [physical]
dev:1222024-02-18 23:46:23.787infoformattedUptime : 0d, 23h, 41m, 7s
dev:1222024-02-18 23:46:23.783infouptime : 85267
dev:1222024-02-18 23:46:23.780infolastPoll : poll1
dev:1222024-02-18 23:46:23.778infolastPollTime : 1708325183777
dev:1222024-02-18 23:46:23.776infolocalIP : 192.168.21.144
dev:1222024-02-18 23:46:23.774infosunset : 18:15:00
dev:1222024-02-18 23:46:23.771infosunrise : 07:11:00
dev:1222024-02-18 23:46:23.764infocurrentHsmMode : null
dev:1222024-02-18 23:46:23.755infotemperatureC : 37.0 °C
dev:1222024-02-18 23:46:23.754infocurrentMode : Day
dev:1222024-02-18 23:46:23.752infotemperatureF : 98.6 °F
dev:1222024-02-18 23:46:23.749infotemperature : 98.6°F
dev:1222024-02-18 23:46:23.741infofreeMemory : 606912KB
dev:212024-02-18 23:46:00.069infoWater Heater Switch : Power is 0 W
dev:212024-02-18 23:37:11.024infoWater Heater Switch : Load controller is on [physical]
dev:1222024-02-18 23:36:23.621infoformattedUptime : 0d, 23h, 31m, 6s
dev:1222024-02-18 23:36:23.616infouptime : 84666
dev:1222024-02-18 23:36:23.613infolastPoll : poll1
dev:1222024-02-18 23:36:23.611infolastPollTime : 1708324583609
dev:1222024-02-18 23:36:23.608infolocalIP : 192.168.21.144
dev:1222024-02-18 23:36:23.605infosunset : 18:15:00
dev:1222024-02-18 23:36:23.604infotemperatureC : 37.0 °C
<<<<<<<<<<<<<<<
A ton of lines cut here to shorten the message...

dev:1222024-02-18 01:06:07.426infofreeMemory : 639652KB
dev:212024-02-18 01:05:31.323infoWater Heater Switch : Power is 0 W
dev:212024-02-18 01:03:48.317infoWater Heater Switch : Load controller is on [physical]
dev:1222024-02-18 00:56:07.401infoformattedUptime : 0d, 0h, 50m, 45s
dev:1222024-02-18 00:56:07.396infouptime : 3045
dev:1222024-02-18 00:56:07.392infolastPoll : poll1
dev:1222024-02-18 00:56:07.332infofreeMemory : 641060KB
dev:1222024-02-18 00:56:07.389infolastPollTime : 1708242967385
dev:1222024-02-18 00:56:07.384infolocalIP : 192.168.21.144
dev:1222024-02-18 00:56:07.336infotemperatureC : 37.0 °C
dev:1222024-02-18 00:56:07.336infosunset : 18:15:00
dev:1222024-02-18 00:56:07.333infosunrise : 07:11:00
dev:1222024-02-18 00:56:07.331infotemperatureF : 98.6 °F
dev:1222024-02-18 00:56:07.321infotemperature : 98.6°F
dev:1222024-02-18 00:56:07.319infocurrentHsmMode : null
dev:1222024-02-18 00:56:07.310infocurrentMode : Day
dev:212024-02-18 00:55:31.268infoWater Heater Switch : Power is 0 W
dev:212024-02-18 00:53:48.262infoWater Heater Switch : Load controller is on [physical]
dev:1222024-02-18 00:46:07.297infoformattedUptime : 0d, 0h, 40m, 45s
dev:1222024-02-18 00:46:07.292infouptime : 2445
dev:1222024-02-18 00:46:07.288infolastPoll : poll1
dev:1222024-02-18 00:46:07.286infolastPollTime : 1708242367284
dev:1222024-02-18 00:46:07.283infolocalIP : 192.168.21.144
dev:1222024-02-18 00:46:07.280infosunset : 18:15:00
dev:1222024-02-18 00:46:07.277infosunrise : 07:11:00
dev:1222024-02-18 00:46:07.269infocurrentHsmMode : null
dev:1222024-02-18 00:46:07.262infocurrentMode : Day
dev:1222024-02-18 00:46:07.222infotemperatureC : 37.0 °C
dev:1222024-02-18 00:46:07.219infotemperatureF : 98.6 °F
dev:1222024-02-18 00:46:07.215infotemperature : 98.6°F
dev:1222024-02-18 00:46:07.166infofreeMemory : 646524KB
dev:212024-02-18 00:45:31.211infoWater Heater Switch : Power is 0 W
dev:212024-02-18 00:43:48.201infoWater Heater Switch : Load controller is on [physical]
dev:1222024-02-18 00:36:07.120infoformattedUptime : 0d, 0h, 30m, 44s
dev:1222024-02-18 00:36:07.114infotemperatureC : 37.0 °C
dev:1222024-02-18 00:36:07.111infotemperatureF : 98.6 °F
dev:1222024-02-18 00:36:07.111infouptime : 1844
dev:1222024-02-18 00:36:07.102infotemperature : 98.6°F
dev:1222024-02-18 00:36:07.102infolastPoll : poll1
dev:1222024-02-18 00:36:07.096infolastPollTime : 1708241767094
dev:1222024-02-18 00:36:07.093infolocalIP : 192.168.21.144
dev:1222024-02-18 00:36:07.090infofreeMemory : 651664KB
dev:1222024-02-18 00:36:07.090infosunset : 18:15:00
dev:1222024-02-18 00:36:07.075infosunrise : 07:11:00
dev:1222024-02-18 00:36:07.067infocurrentHsmMode : null
dev:1222024-02-18 00:36:07.056infocurrentMode : Day
dev:212024-02-18 00:35:31.157infoWater Heater Switch : Power is 0 W
dev:212024-02-18 00:33:48.147infoWater Heater Switch : Load controller is on [physical]
dev:1222024-02-18 00:26:06.951infoformattedUptime : 0d, 0h, 20m, 44s
dev:1222024-02-18 00:26:06.946infouptime : 1244
dev:1222024-02-18 00:26:06.943infolastPoll : poll1
dev:1222024-02-18 00:26:06.940infolastPollTime : 1708241166939
dev:1222024-02-18 00:26:06.938infolocalIP : 192.168.21.144
dev:1222024-02-18 00:26:06.935infosunset : 18:15:00
dev:1222024-02-18 00:26:06.932infosunrise : 07:11:00
dev:1222024-02-18 00:26:06.924infocurrentHsmMode : null
dev:1222024-02-18 00:26:06.918infocurrentMode : Day
dev:1222024-02-18 00:26:06.909infofreeMemory : 652504KB
dev:1222024-02-18 00:26:06.904infotemperatureC : 38.0 °C
dev:1222024-02-18 00:26:06.901infotemperatureF : 100.4 °F
dev:1222024-02-18 00:26:06.898infotemperature : 100.4°F
dev:212024-02-18 00:25:31.095infoWater Heater Switch : Power is 0 W
dev:212024-02-18 00:23:48.013infoWater Heater Switch : Load controller is on [physical]
dev:212024-02-18 00:23:02.095infoWater Heater Switch : Current is 0 A
dev:212024-02-18 00:23:02.085infoWater Heater Switch : Voltage is 249 V
dev:1222024-02-18 00:16:06.797infoformattedUptime : 0d, 0h, 10m, 44s
dev:1222024-02-18 00:16:06.795infotemperatureC : 39.0 °C
dev:1222024-02-18 00:16:06.790infouptime : 644
dev:1222024-02-18 00:16:06.786infotemperatureF : 102.2 °F
dev:1222024-02-18 00:16:06.785infolastPoll : poll1
dev:1222024-02-18 00:16:06.783infolastPollTime : 1708240566781
dev:1222024-02-18 00:16:06.782infotemperature : 102.2°F
dev:1222024-02-18 00:16:06.780infolocalIP : 192.168.21.144
dev:1222024-02-18 00:16:06.777infosunset : 18:15:00
dev:1222024-02-18 00:16:06.774infosunrise : 07:11:00
dev:1222024-02-18 00:16:06.765infocurrentHsmMode : null
dev:1222024-02-18 00:16:06.761infocurrentMode : Day
dev:1222024-02-18 00:16:06.734infofreeMemory : 662048KB
dev:212024-02-18 00:15:31.024infoWater Heater Switch : Power is 0 W
dev:212024-02-18 00:13:48.048infoWater Heater Switch : Load controller is on [physical]
dev:1222024-02-18 00:06:38.901infohubUpdateVersion : 2.3.8.119
dev:1222024-02-18 00:06:38.897infohubUpdateStatus : Update Available
dev:92024-02-18 00:06:23.554errorjava.lang.NullPointerException: Cannot get property 'value' on null object on line 476 (method parse)
dev:1222024-02-18 00:06:20.531infozigbeePower : 8
dev:1222024-02-18 00:06:20.528infozigbeeStatus : online
dev:1222024-02-18 00:06:20.475infofreeMemory : 683260KB
dev:1222024-02-18 00:06:20.271infoformattedUptime : 0d, 0h, 0m, 57s
dev:1222024-02-18 00:06:20.164infouptime : 57
dev:1222024-02-18 00:06:20.160infolastPoll : baseData
dev:1222024-02-18 00:06:20.157infolastPollTime : 1708239980156
dev:1222024-02-18 00:06:20.154infolocalIP : 192.168.21.144
dev:1222024-02-18 00:06:20.150infosunset : 18:15:00
dev:1222024-02-18 00:06:20.147infosunrise : 07:11:00
dev:1222024-02-18 00:06:20.084infocurrentHsmMode : null
dev:1222024-02-18 00:06:20.042infocurrentMode : Day
dev:1222024-02-18 00:06:13.481infolocationId : 1
dev:1222024-02-18 00:06:13.477infolocationName : AxleHub2
dev:1222024-02-18 00:06:13.474infozigbeeStatus : enabled
dev:1222024-02-18 00:06:13.468infozigbeeChannel : 0x19 (25)
dev:1222024-02-18 00:06:13.448infouptime : 51
dev:1222024-02-18 00:06:13.439infofirmwareVersionString : 2.3.7.146
dev:1222024-02-18 00:06:13.434infolocalSrvPortTCP : 39501
dev:1222024-02-18 00:06:13.430infolocalIP : 192.168.21.144
dev:1222024-02-18 00:06:13.388infotype : PHYSICAL
dev:1222024-02-18 00:06:13.385infohardwareID : 000D
dev:1222024-02-18 00:06:13.377infozigbeeEui : 000D6F0017403362
dev:1222024-02-18 00:06:13.374infozigbeeId : 000D6F0017403362
dev:1222024-02-18 00:06:13.309infoname : AxleHub2
dev:1222024-02-18 00:06:13.306infoid : 1
dev:1222024-02-18 00:06:13.277infotemperatureScale : F
dev:1222024-02-18 00:06:13.266infozipCode : 86315
dev:1222024-02-18 00:06:13.249infotimeZone : {"id":"America/Phoenix","offset":"-25200000","dstSavings":"0","useDaylight":"false","transitions":"12","lastRule":""}
dev:1222024-02-18 00:06:13.072infolongitude : -112.210916
dev:1222024-02-18 00:06:13.068infolatitude : 34.674293
dev:1222024-02-18 00:06:13.011infohubModel : C-7
dev:22024-02-18 00:06:09.759warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 6CDE 00 00 0000 00 00 00000A01094F18004F18CFDF00CFDF42FC0042FCB34400B344B43400B4340000030000000003000000000300000000030000
dev:12024-02-18 00:06:09.578warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 CF0E 00 00 0000 00 00 00000A0109C4F800DE6CCFDF00CFDF4F18004F18000003000042FC0042FCB43400B434000003000000000300000000030000
dev:32024-02-18 00:06:09.176warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 4A74 00 00 0000 00 00 00000A01090ECF000ECFF91E003E4B0000030000000003000000000300000000030000000003000000000300000000030000
dev:182024-02-18 00:06:08.900warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 FFEB 00 00 0000 00 00 00000A01094F18004F18DE6C00DE6C0000030000000003000000000300000000030000000003000000000300000000030000
dev:542024-02-18 00:06:08.842warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 1EF9 00 00 0000 00 00 00000A01090000030000000003000027F50027F5EF5000EF508C2C008C2CC0F300C0F3AD9300AD9300000300000000030000
dev:12024-02-18 00:06:08.682warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 CF0E 00 00 0000 00 00 00000A0109C4F800DE6CCFDF00CFDF4F18004F18000003000042FC0042FCB43400B434000003000000000300000000030000
dev:22024-02-18 00:06:08.699warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 6CDE 00 00 0000 00 00 00000A01094F18004F18CFDF00CFDF42FC0042FCB34400B344B43400B4340000030000000003000000000300000000030000
dev:162024-02-18 00:06:08.690warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 44B3 00 00 0000 00 00 00000A0109000003000000000300004F1800CFDFCFDF00CFDF42FC0042FC201F00201F000003000000000300000000030000
dev:42024-02-18 00:06:08.689warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 34B4 00 00 0000 00 00 00000A0109D4F6003E4B4F18004F18CFDF00CFDF42FC0042FC00000300000000030000000003000000000300000000030000
dev:202024-02-18 00:06:08.683warnDID NOT PARSE MESSAGE for description : catchall: 0000 8032 00 00 0040 00 4B3E 00 00 0000 00 00 00000A01094F18004F18F91E00F91E00000300000000030000EF5000F91E8C2C00F91EAD9300F91E00000300000000030000
dev:592024-02-18 00:06:07.470infoTelnet connection to Lutron interface established
dev:592024-02-18 00:06:07.208infoLutron Telnet is still online
dev:1222024-02-18 00:06:05.965infolastHubRestartFormatted : 2024-02-18 00:05:22
dev:1222024-02-18 00:06:05.916infolastHubRestart : 1708239922826
dev:1222024-02-18 00:06:05.823infoHub Information v3.0.36 initialized
app:1552024-02-18 00:05:00.112infoRestarting hub

3

if the greeen light is on maybe it has gotten a different ip through your dhcp server..
have you had any network changes.. new router etc.

also check for the nic address on the bottom of the hub in your router lan status to see if it is up on a different ip.

are your ip setting static , dynamic etc.

next time you can also try the network reset button on the bottom an dsee if that helps.

4

No network changes in the past six+ months. Router has an address reservation set for the C-7, and that is what IP address it always gets when it boots. Just to be sure, thanks to your comment, I've changed the Hubitat to static IP at that same address. I'll report back within a week or so whether that helped.
I was unaware of the dedicated network reset switch on the bottom of the Hubitat. Next time it freezes I'll try that first.

1 Like
5

Can you paste screenshots of your logs, rather than the text itself? It is much easier to read screenshots.

6

Most recent portion of log:

image
image1975×967 149 KB

7

I posted that screen shot at 50% size to save space; it looks like when you double-click on it, it expands. Let me know if that doesn't work for everyone.
Here is a portion after the last intentional reboot:

image
image1810×684 161 KB

8

And here is a snippet that includes the hang just after midnight 2/19, followed by the power-cycle-reboot at 16:20 on 2/19:

image
image1095×981 165 KB

9

Sorry; single-click not double-click, to expand the inline image.

10

I just signed up for Hub Protect for this C-7. I bought it in January 2022, but it sat in the box unused until this past November; so it's actually only been powered up for 3 months.
All that time I continued using my original C-4 (not C-5 as I stated erroneously above), because I had purchased the C-7 with the intention to use both of them, in two parts of the house. But I retired the C-4 when I started using the C-7 last November.
The next time it freezes I'll try the reset button on the bottom first.
I realize that will set it back to DHCP, but my DHCP server (router) has the same address reserved for it.
If that doesn't cause it to respond to the web page request, and the diagnostic port remains unresponsive, then I will have to do a power cycle again.
At that point I think it will be time for me to ping the Support Team.

11

Platform Version is 2.3.7.146.

I bought this C-7 in January 2022. Before that I had used my original C-4 for over a year, in the same home and same set of devices.

The C-4 was pretty reliable; I only recall it hanging/freezing once or twice in that year.

However I continued using the C-4 and left the C-7 in its box until November 2023, when I migrated my devices and apps from the C-4 to the C-7.

The C-7 seemed to be stable for the first month or two, but since Christmas/New Years it has been hanging/freezing every few days.

When this occurs, the green light remains on, but the hub cannot be reached either at its normal web address or at the Diagnostic page (port 8086). Neither does it respond to pings.

Also it does not respond to pushing the reset switch on the bottom; I've held it in for up to 30 seconds with no effect whatsoever.

I should also point out that a major indication of these freeze/hang conditions is that automations aren't working-- either time-driven events or button-triggered events. It's completely dead at that point.

The only thing that brings it back to life is a power cycle.

Note that I've always used an address reservation for the Hubitat in DHCP on my router.

Recently I tried changing it to static IP address, but it froze the very next night.

I've also tried installing Hub Information to keep an eye on Free Memory, but that appears to stay reasonably high.

I installed the Reboot application, and set it up to reboot itself at 00:05 every morning (just after midnight), but the other night the Hubitat froze about 5 minutes before it was due for its app-triggered reboot; so that didn't help obviously.

Power is via its original USB power brick, which came with the C-7. It is plugged into the same UPS-protected power strip that supplies my router etc.

As far as I know, there are no Jumbo Frames being issued on my LAN by any device; however, I'm not sure how to check for that.

I'm attaching the most recent log showing the point where it froze this morning (~11:56 AM).

Several times I've restored backups to effect a soft reboot. This does not help; it still hangs periodically.

Is there any chance this is a hardware flaw?

To rule that out, should I perform a complete factory reset, then let it run without any Zigbee devices paired to it? Just basically idling, to see if it then stays up?

I think that would require me to eventually re-pair all my Zigbee devices (pretty sure I did that after the C-4 to C-7 upgrade).

Right now the only really critical task it has is to turn off the Sinope Load Controller at 4 PM every day, to prevent my water heater from running during peak rate hours (and to turn it back on at 7 PM).

That rule only has to fail to run one time, and it can cause a $30+ excess demand charge on my power bill, for that month. So I really want this hub to be reliable; otherwise I'll have to replace it with a simple Intermatic 30-amp timer switch!

Please advise what additional troubleshooting I should do.

BTW I recently purchased your Hub Protect plan for this C-7.

AxleHub log leading up to freeze, 2024-02-20 11_56 AM
AxleHub log leading up to freeze, 2024-02-20 11_56 AM1819×1060 310 KB

AxleHub apps list
AxleHub apps list1364×786 82 KB

AxleHub device list
AxleHub device list2074×1086 246 KB

12

Tagging @support_team

In the meanwhile, you can submit a Hub Protect Subscription "claim" here. Select "Other" as the reason, and describe the issue you've encountered.

13

Three days ago I disconnected the C-7 and reinstalled the C-4. After upgrading it to the latest firmware, I restored the latest settings from the C-7 and re-paired all my Zigbee devices.
It's been working and stable since then, which is longer than the C-7 could run without freezing lately.
So I'm more convinced than ever that the C-7 has a hardware flaw, especially given the fact that when frozen, it didn't respond at all to the bottom reset button.
We'll see if Hubitat will do anything about it. It's officially out of warranty, but it has only been powered up and in use for about three months, and the freezes started at least a month ago, maybe two (they've gotten more frequent as time went on). Plus I paid for Hub Protect, which is supposed to function as an extended warranty, if I understand the marketing correctly.