Integration stopped working | "Session is closed" | 1000-1503 - Failed communication with adaptor #49
Comments
|
It seems that Smart Cloud got an update rolled out, not it Has new options available via web interface (force defrost, force dhw, force strong/assisted mode etc.). Maybe it influences the communication with the integration? Mine stopped today, yesterday Smart Cloud service for not have those options. Frankly, they would be very useful. |
|
I'll take a look to them |
|
Hi to all. I am a new home assistant guy and try to bind my heat pump to home assistant. But it seems I get the same error. Logger: homeassistant.config_entries Error setting up entry mike@joshuasdream.de for aquarea All is fine via the cloud. Chees, Mike |
|
I'll see if I can release a preview version with a couple of ideas that I have. I'm not able to reproduce this issue in my environment so I'll need your help to see if we can fix this 😊 I'll let you know when I have released it. |
|
Yes of course. We can help. I am here ;-) If you need the login for the cloud or something else. Just let me know! Cheers, Mike |
|
@mikehabermeier I just published one test as beta release: https://github.com/cjaliaga/home-assistant-aquarea/releases/tag/v0.3.1-preview1 Could you please install that version and let me know how it goes for you? Thanks!
|
|
Hi Carlos,
sorry. It is not working.
Cheers, Mike
|
|
@mikehabermeier could you share the logs for the new issue? |
|
Sorry. Of course. I missed it. Sorry.' Traceback (most recent call last): |
|
hi, the integration stopped to work for me. I've tried to reinstall and reput cerdetials, but here is what i got in logs. Any idea if it is something wrong with my configuration (i think i didn't change anything) or with integration itself? 2023-12-04 12:59:38.101 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry michal.cwieka@gmail.com for aquarea |
|
I just published 0.4.1 with some changes on entry load. Could you please give it a try to see if it makes any difference on those messages? |
|
Sorry. It is not working:: Sory. Cheers Mike |
|
I have some bad news. The fix on that version removed the issue so we're no longer getting the session is closed error message that was hiding the real reason. Now we're seeig why the integration wasn't loading. This error message is coming from the Panasonic cloud specifying that's not able to connect to the adapter, we use device direct here so the request goes to their cloud -> your adapter. I'll see if there's something we can do to to help here and ease connectivity issues somehow but basically the best option would be to check the device connectivity, WiFi signal and so on. We have other reports for this error that were solved as soon as the connectivity issues were solved(WiFi, DNS... you name it) |
cjaliaga
changed the title
|
Hi. I will get in touch with these in my holiday. I thought it was working because I can see everything in my cloud. But I will reboot the adapter and look if it works then. Thank you for your help! |
|
Thanks @mikehabermeier. I'll try something too: Right now we're doing device direct, which means (per my understanding, I can be completely wrong 😂) we go to their cloud and the cloud tries to connect to the device to get the latest status. I can try to do something: in case it fails to connect to the adapter, to retry the request without passing the device direct parameter and see if we can retrieve the status from the cached value their cloud maintains. Maybe this will make new changes to take more time to appear, but at least, we can get some details. I'll try to do this as soon as I can. I'd appreciate if you can give me some time to do it and release a new version so we can test in your environment before you reset it. Thanks a lot! |
|
Hi Carlos. Today I have time to go deeper into this topic. First I checked my network. Everything is working fine on this. I logged into the cloud. Every second time I logged in, I get the error "Communication error with adapter. 1008-1503." Everything is working!!! I hope that helps others too. |
|
I got the same issue (1008-1503), in the past it automatically resolves but today not. First, I tried rebooting my switch because it reported a link speed of 10MF instead of 100MF. But this didn't resolve the connection problem. Then I just powered my heat pump off and on again, and this resolved the issue for me. |
|
Happened to me today as well. Home assistant was not able to connect to a system that has been integrated and working fine for months. Only the website the heat pump was visible but I could not try any operations as I kept getting logged off. I powered off the heat pump and powered it back on again and it started working. Thinking about it now, maybe I was being logged off because home assistant was trying to login repeatedly. |
Integration doesn't work anymore. It stopped working 12.9.2023 at 1.30 (GMT+2). There is error logs.
This error originated from a custom integration.
Logger: homeassistant.config_entries
Source: custom_components/aquarea/init.py:52
Integration: Aquarea Smart Cloud (documentation, issues)
First occurred: 18:39:22 (2 occurrences)
Last logged: 18:43:26
Error setting up entry juho.vuotila@gmail.com for aquarea
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/aquarea/init.py", line 52, in async_setup_entry
await client.login()
File "/usr/local/lib/python3.11/site-packages/aioaquarea/core.py", line 201, in login
response: aiohttp.ClientResponse = await self.request(
^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aioaquarea/core.py", line 154, in request
resp = await self._sess.request(method, AQUAREA_SERVICE_BASE + url, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/client.py", line 400, in _request
raise RuntimeError("Session is closed")
RuntimeError: Session is closed
The text was updated successfully, but these errors were encountered: