Squeezebox Problem. Again.

[Stratmangler]

Have you tried swapping out the PSU?
The one supplied with the Touch is a cheap 'n' nasty SMPS, and it's not unknown for them to die.
And the PSU beginning to fail could cause such a problem.

[Stratmangler]

My last post isn't appearing at my end, so I'll attempt to replicate it.

Is the Touch on its original PSU?
If it is it's a cheap 'n' nasty SMPS, and it's not unknown for the supplied PSUs to gradually fail, and in the process cause all sorts of weird and wonderful problems.

The other thing you could try is to factory default the Touch and start again, but if the PSU is beginning its death throes this would not be of any great advantage.

[icehockeyboy]

My last post isn't appearing at my end, so I'll attempt to replicate it.

Is the Touch on its original PSU?
If it is it's a cheap 'n' nasty SMPS, and it's not unknown for the supplied PSUs to gradually fail, and in the process cause all sorts of weird and wonderful problems.



The other thing you could try is to factory default the Touch and start again, but if the PSU is beginning its death throes this would not be of any great advantage.

It's an aftermarket job....

[Stratmangler]

It's an aftermarket job....

So what about doing a factory reset?

[WAD62]

And is there a longer term fix to stop it happening?

...if you don't want to keep waking up to Sonny & Cher ...I'd suggest you use the touch in it's preferred configuration, I.E. with LMS running on another network device, NAS, Pi, laptop etc.

My guess is you're pushing the Touch beyond it's capabilities...

[Stratmangler]

...if you don't want to keep waking up to Sonny & Cher ...I'd suggest you use the touch in it's preferred configuration, I.E. with LMS running on another network device, NAS, Pi, laptop etc.

My guess is you're pushing the Touch beyond it's capabilities...

+1
Last time this problem raised its head Craig was using a second Touch running off the same TinySC server.

[WAD62]

+1
Last time this problem raised its head Craig was using a second Touch running off the same TinySC server.

If I remember correctly the latest Raspberry Pi is something of super computer compared to the spec of the Touch!!!

[Stratmangler]

If I remember correctly the latest Raspberry Pi is something of super computer compared to the spec of the Touch!!!

You're not wrong there!

I wonder if assigning static IPs on the Touch players would improve reliability?
That and reserving the allocated addresses on the router for the Touch players.
If there has been a change of service provider/router then the IP address leasing might not be as long term as it once once.
I had a similar issue when Virgin sent me a new router - the old one held onto licences so that they were effectively static, whereas the new one gives devices a new IP address if you happen to sneeze at the wrong moment.
I ended up reserving an IP address for my NAS on the new router, and then making the address static on the NAS in order to stop the damned thing going walkabout on the network.

Just a thought ....

[icehockeyboy]

You're not wrong there!

I wonder if assigning static IPs on the Touch players would improve reliability?
That and reserving the allocated addresses on the router for the Touch players.
If there has been a change of service provider/router then the IP address leasing might not be as long term as it once once.
I had a similar issue when Virgin sent me a new router - the old one held onto licences so that they were effectively static, whereas the new one gives devices a new IP address if you happen to sneeze at the wrong moment.
I ended up reserving an IP address for my NAS on the new router, and then making the address static on the NAS in order to stop the damned thing going walkabout on the network.

Just a thought ....

If only I were capable of carrying the suggestion out......

[mikeyb]

It's not a BT smart hub you use by any chance, I've ditched mine as it played havoc with my Pi/MoOde setup