App 152 generates excessive hub load

Good day all,

My Hubitat hub has taken a mind of its own and it is arming my alarm and triggering my sirens for no apparent reason.

I've noticed this in the logs, just not sure how to see what application 152 is but my gut feeling tells me it is the Life360 sensor which runs every 5 seconds.

The rule name says 5 minutes, so not sure when that changed to 5 seconds but for sure if I did change it to 5 seconds, I probably did that a while back, so not sure how the problem starts to happen now.

Any help would be very much appreciated.

Thank you

Your logs indicate that app 152 is your rule to refresh Life360 presence.

This is a cloud integration, so the app polls the Life360 cloud. Perhaps something is currently delayed in that cloud polling (eg. your internet connection is slow, or their cloud servers are slow/down). Conditions like these will increase the hub load because successive iterations of your app are logjammed

If you need such rapid polling, I’d suggest writing a custom app that uses some sort of a back-off timer when timely responses are not received.

Alternatively, is it really necessary to run this rule that frequently?

2 Likes

Thank you aaiyar, looks like today there has been an OAUTH issue with Hubitat which I received from Sharptools which could cause some delay.

Also, my network has 17 POE cameras, most of them 5K but they are in their own subnet but maybe that's causing a lot of traffic on my network and slowness.

Anyway, I did restart the whole network, that helps most of the time with slowness and I have also updated Hubitat to the latest firmware available. Also, I did change the Life360 presence rule to rune very 5 minutes instead of every 5 seconds. However, my alarm was still getting armed auto magically, either ARM AWAY, ARM HOME or ARM NIGHT, never DISARMED and also my sirens were still going off for no reason.

I couldn't see anything that trigger those events. So, I went ahead and changed my Sharptools password and that seemed to solve the alarm being armed for no apparent reason. Also, I do Arm my alarm manually and not via the presence sensor, although I still have that functionality in place in case I need it. Looks like someone probably hacked my account or something but I don't want to jump to conclusions yet. I will give it another day. Maybe just a coincidence but I've noticed the sirens are still going off for no reason. So not sure where to look to see what is causing the issue.

Please advise.

Probably not, but I’ll tag @josh anyway.

2 Likes

In your first screenshot with all the log entries, when you tap the blue 'app:152' link to the left of one of the log entries, it selects and highlights that app name at the top of the list and filters down to just the entries from that app.

So in your case, app 152 is "Life360 refresh (5 minutes)" which per your second screenshot appears to be a rule to refresh the status of that integration.

I assume you mean that you saw a warning within the SharpTools UI telling you that the Hubitat OAuth servers were experiencing performance issues:

...which links to the following thread describing the issues that the Hubitat OAuth servers have been experiencing. That message only shows up when the Hubitat OAuth servers are actually running slow.

And that should only impact you when you are going through the authorization flow - it should not impact normal usage of your hub nor outbound connections from your hub to external services.

As @aaiyar mentioned, it could be coincidental timing that Life360 was having issues and those 5 second polls were slowing down the whole hub as they waited for network responses. That would bring the whole hub to a halt in some cases.

That would automatically log your account out on any devices.

Checking the logs, I don't see anything suspicious. While I do see lots of requests much earlier in the day to change HSM and a few other devices (including a siren device), those are all coming from the normal IP address your account has used.

I'll send you more details via PM, but I suspect one of your browsers was acting wonky.

3 Likes

Thank you aaiya.

Thank you so much @josh very much appreciated all the detailed answers.

Yes, I saw that message about the OAUTH from within Sharptools.

Also, I did notice about a week ago, that any of my automation will run delayed for some reason, for example if I went to open the garage door, the lights will not go on right away, they will take a few seconds to turn on, so I would assume that doing the Life360 refresh every 5 seconds was causing that, the interesting thing is that I don't remember changing that from 5 minutes to 5 seconds or maybe I did to run a test and forgot to change it back to 5 minutes but that was at leas 6 months ago or more.

Also, yesterday I changed my Google password which I used to authenticate to Sharptools and coincidentally the HSM strange behavior to arm the alarm went away. As for of one of the sirens turning back on, I think that was caused because I was trying to turn it off manually via a button in sharptools dashboard and at the time I had to disconnect all my Konnedted boards because the sirens were driving me crazy :slight_smile: so that explains why I was trying to turn it off, the command was send to the board but there was no response from it and it was defaulting back to be on.

Also, thanks for pointing out the iPad in your PM. I did notice that one of my iPads that I have in my garage which I have Sharptools running on it was acting up. It was making clicking noises like someone was trying to type on it. The garage was hot at 94 degrees Fahrenheit, not sure if the heat or just the iPad going bad (it is old) was causing the buttons on the Sharptools dashboard to be magically tapped, including the sirens which I had then as switch buttons, and now I have change them as just view only mode. A quick iPad reset fixed the problem.

Also, I now understand why the DISARM button wasn't getting triggered and that's because it has a PIN associated with it.

So, my conclusion is that I wasn't hacked like @aaiyar said and changing the password was just a good security measure to take but that wasn't really the problem. Although, I have to mention that an issue I had with the Nest App for a week or so went away as well. The Nest App would tell me that no one was home but in fact I was home and will also tell me that my front door was unlock which in fact it was locked. So that's the only thing I can't explain. Was it related, not sure.

Today, the system is running great, thank you so much for your help to both of you.

2 Likes

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.