9.3.7 WiFi Issue.

[KeithC]

I have several Moode systems on a range of Pi's, with music stored on SD cards, NAS, USB, and NVME.

Since upgrading to 9.3.7, connections over wifi hang after playing one or two tracks, requiring a reboot. The players still pump out audio, however neither browser nor ssh interfaces recognise the server.

Wired connections still work correctly.

I have seen this on various CM5, Pi5, Pi400, Pi4, Pi 2W systems with small local libraries (100MB to 450MB), larger libraries on attached drives (to 2GB) and 2GB libraries held on NAS. I typically play tracks randomly, however the same happens if I use a playlist. Different output devices (hdmi, usb, digi & dacs). 

Unfortunately, I did not note what version I upgraded from, and no errors are reported in the system log.

I initially thought there may be a hardware or power issue, but exhaustive testing eliminates albut wifi. 

I usually access via Mac or iPhone, but did try Firefox on a W11 system.

All wireless access has been via a Linksys MX4000 mesh network.

[TheOldPresbyope]

@KeithC

I, for one, am having difficulty parsing this paragraph

Since upgrading to 9.3.7, connections over wifi hang after playing one or two tracks, requiring a reboot. The players still pump out audio, however neither browser nor ssh interfaces recognise the server.

What "connections"? What "server"? Do you mean you can't reach your moOde player from other hosts or your moOde player can't reach other servers?

I've not had any trouble with various moOde 9.3.7 players connected via WiFi to my LAN. Some have been powered up 24/7 for weeks without any connection problem.

Regards,
Kent

[Tim Curtis]

Try a fresh r937 image and if the problem reoccurs post the 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.

[Nutul]

Wired: WORKS
Wireless: DOES NOT
1. check IPs (particularly static ones on wi-fi - against DHCP pool and its reserved range, and the like...)
2. check bandwidth (aka, switch to 5GHz instead of 2.4)

As I see now that I read till the end...
MESH networks - not always, but... - make a mess when they decide "there is a need to reconnect this client on a different pool"...

It is me, I know, but... I never liked mesh nets. IMHO they do not yet work reliably. And in audio streaming it is crucial.

[KeithC]

@KeithC

I, for one, am having difficulty parsing this paragraph

Since upgrading to 9.3.7, connections over wifi hang after playing one or two tracks, requiring a reboot. The players still pump out audio, however neither browser nor ssh interfaces recognise the server.

What "connections"? What "server"? Do you mean you can't reach your moOde player from other hosts or your moOde player can't reach other servers?

I've not had any trouble with various moOde 9.3.7 players connected via WiFi to my LAN. Some have been powered up 24/7 for weeks without any connection problem.

Regards,
Kent

"Connections" = browser or ssh interface on my iPad/Iphone/Mac. "Server" = whatever MoOde pi device is outputting the audio. Music output continues, however I cannot interact with the MoOde device without a hard reboot.

Didn't have any problems before updating to 9.3.7. (that'll learn me.... ). I have 3/4 MoOde servers with wired connections, 2 with wireless connections due to location, and 2 wireless for outdoor use. All act independently - I don't do any multi-server nonsense - my wife is much happier if I restrict the noise to a single room. Preferably in a different building. 

Since discovered that when a wireless ip locks out, connecting to the pi via a wired connection not only works, but subsequently the wireless ip also works. Weird.

[TheOldPresbyope]

@KeithC

Ok, thanks for the explication.

What you describe is not normal. I'm not sure where the difficulty is arising. All I can suggest without further details about Interface settings and about your local WiFi access point is that you

1) connect to each player via Ethernet and reenter the WiFi interface credentials: set the Network SSID to None, then SCAN, select the SSID, and enter the Password. Save. Power down, disconnect the Ethernet cable, and reboot.

-or-

2) start over again with a fresh image of 9.3.7.

Incidentally, if you want to use a fixed WiFi IP address, I recommend keeping DHCP as the address method and reserving the desired IP address on the Access Point (consult your AP docs and, if needed, you favorite InterWeb™ search engine).

Regards,
Kent