Received cloud request for App 247 that does not exist, path: /events from

🛎️ Get Help Devices
1

Every since the most recent HUB OS update (to 2.3.4.122) I have been receiving the following warning in my logs every minute.

sys:12022-12-21 04:36:41.914 AMwarnReceived cloud request for App 247 that does not exist, path: /events from 74.125.212.87

sys:12022-12-21 04:36:38.572 AMwarnReceived cloud request for App 247 that does not exist, path: /events from 74.125.210.161

sys:12022-12-21 04:36:33.958 AMwarnReceived cloud request for App 247 that does not exist, path: /events from 74.125.212.76

sys:12022-12-21 04:36:32.179 AMwarnReceived cloud request for App 247 that does not exist, path: /events from 35.187.139.184

sys:12022-12-21 04:36:31.640 AMwarnReceived cloud request for App 247 that does not exist, path: /events from 74.125.210.191

sys:12022-12-21 04:36:17.244 AMwarnReceived cloud request for App 247 that does not exist, path: /events from 35.187.139.162

sys:12022-12-21 04:36:10.968 AMwarnReceived cloud request for App 247 that does not exist, path: /events from 74.125.212.90

sys:12022-12-21 04:35:39.868 AMwarnReceived cloud request for App 247 that does not exist, path: /events from 74.125.212.78

sys:12022-12-21 04:35:34.971 AMwarnReceived cloud request for App 247 that does not exist, path: /events from 74.125.212.78

sys:12022-12-21 04:35:33.618 AMwarnReceived cloud request for App 247 that does not exist, path: /events from 74.125.210.179

sys:12022-12-21 04:35:19.191 AMwarnReceived cloud request for App 247 that does not exist, path: /events from 35.187.139.183

sys:12022-12-21 04:35:18.656 AMwarnReceived cloud request for App 247 that does not exist, path: /events from 74.125.210.178

Does anyone know how I go about debugging this one?

Thanks

2

At least one of those IPs is Google. Did you maybe have Google integration installed or maybe an integration with something hosted at Google?

2 Likes
3

This is a warning the hub logs when it receives an external request from a service referencing an app that doesnt currently exist in the hub’s database. But it probably did at some point and was deleted from the hub.

So as @brad5 mentioned, did you have any google-related services integrated with Hubitat that you deleted from the Hubitat end (but not the google end) recently?

2 Likes
4

Surest way to find out, is to restore a prior backup (create a new one first) to find out what App 247 was and eliminate the cloud side of it, and then restore to the current backup.

3 Likes
5

i am a newbie, and I bought this used on ebay. If I factory reset this, will this problem be solved?

6

No, reset won’t fix it. Something externally is trying to connect to it. A reset won’t change the cloud hub ID. Did the other person de-register the hub and you registered a new account?

What integration apps have you installed and then removed? Alexa? Google Home?

The suggestion above was to revert to a backup that has the app you deleted so you can identify it. If you don’t have a backup guessing is the only way.

4 Likes
7

That is a bummer. Can you contact the eBay seller and ask them to disconnect any cloud-based services they were using with Hubitat?

1 Like
8

What I don't understand is if the hub has gone through a soft reset, the public IP address has changed, and the registered user has changed, how is it that the cloud service, whatever it is, still knows how to find the hub?

2 Likes
9

Cloud is registered at the MAC / hub ID. The external app no longer has a valid access key, but the cloud doesn’t know that so passes along the request for the hub to decide.

2 Likes
10

??? MAC addresses are only locally significant, and the hub ID would only have Hubitat themselves in common. I'm pretty sure Hubitat doesn't provide an API that anyone can use to look up the IP address for any given hub ID.

So, when the device is moved, other than it checking in with the cloud service (so the service can discover the new IP), explain the exact process the cloud service can use to know its IP address.

(I'm assuming typical/common use, where there's no DNS entry following the device around)

I believe that the hub must have checked in to the cloud service at least once from its present location.

11

The external cloud service doesn’t need to know the hub’s ID or current public IP address.

The hub checks in with the Hubitat cloud service, which is tied to the hub ID, a unique ID tied to the hardware that does not change after a full reset (much like a MAC address).

The external service checks in with Hubitat’s cloud relay, which forwards the request to the hub.

At least that’s my understanding of how a log warning like this could persist if someone buys a used hub, and the previous owner didn’t shut off something like an Alexa skill, or whatever the equivalent for the google assistant is called.

3 Likes
12

Think of the HE Cloud service as a postman, it receives requests, and passes them along...

3 Likes
13

So, Hubitat provides a service which makes an additional level of redirection available? That adds an additional point of failure, and seems even more beyond the local control focus Hubitat preaches. AFAIK, none of the cloud integrations (Aladdin Connect, Life360, LG Thinq) I use flow through Hubitat.

Or is it that the cloud service may be Hubitat itself (e,g, a Dashboard)?

14

Well, some users chooses to integrate with a cloud-based service to perform a function that isn’t possible to accomplish locally.

For those that do, Hubitat’s cloud relay does act as a middle man, as far as I know. Although I am not a developer myself, and certainly can’t speak to every single integration, including all those created by community developers.

Personally, I prefer that arrangement, since I can avoid exposing any details of my Hub or other related information about my home’s connection to the WAN directly to other services that may not be as privacy conscious as Hubitat is.

Although, I believe it is also possible to get this morning on your Hub from a Hubitat related cloud service itself, such as the mobile app.

1 Like
15

Can you give an example of a third-party cloud integration which flows through Hubitat?

16

The Amazon Alexa skill.

1 Like
17

Or anything the user enters a cloud maker API endpoint into. Or a rule machine cloud endpoint. Or, I assume any community integration that makes use of a Hubitat–related cloud endpoint.

1 Like
18

But that's a Hubitat provided integration.

19

Yes. Perhaps I misspoke or you misunderstood me.

It is not impossible for your hub to directly connect to another provider’s cloud service. But there are also many external cloud services for which Hubitat can serve as an intermediary.

Edit: it sounds like you are interested in discussing that more. Please consider starting another thread, since we are getting pretty off topic from the OP’s issue.

1 Like
20

Apps can expose endpoints (cloud or local) if they use OAuth, but @marktheknife is correct we are off topic.

3 Likes