core: Netatmo Integration error at Startup: Error during webhook registration - 400 - Bad request
The problem
At startup of home assistant the Netatmo Integration generates a error message. This does not seem to be critical for my usage as it seems to work fine, I’m only using a Netatmo weather station.
Environment
- Home Assistant Core release with the issue: 0.115.3
- Last working Home Assistant Core release (if known):
- Operating environment (OS/Container/Supervised/Core): Supervised
- Integration causing this issue: Netatmo
- Link to integration documentation on our website: https://www.home-assistant.io/integrations/netatmo
Problem-relevant configuration.yaml
No yaml based configuration, connected with Netatmo trough the Netatmo Intergration UI.
Traceback/Error logs
Log Details (ERROR)
Logger: homeassistant.components.netatmo
Source: components/netatmo/__init__.py:159
Integration: Netatmo (documentation, issues)
First occurred: 9:48:37 AM (1 occurrences)
Last logged: 9:48:37 AM
Error during webhook registration - 400 - Bad request - Allowed ports for webhooks are 443 and 80. (21) when accessing 'https://api.netatmo.com/api/addwebhook'
Additional information
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 25 (10 by maintainers)
Have you set the external url under
/config/core?The webhook is not required for most Netatmo devices to work, but it improves responsiveness. In case of outdoor cameras and smoke detectors it is actually required.
To use the webhook you eiher need to expose HA to the web (securely) for example through a reverse proxy or you subscribe to Nabu Casa, which does all that for you and supports the project.
If you don’t need all of that, you can safely ignore that message.
Found, it was set from before Nginx with: 8123, and I forgot to correct it … in 2 minutes you solved a 15 day gripe, thank you very much!
Light.netatmo has already started working too!
The webhook message can be safely ignored for weather stations as it does not provide data this way and is always polling. The polling frequency can not me changes by the user.
Netatmo had server issues in the past days. Usually the sensors just come back once the backend is fixed.