it’s something on your HA machine, but not HA and not internal to HA. Otherwise it would have a docker IP. Unless it’s just lazily set to local_host and resolving the IP, which is probable now that I think about it. It’s going to be hard to figure out because HA won’t know where it came from.
is that a warning or error? If it’s a warning, the webhook is probably still creating the event. Try subscribing to webhook events and seeing what comes through.
@sloma Are you sure that is HA’s ip address?
It could then be an addon (try disable them to see which one it is)
If it is an ip on your network, try switching off your mobile(s), and check if the problem disappears…
you should first disable the sensor in the mobile app so it knows to stop sending that data
So the error can also happen if for example you removed a mobile app integration. The easiest way to clear this error is to start fresh with the app and integration. It happens when users remove things on accident that are linked to the apps. I have a bunch of android devices here so sometimes it takes me longer to find the faulty device.
If you have access to .storage in your config directory you can check if its caused by mobile app by looking to see if the webhook ID exists in the mobile_app file in .storage