Closed atchoum31 closed 1 year ago
Alomon31
commented
2 years ago So sad my ISP does not allow renewing public IP! Still waiting for a fix :( We didn't mention our setups, which might help finding the cause: here HA runs under Raspbian, as a Docker container (supervised version).
Friedi1970
commented
2 years ago Just to make sure, everyone of you that is having this issue is using the HA Cloud Link option for the Netatmo integration?
Not for me. I'm using the integration via thé configuration.yaml
Neither for me :( Even worse now: after restore of 2022.2.9 it also doesn‘t work :(
atchoum31
commented
2 years ago If I restart my router (and obtain a new external IP address), the Netatmo integration works again. (without rebooting HA)
Amazing... it worked 🥇
Same for me. Working after a public IP address renewal
Friedi1970
commented
2 years ago Today I updated to 2022.03.03 and I updated to the latest supervisor and I deleted the Netatmo integration. After the HA found new devices for integration I reconfigured Netatmo again with the same result:
Logger: homeassistant.config_entries
Source: components/netatmo/data_handler.py:166
First occurred: 19:51:15 (2 occurrences)
Last logged: 19:56:39
Error setting up entry Home Assistant Cloud for netatmo
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/aiohttp/connector.py", line 986, in _wrap_create_connection
return await self._loop.create_connection(*args, **kwargs) # type: ignore[return-value] # noqa
File "/usr/local/lib/python3.9/asyncio/base_events.py", line 1056, in create_connection
raise exceptions[0]
File "/usr/local/lib/python3.9/asyncio/base_events.py", line 1041, in create_connection
sock = await self._connect_sock(
File "/usr/local/lib/python3.9/asyncio/base_events.py", line 955, in _connect_sock
await self.sock_connect(sock, address)
File "/usr/local/lib/python3.9/asyncio/selector_events.py", line 502, in sock_connect
return await fut
File "/usr/local/lib/python3.9/asyncio/selector_events.py", line 537, in _sock_connect_cb
raise OSError(err, f'Connect call failed {address}')
OSError: [Errno 101] Connect call failed ('169.254.72.2', 80)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 335, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/netatmo/__init__.py", line 144, in async_setup_entry
await data_handler.async_setup()
File "/usr/src/homeassistant/homeassistant/components/netatmo/data_handler.py", line 108, in async_setup
await asyncio.gather(
File "/usr/src/homeassistant/homeassistant/components/netatmo/data_handler.py", line 210, in register_data_class
await self.async_fetch_data(data_class_entry)
File "/usr/src/homeassistant/homeassistant/components/netatmo/data_handler.py", line 166, in async_fetch_data
await self.data[data_class_entry].async_update()
File "/usr/local/lib/python3.9/site-packages/pyatmo/camera.py", line 649, in async_update
await self._async_update_all_camera_urls()
File "/usr/local/lib/python3.9/site-packages/pyatmo/camera.py", line 659, in _async_update_all_camera_urls
await self.async_update_camera_urls(camera_id)
File "/usr/local/lib/python3.9/site-packages/pyatmo/camera.py", line 724, in async_update_camera_urls
] = await self._async_check_url(
File "/usr/local/lib/python3.9/site-packages/pyatmo/camera.py", line 731, in _async_check_url
resp = await self.auth.async_post_request(url=f"{url}/command/ping")
File "/usr/local/lib/python3.9/site-packages/pyatmo/auth.py", line 335, in async_post_request
async with self.websession.post(
File "/usr/local/lib/python3.9/site-packages/aiohttp/client.py", line 1138, in __aenter__
self._resp = await self._coro
File "/usr/local/lib/python3.9/site-packages/aiohttp/client.py", line 535, in _request
conn = await self._connector.connect(
File "/usr/local/lib/python3.9/site-packages/aiohttp/connector.py", line 542, in connect
proto = await self._create_connection(req, traces, timeout)
File "/usr/local/lib/python3.9/site-packages/aiohttp/connector.py", line 907, in _create_connection
_, proto = await self._create_direct_connection(req, traces, timeout)
File "/usr/local/lib/python3.9/site-packages/aiohttp/connector.py", line 1206, in _create_direct_connection
raise last_exc
File "/usr/local/lib/python3.9/site-packages/aiohttp/connector.py", line 1175, in _create_direct_connection
transp, proto = await self._wrap_create_connection(
File "/usr/local/lib/python3.9/site-packages/aiohttp/connector.py", line 992, in _wrap_create_connection
raise client_error(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host 169.254.72.2:80 ssl:default [Connect call failed ('169.254.72.2', 80)]
Please repair this great integration!!!
Ottmar0815
commented
2 years ago After restarting my router it works fine. Interesting.
Ottmar0815
commented
2 years ago After a restart of HomeAssistant same problem again.
cgtobi
commented
2 years ago What custom components do you have installed?
atchoum31
commented
2 years ago What custom components do you have installed?
I have : HACS, Garbage Collection and adaptive_lighting
Friedi1970
commented
2 years ago Is it possible that there is a problem of the integration with Nabu Casa which I use for cloud integrations?
Alomon31
commented
2 years ago Is it possible that there is a problem of the integration with Nabu Casa which I use for cloud integrations?
I don't use it
Friedi1970
commented
2 years ago What custom components do you have installed?
HACS, Deutscher Wetterdienst, Auto Backup, ICS, Alexa Media Player, Meross Integration and Nuki Lock. All of them since ages ...
cgtobi
commented
2 years ago For those who still suffer from this issue please raise the log level for the Netatmo integration to DEBUG and check your log file for relevant entries. Maybe even set the log level for pyatmo to debug as well to gather even more insights. Be aware that this may contain sensitive information. So either clean it up/redact the data before posting or send me the information on Discord via PM.
Log config:
logger:
logs:
pyatmo: debug
homeassistant.components.netatmo: infoFor those who still suffer from this issue please raise the log level for the Netatmo integration to DEBUG and check your log file for relevant entries. Maybe even set the log level for pyatmo to debug as well to gather even more insights. Be aware that this may contain sensitive information. So either clean it up/redact the data before posting or send me the information on Discord via PM.
Log config:
logger: logs: pyatmo: debug homeassistant.components.netatmo: info
Done (Discord). Thanks!
Molodax
commented
2 years ago After restarting my router it works fine. Interesting.
After a restart of HomeAssistant same problem again.
Exactly the same behaviour. Also, in my case, only components of weather station become unavailable while climate and camera are still working.
Friedi1970
commented
2 years ago For those who still suffer from this issue please raise the log level for the Netatmo integration to DEBUG and check your log file for relevant entries. Maybe even set the log level for pyatmo to debug as well to gather even more insights. Be aware that this may contain sensitive information. So either clean it up/redact the data before posting or send me the information on Discord via PM.
Log config:
logger: logs: pyatmo: debug homeassistant.components.netatmo: info
I did this but there is nothing new in the logs. Where shall the additional information be?
Btw. I updated today to ha-2022.03.04; still the same problem —> no Netatmo
Friedi1970
commented
2 years ago ha-2022.03.05 Still no Netatmo and still the same error in the logs.
Friedrieck
commented
2 years ago I had issues of this kind in the past, but it was limited to the Presence cameras. If it is the same cause, then now it affects the entire integration setup.
As I wrote before, I already had similar issues in the past with my Presence cameras. The novelty here is that the whole Netatmo integration was not set up.
But in the past, I solved my issues with the Presence cameras by rebooting them individually (power off and on), then rebooting HA.
So, for those still having the behaviour in this issue, maybe try that (if not already done)?
cgtobi
commented
2 years ago Thanks @Friedrieck for pointing that out. Since I cannot reproduce this issue it is very difficult to provide a fix.
Friedi1970
commented
2 years ago So, for those still having the behaviour in this issue, maybe try that (if not already done)?
I did this (of course) several times. Doesn't work at all.
Thanks @Friedrieck for pointing that out. Since I cannot reproduce this issue it is very difficult to provide a fix.
Unfortunately the way of @Friedrieck doesn't help.
Once all devices were there, suddenly. But after a reboot of HA the same error occurs again.
Due to the fact the problem is since core-2022.03. Wouldn't it possible to ask e.g. @frenck to support? I mean, it seems something weird since that :-/
buhito81
commented
2 years ago @cgtobi have it too, I don't know how to contact you on discord but I'd be happy to give you access to my environment and provide with whatever is needed. Relatively new to HA, so in all the above I find it complicated to figure out what I could do to generate what you'd need to reproduce.
miki3421
commented
2 years ago Same here same problem after the last release. I'm using the configuration in the configuration.yaml. Do I need to reinstall the integration? I hope not I have plenty of configuration that are dependant from this integration. Thanks
miki3421
commented
2 years ago I've tried to remove the configuration in the configuration.yaml and add with the intergration with the cloud integration and I have the same problem
Error setting up entry Home Assistant Cloud for netatmo Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/aiohttp/connector.py", line 986, in _wrap_create_connection return await self._loop.create_connection(*args, **kwargs) # type: ignore[return-value] # noqa File "/usr/local/lib/python3.9/asyncio/base_events.py", line 1056, in create_connection raise exceptions[0] File "/usr/local/lib/python3.9/asyncio/base_events.py", line 1041, in create_connection sock = await self._connect_sock( File "/usr/local/lib/python3.9/asyncio/base_events.py", line 955, in _connect_sock await self.sock_connect(sock, address) File "/usr/local/lib/python3.9/asyncio/selector_events.py", line 502, in sock_connect return await fut File "/usr/local/lib/python3.9/asyncio/selector_events.py", line 537, in _sock_connect_cb raise OSError(err, f'Connect call failed {address}') OSError: [Errno 113] Connect call failed ('169.254.68.11', 80)
SiebeRoets
commented
2 years ago Encountering the same error after upgrade to 2022.3.6
Logger: homeassistant.config_entries Source: components/netatmo/data_handler.py:166 First occurred: 10:19:54 AM (1 occurrences) Last logged: 10:19:54 AM
Error setting up entry Home Assistant Cloud for netatmo
Any progress on this issue? Rebooting does not work
Alomon31
commented
2 years ago Tried rebooting your camera, deleting the integration then adding it back? It worked for me, even after rebooting HA, now crossing fingers...
buhito81
commented
2 years ago @cgtobi have it too, I don't know how to contact you on discord but I'd be happy to give you access to my environment and provide with whatever is needed. Relatively new to HA, so in all the above I find it complicated to figure out what I could do to generate what you'd need to reproduce.
Mine is a thermostat. The relay is now completely missing and cannot be added at all anymore.
miki3421
commented
2 years ago Tried rebooting your camera, deleting the integration then adding it back? It worked for me, even after rebooting HA, now crossing fingers...
what type of installation do you have?
Fr3n3z1
commented
2 years ago Hello everyone.
I have the same issue since 1 day. I downgraded my home Assistant to core-2022.2.9, supervisor-2022.03.5, and Home Assistant OS 7.4, to get it working again. It's very boring. Do you think it will be fixed soon?
cgtobi
commented
2 years ago Is this reproducible that downgrading core/subervisor/HASS OS fixes the issue? I still can not reproduce this in any of my environments.
Friedi1970
commented
2 years ago It is. With core 2022.02.x it works. Since 2022.03. the problem started.
cgtobi
commented
2 years ago Could one of you please set up an isolated core instance of HA 2022.2, get Netatmo working and then upgrade to 2022.3?
Fr3n3z1
commented
2 years ago @cgtobi, yes i can do that. it's possible... What should I do exactly? just upgrade to 2022.03? I'am with core core-2022.2.9 and Netatmo work fine in this version... HA propose me to upgrade now in core 2022.3.6. (i will juste make a backup before ;- ))
Fr3n3z1
commented
2 years ago OK, I made a backup, I'm ready. I will update tomorrow when I get home from work. Tell me what informations you want (logs, integration logs...) Regards
cgtobi
commented
2 years ago Yeah, logs would be the starting point. Feel free to ping me on discord to discuss this more interactively and protect your data.
miki3421
commented
2 years ago @cgtobi me too I have a test instance where I've already reproduced the problem. you can contact me on discord my contact is mikimanza #9912
miki3421
commented
2 years ago the version DEV published recently is working fine! "Home Assistant 2022.4.0.dev20220323"
cgtobi
commented
2 years ago Since I haven't had any commits to 2022.4 so far the issue most certainly is not the integration itself.
Friedi1970
commented
2 years ago Since I haven't had any commits to 2022.4 so far the issue most certainly is not the integration itself.
Sorry, I don’t understand that statement. Could you please explain? I mean it’s obvious there is a problem, isn’t it?
miki3421
commented
2 years ago I think the Issue is on an external component that your integration is calling and in the last dev version someone fixed.
Just my 5 cents
On Wed, 23 Mar 2022 at 18:12, Tobias Sauerwein @.***> wrote:
Since I haven't had any commits to 2022.4 so far the issue most certainly is not the integration itself.
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/67560#issuecomment-1076590721, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKFA25UHE3RDU73JGNOPA33VBNGJXANCNFSM5P3IT2WQ . You are receiving this because you commented.Message ID: @.***>
Fr3n3z1
commented
2 years ago @cgtobi OK but sorry but i can't find your discord... I warn you my English is catastrophic
cgtobi
commented
2 years ago cgtobi#7113
cgtobi
commented
2 years ago @Ottmar0815 I seriously don't understand such a reaction. What exactly do you ant to express with a thumbs down to my comment? The crazy IP addresses certainly aren't my fault.
Fr3n3z1
commented
2 years ago cgtobi#7113
I can't add you as a friend on discord: he tells me that you haven't activated the addition of a friend.. it's mine: Manu'El Bastos#3691
Molodax
commented
2 years ago @cgtobi I've added a thumb down reaction to your comment too. It doesn’t mean that I blame you or anyone else about any kind of "fault". It just reaction to the comment that reads as a denial of the existing problem. Hopefully, you didn't mean that. Those who are affected by this issue hope to see that someone with the knowledge is looking into the issue and, I believe, willing to help you as much as they can including me.
miki3421
commented
2 years ago this version is not working Home Assistant 2022.4.0.dev20220324 just published ... here there is a sort of magic behind
same error
Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/aiohttp/connector.py", line 986, in _wrap_create_connection return await self._loop.create_connection(*args, **kwargs) # type: ignore[return-value] # noqa File "/usr/local/lib/python3.9/asyncio/base_events.py", line 1056, in create_connection raise exceptions[0] File "/usr/local/lib/python3.9/asyncio/base_events.py", line 1041, in create_connection sock = await self._connect_sock( File "/usr/local/lib/python3.9/asyncio/base_events.py", line 955, in _connect_sock await self.sock_connect(sock, address) File "/usr/local/lib/python3.9/asyncio/selector_events.py", line 502, in sock_connect return await fut File "/usr/local/lib/python3.9/asyncio/selector_events.py", line 537, in _sock_connect_cb raise OSError(err, f'Connect call failed {address}') OSError: [Errno 113] Connect call failed ('169.254.68.11', 80)
Friedi1970
commented
2 years ago @Ottmar0815 I seriously don't understand such a reaction. What exactly do you ant to express with a thumbs down to my comment? The crazy IP addresses certainly aren't my fault.
Please correct me if I am wrong but the error is since 2022.03. and you tell us it is not due to your integration. But then I would expect that you ask for help e.g. @frenck or anyone else who can help. I mean who if not you can tell/decide who would be the responsible for this issue?
cgtobi
commented
2 years ago Since I can't reproduce the issue please create a custom component from the last working release for the Netatmo integration and see if this is reproducible in the 2022.3 release of HA. Likewise create a custom component of the current release for the Netatmo integration and run that in the 2022.2 release of HA. I am not aware of any changes inside the integration that would result in this behaviour. The strange IP addresses make no sense to me nor do I have an idea how the integration or the underlying module would have an effect on them.
buhito81
commented
2 years ago Upgraded to core 2022.3.7:
From the error-log: 2022-03-24 12:31:10 ERROR (MainThread) [homeassistant.components.climate] Platform netatmo does not generate unique IDs. ID 2842156701-NATherm1 already exists - ignoring climate.downstairs 2022-03-24 12:31:10 ERROR (MainThread) [homeassistant.components.climate] Platform netatmo does not generate unique IDs. ID 2842156701-NATherm1 already exists - ignoring climate.downstairs [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. 2022-03-24 12:33:41 ERROR (MainThread) [homeassistant.util.logging] Exception in manage_cloudhook when dispatching 'CLOUD_CONNECTION_STATE': (<CloudConnectionState.CLOUD_DISCONNECTED: 'cloud_disconnected'>,) Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/netatmo/init.py", line 212, in manage_cloudhook await unregister_webhook(None) File "/usr/src/homeassistant/homeassistant/components/netatmo/init.py", line 162, in unregister_webhook await hass.data[DOMAIN][entry.entry_id][AUTH].async_dropwebhook() KeyError: 'KEYNUMBERREMOVED'
2022-03-24 12:33:41 ERROR (MainThread) [homeassistant.util.logging] Exception in manage_cloudhook when dispatching 'CLOUD_CONNECTION_STATE': (<CloudConnectionState.CLOUD_DISCONNECTED: 'cloud_disconnected'>,) Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/netatmo/init.py", line 212, in manage_cloudhook await unregister_webhook(None) File "/usr/src/homeassistant/homeassistant/components/netatmo/init.py", line 162, in unregister_webhook await hass.data[DOMAIN][entry.entry_id][AUTH].async_dropwebhook() KeyError: 'KEYNUMBERREMOVED'
2022-03-24 12:33:51 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /homeassistant/restart request
Fr3n3z1
commented
2 years ago @cgtobi Hi guy, i maked test with netatmo_custom, i'll tell you on Discord...
cgtobi
commented
2 years ago @buhito81 please remove the integration, restart HA and re-install the integration again.
buhito81
commented
2 years ago @buhito81 please remove the integration, restart HA and re-install the integration again.
Tried that, system gives the following:
[281472888593088] Option not valid for Netatmo NAMEOFMYTHERMOSTAT Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 192, in handle_call_service await hass.services.async_call( File "/usr/src/homeassistant/homeassistant/core.py", line 1636, in async_call task.result() File "/usr/src/homeassistant/homeassistant/core.py", line 1673, in _execute_service await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)( File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 204, in handle_service await self.hass.helpers.service.entity_service_call( File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 671, in entity_service_call future.result() # pop exception if have File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 949, in async_request_call await coro File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 708, in _handle_entity_call await result File "/usr/src/homeassistant/homeassistant/components/select/init.py", line 53, in async_select_option raise ValueError(f"Option {option} not valid for {entity.name}") ValueError: Option not valid for Netatmo NAMEOFMYTHERMOSTAT
The problem
Since the 2022.3 update, the Netatmo integration didn't work. After a delete/reinstall here is the issue. I have one camera and several temperature sensors.
For information the IP address 169.254.214.58 doesn't mean anything, my local IP range is 192.168.x.x
What version of Home Assistant Core has the issue?
core-2022.3.0
What was the last working version of Home Assistant Core?
core-2022.2.9
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Netatmo
Link to integration documentation on our website
https://www.home-assistant.io/integrations/netatmo/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response