-
-
Notifications
You must be signed in to change notification settings - Fork 30.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Russound_Rio reconnect after power cycle amp #124996
Comments
Hey there @noahhusby, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) russound_rio documentation |
How much time are you giving the unit from power up to sending the first command? |
That could be within a minute, it takes approx 30 seconds for it to boot up |
Have you given it up to 15 minutes to reconnect? It's supposed to be pretty quick, but there is a cycle that occurs 15 minutes that might force a reconnection. The reconnection will never be instant, but I might be able to make that cycle a configuration option that you can lower for your use-case. |
Turned it off last night, and 20ish hours later, I turned it on and let it run 30 minutes. These are the last logs from the integration:
After that, nothing about russound_rio and only this error, which I amd not sure is related:
Sometimes the amp is left off for days and I noticed that reloading the interface does not work, HA has to be restarted |
I have the same issue. I have tried a number of things including re-starting the Russound integration when the amp is powered on. The only thing that seems to work reliably is to restart Home Assistant. |
@horbye So that error was from around the time that you powered the unit off? If you open the logs, do you continue to see "Connecting to 192.168.16.250:9621" consistently? |
Amp was turned off 19:32, this is all that was logged before and after
|
Between 19:51:57.635 and 23:27:36.417 nothing is logged |
Sorry for the delay, I've been rewriting the connection handler to be more resilient. The issue is that OSError is not handled in the code causing the execution to end after a reconnection is attempted thus preventing the reconnection from succeeding. This behavior is being changed in a future version of the library and should resolve this issue. I'll keep you posted on the status of the fix. Until then, I'll leave this issue open. |
Thanks :) |
The issue is resolved and will be included in the new release of Home Assistant 2024.10 (comes out next week Wed). It takes roughly 1 minute (at most) to detect that the controller is no longer connected and to run the reconnect handler. From there, reconnect is properly attempted every 30 seconds. The entire IO loop was rewritten and handles errors much better now. All errors will get logged and the reconnect handler will take over to try to re-establish connection |
@horbye The fix was released in the update today. Can you give it a try to confirm that it's functioning properly? |
I upgraded and it looks like the fixes are working. I was also having some issues with source switching which seem to be resolved. @noahhusby I really appreciate all your work. My Russound stuff is working way better in Home Assistant. THANKS!!!!! |
Hi I left the amp off for a few days and when I turned it on today, somthing went wrong, had to reconnect the rj45 cable in my switch, as not event eh russound app would connect, after reconnecting the cable, russound app was could connect, but not HA
Besides that It was working nicely just after teh update, was happy to see that HA was able to reconnect, even though amp was turned off when HA was restarted also |
This is from the Switch log, showing, I disconnected the cable 30 minutes after interface crashed
@noahhusby Thanks for rebuilding the interface and looking into this. |
The problem
After the amp has been turned off and later turned on again, HA has to be restarted or the integration has to be reloaded to reconnect the Russound_Rio entities.
What version of Home Assistant Core has the issue?
core-2024.8.0
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
russound_rio
Link to integration documentation on our website
https://www.home-assistant.io/integrations/russound_rio
Diagnostics information
home-assistant.log
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
Due to standby power consumption of the MCA-C5 (nearly 20W), I keep it turned off by a smartswitch, when it is not in use.
The text was updated successfully, but these errors were encountered: