So, I have had to reset my device, and restore from backup. Since then, I am getting the following error message that repeats 3 times every 15-30 seconds:
Received cloud request for App X that does not exist, path: /events from X.X.X.X
Each group seems to be from an AWS address block, some from the 66.102.6.0 block, some from the 74.125.210.0 block. I don't seem to be missing any functionality, but the constant connection attempts are filling the log and making troubleshooting difficult.
I have checked the ActionTiles integration, which I have removed, and that eliminated a few attempts. I have not set up Life360 on my Hubitat, and I do not have an account on that service.
Amazon Alexa (integrated in Hubitat with Echo Speaks)
iComfort S30 (unable to integrate) Alarm.com (integrated in Homebridge, single panel)
Homebridge v2 (integrated in Hubitat)
Nest Cameras (integrated in Hubitat with Google SDM API)
Chamberlain Garage Door (integrated in Hubitat with MyQ Lite)
Lutron Integration (integrated in Hubitat)
IFTTT Integration (integrated in Hubitat)
Hue Bridge (integrated in Hubitat)
Echo Speaks (integrated in Hubitat)
If you only removed the Hubitat side, this could cause precisely a message like the above. The log entry is telling you that something external to the hub is trying to reach something that used to be installed on the hub but no longer exists. Make sure you also log in to your AT account and remove the Hubitat association there. (That being said, I don't know if this exact message is one AT would do; I don't recognize that endpoint off the top of my head, and as is often the case with these, it's fairly generic so it's likely multiple apps may use it.)
The solution, in any case, is to find the other thing--but it exists outside your hub. If you really can't figure it out, you could restore an old backup and see if any app IDs match the ones in this log entry (the "X" you've edited out; you'd see this in the URL when viewing the app in the admin UI). Keep a current backup saved locally if you do this so you can restore it later without depending on the on-hub backups. You can also ignore it--it's not an error per se--but I'd personally probably prefer to find it if I could. (And if it's a cloud integration, Hubitat might like that too. Haha.)
