"No Receivers Found"

[Matt5]

Hello! If you're building moOde, thank you, if you're maintaining it, thank you, and if you're just helping people fix problems, thank you for that, too!
I've had the system working on multiroom for quite awhile, now.  Somewhat recently (not sure specifically when - but definitely over three months ago), whenever I click "DISCOVER", the system responds with "no receivers found".  This is especially bizarre because it still plays on most of them. 

That said, I am unable to adjust individual volumes or click and unclick the boxes that activate and deactivate certain receivers.  I am also unable to add new receivers easily.  Bizarrely, even without discovery, the new receiver will be found, but then the system will only play on that receiver or on all of the others.  Occasionally, it will randomly flip between the new one and all of the others.  Weird, right?

So, I've Googled it, Dogpiled it, Duckduckgoed it, and searched through the threads and the github, and literally no one has used the phrase "no receivers found" (that I can find, anyway). 

moodeutl tells me I'm running 8.3.9.  I'm using a pi 4 with 8Gb memory (I know - overkill, but I didn't have one with 2Gb available).

when I click "DISCOVER" and then moodeutl -l on a terminal, this is all that comes up (on many repeats):

20240906 201125 waitWorker(): Start trx-config, w_active=0
20240906 201125 waitWorker(): End   trx-config, w_active=0
20240906 201126 enhanceMetadata(): error: currentsong file is NULL

Thank you again!

[the_bertrum]

I'd begin with a full reboot of the sender, receivers and network devices (hubs, routers, etc). Turn them all off of a few minutes, then restart them one by one beginning with the network devices.

[Tim Curtis]

Odd because multiroom usually just works.

After doing what @the_bertrum suggests, post the contents of the sender startup log.

The log can be viewed via the SSH command moodeutl -l or downloaded via the Logs section in System Config, or via Menu, System info from any of the Config screens. The startup log will be at the end of System info output.