I started getting some weird behavior from my HE. I have a motion lighting rule with mode based scenes. It's also tied to a button so I can toggle the lights on and off manually.
Recently the motion lighting App started crashing. I have rebuilt the rule and scenes from scratch just in case but the problem remains. I've been able to replicate it since. Pushing the button will call for the scene to be turned off but it won't actually turn it off. From there the problem will propagate until no scenes can be activated at all. The problem spreads to other rules from there but only motion lighting rules it seems. It will work normally after a reboot, at least until I try to turn it off manually with the button again. There are no other rules tied to that button other than a rule to update the status RGB.
The app will also crash on its own, but I haven't been able to pin point that, as it does it sporadically. But I would be willing to guess it's also tied to turning off a scene.
I have logging enabled on the scenes so it should have logged the lights as they were turned off. Lights remained on, log confirms nothing happens. After that event, button pushes are registered but no action is taken by HE. Trying to open the rule to make changes results in the screen loading indefinitely. A reboot again brings everything back to normal.
Please enable logging in Motion Lighting. Also, please show a screenshot of the Motion Lighting main setup page. I fixed it so you can post a picture here.
I took these yesterday. I'll grab fresh ones when I get home.
I took the screenshot after pressing the button. The lights did not actually turn off. Had to reboot after to get the lights to respond.
This appears to be an error with the device, not the app. It doesn't seem to like the button 4 push. See if you can do that from its device page.
I have more logs. I arrived home to find the same problem again. This time it happened on its own. It seems to be when a scene is activated or turned off.
On the first log you can see hubitat reacting to motion and following the rile accordingly. It keeps working fine until a mode change triggers a new scene.
After the scene is triggered the app stops responding to motion events.
Later I get home and try to turn on my daughter's lights, this is on a completely different rule, button, and scene than what made it crash but it won't respond now either.
Hubitat will stay this way until I reboot. It also becomes impossible to access any, motion lighting, groups and scenes, and button controller rules until after a reboot. Trying to access any of those roles is met with this screen and never loves past it.
Whatever driver you are using for that device is going into an infinite loop, and this in turn is killing your hub.
What is the driver? This probably has nothing to do with Motion Lighting, beyond that perhaps it triggers this cascade of issues. You have to go back to that error you posted before, and figure out what causes it.
I did actually look back at that error and don't think it's related. It was caused by a phone running kiosk browser. It has a rule to wake up it's screen when motion is detected by the living room sensor. My daughter had unplugged it to charge her tablet and it died. I plugged it back in this morning. That's why it does not appear on the logs when it crashed again later in the day.
The "door multi switch" is a zooz scene wall switch.
What puzzles me is the rule worked in it's current config for a few weeks. Long enough for the fam to become reliant on it.
I have a very hard time dealing with phone screen shots. Do you have a laptop or desktop? I just can't help with the logs shown the way you are doing it. Do you know how to isolate the logs to only the relevant app?
I'll get you PC logs tomorrow. I left my laptop at work. Are you talking about the filters up top? Or turning off logging to other stuff altogether?
Btw. Thanks for the quick replies!
I appreciate the help. I just got my HE on April 1st.
Yes, these help, so you only show relevant information, making it possible to see what is going on.
