I really hate the Duet

[paulster]

I give up. Felix hasn't responded to the bug once despite being the owner since it was originally logged, and neither he nor Andy has responded to PMs about it to try and get it re-assigned since Andy usually works on the IP3K firmware.

Now I'm well aware that every bug can't have the same priority but this has been something Logitech has introduced that's essentially broken the product in a normal use case, and I really don't think ignoring it is really acceptable.

[Mnyb]

I give up. Felix hasn't responded to the bug once despite being the owner since it was originally logged, and neither he nor Andy has responded to PMs about it to try and get it re-assigned since Andy usually works on the IP3K firmware.

Now I'm well aware that every bug can't have the same priority but this has been something Logitech has introduced that's essentially broken the product in a normal use case, and I really don't think ignoring it is really acceptable.

Can't see much action in the bug report, you communicated some other way ? :-/

In the meantime set your receivers to static-ip , while I used mine, it was always static .

But this bug is going to frustrate a large user segment that is using DHCP .

Historically slim devices dhcp implementations has been so and so , so I always used static ip.
But the Touch seems to work really nice in this respect had one of mine running by dhcp for a couple of months just to try , this won't make any duet user happier just saying..

[verypsb]

All my Squeezeboxes (Touch, Boom, Classic, and Receiver/Duet) have always been using DHCP, none, including the Receiver, exhibit the problems mentioned in the bug report. Not that I'm saying the bug doesn't exist, but the DHCP problem doesn't seem to be present in all environments...

[w3wilkes]

I've also experienced the "stuck on blue LED" on my SBR here on firmware 77. I thought that the blue LED meant I was done with connecting to my network and have a IP address from DHCP, but haven't connected to either MySB.com or my own Squeezebox server. Last time this happened I was not able to get past the blue LED with any of the standard factory reset options that Logitech provides or recommends. The only way I finally got connected to my local Squeezebox server was to use NET::UDAP to populate my Squeezebox server IP address (This is a static IP on my network) in the Squeezebox Receiver! See this post for details of what I ended up doing;
http://forums.slimdevices.com/showth...l=1#post702992
This leads me to believe the problem might not be getting a IP from DHCP since the blue LED says I have a IP and I can ping the receiver by IP when the LED is blue. Perhaps if the receiver were stuck on a green LED I'd believe it was related to getting a IP from DHCP.

[TheLastMan]

When I first got my Duet it was endlessly frustrating. Major networking issues, and parties ruined, with early firmware. I nearly junked the kit around the release of SBS 7.1. It eventually became stable with SBS 7.3.3, which I stuck with as long as possible. It started to work so well that I bought another receiver (glutton for punishment!).

Around the time of that firmware release I had discovered net:UDAP (the Windows EXE version) and fixed the IP addresses of my two receivers along with references to the fixed IP of my server and router/gateway. I actually found the instructions very clear with a very short learning curve. It probably helps to be reasonably familiar with network terminology.

They are now the most stable devices on the network! I cannot remember the last time I saw the dreaded "blue light".

I have fixed the IP of the Controller in the past but now it works really well with just a reserved IP.

I control the system with iPeng and the Controller as well as my laptop.

The Controller and Receivers have now worked pretty well flawlessly for two years. Music plays really well, all the family enjoy using the system, much enhanced by Triode's Spotify and BBC iPlayer plugins. I have taken advantage of a cheap offer and picked up a second Controller for £75 to use as a backup in case my first one fails.

One Receiver is wireless and the other uses a wireless to cable "bridge". Both synchronise fine.

So, I am afraid, apart from the first 12 months or so of ownership, my experience could not be more different to poor old Model Citizen.

I think he would have been OK if he had cracked net:UDAP. If he has Windows, there is a simple .exe that cuts out a lot of the messing around (it is on the fourth or fifth post in the net:UDAP thread).

I found a major point that some miss is that it is best to use net:UDAP with a computer that is not connected to any other network at the time. I use a laptop and just switch off the wi-fi. When you plug the Receiver network cable in it automatically sets up a sub-net between itself and the PC / laptop. If your PC / laptop already has an IP this can lead to the Receiver not being discovered.

Once the Receiver was discovered the rest of the process was a matter of copying and pasting a pre-prepared command line entry followed by the save and exit procedure. Once you have done it once or twice it takes about 2 or 3 minutes. The only times I have changed the setup is when I have been updating the rest of my network and needed to enter new IP addresses.

I agree completely that you should not have to use third party software like this to get it to work reliably. This is clearly a design flaw of the "screenless" Receiver. A mistake Logitech are unlikely to repeat.