It is a (slightly) different error. And this one makes sense. It tells the user that there is an issue with the configuration/setup.
Part of this error was already included in my first posting
2021-06-25 06:21:29 ERROR (MainThread) [homeassistant.components.netatmo] Error during webhook registration - 400 - Bad request - Allowed ports for webhooks are 80, 88, 443 and 9443. (21) when accessing 'https://api.netatmo.com/api/addwebhook
Unfortutaly I’m not very experienced with code and have absolutely no clue what to do about it. If anybody could give me a hint. Any help would be very much appreciated.
As I don’t need my HA installation to be accessible over the internet is this really an issue in terms of functionality, usability and stability. Or can I simply ignore the port-message?
As for the other one: Why is it referring to [homeassistant.components.light]?
23:31:42 WARNING (MainThread) [homeassistant.components.light] Platform netatmo not ready yet: None; Retrying in background in 30 seconds
I know the webhook-unregister-part in documentation but do not know how to use it
If the lights show as unavailable the issue usually is that webhook is banned by Netatmo. To solve that unregister the webhook, go to the Netatmo Developer Page to unban your webhook and then register the webhook.
As the error message reports your instance is not exposed via one of the valid ports (according to Netatmo) approved for webhook registration. To make use of Netatmo webhook events you have to expose your instance via 443 (or 80/88/9443) or use the Nabu Casa remote service to handle this for you. If you have further question, just let me know what’s not clear.
If you don’t need/want to use the webhook events you can safely ignore the message.
2 Likes
Thank you for the clarification.
1 Like
Hi,
I have been struggling for weeks with the Netatmo integration, which is losing connection for about 80% of the time, but also randomly comes back. I have Nabu Casa installed, and using the cloud integration (though also have a netatmo dev account with an app that I do not use).
i have done a totally virgin install, on a device (RPi5) that is plugged directly into the router.
When the integration fails, I can ping api.netatmo.com from my computer, but not from the terminal of the device.
Logs from ping are below. I did not add the port 443. I do not seem to have this problem on a container install on my NAS, but want to use HAOS.
Are you able to offer any insights? They would be much appreciated - you seem to know more than most. The whole sorry tale is here: Netatmo 443 error · Issue #120292 · home-assistant/core · GitHub
Thanks:
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host api.netatmo.com:443 ssl:default [None]
2024-06-27 20:56:10.612 DEBUG (MainThread) [homeassistant.components.ping.helpers] ping address: api.netatmo.com
2024-06-27 20:56:10.613 DEBUG (MainThread) [homeassistant.components.ping.helpers] Error resolving host: api.netatmo.com
2024-06-27 20:56:10.613 DEBUG (MainThread) [homeassistant.components.ping.coordinator] Finished fetching Ping api.netatmo.com data in 0.002 seconds (success: True)
