... app might be deleted that is causing this. I haven't deleted any apps in weeks that I can recall. This just started showing when I upgraded from 2.3.4.116 to 2.3.4.119.
Since this seems to happen it would be nice if deleted apps/rules were in some kind of log where we could track things like this down. I have no idea where to start here.
It will be an app that has an external component, usually something like Life360…
Okay I know what it is. Turns out it was doing it on 116 I just didn't notice it. It started earlier today. I have a Inovelli ZEN45 light strip that I have had sitting here and I played around with it today. I installed it and then got the Inovelli drivers package from Package Manager. When I was done I removed the device for now but the driver package was still installed. Why a driver would show as an app I don't know. At any rate I've removed that package. So I'm assuming at 47 minutes past the next hour it will not complain again. It had been hourly since installing that package and then removing the device. I'm assuming that it should not do that. I'll try to point the author to this.
Well the author is Inovelli.... 
My guess is you switched from using Homebridge + PlugIn to the built-in HomeKit integration. Looks to me like that Homebridge plugin is still trying to talk to the Hubitat hub.
No cuz it really did start when I was fooling with the Inovelli drivers. I switched from Homebridge to Homekit when it was first available and the errors just started today at 10:47am which was 42 minutes after I removed the device that the drivers were being used for.
For the record I didn't make any rules with the light strip in it I just played with it from the devices page.
It won't; this is hitting an Oauth endpoint, which is only available for apps, and it must be something on your LAN since it's local and not cloud. HomeBridge is a good guess above, though I don't know if it uses this path off the top of my head (that offers good clues sometimes). It definitely can't be the Inovelli driver, or any driver, and I don't think HPM uses Oauth either, so it alone also probably doesn't matter.
pluginStatus() is function in @tonesto7's Homebridge Hubitat 2.0 integration. This is why I am guessing it is Homebridge running on the local LAN.
I uninstalled Homebridge 2.0 days ago. Thirty more minutes and we will see if removing the Inovelli Advanced Drivers took care of it. 
You uninstalled the Hombridge App on Hubitat? Or removed the Hubitat Homebridge PlugIn from your local server running Homebridge?
"/pluginStatus" is definitely an exposed endpoint of the Homebridge Hubitat 2.0 OAUTH App. Also, "/devices" is another endpoint of this app.
I removed the Homebridge App on Hubitat.
This won't fix it.
What @ogiewon has indicated is what you have to do to get rid of that endpoint being hit on your hub.
Yea, that is exactly why the plugin code running on your Homebridge server can no longer communicate with that app on your Hubitat hub. The errors in your logs are coming from your Homebridge server.
Remove the Homebridge Hubitat 2.0 Plugin from your Homebridge server.
Hmmm okay well I'll shut that down I should have already. Not sure why it wouldn't start logging until today and right after I fooled with the Inovelli light strip. Weird. But ya looking at the log over there it is showing errors at the same time and prior to then as well.
Thanks!
Yes, I understand. Perhaps your log history simply does not go back any further in time? Maybe the old entries have been purged already from the logs?
No I'm being a total idiot today... that's the LIVE log... I'll go hide in the corner now and await punishment. 
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
