Closed chrkov closed 1 year ago
MA finally did see the group. While Google cast saw it within minutes, MA took about 30 hours .
30 hours ? That is a lot, normally it should pick it up within 10 minutes or even faster
I thought so also. Tried restarting several times as well thinking it would force a rescan or something. Ended up just giving up and posting a ticket here. Then this morning, the group is there.
I have the exact same issue... In the cast integration is visible. In Spotify connect is visible. In MA it is not. I have reloaded, restarted, reinstalled... But nothing.
Could wait a bit, but MA does not seem to behave like other 3rd parties when it comes to google cast groups.
Check the logs please
Apologies, should've posted that upfront.
The logs seem pretty reasonable... They cover ~15 minutes (plenty of time for the groups to pop) and there's no mention of the group. The individual speakers are registered, there's no errors (or otherwise) about speakers.
2024-01-11 08:59:23.332 INFO (MainThread) [music_assistant.music] Sync task for URL completed
2024-01-11 08:59:23.343 INFO (MainThread) [music_assistant.providers.slimproto] Started SLIMProto server on port 3483
2024-01-11 08:59:23.344 INFO (MainThread) [music_assistant.providers.slimproto.cli] Registering jsonrpc endpoints on the webserver
2024-01-11 08:59:23.345 INFO (MainThread) [music_assistant] Loaded player provider Chromecast
2024-01-11 08:59:23.348 INFO (MainThread) [music_assistant.providers.slimproto.cli] Starting (telnet) CLI on port 9090
2024-01-11 08:59:23.353 INFO (MainThread) [music_assistant] Loaded player provider Slimproto
2024-01-11 08:59:24.335 INFO (MainThread) [music_assistant] Loaded player provider Airplay
2024-01-11 08:59:29.487 INFO (MainThread) [music_assistant.players] Player registered: 9c02b6a2-718d-4e69-805f-88977bc10098/Bedroom speakers
2024-01-11 08:59:42.765 INFO (MainThread) [music_assistant.players] Player registered: 91ce8630-0385-3ebc-825a-97e86278ed67/Kitchen speaker
2024-01-11 08:59:43.489 INFO (MainThread) [music_assistant.players] Player registered: f5fb0aa9-6b8c-4f4b-8e59-d4cf0467a51c/Living Room Stereo
2024-01-11 08:59:43.965 INFO (MainThread) [music_assistant.players] Player registered: b868330f-46ba-b8f1-d48a-8396d64c65b5/Hallway speaker
2024-01-11 08:59:45.665 INFO (MainThread) [music_assistant.players] Player registered: aa:aa:f8:1d:80:c6/LN9P94WXQ3 (2)
2024-01-11 09:07:11.608 INFO (MainThread) [music_assistant.providers.slimproto] Player LN9P94WXQ3 disconnected
authorized
2024-01-11 09:12:30.118 INFO (MainThread) [music_assistant.providers.spotify] Successfully logged in to Spotify as calamarbicefalo
2024-01-11 09:12:30.119 INFO (MainThread) [music_assistant] Loaded music provider Spotify
2024-01-11 09:12:55.799 INFO (MainThread) [music_assistant] Loaded music provider Filesystem (local disk)
2024-01-11 09:13:04.786 INFO (MainThread) [music_assistant.providers.slimproto] Player LN9P94WXQ3 disconnected
2024-01-11 09:13:39.326 INFO (MainThread) [music_assistant.providers.slimproto] Player LN9P94WXQ3 disconnected
What version of Music Assistant has the issue?
2023.6.0.b1
The problem
Installed a new google display. Created a new group. New display is found by MA but the new group is not.
Google Cast integration in HA does see both.
How to reproduce
Create a new google cast group.
Relevant log output
Nothing relevant in log.
Additional information
No response
What version of Home Assistant Core are your running
2023.7.1
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Generic x86-64 (e.g. Intel NUC)