Risco cannot connect local panel RW132

[teruggim]

The problem

Cannot connect local panel RW132.

What version of Home Assistant Core has the issue?

core-2023.8.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

Risco local

Link to integration documentation on our website

https://www.home-assistant.io/integrations/risco

Diagnostics information

Traceback (most recent call last): File "/usr/local/lib/python3.11/asyncio/tasks.py", line 490, in wait_for return fut.result() ^^^^^^^^^^^^ asyncio.exceptions.CancelledError The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/pyrisco/local/risco_socket.py", line 105, in send_command return await asyncio.wait_for(future, 1) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/asyncio/tasks.py", line 492, in wait_for raise exceptions.TimeoutError() from exc TimeoutError During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/pyrisco/local/risco_socket.py", line 36, in connect panel_id = int(await self.send_result_command('RID'), 16) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/pyrisco/local/risco_socket.py", line 95, in send_result_command command = await self.send_command(command) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/pyrisco/local/risco_socket.py", line 107, in send_command raise OperationError(f'Timeout in command: {command}') pyrisco.common.OperationError: Timeout in command: RID The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/risco/config_flow.py", line 159, in async_step_local info = await validate_local_input(self.hass, user_input) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/risco/config_flow.py", line 87, in validate_local_input await risco.connect() File "/usr/local/lib/python3.11/site-packages/pyrisco/local/risco_local.py", line 26, in connect await self._rs.connect() File "/usr/local/lib/python3.11/site-packages/pyrisco/local/risco_socket.py", line 47, in connect raise CannotConnectError from exc pyrisco.common.CannotConnectError

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @onfreund, mind taking a look at this issue as it has been labeled with an integration (risco) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `risco` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign risco` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

risco documentation risco source _{^{(message by IssueLinks)}}

[teruggim]

[OnFreund]

This model most likely only has a single network connection. You'll need to disable its cloud access, and make sure no other connection is running (e.g. the MQTT addon)

[teruggim]

Good evening @OnFreund Thanks for the reply. Even with the Cloud turned off the logs are identical:

2023-08-28 21:44:31.110 DEBUG (MainThread) [homeassistant.components.risco.config_flow] Cannot connect Traceback (most recent call last): File "/usr/local/lib/python3.11/asyncio/tasks.py", line 490, in wait_for return fut.result() ^^^^^^^^^^^^ asyncio.exceptions.CancelledError The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/pyrisco/local/risco_socket.py", line 105, in send_command return await asyncio.wait_for(future, 1) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/asyncio/tasks.py", line 492, in wait_for raise exceptions.TimeoutError() from exc TimeoutError During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/pyrisco/local/risco_socket.py", line 36, in connect panel_id = int(await self.send_result_command('RID'), 16) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/pyrisco/local/risco_socket.py", line 95, in send_result_command command = await self.send_command(command) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/pyrisco/local/risco_socket.py", line 107, in send_command raise OperationError(f'Timeout in command: {command}') pyrisco.common.OperationError: Timeout in command: RID The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/risco/config_flow.py", line 159, in async_step_local info = await validate_local_input(self.hass, user_input) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/risco/config_flow.py", line 87, in validate_local_input await risco.connect() File "/usr/local/lib/python3.11/site-packages/pyrisco/local/risco_local.py", line 26, in connect await self._rs.connect() File "/usr/local/lib/python3.11/site-packages/pyrisco/local/risco_socket.py", line 47, in connect raise CannotConnectError from exc pyrisco.common.CannotConnectError

[OnFreund]

Have you disabled the could in the panel? Not having a subscription is not enough - the panel will still communicate with the cloud unless you explicitly disable it.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.