Error during webhook registration - 400 - Bad request

Configuration
42

@cgtobi
Hi Tobi, to make sure I understand, I need to change the default HA port from 8123 to 80 or 443 and do a port forward in my router to selected port get it to work properly?

43

I would rather suggest to open port 80 on your router and forward that to 8124 or even better setup a reverse proxy that does ssl encryption for you and expose that in front of HA.

44

Seems everytime my Home Assistant restarts due to a blackout it can’t set up the webhooks for Netatmo, which essentially breaks all my climate automations. Using Nabu Casa as a paying customer.

2021-02-04 07:29:03 ERROR (MainThread) [homeassistant.components.netatmo] Error during webhook registration - 403 - Forbidden - Invalid access token (2) when accessing ‘https://api.netatmo.com/api/addwebhook’

It usually works if I reboot the computer, but not this time.

45

What exactly do you refer to by “your Netatmo”?
Are you using a dev account or HA Cloud Link?
By set up the webhook, you mean by using the service call netatmo.register_webhook?
Have you checked your webhook status on dev.netatmo.com whether it is banned?

46

Edited post, wrote Netatmo instead of HA.

47

The Netatmo app page says green status for the app and webhooks.

Seems like I use the dev account ie manual configuration in configuration.yaml.

Edit: Deleted Netatmo, added using HA Cloud Link, now it is working. Just that all entities change names, so I have a bit of work to do now with all automations and Lovelace. Oh, well.

Thanks anyway.

48

I would not recommend that if you rely on webhooks being functional. The dev account is really the recommended way in that case.

49

Thanks, yes I switched back to dev account and it works now, apparently needed to re-register for some reason. Still all entity names have changed, but no worries.

1 Like
50

I’ll see if I can replicate this issue.

51

Might all be about entities having changed names, which broke down when I rebooted and every entity name was refreshed. Not really a webhook error - was the only error in my log file. So not really a bug, just had no clue that the entity names had changed.

52

Ok, but that shouldn’t have happened form rebooting though.

53

Things worked as they should until I had a one of three phases blackout at 03 this night and being aslepp my UPS ran out of power after a couple of hours. When things started up again the entity names had changed apparently. Maybe the change is initiated with a new Netatmo session and old entity names were working until the reboot?