Having to hard reboot C-7 Daily

🛎️ Get Help
1

Web interface & IP Address:8081 has not been responding the past 2-3 days. Green light is on. Basically, i have been pulling the USB power cable, leaving out for 5 minutes, then plugging back in. Once back online, I've been removing apps where i see a bunch of failures in the logs (magic cube, ring unofficial integration). Things have been a bit buggy the past few weeks with my hub.

I keep updating to the latest release, thinking things would be fixed. I'm currently on 2.2.5.xx, whatever the latest that was available yesterday.

2

So do Hub stats or App stats show anything that is hogging memory? Are these all Zwave, Zigbee, or a mix? Is this new, like maybe an update set this off?

Maybe post screenshots of what you are seeing in logs and someone will recognize what is going on?

1 Like
3

If you’re doing a lot of hard restarts it might be time to try the trick of taking a backup and then doing an immediate restore or that backup. That can do some magic with the DB to fix potential corruption. You can also try a soft reset followed by a restore of a captured backup.

I’m not sure it’s necessarily DB corruption, but certainly is something you can try.

4 Likes
4

Yup - that's a good idea.

If that doesn't help if I was having these issues I'd take a backup, do a soft reset, and then restore the backup immediately.

4 Likes
5
Name Total ms Count Avg ms %
Amazon Echo Skill 8,763 149 59 34.7
Hubitat® Dashboard 7,946 26 306 31.5
Mudroom Motion 5,481 36 152 21.7
Leak in the house 1,070 59 18 4.2
Lights 1,069 9 119 4.2
Main Floor Lights 353 3 118 1.4
Battery 175 4 44 0.7
Motion 103 4 26 0.4
Temp 99 4 25 0.4
Test 96 4 24 0.4
christmas 86 4 22 0.3
6
Name Total ms Count Avg ms %
Kids Bathroom - Leak 519 4 130 12.8
Main Floor Lights 376 3 125 9.3
Mudroom - Dimmer 545 13 42 13.4
outdoor - front door light switch 300 8 38 7.4
Living Room - Lamp
7

just performed a backup, soft reset, restored backup, crossing fingers. Thanks for the advice, hopefully see some improvements!

8

If not, it's usually @neonturbo's fault. Please remember to hold him accountable.

:wink:

1 Like
9

Sure, blame me today. Everyone else has been.

All day I have been getting "but you didn't tell me!!!" but I had contacted them, multiple times via email and other methods. They just failed to look for the information.

So yea, I will take the blame. Doesn't bother me.

2 Likes
10

One of those days...not fun. Hopefully, as Scarlett said, tomorrow will be another day. :slight_smile:

1 Like
11

Mixture.

I have one Zooz 4-in-1 left that may be causing problems, and i know there has been issues discussed on here with it, many inactive calls. I'm really hesitant to take it off, since it is the one of the few WAF items (Mudroom Motion - lights) that earns me points.

12

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

13

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.

14

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:

15

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
16

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

1 Like
17

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
18

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

19

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.

20

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.