-
-
Notifications
You must be signed in to change notification settings - Fork 29.9k
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
Cutting off power from one speaker breaks the integration #123745
Comments
Hey there @thrawnarn, @LouisChrist, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) bluesound documentation |
I have created a PR which fixes two things:
There are two things i cannot test/reproduce:
|
Think I'm having a similar issue but maybe the next HA patch will now fix it hopefully. I'm not cutting the power to my Node 2i but it seems it drops offline in HA randomly. Works normally via BluOS app and reloading the integration does indeed seem to restore it back online. I'll wait until the PR is accepted to see if the fix helped. |
It should get back to available in 2024.8.2 without a reload. That's due to #123790. But it should not stop in the first place. Do you have any errors Logs? There should be one of those:
|
@Niekmanz Can you try 2024.8.2 and check if the errors have been fixed? Especially if all speakers go to |
I've updated to 2024.8.2 but not yet sure if that fixed the issue as it was sort of random when it occurs. However I checked the logs and see these two from earlier today: Logger: homeassistant.components.bluesound.media_player Client connection error, marking Living Room as offline Logger: homeassistant.components.bluesound.media_player Node 192.168.1.252:11000 is offline, retrying later. Edit: seems it was only unavailable for 3-4 minutes, but I'll monitor it. I have recently changed Google wifi routers to Unifi equipment so I'm not totally sure if there could be some new issue caused by that hw change. Br |
That seems to work as expected. 3 Minutes is the timeout between retries. I left that one as is, but i think it might be reasonable to reduce it. Or use an exponential backoff. Off Topic regarding WiFi a the Node 2i: I think PMF(Protected Management Frames) are not supported by the Node 2i. I have a separate WiFi where i disabled them completely. |
Mine has been working normally now after updating to 2024.8.2. Thanks for the tip regarding the wifi. Will look into that if the problems would reoccur. |
First, thanks for the work you guys are putting into this integration! Unfortunately I am also experiencing issues with a Bluesound Node 2i and a Powernode 2i that are cut off from power when not in use. Updating (currently on 2024.8.3) has not resolved this for me unfortunately, the media_player entities remains in state I have tried removing all/both players, rebooting HA and adding them again which does not resolve I'm afraid. I had no issues up until version 2024.7.4. Here are some related logs:
|
@klingbing I found a small bug(the second log you posted), but still not the main one. Is the second player instantly unavailable, when power is cut from the first one? Or after a few minutes? Or once the the power is restored to the first one? The first log is very suspicious: |
EDIT: updating HA to 2024.9 appears to have resolved this for me. @LouisChrist I can confirm the MAC address is the one that belongs to this player. The two Bluesound players are powered on/off independently and they are behaving the same regardless of order powered or time between a power cycle: Working fine after a HA reboot, but failing (media_player entity remains |
@Niekmanz can you try 2024.9 and see if it is fixed for you too? |
I haven't had any issues since updating in my usecase.
But that is because the power is cut off at night and I don't use the other speaker at that time.
Testing shows that de second speaker(pulse mini) becomes unavailable within a minute of cutting of power to the first player(node 2i).
Availability is restored in 3 minutes time after restoring power.
version 2024.9.1
…________________________________
Van: Louis Christ ***@***.***>
Verzonden: donderdag 5 september 2024 19:37
Aan: home-assistant/core ***@***.***>
CC: Niekmanz ***@***.***>; Mention ***@***.***>
Onderwerp: Re: [home-assistant/core] Cutting off power from one speaker breaks the integration (Issue #123745)
@Niekmanz<https://github.com/Niekmanz> can you try 2024.9 and see if it is fixed for you too?
—
Reply to this email directly, view it on GitHub<#123745 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGDCH5JHZCW74DG7UBH6CGTZVCJFHAVCNFSM6AAAAABMM4C3LGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZSGI4TANZSGQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Hi @LouisChrist I have 4 BluSound nodes and a NAD amplifier for home cine. I sometimes include the NAD amplifier in the blusound group, but often I will leave the amplifier turned off. When I restart HA with the amp on, everything works beautifully. But if I turn the amp off at any stage then all of the BluSound nodes become unavailable. After 3 minutes they show their real status again but as soon as I try to add/remove a node then the whole group becomes unavailable again (unless the amp is turned on). This used to work perfectly before. I'm on 2024.9.1 |
Thank you for the log. I am pretty sure that your bug is fixed with #125779. It is already merged and should be part of the next release. |
Just to confirm that this is fixed for me in 2024.9.2. Many thanks! 👍 |
The problem
In my setup the power to my media setup (TV, receiver and Bluesound Node 2i) is cut off completely at night and when we're away.
Another speaker (Pulse Mini P200) is always on.
Everytime the Node is cut off from power all Bluesound speakers are reported 'off' in HA; they cant be controlled anymore.
When power comes back on their status doesn't update until I reload the integration. And even then it's a hit or miss.
Accessing the speaker directly through a browser works fine.
In the previous (yaml) configuration this problem didn't occur.
Also, HA would correctly present the status of the Node as 'unavailable' when power was cut off.
What version of Home Assistant Core has the issue?
core-2024.8.1
What was the last working version of Home Assistant Core?
core-2024.7.4
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Bluesound
Link to integration documentation on our website
https://www.home-assistant.io/integrations/bluesound
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: