Back when I purchased the devices and built up my network, all devices were given static IP addresses, just to reduce complexity. The only device I never managed to assign a static address to was the Receiver. The entire set-up was a pain to administer, so at some point in time, I switched back to DHCP and only fixed the addresses centrally on the router.
Results 21 to 30 of 61
Thread: Receiver keeps disconnecting
-
2020-11-15, 15:49 #21SCALEO Home Server 2105 & piCorePlayer 6.1.0 | Logitech Media Server 8.2.0 | Server Power Control 20120716.103808 | Transporter & Duet & Touch & Boom & Radio | Rotel RC-995 & RMB-100 | Nubert NuVero 140
-
2020-11-15, 23:56 #22
- Join Date
- May 2017
- Posts
- 756
SqueezeBoxes: 1x Transporter (Living room) 1x SB2 (shed), 1x Radio (Kitchen), 1x Boom (Dining room), 1x piCorePlayer (jacuzzi), 1x piCorePlayer (Garden) 1x OSMC + Squeezelite (Movie room), 1x Touch (Study 2), few spare unit's (SB2, SB3, Boom, Touch)
Server: LMS on Pi3B+ 8.1.2 on PcP 7.0.1
Network: Draytek, Netgear Smart Switch 24p, Ubiquiti PoE, 3x Ubiquity
-
2020-11-16, 12:34 #23
Just disconnected again, but re-connected over dinner.
SCALEO Home Server 2105 & piCorePlayer 6.1.0 | Logitech Media Server 8.2.0 | Server Power Control 20120716.103808 | Transporter & Duet & Touch & Boom & Radio | Rotel RC-995 & RMB-100 | Nubert NuVero 140
-
2020-11-18, 02:13 #24
- Join Date
- Dec 2009
- Posts
- 78
I've just been fighting a similar battle with a Receiver.
I too initially suspected WiFi. But it's not!
I have replaced the power supply and normal service has been resumed. I used an old 9v PSU from a Binatone DECT phone set. This improved matters initially but was not perfect. So I soldered a capacitor across the 9v input inside the unit and now it works properly. Conclusion at this point is that these units are not very tolerant of a poor PSU and the supplied PSU degrades over time.
Tony
-
2020-11-21, 17:00 #25
I may try the capacitor, too, because nothing I do seems to fix the problem for good.
SCALEO Home Server 2105 & piCorePlayer 6.1.0 | Logitech Media Server 8.2.0 | Server Power Control 20120716.103808 | Transporter & Duet & Touch & Boom & Radio | Rotel RC-995 & RMB-100 | Nubert NuVero 140
-
2020-11-27, 05:09 #26
-
2020-11-27, 05:28 #27
The Touches use DHCP, too, but the Receivers always lost the connection with DHCP. That's why I switched to static(! not designated) IPs for my Receivers, see here.
There's a new configuration tool you might want to try (full disclosure, I didn't test it, yet).QLMS 8.2@2.21 x64 (digimaster) with perl 5.30.1 / QNAP 469L QTS 4.3.4
-
2020-11-27, 13:28 #28SCALEO Home Server 2105 & piCorePlayer 6.1.0 | Logitech Media Server 8.2.0 | Server Power Control 20120716.103808 | Transporter & Duet & Touch & Boom & Radio | Rotel RC-995 & RMB-100 | Nubert NuVero 140
-
2020-11-27, 16:14 #29
-
2020-11-28, 14:18 #30
Any hints on how it is supposed to work? When I put the Receiver into configuration mode, it disconnects from the network. The tool does not discover the player. I tried to disconnect the PC, too, and I can see the network provided by the Receiver, but neither can I connect to it nor does the tool discover the Player. Do I have to set up a wired connection between the PC and the Receiver?
SCALEO Home Server 2105 & piCorePlayer 6.1.0 | Logitech Media Server 8.2.0 | Server Power Control 20120716.103808 | Transporter & Duet & Touch & Boom & Radio | Rotel RC-995 & RMB-100 | Nubert NuVero 140