Hub froze

Mine locks up on a occasion still, too. So you definitely have company. Can't ever find anything in the logs to follow.

It is basically impossible to troubleshoot slowdowns or lockups outside of blind trial and error. We can't see system events/sec, we can't see radio throughput/commands per sec, we can't see CPU, we can't see memory in the java heap. Nada.

Basically all you can do is look through the debug logging and hope you see something. Not very effective. Or just turn user drivers/apps off one at a time and pray it happens/doesn't happen again. Not very effective.

So I guess I'll just submit a ticket every time it happens, and hope support can figure it out. With the (in my opinion) large number of hub freezes and slowdowns being reported in the forums in the last few months I doubt support has time to chase them all down, though.

2 Likes

My lockups started just after 2.06 upgrade and I didn't add any devices or apps starting with 2.04. Since 2.06 I had to power cycle the hub 6 times already. I'm lucky that DB wasn't corrupted. Nothing in the logs after lockups. One time I was able to soft reboot after my Zigbee radio abruptly switched to off and all automations stopped working. Something definitely happened with 2.06, but I have no idea, because there are no tools to monitor the hub.

1 Like

So do those that have hub lockups have google homes?

I just looked in my logs and it was full of messages for one of my Google home devices.

dev:1822019-03-16 04:19:32.599 pm errorsu.litvak.chromecast.api.v2.ChromeCastException: Unable to load media (runQ)

dev:1822019-03-16 04:19:30.597 pm errorsu.litvak.chromecast.api.v2.ChromeCastException: Unable to load media (runQ)

dev:1822019-03-16 04:19:28.813 pm errorsu.litvak.chromecast.api.v2.ChromeCastException: Unable to load media (runQ)

dev:1822019-03-16 04:19:26.886 pm errorsu.litvak.chromecast.api.v2.ChromeCastException: Unable to load media (runQ)

dev:1822019-03-16 04:19:25.137 pm errorsu.litvak.chromecast.api.v2.ChromeCastException: Unable to load media (runQ)

dev:1822019-03-16 04:19:23.046 pm errorsu.litvak.chromecast.api.v2.ChromeCastException: Unable to load media (runQ)

dev:1822019-03-16 04:19:21.335 pm errorsu.litvak.chromecast.api.v2.ChromeCastException: Unable to load media (runQ)

dev:1822019-03-16 04:19:19.491 pm errorsu.litvak.chromecast.api.v2.ChromeCastException: Unable to load media (runQ)

dev:1822019-03-16 04:19:17.561 pm errorsu.litvak.chromecast.api.v2.ChromeCastException: Unable to load media (runQ)

dev:1822019-03-16 04:19:15.575 pm errorsu.litvak.chromecast.api.v2.ChromeCastException: Unable to load media (runQ)

dev:1822019-03-16 04:19:13.643 pm errorsu.litvak.chromecast.api.v2.ChromeCastException: Unable to load media (runQ)

dev:1822019-03-16 04:19:11.781 pm errorsu.litvak.chromecast.api.v2.ChromeCastException: Unable to load media (runQ)

dev:1822019-03-16 04:19:10.074 pm errorsu.litvak.chromecast.api.v2.ChromeCastException: Unable to load media (runQ)

dev:1822019-03-16 04:19:08.213 pm errorsu.litvak.chromecast.api.v2.ChromeCastException: Unable to load media (runQ)

dev:1822019-03-16 04:19:06.475 pm errorsu.litvak.chromecast.api.v2.ChromeCastException: Unable to load media (runQ)

dev:1822019-03-16 04:19:04.732 pm errorsu.litvak.chromecast.api.v2.ChromeCastException: Unable to load media (runQ)

dev:1822019-03-16 04:19:02.863 pm errorsu.litvak.chromecast.api.v2.ChromeCastException: Unable to load media (runQ)

dev:1822019-03-16 04:19:01.142 pm errorsu.litvak.chromecast.api.v2.ChromeCastException: Unable to load media (runQ)

1 Like

Yeah, the uniQ is a known issue. I turned off my Chromecast integration until support gets it resolved.

I don't think that lockups are related to Google home or Chromecast integration, because their release was way before 2.06 and lockup for me started right after 2.06

I do, but don't / didn't see those messages.

I rebooted that Google home and the messages went away.

My hub froze again. It has only happened twice in the past year. Starting to think it is related to this new firmware.

Any new apps you've added lately?

I had another hub freeze overnight last night. Automations were running slow at bedtime. Tried using a button automation around 5am and nothing worked. Last reported event was around 3:16am.

This is the second overnight hub lockup in the past 5 days, although it was a different hub that froze.

1 Like

can you have a look at the driver details for that google cast device that you rebooted?, in the state variable section, uriQ, is it empty?

@mike.maxwell I wasn't the one you were talking to, but for the record all of my Google Home devices have a blank-ish uriQ... Don't know if that is good or bad, just thought I would share.

Me too.

My hub also locked up around 2:00ish last night. It had the red light which I haven't seen before. It has locked up at least twice in the last couple of weeks. I had put 2.06 firmware on but ran into troubles with Ecobee so I reverted back to 2.04.

it should always be empty unless you are actually in the midst of playing some tts...

1 Like

I had my first lockup in weeks this morning as well. At just about 9:30am EDT.

Im starting to get FOMO here, mine hasn't locked up. I have no google home, in case thats relevant.

I just installed chromecast beta on my main hub (will eventually move it to my controller) a few days ago. Google Home has been on for a while but I don't really use it. Both seem to be working but will keep an eye out.

All 3 hubs are okay right now. There is a slight access lag when I first go back into the GUI after a while away but it speeds up after the next few clicks.

Here is the uriQ for that device: