So I'm still working through migrating my devices from Smartthings to the new C7 hub, running the latest firmware.
I'm definitely still learning the nuances of Hubitat and can't say how long this has been spamming my logs, but I'm getting thousands of the below message:
[sys:1]2020-12-06 08:52:21.209 am warnReceived local request for App 9 that does not exist, path: /device/807d3a3e0591 from unknown
Seriously, like a dozen of these message per second.
As far as setting up Apps, I haven't done a whole lot of that yet, just Ecobee and Echo, which are both working fine. I've really just been adding devices. I did "explore" the Apps section a bit when I first connected it up a month or so ago, but never fully committed to setting anything up. Just installed the app, looked at the options, then deleted it.
I'm assuming it has something to do with that, but how can I figure this out? I feel like this may be causing some simple automations to not get process due to the amount of message spam I'm getting here so it is becoming a larger issue and the logs aren't giving me a whole lot to go off of here.
Did you try HubConnect, by any chance? If so, please remove the HubConnect SmartApp instance on SmartThings. Even a second Hubitat hub running HubConnect could cause something like this as well.
Or, if you tried something like HomeBridge on a local server, it may still be trying to connect to the hub as well.
Any chance you installed Maker API on your hub, then configure something like Node-RED to communicate with the hub?
Basically, there is a piece of code running somewhere, that is trying to communicate with App 9 on your hub, that you probably removed.
Yeah that's what I've gathered as well. No, I haven't linked any hubs yet and just validated that my Smartthings hub isn't linked or sending any messages.
Haven't gone into any depth with anything yet, no Maker API or Homebridge, don't even use those.
This one really has got me stumped. I wish this was some way to get some more identifiable information from the logs.
And just like that I remembered something and think I found it. It wasn't a built in app, but I was poking around the external Harmony integration and I think that was it, although it appeared to be working, as soon as I removed the code the messages stopped. I'll look into this integration later I guess. Thanks for getting my brain moving in the right direction!
Add Harmony to that list as well, so I've shut down, Bond, Harmony, Smartthings, and Hue an still seeing the messages.
Would it say cloud if it was a cloud app? Wondering if it would be beneficial to shut down my LAN and see if messages are still coming through. Might help in continuing to troubleshoot where this is generating from.
Or since it says local request does that mean that is is not a cloud connection? Just confirming.
One simple way to determine if the call is coming via the LAN versus the WAN would be to simply disconnect your internet connection from your router. If the error subside, it is a cloud system attempting to connect. Otherwise it is some on the LAN, or even possibly something on the hub trying to make a http call to the hub itself. Perhaps a RM rule with a http get/post action?
Went through regression testing. Added a firewall rule to my Hubitat to block all incoming traffic and still got the messages so I knew it was something on my local network.
Turns out it was my Konnected Alarm Panel, which is now setup lol.
I must have started the setup some time ago and then backed out, so I re-added the app, went through the install process and voila, no more messages.
