Problems with the controller

[Cold-1]

Hi,

I just upgraded my Duet to the 7.4 firmware. Also SqueezeBox Server was upgraded.
Now, I have the following problems:
1) After several factory resets, I finally managed to connect the receiver to my SB Server. However, if I go to "My Music" on the Controller, all I see is a blank page
2) The controller doesn't seem to be connected either to mysqueesebox.com nor to the SB Server (and yes, the beta option for the controller being a player is active).
3) I can't register the controller. If I go to "Connect to mysqueezebox.com", I get the "Not working" sound.
4) The controller doesn't see my old SB3. But I think this is because of the controller not registered.

If I select the receiver on the SB Server's web frontend, everithing is fine. I can make playlists and everything.

How do I reset the controller without resetting the receiver?

Controller and receiver are connected through WiFi. Both have an IP and I can ping them.

Regards, Cold-1

[Cold-1]

Ok,

some new findings:
I now mangage to join both the receiver and the SB3 to mysqueezebox.com. The I can select them with the controller. BUT the controller itself never shows as "Connected" under "Players" on mysqueezebox.com.
Also:
1) IRBlaster is not working (which is somewhat obvious)!
2) "My Music" is empty. My assumption is that Logitec takes the external IP instead of the actual IP of the server, which is just plain stupid.

Anyway, I then go to my SB Server and take the players off mysqueezebox.com. Now they can see the local music and they are also managable from within the web frontend. BUT, the controller can't see them anymore now! I have also not found any way to connect the controller to the SB Server.

With Firmware 7.3, this was working flawlessly.

Conclusion so far: mysqueezebox.com is just useless, controller is (now) useless to and I am frustrated as hell!

[Cold-1]

Ok, I wanted to give a quick update on my problems I had (see the past tense?).

My setup was this:
- Squeezeboxes are in my LAN subnet. Squeezeserver is in my SERVER subnet.
- My Slimbox 3 had no problems connecting to the Server.
- Duet (Controller and Receiver) weren't able to connect.

After uncounting attempts to get them working anyway, I was frustrated and let them be as they were (unfonctional). Last weekend I wrapped myself up to give them another chance and then I had that idea (actually, I always assumed this would work but didn't want to accept it) to set up another interface on the Squeezeserver (hail to ESX) that would be in the LAN subnet.

Now everything works. The Duet found the Server flawlessly and I am now able to control all Slimdevices with the controller.

Nevertheless, I am not fully satisfied with this solution. I put the Squeezeserver in a separate subnet by purpose. The problem is that it is not possible to manually enter the IP of the Server. The Duet always uses its autodiscovery mechanism. This is just plain stupid and hopefully gets corrected in a future FW update by Logitech.

Have good one, Cold-1

[gizek]

I don't quite follow but you can put IP of the server into Controller. I assume we are talking here about server - squeezecenter.

[Mnyb]

Ok, I wanted to give a quick update on my problems I had (see the past tense?).

My setup was this:
- Squeezeboxes are in my LAN subnet. Squeezeserver is in my SERVER subnet.
- My Slimbox 3 had no problems connecting to the Server.
- Duet (Controller and Receiver) weren't able to connect.

After uncounting attempts to get them working anyway, I was frustrated and let them be as they were (unfonctional). Last weekend I wrapped myself up to give them another chance and then I had that idea (actually, I always assumed this would work but didn't want to accept it) to set up another interface on the Squeezeserver (hail to ESX) that would be in the LAN subnet.

Now everything works. The Duet found the Server flawlessly and I am now able to control all Slimdevices with the controller.

Nevertheless, I am not fully satisfied with this solution. I put the Squeezeserver in a separate subnet by purpose. The problem is that it is not possible to manually enter the IP of the Server. The Duet always uses its autodiscovery mechanism. This is just plain stupid and hopefully gets corrected in a future FW update by Logitech.

Have good one, Cold-1

On the controller settings>advanced>remote libraries
Here you can manually put in the ip for the server

[Cold-1]

Hi gizek and Mnyb,

I know that I can set the IP there, but this doesn't work. Don't ask me why. For the time being, SqueezeCenter hast to be in the same subnet as the Duet components (Receiver, Remote) are, otherwise, it won't work. It's that simple.

In an aftermath, I wouldn't buy the Duet anymore. The architecture is too complicated and the receiver (for me, at least) has an huge disadvantage to the other Squeezeboxes: It can't use an IR-Blaster or alike to switch on other components. This renders it almost useless to me. Sadly, I didn't see this when I bought it.

Regards, Cold-1