BOOM suddenly refuse to connect to server

[jasell]

My 3 squeezebox Boom has work almost flawlessly during 10 year (apart from fixing displays and power adapters).
But a few days ago they disconnected form my server and refuse to connect.

As all stopped at the same time I don't think it is hardware related, I wonder if it could be a Nightly release?
I'm currently at LMS Version: 8.3.0 - 1654547000

Other squeezeboxes works fine.

Any help is appreciated.

[Paul Webster]

LMS logs?

[toby10]

Reboot LMS server and each Boom? IP address change on LMS host?

[jasell]

Logs do not show anything related (just regular issues of spotty seeing an empty credential file).

LMS is restarted.
QNAP (LMS host) is rebooted.
LMS runs on same IP-address and port as the last 15 years.

Boom is restarted (long press on power button untill logo appears).
Boom restarts and and acquire IP-address.
Then it tries to access server... for days without success.

[jasell]

Seems like BOOM kan get a very short connection, sometime it pulls a screensaver that appear frozen, one time it picked up a radio stream.
When radio-stream was picked up, it played but then connection to server was lost so volume or stop did not work.

[Paul Webster]

Perhaps force it through a reset

https://wiki.slimdevices.com/index.php/Special_IR_Keys_on_Reboot_for_Factory_Reset_and_Last_FW.html

[jasell]

Perhaps force it through a reset
https://wiki.slimdevices.com/index.p...d_Last_FW.html

Tried both reset and Xilinx reprogramming.
No improvement.


Sent from my iPhone using Tapatalk

[bpa]

LMS servers announce their presence to players using a reply to a broadcast UDP packet sent by the player. So if broadcast UDP has been blocked - player will not find LMS servers.

Can you manually LMS Server IP address into a Boom (use Boom FW menu) and see if contact can be made ?

[Heuer]

Could be the host. Try installing LMS on a PC/Rpi/mac and see if the Booms connect to that server

[jasell]

LMS servers announce their presence to players using a reply to a broadcast UDP packet sent by the player. So if broadcast UDP has been blocked - player will not find LMS servers.

Can you manually LMS Server IP address into a Boom (use Boom FW menu) and see if contact can be made ?

I tried to reset WiFi settings, I use DHCP so it is a matter of requesting new IP-address.
No difference.

After a BOOM reboot I can see it in LMS for a short time, but as soon I try to access the player disappear, or just waiting a few seconds without doing anything make it disappear as well.
I tried different versions of LMS (8.3.0 and 8.2.1,) and different version of Perl (my LMS run an a Qnap with QLMS).

----

I started to investigate my network, so I started to ping my squeezeboxes, I noticed that all responded but the BOOM's.

When checking my DHCP server vs. my WiFi controller I could see DHCP reported BOOMs with unique IP, but WiFi controller (Unifi) reported all BOOMs on the same IP!
I'm not sure why, or even how this could happen. But of course this is the reason.

I did static mapping/reservation to all players and now they have unique IP addresses on both DHCP and Server, and as expected BOOMs started to work immediately.

I assume a new firmware on the AP caused this.

All is good after a few days debugging... never thought this would be the root cause.

[bpa]

I tried to reset WiFi settings, I use DHCP so it is a matter of requesting new IP-address.
No difference.

Nothing to do with DHCP.
You misunderstand - manually enter the IP address of the LMS server in the player not the IP address of the player.

After a BOOM reboot I can see it in LMS for a short time, but as soon I try to access the player disappear, or just waiting a few seconds without doing anything make it disappear as well.
I tried different versions of LMS (8.3.0 and 8.2.1,) and different version of Perl (my LMS run an a Qnap with QLMS).

Enable LMS logging such as network.protocol.slimproto to INFO, make it persistent and then restart LMS. Then reboot one Boom player (the UDP Discover broadcast packet is only sent on player power up)

[stereoptic]

Years ago I had a similar issue with wifi. I had to replace or reseat (I forget which) the wifi card. There are some instructions here somewhere how to take the player apart to get to it.
Can you connect via ethernet to see if it connects that way?

[slartibartfast]

Years ago I had a similar issue with wifi. I had to replace or reseat (I forget which) the wifi card. There are some instructions here somewhere how to take the player apart to get to it.
Can you connect via ethernet to see if it connects that way?

It would be a massive coincidence if the WiFi cards in 3 Booms failed at the same time [emoji2]

Sent from my Pixel 3a using Tapatalk

[stereoptic]

It would be a massive coincidence if the WiFi cards in 3 Booms failed at the same time [emoji2]

Sent from my Pixel 3a using Tapatalk

Yeah, play the lottery!! . I missed the post where the OP explained that he had sorted it out.

[jasell]

Problem solved!

It was my wifi controller (Unifi ) that registred each BOOM, in spite of unique MAC, by same IP address.

The address showed correct on each BOOM and thoose corresponded with the DHCP record.

As PING did not work on any of the BOOMs, I looked further trying to find some indication of what could be wrong. By coincident I saw the fault when I was looking for connection quality.

I have no explanation how this could happen, seems extremely odd.


Sent from my iPhone using Tapatalk