corvis
commented
3 years ago Hi Mislav,
Thank you for the feedback and such a comprehensive report.
I saw similar behavior but typically this happened after ~ month of work. So it seems like this issue has higher priority then I thought initially. I'll investigate whenever have a chance.
On Thu, May 6, 2021, 10:50 PM Mislav Mandarić @.***> wrote:
Hi.
First of all, thank you for the great work on this integration. I never thought I'd see my recuperator integrated with HA and I really appreciate the work you've done, both on the integration and the awesome prana_rc library.
I set up this integration and prana_rc server on my RPi (both running on the same HA OS) and when I first start the prana_rc docker container, everything works well.
But after some time, I always get the error from the title after which my recuperator disconnects from HA and becomes unavailable.
This is my setup:
- HA OS running on RPi4, version 5.12; HA Core version is core-2021.4.6; Supervisor version is supervisor-2021.04.3
- Prana RC server running on the same machine, deployed using Portainer (config from the prana_rc repository is used -- /run/dbus/system_bus_socket, hassio network, restart unless stopped policy, with default 8881 port mapping), version corvis/prana-rc:0.4.4 of the image
- Integration installed using HACS as custom repository
- RPi is ~6m away from the recuperator, in the same room
I can ping the prana_rc server from my laptop terminal, which means the server itself is running and it does show proper connection to the recuperator:
curl -X POST -H "Accept: application/json" http://homeassistant.local:8881/ -d '{ "jsonrpc": "2.0", "id": 1, "method": "prana.healthcheck" }' {"result": {"version": "0.4.4", "timestamp": "2021-05-06T19:21:15.699394", "current_connections": ["XX:XX:XX:XX:XX:XX"]}, "id": 1, "jsonrpc": "2.0"}
But this is the log from HA, showing connection errors. I enabled the debug log and there is nothing in addition to these error snippets, which occur 3-4 times in the log.
2021-05-06 21:22:46 WARNING (MainThread) [custom_components.prana.fan] Can't read data from prana recuperator Prana (prana_XX_XX_XX_XX_XX_XX): RPC Invocation error -32000: Server error. Cause: RuntimeError: Connection to device XX:XX:XX:XX:XX:XX failed after 5 attempts 2021-05-06 21:22:46 ERROR (MainThread) [custom_components.prana.fan] Unexpected error fetching prana_XX_XX_XX_XX_XX_XX data: RPC Invocation error -32000: Server error. Cause: RuntimeError: Connection to device XX:XX:XX:XX:XX:XX failed after 5 attempts Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 173, in _async_refresh self.data = await self._async_update_data() File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 143, in _async_update_data return await self.update_method() File "/config/custom_components/prana/fan.py", line 67, in async_get_state raise e File "/config/custom_components/prana/fan.py", line 62, in async_get_state return await prana_client.get_state( File "/usr/local/lib/python3.8/site-packages/prana_rc/contrib/client/common.py", line 45, in get_state await self.async_invoke( File "/usr/local/lib/python3.8/site-packages/sizzlews/client/common.py", line 179, in async_invoke return await self._invoke_request(rq, expected_response_type) File "/usr/local/lib/python3.8/site-packages/sizzlews/client/aiohttp.py", line 47, in _invoke_request return self._parse_rpc_response(await response.json(), expected_response_type) File "/usr/local/lib/python3.8/site-packages/sizzlews/client/common.py", line 119, in _parse_rpc_response raise RPCInvocationError.from_rpc_dict(response[RESPONSE_FIELD_EROR]) sizzlews.client.common.RPCInvocationError: RPC Invocation error -32000: Server error. Cause: RuntimeError: Connection to device XX:XX:XX:XX:XX:XX failed after 5 attempts 2021-05-06 21:22:46 DEBUG (MainThread) [custom_components.prana.fan] Finished fetching prana_XX_XX_XX_XX_XX_XX data in 2.729 seconds
This is the screenshot of how it looks like from the UI (all entities are disabled and unavailable). [image: image] https://user-images.githubusercontent.com/2945713/117355165-7d07b180-aeb2-11eb-93e9-c8ecb424f697.png
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/corvis/homeassistant_prana/issues/3, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABKVUD2SU73JKY4BYBXSC63TMLXKFANCNFSM44HZMT3Q .
MislavMandaric
aurelian17
yuriilemberg
Hi.
First of all, thank you for the great work on this integration. I never thought I'd see my recuperator integrated with HA and I really appreciate the work you've done, both on the integration and the awesome prana_rc library.
I set up this integration and prana_rc server on my RPi (both running on the same HA OS) and when I first start the prana_rc docker container, everything works well.
But after some time, I always get the error from the title after which my recuperator disconnects from HA and becomes unavailable.
This is my setup:
/run/dbus/system_bus_socket, hassio network, restart unless stopped policy, with default 8881 port mapping), version corvis/prana-rc:0.4.4 of the imageI can ping the prana_rc server from my laptop terminal, which means the server itself is running and it does show proper connection to the recuperator:
But this is the log from HA, showing connection errors. I enabled the debug log and there is nothing in addition to these error snippets, which occur 3-4 times in the log.
This is the screenshot of how it looks like from the UI (all entities are disabled and unavailable).
If there is anything I can do more to help out in in resolving this issue, I'll gladly contribute.