Hubitat locking up

🛎️ Get Help
1

I have 2 hubs. 1 that runs all of my lights and one that runs basically everything else. The one that runs the lights is locking up quite a bit. I can not get to the web interface, yet I can ping the IP address of the hub. After I power cycle, everything is working great. Both hubs are running 2.2.4.158. Looking for some help on how to figure out what is causing the lockups. I don't believe the logs are available after a power cycle. The 2nd hubitat has never locked up. Suggestions appreciated.

C:\Windows\system32>ping 192.168.1.235

Pinging 192.168.1.235 with 32 bytes of data:
Reply from 192.168.1.235: bytes=32 time=24ms TTL=64
Reply from 192.168.1.235: bytes=32 time=2ms TTL=64
Reply from 192.168.1.235: bytes=32 time=1ms TTL=64
Reply from 192.168.1.235: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.235:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 24ms, Average = 7ms

2

I believe they are. Can post a screenshot of "past logs"?

3

it shows no activity between 11:12am and 4:33pm which is when I reset it (less than 10 min ago) but it doesn't tell me much...

dev:42021-01-17 04:35:11.992 pm infoTable Lamp was set to 0%
dev:42021-01-17 04:35:11.951 pm infoTable Lamp was set to 0%
dev:42021-01-17 04:35:11.815 pm infoTable Lamp was turned off
dev:42021-01-17 04:35:11.764 pm infoTable Lamp was turned off
dev:7102021-01-17 04:34:06.789 pm infoOSRAM 2 was turned on
dev:812021-01-17 04:34:04.278 pm infoEntry Way switch was turned on
dev:3342021-01-17 04:33:24.282 pm infowebsocket is open
dev:3342021-01-17 04:33:23.371 pm infoinitialize() called
dev:42021-01-17 11:12:15.255 am infoTable Lamp was turned off
dev:2142021-01-17 11:12:14.798 am infoOverhead Lights switch is off
dev:42021-01-17 11:07:15.386 am infoTable Lamp was turned off
dev:2142021-01-17 11:07:15.026 am infoOverhead Lights switch is off
dev:7102021-01-17 11:03:58.121 am infoOSRAM 2 saturation is 100%
dev:7102021-01-17 11:03:58.060 am infoOSRAM 2 hue is 17%
dev:42021-01-17 11:02:15.262 am infoTable Lamp was turned off
dev:2142021-01-17 11:02:14.897 am infoOverhead Lights switch is off
dev:42021-01-17 10:57:15.333 am infoTable Lamp was turned off

4

I see some "crash" files on 12/20, 1/8, 1/9, and 1/17. Does that match the times hub went AWOL?
If so, the best way to restart it is through the update tool: http://192.168.1.235:8081/

There isn't a lot going in the logs otherwise... a few random errors from driver AmbientEcowittWeather. but that shouldn't be enough to crash it. I'll have to take a closer look.

5

ok, so first off, since I have never had an issue before, how are you seeing that from what I see above? Yes, those dates match to what I am seeing and about when everything started crashing on this guy about 12/20. Next time it does it (if it does) I will go to that port and restart. I can always reach my lan via my phone, so that should not be a problem. I did not know about the :8081 portion, which will help

6

There are back end logs, which can be downloaded on demand from an internal support tool. We routinely troubleshoot using those.

Yes, this is a new issue, and right now I'm puzzled as to why it happens. Crash reports have very limited information. Will need to do some research.

7

thank you! It is interesting that only one of the hubitats is doing this. Also, is there something that I can do on my side, if/when this happens again? Step details would be appreciated. Would like to help if this is a new issue.

8

The Hubitat is currently locked up. I am leaving it that way so that maybe someone can help prior to me resetting?

9

The hub is not responding to remote commands either, so please go ahead and reset it.
I'll check again once it's up and running.

10

TY, it is back up...

11

Ok, I see what happened there.
Can you take a backup and try updating to 2.2.5? The latest version should auto restart when it crashes in the manner seen on your hub.

12

yep, thank you... just noticed there was a new version. If this fixes it, I will mark as solved after a couple weeks.

13

locked up at some point today... resetting it now. :frowning:

14

i am also in the same boat with random lockups. mine presented after upgrade past 2.2.4.158 and ive disabled most all 3rd party items. even a daily reboot hasnt helped....following this thread for any pertinent guidance.

15

Same here. I've been resetting and updating for the last week or so. It just froze today as well. Ive been running latest firmwares.

16

Weird that this is only happening to one of my two hubs. Also, it seemed pretty stable for awhile and to note, a new update was pushed out a couple days ago...

17

Piling on. On 2/8 (at or about 7pm Mountain Time), my hub became unresponsive.
C7 and I have been applying each firmware update within 24 hours of notification.

At first, I noticed a light that failed to turn off after a 15 second delay. Then several motion-based automations did not trigger. I cycled power at the plug and all has been good since, but it has only been 36 hours.

18

another random lockup @ ~11pm on 2/10
did not know there was any issue until morning automations didnt fire

@gopher.ny any way you can look into my logs to give me some hints as to what may be going on? ive done soft resets, ive done fw upgrades, ive disabled most everything that is not required for day-to-day....very frustrating that the unit goes 30+ hours then just craps out

19

Doesn't seem to make a difference. This behavior is new to 2.2.5, right?

20

+1 to this issue. I started documenting mine in this post:

1 Like