Hi all.
I've just noticed this error in the logs.
Received local request for App 7195 that does not exist, path: /list from unknown
As per the error message app 7195 does not exist.
I have 3 hubs so I suppose the request could be coming from another hub.
Is there anyway I can identify what could be causing this.
I have disabled all apps and devices on the hub receiving this error but it is still being generated.
Any pointers suggestions greatly appreciated.
1 Like
Sounds like you delete something that something is making a call to. Perhaps maker api is looking for something?
1 Like
You permitted, via app 7195, some system/device access. MakerAPI, HubConnect, etc.
Perhaps soft reset back to a much older backup for the time it takes to find out what App 7195 was, back then?
Yesterday I soft Reset my development hub and did NOT install a backup. Naturally I got hundreds of these:
sys:1 2022-05-31 06:49:10.705 am Received cloud request for App 397 that does not exist, path: /ping from 54.83.150.101
sys:1 2022-05-31 06:48:10.117 am Received cloud request for App 397 that does not exist, path: /ping from 54.83.150.101
sys:1 2022-05-31 06:47:10.722 am Received cloud request for App 397 that does not exist, path: /ping from 54.83.150.101
sys:1 2022-05-31 06:46:10.097 am Received cloud request for App 397 that does not exist, path: /ping from 54.83.153.160
sys:1 2022-05-31 06:45:10.104 am Received cloud request for App 397 that does not exist, path: /ping from 54.83.150.101
sys:1 2022-05-31 06:44:10.660 am Received cloud request for App 397 that does not exist, path: /ping from 54.83.150.101
sys:1 2022-05-31 06:43:10.879 am Received cloud request for App 397 that does not exist, path: /ping from 34.197.42.9
sys:1 2022-05-31 06:42:10.689 am Received cloud request for App 397 that does not exist, path: /ping from 54.83.150.101
sys:1 2022-05-31 06:41:11.653 am Received cloud request for App 397 that does not exist, path: /ping from 54.83.150.101
In my case, I knew that the previous config had a HubConnect connection to ST and these messages were 'expected.' This morning, I restored a backup from 10 days ago, and the errors became HubConnect messages:
app:397 2022-05-31 07:13:10.925 am trace Received ping from ST Hubless.
app:397 2022-05-31 07:12:10.920 am trace Received ping from ST Hubless.
app:397 2022-05-31 07:11:14.917 am trace Received ping from ST Hubless.
app:397 2022-05-31 07:10:10.787 am trace Received ping from ST Hubless.
app:397 2022-05-31 07:09:10.250 am trace Received ping from ST Hubless.
app:397 2022-05-31 07:08:10.165 am trace Received ping from ST Hubless.
app:397 2022-05-31 07:07:10.847 am trace Received ping from ST Hubless.
1 Like
I forgot to mention that the error is being generated every 10 seconds.
I've scanned the various logs to see if anything is being scheduled every 10 seconds but cannot seem to find anything.
Scanning the logs from this hub won't likely help--this type of request is almost always coming from something else on your LAN. It could be another Hubitat hub, but it could be any LAN integration you previously configured. (It could be something on the hub, but it's likely it would need an OAuth endpoint to do its thing.) Since you have at least two more, I suppose it wouldn't hurt to check those in case you only checked this one.
I'm not sure this could be MakerAPI or HubConnect, since it doesn't look like either have a mapping for /list. Not helpful, I know. But maybe someone recognizes something this could be. Otherwise, restoring an old backup as @csteele suggested should show you what app 7195 is (if you can find one from when you had that app installed).
I've restored a backup from 2 days ago and still getting the error.
Not sure I want to go back much further.
Will have to keep digging.
Look at your integrations? Again maybe maker API? Look at apps/driver code and see if there is something in there that you don't use anymore that may trigger something in your noggin? Maybe an old cloud integration?
The IP address would be listed if it was coming from within your network, or a service like mobile app, or any AWS cloud service. I see these most often with Hub Link hooked on ST or Life 360, but unfortunately, you are looking for the needle in the haystack if you don't remember what LAN/cloud integration you've tried and later removed.
1 Like
That was what I was worried about.
If it was coming through hub mesh would that show up as something different in the error message?
I wouldn't show as sys, but if it did, it would show the other hub's IP address, not "unknown".
1 Like
So would it be a fair assumption that it is something on the hub, device or app, that is causing this. Not anything external.
Did a soft reset and restored a backup from the 10th of May.
GOT HIM!!!!!!!!!!!! 
What program was the culprit?
Many moons ago I had a Xiaomi hub that I hooked up to HE using an app called Mi Connector that used a docker instance on an RPi.
You pair the Xiaomi devices to the Xiaomi hub and then through docker, connect the devices to HE. Stopped using it over a year ago.
Did a clean up over a week and deleted the app from HE.
The docker instance must have still been calling the Mi Connector app.
I've just deleted the docker instance from my RPi and hey presto, all is quiet again.
4 Likes
