Having to hard reboot C-7 Daily

I think you can pair that Zooz without security with a UZB stick.

Unresponsive again this morning after initial motion action, unable to login via 8081. pulled power, went back into logs to see what happened.

My rebooter app triggered middle of the night on schedule (3x per week):

Name Description Value Event Type Date

Name Description Value Event Type Date
systemStart System startup with build: 2.2.5.127 2.2.5.127 2021-02-03 06:56:40.135 AM CST
systemStart System startup with build: 2.2.5.127 2.2.5.127 2021-02-03 02:16:45.560 AM CST
systemStart System startup with build: 2.2.5.127 2.2.5.127 2021-02-02 07:16:29.048 PM CST

Last log activity before lockup/restart:
dev:422021-02-03 06:56:36.088 am infoLiving Room - Lamp is off

dev:1872021-02-03 06:08:11.387 am infoSBR - Motion is inactive

dev:1872021-02-03 06:07:16.765 am infoSBR - Motion is active

dev:1872021-02-03 06:06:02.612 am infoSBR - Motion is inactive

dev:1872021-02-03 06:05:32.417 am infoSBR - Motion is active

dev:12021-02-03 06:05:28.122 am infoMudroom - Sensor: illuminance is 7lux

dev:12021-02-03 06:05:28.096 am infoMudroom - Sensor: temperature is 69.69°F

dev:12021-02-03 06:05:28.094 am infoMudroom - Sensor: humidity is 38%

dev:1872021-02-03 06:03:20.738 am infoSBR - Motion is inactive

app:2742021-02-03 06:03:14.001 am infoDelaying off for 8 minutes

app:2742021-02-03 06:03:13.907 am infoMotion inactive Mudroom - Sensor

dev:12021-02-03 06:03:13.856 am infoMudroom - Sensor: motion is inactive

dev:12021-02-03 06:03:13.832 am infoMudroom - Sensor: motion is inactive

dev:1472021-02-03 06:03:00.103 am infoMudroom - Outdoor Light switch is on

dev:1922021-02-03 06:02:59.479 am infooutdoor - garage lights switch switch is on

dev:1872021-02-03 06:02:50.549 am infoSBR - Motion is active

dev:12021-02-03 06:02:47.467 am infoMudroom - Sensor: motion is active

dev:12021-02-03 06:02:47.452 am infoMudroom - Sensor: motion is active

dev:12021-02-03 06:02:33.631 am infoMudroom - Sensor: motion is active

dev:12021-02-03 06:02:33.604 am infoMudroom - Sensor: motion is active

dev:12021-02-03 06:02:25.142 am infoMudroom - Sensor: motion is active

dev:12021-02-03 06:02:25.114 am infoMudroom - Sensor: motion is active

app:2742021-02-03 06:02:19.541 am infoMudroom - Dimmer set to 95

app:2742021-02-03 06:02:19.536 am infoMudroom - Dimmer turned on

dev:1152021-02-03 06:02:19.451 am infoMudroom - Dimmer was set to 95

dev:1152021-02-03 06:02:19.431 am infoMudroom - Dimmer was turned on

A little wary to buy this to use a work around to use it. Almost to the point to just buy a new motion sensor that works.

Device App Events are low since reboot, nothing standing out there.

Let me know what else i can provided.

EDIT: Paused motion and lighting app using that 4-in-1 zooz sensor, to see if that clears it up before removing that device.

If you have another motion sensor around to replace it with, I'd do that.

I'm not 100% sure, but I think to remove the impact of the Zooz on your network you'd have to remove the Zooz, rather than just pause automations that use it, as I believe the Zooz using S0 is going to be chatty even if it's not doing much.

Tagging @gopher.ny and @bobbyD - guys, a little help here? :slight_smile:

I also recall in the rebooter app thread people were having issues with 2.2.5 and the "process restart" option in that app. The suggestion was to flip it back to a normal full reboot. I'd give that a try if that seems to be triggering your issue.
image

2 Likes

Appreciate that catch. I'm wondering if that is one of the causes. Disabled that setting, and we'll see what happens.

1 Like

Cool, yeah, something seemed to have changed in HE 2.2.5 and some people like this comment [RELEASE] Hub Rebooter App seem to have a similar issue using 'restart' instead of reboot.

1 Like

I'll check the hub once it's gone through 1 or 2 full reboots and if the issue persists.

Unfortunately locked up again this morning, unable to log in. Was working last night fine. I don't think rebooter happened last night. I'll hard reboot and fully remove that single Zooz 4-in-1 later today.

I do have a support ticket open on this.

It occurred again this morning. Last night i excluded the ZSE40 device from the hub (also opened up a ticket with zooz on this.) I also removed apps (Hub Watchdog, Unofficial Ring). I keep noticing i'm unable to login to my dashboards, then unable to log into my hub, even on 8081. My morning mode doesn't switch. BTW, Surprised on a reset it doesn't look at modes, have to manually adjust them.

Once i reboot the hub via power pull, i notice logs stop collecting overnight. I look at my unifi network, and the hub is disconnected at that time in the logs. Haven't had issues with any other network devices.

The last thing i run each night is an Echo 'Good Night' Routine. I do see sensor logs occurring in logs after that call.

Support didn't find anything causing the issue in my logs, recommended that i start removing apps to see if that clears it out. It's strange, i see the logs stop each evening overnight, where the hub becomes unresponsive, including 8081. Rebooter last night reforming a reboot prior to the event didn't even keep the issue from occurring later on.

I'll keep removing user, then built-in apps. If that doesn't fix it, i'll factory reset and start over. I am still liking Hubitat over ST, but a bit frustrated that this popped up on the 2.2.5 FW update a couple of weeks ago.

I'm still having the issues 1-2x a day, where a power cycle is needed for devices to become responsive via modes, rules, or Alexa, be able to use dashboards, and to log into the hub (inc 8081). I think i'm going to try to factory reset this weekend and start over from scratch.

My apps now are down to using 6 simple automation rules, mode manager (which i've found is a pain to adjust if mode didn't change due to lockup), and 2 notifications (leak/battery).

I've removed all the user/ & built in apps, besides the 3 above.

While I'm still i would say on the lower end of devices, is it best to exclude all the devices before factory reset, and then re-include?

Main Device Types/Brands
Zooz/Innovelli Switches/Dimmers
Iris sensors
Samsung Leak Detectors
Sengled Zigbee bulbs
ZSE40 Zooz 4-in-1 (already removed, getting a stick to include again)
ZSE25 dual switches

@gopher.ny - were you able to find anything in his hub to explain this?

The hub is back on 2.2.4. For some reason it was not accessible from support tool while running later versions of 2.2.5, and logs don't show any reason.

@spartysh32, please let me know how 2.2.4 fairs. If things don't freeze on it, I'll be taking a closer look at code differences. The freezes manifest as "nothing happens for several hours" gaps in the logs, there's no additional information otherwise.

Do you happen to have dashboards that are viewed on an Amazon Fire tablet by any chance?

woke up, didn't have to power cycle/reboot today on 2.2.4 the past 20ish hours. Interesting on the support tool btw 2.2.4 and 2.2.5.

I only have dashboards available on my android phone. i haven't set them up on any Fire Tablets that i use.

@spartysh32
I am interested to see if you were able to resolve your issues and upgrade to 2.2.5 . I have been experiencing very similar problems in my efforts to upgrade to 2.2.5.131 and have had to revert to 2.2.4.158 in order to keep my hub running. I have been following several threads on this topic and would like to know if you have been able to identify the problem and resolve the issue.

I'm still sitting on 2.2.4. I have a support ticket open, and am planning to wait for a response before trying to update to 2.2.5 again. Strange that it only affects a few.

Thank you for your response. I too have reverted as the 2.2.5 platform is unstable for me. As it does appear that we have a couple of devices, Zooz ZSE40 motion sensons, Zooz switches and Sengled bulbs, in common, I wonder if these could be where the problem lies.

Having the same issue on 2.2.6, rolled back to 2.2.4. this looks to be a somewhat isolated issue, a few others may have this issue it seems.

I have a C7 on 2.2.6.137 and have noticed that starting a few days ago I am having to do one or more reboots per day. If I don't anything going through the hub stops working. I am using all Inovelli switches except one Aeotec Smart Switch 7. I have 24 Red Dimmers, 5 Black switches and 5 fan+lights. Switches that control the load still work and any switches connected via an association to another switch still works. As soon as I do a controlled shutdown, reboot it all starts to work again for some hours - but only for some hours.

Could you post a screenshot of your zwave info page?