Multiroom detection problem / takes very long

Help and Support Help
#1

I’m very happy with the new multiroom feature but most of the times it takes very long (several minutes or never) until the two instances find each other. (until the second instance appears in “group devices”)

Is there a way to make it faster and/or more reliable?

Volumio Information

Instance 1 (labmusic):
{“systemversion”:“3.173”,“builddate”:“Wed 08 Dec 2021 12:21:52 PM CET”,“variant”:“volumio”,“hardware”:“pi”}

  • HifiBerry AMP
  • Pi 3 Model B

Instance 2 (Kitchen):
{“systemversion”:“3.173”,“builddate”:“Wed 08 Dec 2021 12:21:52 PM CET”,“variant”:“volumio”,“hardware”:“pi”}

  • Inbuild line out
  • Raspberry Pi 3 Model B Rev 1.2

log_instance1.txt (21.4 KB)
log_instance2.txt (6.3 KB)

#2

Here multiroom doesn’t work at all, fast or slow, after the upgrade to 3.165. The various instances can’t find one another:

Dec 09 01:55:20 kitchen volumio[676]: info: CorePlayQueue::getTrack 0
Dec 09 01:55:20 kitchen volumio[676]: info: MRS: Pushing multiroomSync output update for this device
Dec 09 01:55:20 kitchen volumio[676]: info: MRS: Pushing multiroomSync output
Dec 09 01:55:20 kitchen volumio[676]: info: MRS: Pushing multiroomSync output update for this device
Dec 09 01:55:20 kitchen volumio[676]: info: MRS: Pushing multiroomSync output
Dec 09 01:55:33 kitchen dnsmasq-dhcp[668]: no address range available for DHCP request via wlan0
Dec 09 01:55:44 kitchen volumio[676]: verbose: New Socket.io Connection to 192.168.1.108 from 192.168.1.100 UA: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Total Clients: 4
Dec 09 01:55:46 kitchen volumio[676]: info: CoreCommandRouter::volumioGetVisibleSources
Dec 09 01:55:46 kitchen volumio[676]: info: CoreCommandRouter::executeOnPlugin: my_music , getDisabledSources
Dec 09 01:55:46 kitchen volumio[676]: info: CoreCommandRouter::volumioGetState
Dec 09 01:55:46 kitchen volumio[676]: info: CorePlayQueue::getTrack 0
Dec 09 01:55:46 kitchen volumio[676]: info: CoreCommandRouter::executeOnPlugin: multiroom , getMultiroom
Dec 09 01:55:46 kitchen volumio[676]: info: Error : CoreCommandRouter::executeOnPlugin: No method [getMultiroom] in plugin multiroom
Dec 09 01:55:46 kitchen volumio[676]: info: Listing playlists
Dec 09 01:55:46 kitchen volumio[676]: info: CoreCommandRouter::volumioGetQueue
Dec 09 01:55:46 kitchen volumio[676]: info: CoreStateMachine::getQueue
Dec 09 01:55:46 kitchen volumio[676]: info: CorePlayQueue::getQueue
Dec 09 01:55:54 kitchen dnsmasq-dhcp[668]: no address range available for DHCP request via wlan0
Dec 09 01:55:58 kitchen dnsmasq-dhcp[668]: no address range available for DHCP request via wlan0
Dec 09 02:11:00 kitchen dnsmasq-dhcp[668]: no address range available for DHCP request via wlan0
Dec 09 02:21:04 kitchen dnsmasq-dhcp[668]: no address range available for DHCP request via wlan0

#3

Hi, same issue here.
Multiroom doesn’t work right, it has a very erratic behavior.
Current version in all devices: 3.173

#4

I actually now have it working – the instructions were just too vague and brief for me to know right away how to go about it.

#5

What did you do? My issue here that I think I know how it works (after all I had it running several times) It just doesn’t seem to work reliable…

#6

I have to say, I’ve got it working, but I’m not sure how it should work:

So if I stop on the ‘master’ and then, at a later date play again, should I expect the 'slave’t to also play?

Should the volume for each device in in sych?

Other questions may arise :wink:

C

#7

My understanding is that as soon as you create a group all should play the stuff of the master in sync. (including stopping and starting). Volume can be controlled separately.