Issues after Risco Local Integration

[03397]

The problem

In continuation to the issue #114049 which was supposed to be fixed with #115226 unfortunately I still have the same issue after upgrading to 2024.4.3. I played with the configurable value up to 0 but no success. Again, no logs here.

What version of Home Assistant Core has the issue?

2023.4.3

What was the last working version of Home Assistant Core?

2024.3.3

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Risco

Link to integration documentation on our website

No response

Diagnostics information

No response

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. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

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

[OnFreund]

A value of 0 would not communicate with the panel at all, so no logs would show. For values 1 and above you should be seeing error logs.

[03397]

@OnFreund No error logs for any value. Just failing to connect and retrying for all values. I even enabled debug for the integration and still no logs.

[OnFreund]

First of all, please add a description to the issue, rather than reference an older one with lots of comments in it. Second, I'm not sure what's causing this for you, especially if there are no logs. Is it only during HA startup? What happens if you disable the integration, restart HA and only enable it again after HA is fully loaded?

[jakob1911]

I know this is not helpfull for you @03397. For me its the first working release with the official integration (no more customization on my side needed) I got the „fails“ with unloaded zones, at first initialization (with error Logs), then put the Parameter „Max concurrency“ from 4 to 2, restarted Home Assistant and everything was/is working like a charm. I can do several restarts without having any problems.

[03397]

Hello @jakob1911 . I have managed to connect successfully with the local integration after leaving it trying for 10min or so. The thing is that every time I restart Home Assistant, 9 out of 10 times I get failures(retrying) and after 4-6 min it connects successfully. I tried values from 1 to 4, now it is set to 2. During the retries the weird think is that I do not have any error or warmings in the logs.

In addition, thought out the day I am getting these:

File "/usr/local/lib/python3.12/site-packages/pyrisco/local/risco_socket.py", line 68, in _listen raise OperationError(f'Risco error: {command}') pyrisco.common.OperationError: Risco error: N04 2024-04-14 11:03:56.983 ERROR (MainThread) [homeassistant.components.risco] Error in Risco library Traceback (most recent call last): File "/usr/local/lib/python3.12/asyncio/tasks.py", line 520, in wait_for return await fut ^^^^^^^^^ asyncio.exceptions.CancelledError The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.12/site-packages/pyrisco/local/risco_socket.py", line 109, in send_command return await asyncio.wait_for(future, 1) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/asyncio/tasks.py", line 519, in wait_for async with timeouts.timeout(timeout): File "/usr/local/lib/python3.12/asyncio/timeouts.py", line 115, in aexit raise TimeoutError from exc_val 
TimeoutError During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.12/site-packages/pyrisco/local/risco_socket.py", line 87, in _keep_alive await self.send_result_command("CLOCK") File "/usr/local/lib/python3.12/site-packages/pyrisco/local/risco_socket.py", line 98, in send_result_command command = await self.send_command(command) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/pyrisco/local/risco_socket.py", line 111, in send_command raise OperationError(f'Timeout in command: {command}') pyrisco.common.OperationError: Timeout in command: CLOCK