Warning cloud request error

🛎️ Get Help
1

I purchased a used hub and have it registered to me on portal. At this time there are no apps installed and no devices installed. I believe it was scrubbed clean but I keep getting this on the hub log. (16 times today so far)

sys:12019-10-15 05:52:01.079 pm warnReceived cloud request for App 11 that does not exist, path: /webhook

The only item I could find on a search involved a hub that was part of a hub connect network that was still getting hit by Smartthings. I have not installed this app, or any other so far.

2

I'd do a full reset yourself just to be sure. If you have no apps or devices, there should be no impact.

What you're seeing is likely something cloud service that is still trying to connect to your hub (not sure if that's a path HubConnect uses, but since the theme is that it's no longer installed on your hub, I guess that part is of little import to you). I think a reset might generate a different cloud endpoint/URL/ID (not sure how it matches), which is why this might work around that until the original person removes whatever it was on the cloud side, though I'm not 100% sure it will (if it uses hub UUID, then it won't), and I'm not sure if Support will chime in on this since I don't think Hubitat terms officially allow for transfer of device ownership.

In the meantime, these are really just warnings, not errors, and shouldn't cause any problems unless there are excessively frequent logs of these. (The original app had undoubtedly long lost its OAuth on your hub that would allow it to do anything.)

3

I believe they do as to get it registered on the portal to me Bobby had to make some manual entries on Hubitat's end to remove previous owner as administrator.
I will try the complete reset again. Nothing to lose at this point.

edit. tried full reset (on 8081 port) and all I'm getting is "Error: network error"

4

If the Hub ID that is used to generate outside HTTP calls, for example from the Maker API, https://cloud.hubitat.com/api/[HUB_ID]/apps/[APP#]/devices/[Device ID]?access_token=[TOKEN]
is not reset, which I assume it's not, that means that you'll receive outside cloud calls forever and it will continue to post that error since you don't have an app installed that matches that number and the token won't match. They would have to reset the HUB_ID somehow to allow Cloud calls to the old hub ID to not be directed to you. Let us know if they are able to resolve this. If not, the market for buying or selling used hubs just disappeared.

5

well I reset hub, installed rule machine, dashboard, simple lighting and motion lighting. Error changed number but still there:
sys:12019-10-15 09:55:28.663 pm errorError at point 184a6b Expired JWT

sys:12019-10-15 09:54:18.348 pm warnReceived local request for App 33 that does not exist, path: /menu (was 11)

sys:12019-10-15 09:54:18.229 pm warnReceived local request for App 33 that does not exist, path: /menu (was 11)

6

I'll bet the previous owner has a hub link app installed in his smartthings account.

Resetting the hub doesn't reset a new UUID that identifies the hub.

7

Actually just getting ready to contact Bobby for assistance and realized the error changed from cloud to local error. Could be reset got rid of warnings. Will update in a few days.

8

Oh well, still have the problem. this morning I thought maybe it's a cloud request from Hubitat as I use the app on my other hub and Hubitat maybe looking for update. Created the virtual device for the iphone but still getting warnings.
sys:12019-10-16 03:47:19.651 pm warnReceived cloud request for App 11 that does not exist, path: /webhook

sys:12019-10-16 03:44:24.593 pm warnReceived cloud request for App 11 that does not exist, path: /webhook

sys:12019-10-16 03:40:35.549 pm warnReceived cloud request for App 11 that does not exist, path: /webhook

sys:12019-10-16 03:37:07.152 pm warnReceived cloud request for App 11 that does not exist, path: /webhook

sys:12019-10-16 02:20:52.386 pm warnReceived cloud request for App 11 that does not exist, path: /webhook

sys:12019-10-16 02:17:48.578 pm warnReceived cloud request for App 11 that does not exist, path: /webhook

sys:12019-10-16 02:09:25.261 pm warnReceived cloud request for App 11 that does not exist, path: /webhook

sys:12019-10-16 02:09:25.073 pm warnReceived cloud request for App 11 that does not exist, path: /webhook

sys:12019-10-16 02:07:34.854 pm warnReceived cloud request for App 11 that does not exist, path: /webhook

sys:12019-10-16 02:01:25.191 pm warnReceived cloud request for App 11 that does not exist, path: /webhook

sys:12019-10-16 02:00:57.670 pm warnReceived cloud request for App 11 that does not exist, path: /webhook

sys:12019-10-16 01:52:58.199 pm warnReceived cloud request for App 11 that does not exist, path: /webhook

sys:12019-10-16 01:44:01.842 pm warnReceived cloud request for App 11 that does not exist, path: /webhook

sys:12019-10-16 01:26:22.619 pm warnReceived cloud request for App 11 that does not exist, path: /webhook

Have forwarded the info to Bobby for possible solution.

9

I bet it is Life360. The previous user probably used Life360 and didn’t clean it out of their system cleanly, so right now the Life360 is trying to call the hub to provide location updates. The Hub ID stays the same, even after a soft reset and that is used for cloud integrations. I am sure that Bobby can fix that for you

10

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