05-10-2024, 06:31 PM
~pre6 installed from image on 5 Pis: 3A+, 3B+, 4B, 5B, and Zero 2W. All communicating over my LAN via WiFi, some on 2.4GHz band, some on 5GHz. There's also one moOde 8.3.9 player on the LAN for comparison
I'm still exploring the player detection code in the php modules.
The m>Players command in the WebUI on each player doesn't always return all of the neighboring players. Sometimes one or two are missing, sometimes more, and not always the same on all players. This despite every player's /tmp/mpd_nmap.scan file containing proper entries for all the players after I've done a first scan. Usually I'll get all players returned in the WebUI at some point but not necessarily again later.
There's a similar effect, although perhaps not as severe, with the discovery of receivers on the multiroom configuration screen. In this case, however, for any missing players I see corresponding timeout errors in the moOde log if debug logging is enabled (e.g., "get_rx_status failed").
I just got back from a road trip to see my grandson graduate from Virginia Tech (yay, three grandkids down; one to go) and haven't had time to think this problem through. I haven't even tried, for example, to correlate the failures in the two searches. It looks, though, like I may have to plant some additional debugging statements.
Obvious confounding influences include differing numbers of cores and clock speeds, different networking subsystems, and higher congestion in 2.4GHz band. Sadly, I don't have any spare ports on my Ethernet switch to see if any difference shows up between wired and wifi connections.
Regards,
Kent
I'm still exploring the player detection code in the php modules.
The m>Players command in the WebUI on each player doesn't always return all of the neighboring players. Sometimes one or two are missing, sometimes more, and not always the same on all players. This despite every player's /tmp/mpd_nmap.scan file containing proper entries for all the players after I've done a first scan. Usually I'll get all players returned in the WebUI at some point but not necessarily again later.
There's a similar effect, although perhaps not as severe, with the discovery of receivers on the multiroom configuration screen. In this case, however, for any missing players I see corresponding timeout errors in the moOde log if debug logging is enabled (e.g., "get_rx_status failed").
I just got back from a road trip to see my grandson graduate from Virginia Tech (yay, three grandkids down; one to go) and haven't had time to think this problem through. I haven't even tried, for example, to correlate the failures in the two searches. It looks, though, like I may have to plant some additional debugging statements.
Obvious confounding influences include differing numbers of cores and clock speeds, different networking subsystems, and higher congestion in 2.4GHz band. Sadly, I don't have any spare ports on my Ethernet switch to see if any difference shows up between wired and wifi connections.
Regards,
Kent
