I'm getting these log warnings after having updating from the old to the new app:
Received cloud request for App 208 that does not exist, path: /mobile/0d66b596-3855-4fd9-ab9d-229822d0dc1b/mobile-app-events from cloud
There's a set of these App 208 messages with what looks like a GUID for my phone, and another set with a different GUID for my wife's phone.
There's a new set of messages logged each time I open the app, switch to it from a different app, or wake up my phone when it is the frontmost running app.
This is caused by removing a cloud based integration from hubitat but not shutting it down from the provider source. It will still keep making calls to the API.
This sounds like something different. It only occurs when I open the HE app on my phone. And it does it everytime I open the app on my phone. If it was coming from some cloud app why would the phone app have any affect on it. And I haven't deleted any cloud connection for probably over a year. And it hasn't been happening till the latest phone app update.
In my case it's app 2504. Clicking on the warn symbol does nothing.
sys:12024-11-04 09:54:01.099 AMwarnReceived cloud request for App 2504 that does not exist, path: /mobile/46461864-B8D0-4DD3-8043-987EB21453DE/mobile-app-events from cloud
Simply open a web browser on your pc and go to the ip address of your hub. Click logs. I could never do more then dashboards on the phone app. Phones are horrible to do rules on or add things.
On my wife's phone I installed the new Hubitat Elevation Android app by following the prompt that I got after opening the old Hubitat Mobile app, so for a certain amount of time both apps were installed on her phone.
On my phone I first uninstalled the old Hubitat Mobile Android app before installing the new Hubitat Elevation app, with the same result: the log messages that I see attributable to both phones are identical except for the phone IDs.
FYI I'm currently on a C7 running 2.3.9.184.
Also, if you could explain "removing a cloud based integration from hubitat but not shutting it down from the provider source. " and how it relates to the Hubitat mobile apps I might be able to do more effective debugging of this phenomenon.