How to track down which app by number from error message sys:1

🛎️ Get Help Apps
1

Anyway to determine the name of app 35 from the sys:1 error message?

sys:12023-08-13 02:50:59.037 PMwarnReceived cloud request for App 35 that does not exist, path: /mobile/6587bd66-dc4a-4fa5-af89-4a4aaf1b9fe8/updates from 174.207.43.57
sys:12023-08-13 02:50:59.021 PMwarnReceived cloud request for App 35 that does not exist, path: /mobile/6587bd66-dc4a-4fa5-af89-4a4aaf1b9fe8/devices from 174.207.43.57
2

That's the hub, and it's letting you know there is no app or driver on the hub that matches. So, there's no way to tell now, but one way would be to restore a backup from whenever it did exist so you can see for yourself, which would give you some ideas as to how to make whatever that was stop trying to contact your hub. Ultimately, that's going to be the solution -- something outside your hub is trying to reach it via the cloud, that endpoint no longer exists, and you'll need to figure out what that was and stop it.

Usually, this is some external cloud service integration: Alexa, Google Home, Life360, IFTTT, the webCoRE mobile app (not just webCoRE itself), the Hubitat mobile app, etc. If you've used any of these and removed one of these apps on the hub (or reset your hub or bought it second hand and the original owner did this) without deleting/resetting/etc. that external service, that was probably the cause.

Sometimes, the endpoint URLs give clues because some popular apps use easily identifiable ones, but I don't recognize the ones in your logs (maybe the Hubitat mobile app? logging out and back in, selecting your hub and existing mobile app when prompted, can't hurt -- on any device you use it with). Maybe someone else knows what these might be from. But since the app no longer exists on your hub, it's usually a guessing game (unless you have a backup you can reference).

3 Likes
3

A reverse lookup on 174.207.43.57 shows its coming from a Verizon business sub domain.
57.sub-174-207-43.myvzw.com
Might be a clue.

4 Likes
4

I figured it out and posting here if anyone else ever sees these errors.

I have a presence sensor in my car and the battery died. The warning messages were from HD+ on my phone using Maker API to update when I came and went in my car. Once I replaced the sensor battery, I no longer see the warning messages.

5

And presumably your phone was on Verizon.

1 Like
6

Yes.

7

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