Webhook identification

I’m having trouble figuring out the origin of a webhook in my hass log file.
Is there any way i somehow can identify what component (or what ever it is) that is making an entry in my log every 2-10 secs?

    2019-06-20 08:37:02 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook 4a35dd5f55dd399f5a32aeb63547961ce82df3e20da08d21e0dfc9db50148fd2
    2019-06-20 08:37:27 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook 4a35dd5f55dd399f5a32aeb63547961ce82df3e20da08d21e0dfc9db50148fd2
    2019-06-20 08:37:53 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook 4a35dd5f55dd399f5a32aeb63547961ce82df3e20da08d21e0dfc9db50148fd2
    2019-06-20 08:38:03 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook 4a35dd5f55dd399f5a32aeb63547961ce82df3e20da08d21e0dfc9db50148fd2
    2019-06-20 08:38:10 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook 4a35dd5f55dd399f5a32aeb63547961ce82df3e20da08d21e0dfc9db50148fd2
    2019-06-20 08:38:25 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook 4a35dd5f55dd399f5a32aeb63547961ce82df3e20da08d21e0dfc9db50148fd2
    2019-06-20 08:38:28 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook 4a35dd5f55dd399f5a32aeb63547961ce82df3e20da08d21e0dfc9db50148fd2
    2019-06-20 08:38:53 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook 4a35dd5f55dd399f5a32aeb63547961ce82df3e20da08d21e0dfc9db50148fd2
    2019-06-20 08:38:58 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook 4a35dd5f55dd399f5a32aeb63547961ce82df3e20da08d21e0dfc9db50148fd2
    2019-06-20 08:39:04 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook 4a35dd5f55dd399f5a32aeb63547961ce82df3e20da08d21e0dfc9db50148fd2
    2019-06-20 08:39:21 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook 4a35dd5f55dd399f5a32aeb63547961ce82df3e20da08d21e0dfc9db50148fd2
    2019-06-20 08:39:25 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook 4a35dd5f55dd399f5a32aeb63547961ce82df3e20da08d21e0dfc9db50148fd2
    2019-06-20 08:39:29 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook 4a35dd5f55dd399f5a32aeb63547961ce82df3e20da08d21e0dfc9db50148fd2
    2019-06-20 08:39:34 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook 4a35dd5f55dd399f5a32aeb63547961ce82df3e20da08d21e0dfc9db50148fd2

When i visit https://my-hass-address/api/webhook/4a35dd5f55dd399f5a32aeb63547961ce82df3e20da08d21e0dfc9db50148fd2
i get the following:

405: Method Not Allowed

Thx in advance :slight_smile:

Are you using the Ariela android app??

yes? Is thats whats calling it?

The new mobile_app component is entirely based on webhooks. Home Assistant Companion for iOS, Hassapp for iOS, Ariela for Android and HA Client for Android all use mobile_app. If you are using one of these apps, its possible that’s what the webhook logs are referring to.

1 Like

If it’s an 'Unregistered" webhook, it indicates that it is not configured correctly in Hass right? How do I allow/registre the webhook, to allow the sensor data (if that is it) to get through?
There is a lot of sensor data being send from Ariela and i have a lot of them configured. So it might be one of them i guess.
But I haven’t configured any of them… They have just worked. After the implementation of the mobile_app in ariela. Used MQTT before. I could of course remove it again and go back to MQTT, but if there is a way to fix it, I would prefer that

Thanks for the pointer. It looks like it was the Device Tracker - Mobile App in Ariela Pro that where the origin of the problem. Thanks a lot @aidbish and @robbiet480
Whatever the reason for it is not working, i’ll switch to MQTT for device tracking for now
Cheers

1 Like

Thanks for this, has been driving me made for hours trying to work out why I kept getting this received message for unregistered webhook on my system, was an old Ariela config on another tablet I had

Thanks.
I got these messages as well and could link them to the mobile app. I removed the integration for the app, but now am still getting the same error messages.

Did I overlook something?

UPDATE: I see references in my .storage (/config/.storage/mobile_app). Should I empty that? How?

I am still getting

WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook 26fcff4f1bcd05fabfd1eecfe61d58f70edd487e4b78e6d887406b64be792330

I have seen in the forum that people believe these messages are caused by an improperly configured mobile apps. I have tried three different ones in the past. Ariela, HA Client and Home Assistant. I have deleted all as well as the integration and mobile_app: from my configuration.yaml file. Nothing helps. On reboot I get this warning in my error log. Shows up about once a minute. How do I make it stop?

I have the same messages in the log file, every 3 or 4 minutes 3 lines:

Mar 22 15:17:06 pi hass[16268]: 2020-03-22 15:17:06 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook 008712b85516c1dec7e15287fe38a4c9b4613212748eada1572d113e362ef41f
Mar 22 15:17:06 pi hass[16268]: 2020-03-22 15:17:06 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook 008712b85516c1dec7e15287fe38a4c9b4613212748eada1572d113e362ef41f
Mar 22 15:17:06 pi hass[16268]: 2020-03-22 15:17:06 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook 008712b85516c1dec7e15287fe38a4c9b4613212748eada1572d113e362ef41f

When I uninstall the official HA Android app from my phone I do not get any of these. My app was working fine, so it seems there is a problem somewhere. Did any of you report an issue about this already?

Hi there,

Sorry to revive an old thread, but is there any way to identify what is calling a specific webhook id? I have a huge number of warnings similar to the ones above

Received message for unregistered webhook xxxxx

and I cannot seem to figure out what is calling it. I had one of the unofficial apps on a tablet, but it is removed. If not possible to identify the webhook ids, what are the top 10 candidates to check for? Will the official app (for android in my case) cause such warnings in case connection cannot be made at the time?

Please help - all those lines in my log drives me crazy :slight_smile:

I have opened a PR that adds some logging. This could prove useful in identifying the origins of requests for unregistered webhooks. :+1:

4 Likes

That looks great, it would be really helpful! Looks like it is approved as well, right?

In the meantime, any hints on how to check it manually? Or is it just trying and guessing?

Thanks.

Hello Daniel,
I not familiar with the merge, pull-request meaning, but I looks at the PR# #34882 you created.
Do we know if the enhancement has been integrated and in which version? If so, how to use and enabled the increased logs?
Thanks a lot,
Ben

It’s available with version 0.100. You’ll see the remote IP without any changes to the configuration. To get the debug logging you have to modify your configuration to look something like this:

logger:
  default: warning
  logs:
    homeassistant.components.webhook: debug

You can also do it on the fly with the logger.set_level service.

I thought I’d reply here to say I’m seeing my Google Home devices causing this message to my 2nd Home Assistant instance (I’m setting up a Pi4 to replace my existing instance).

Example

Received message for unregistered webhook b866374971feef8ccaf2ff56a3164fefdd1e8fab6380f1a1dde5bc9dd49e725d from 192.168.x.x

Interestingly enough that webhook is showing as configured on the Pi3:
Local Support (google_assistant)

I’m guessing this is related to the Nabu Casa integration which I have yet to migrate to the new instance on the Pi4.

1 Like

Hi again, great update! It should be easier to find the source of webhooks now. In my case, the IP being logged is my own external IP-address on the internet. When I try to access it, I come to my router login, so I’m still not sure why it happens. Anyone capable of helping me on the way to further identify what it can be in this case? I’m using DuckDNS, could this be behind it? I can’t think of anything else that would appear from “outside” as often as this message appears.

Any hint appreciated. Thanks.

Did you turn on debug-logging to see the content of the webhook-call? I’ve mentioned how to do that a few posts above.

Ah, sorry, I read only Warning, but I see know that the detail says debug level for webhook. Sorry, my bad. Will enable it and check again. Thanks!

I’m seeing a simular log from my google nest mini as well. Started showing up after I upgraded to HassIS 4.8.

2020-06-02 14:18:28 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook c4169d04c52bddc37ed3beee3d737be63065cea01e7a38dc562152e8e364ef43 from 192.168.1.66

I’m very new (about a week) to Home Assistant, so still learning but, I have no idea what this means.