C8 unresponsive after updating from 2.3.8.117 to 2.3.8.118

[Daro66]

So, the issue isn’t there if i revert, and comes back with the update. Are there any HE supporters checking this form?

It’s not a big deal if I skip this one update, but the problem will be more difficult to find if it’s in the next upgrade as well, and at some point my C8 will become hopelessly out of date, and mostly a liability, so customer service, now is time to look into this.

Thank you!

[Daro66]

Let’s see how this works…

[danabw]

2.3.8.119 has a specific fix for the issue you were seeing, hopefully resolves your issue. I hadn't seen any of these warnings so can't report myself.

[Daro66]

This is in the release notes:

Fixed false elevated CPU load alarms on C8 pro hubs.

There was nothing false about the hub repeatedly hanging up.

[danabw]

May be a relationship, I've learned to never say never until I've run an update for a bit.

[Daro66]

Here’s to hoping!

[Daro66]

Unfortunately I’ve had to power cycle the hub twice since updating to 119.

I’ll create a new post about the update from 117 to 119 is causing the (from my point of view) same problem as well.

[bertabcd1234]

@Daro66

I’ll create a new post

Why? It looks like the same issue already described here. With it being a weekend, I'd suggest waiting until Monday and seeing if Support can dig in.

In the meantime, I'd try the usual troubleshooting on your own, like reviewing Apps Stats, Device Stats, and Logs (past logs) to see if you can find any problems on your own, along with disabling any apps or devices you think might be causing a problem.

[Daro66]

@bertabcd1234

Why? It looks like the same issue already described here.

Because as I wrote here, if the issue persists between updates, there’s a good chance that it will never be fixed, and the hub will remain un-updatable and at some point become unstable, and finally unusable. This is also why I changed the post’s title.

@bertabcd1234

I'd suggest waiting until Monday and seeing if Support can dig in.

I’d be happy to wait until Monday, but I also questioned above whether HE support actually monitors this form. So, if it is being monitored, and someone is looking, good customer support would be at least to send me a PM that it was being looked into.

@bertabcd1234

In the meantime, I'd try the usual troubleshooting on your own

The hub has been running stably for a while and no reboots have been required since updating to version 2.3.7.145 ( at least), so clearly something that was not an issue in 117 or earlier, has become one.

@bertabcd1234

like reviewing Apps Stats, Device Stats, and Logs (past logs) to see if you can find any problems on your own, along with disabling any apps or devices you think might be causing a problem.

As a matter of fact I did. The thinQ integration seemed to have used the most resources, so I uninstalled it as I don’t use it in HE at all. Other than that, there was nothing that stood out to me, which is why I need help… I can understand that such a small company like HE needs to rely on crowd sourcing, but they also need to realize what trust we are putting in them.

[bertabcd1234]

@Daro66

Because as I wrote here, if the issue persists between updates,

Sure, but to be clear, my question is: what additional information would that provide that was not already shared above? Without that, it seems more likely to simply generate more clutter and make things harder for everyone.

@Daro66

I also questioned above whether HE support actually monitors this form.

A quick look at posts will reveal that the answer is "yes" -- and even on weekends, but I wouldn't count on that always.

[aamann]

Just an additional data point: I had to revert my C-7 from 119 to 118 as it becomes unresponsive on 119 pretty quickly. No issues on my C-8 with 119 though…

[danabw]

@Daro66

I also questioned above whether HE support actually monitors this form

If you searched on the screen names of HE staff you'll find they are here constantly...Hubitat has the most active staff involvement in a forum that I've ever seen for any product. They are here all hours of the week and even on weekends, and include both support and dev personnel. Of course this is a very active forum and there are a lot of posts here, and they can't be everywhere all the time. They also provide freqent updates and may be busy getting ready for another release.

You didn't say if you are still getting the hub excessive load messages on .119 - did those at least go away?

If removing ThinQ doesn't have any affect then probably time to tag Support_Team so they can check your hub's engineering logs to see if anything stands out.

[Daro66]

@danabw

Hubitat has the most active staff involvement in a forum that I've ever seen for any product.

I’m very glad to hear that support is active.

@danabw

You didn't say if you are still getting the hub excessive load messages on .119 - did those at least go away?

I don’t login to the C8 unless I’m actually doing something with it, so I have been noticing the hangups when things did not happen. I assume the load message is a normal boot up thing until all processes have started and completed their initialization routines.

@danabw

If removing ThinQ doesn't have any affect then probably time to tag Support_Team so they can check your hub's engineering logs to see if anything stands out.

Thanks for the tip.
@support_team

[user5475]

Can I understand why my reply on this thread was removed ? I have the exact same problem and think it's important this is confirmed as an issue affecting multiple users ?

[jtp10181]

Your post was split to another post (by one of the other mods) as it seemed like it was not the same issue

Alexa "not responding" problems

Please note I'm experiencing a similar issue with the Alexa integration since a few days. I'm frequently getting an error message that a device is not responding and finally the change will happen much delayed. This has made my whole system unusable as we heavily rely on voice for light control.

[Daro66]

@jtp10181

Your post was split to another post (by one of the other mods) as it seemed like it was not the same issue

Please note I'm experiencing a similar issue with the Alexa integration since a few days. I'm frequently getting an error message that a device is not responding and finally the change will happen much delayed. This has made my whole system unusable as we heavily rely on voice for light control.

Exactly. Your issue is that Alexa issued commands are delayed. My issue is that the hub simply freezes until it is power cycled, so it was off topic.

[user5475]

Thanks! I wasn't notified in any way of the new thread, I should have searched for it !

[danabw]

Typically there will be a note in the topic saying that something was split off, but for some reason that didn't seem to appear this time. Not really your fault.