-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Chromecast speaker goes unavailable once a while #1409
Comments
Might be a problem with the device or a network issue? |
Good suggestion to check, will do. But I would expect that the device becomes available after the connection is re-established. Keep you posted. |
I see you say restarting HA brings it back online, Did you mean MA? |
Not sure why restarting HA will bring a MA player back online? Unless you are restarting the host. If so you should be able to just trying restarting the addon and that should fix it. Doesn't solve your original problem I know but just trying to minimise your pain. It will be difficult without logs to fix this. Exactly what type of speaker are you using? Do other speakers have this problem? |
Thanks for the advice! Restarting MA (add on) makes sense and works.
I'll have limited time the next 2 weeks to check, but will continue with this after these 2 weeks. |
Hi again. Checking how this is going. Please only test with the latest beta. |
👋 back home. Will test the next few days. Reading other issues, I saw that some people have issues with unifi networks (as is mine). So it might be a network issue after all. Will keep you posted |
Hi again. Just checking how this is going. We will need to close this soon if there is no more news. |
Hello, I will close the issue. Last week I only experienced the issue once more. I will try to tweak the network settings, but don't have time for this in the next few weeks. If I come up with something I will share it here. Thank you for all the work on MA! |
FYI, I think I have found the issue. Every night around 3:00 am both my speakers become 'unavailable' in HA. The one in the bathroom changes to 'off' a few minutes later, but the other one (i.e., the problematic one) does not, and remains 'unavailable'. What I have done is pinned the problematic one to the nearest Access Point (Unifi network) to force a better network connection hopefully. Have other users experienced the same problem? |
There is discussion about issues with Unifi networks if you don’t ensure the mdns traffic can flow freely. Check all the settings… |
We will close this soon and ask you to report again if you have more info to add |
I close this issue myself. The problem is unrelated to MA, but a more general issue in HA. Luckily I am not the only one experiencing these frustrating issues :( |
What version of Music Assistant has the issue?
2.0.0b60
The problem
Chromecast speaker goes unavailable once a while:
I can reach the speaker through the Google Home app and the google cast integration in HA.
How to reproduce
I don't know yet. It happens once in a while. It seems related listening to Spotify music (children's books) for a while. Restarting HA brings the speaker back online.
Relevant log output
I am unsure which log files to include, but this morning -- before the error occurred again -- I got several of these errors. Please let me know if there is something else to look for.
Additional information
I have another Google nest mini which does not has these issues.
I also experience issues with the Spotcast integration, don't know if they are related: fondberg/spotcast#397 . Sometimes I cannot activate the nest mini player through the media player front card, but can activate it on the integration page and, often I cannot start playing Spotify content through the media player.
Note that turning the Nest mini on through the integration page does not turn the speaker on on the Music Assistant page.
What version of Home Assistant Core are your running
2023.7.3
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
ODROID
The text was updated successfully, but these errors were encountered: