Author
Topic: squeezebox (Read 10036 times)

Hi, I read on the logitech site that configure the Squeezebox Receiver need a Squeezebox classic. This applies even if you use LinuxMCE? But most of all, you can use the Squeezebox Receiver with Linuxmce?

I just noticed that SqueezeCenter is using my external IP address of the Hybrid, and not the internal, also if I go to (Advanced/Configuration/SLIM Server) it says Loading SqueezeCenter but nothing happened !! How do you set SqueezeCenter IP to 192.168.80.1 Because both players set for 192.168.80.1 SqueezeCenter server.

Update, if I go to "http://localhost:9000" I get the SqueezeCenter, from there I can play music on both devices (Boom & Receiver) but if I play a song on the MD, and go to the FloorPlan and select the squeezbox no audio output In the past I don't remember I did anything special to do that !!!!

Yes, LMCE detected both SqueezeBoxes, and created a Slim Server Streamer, and it is registered, also 2 Child "SqueezeBox Player" devices were created under the Streamer, but these Child devices the status shows "**RUN_Config**" and "Registered =NO" Here's the Follow Log from the Streamer

This may be stupid, but I was pulling my hair out for a while over a squeezebox that wasn't working with an earlier 0810 alpha build. Nothing seemed wrong, but I couldn't get it to play (using lmce), despite multiple router reloads. I decided to reboot the PC, and it started working and has been since.

OK, trying to recall as I haven't got the slimserver/squeezecenter device installed at the moment....

port 9000 as I recall is used for the web interface to what is now known as SqueezeCenter (although it seems as though 0810 still calls it SlimServer). You can connect to that address:port with a web browser to control the SqueezeCenter directly. However, SqueezeCenter (and the older SlimServer) also has another port called the CLI port that allows you to connect to and relay commands to programatically. This is the interface that LMCE uses to send commands to the Squeeze system.

The LMCE DCE device responsible for this (slimserverstreamer, I think) connects to SqueezeCenter through this port, then receives LMCE DCE commands/events from the DCERouter, translates them, and relays them to the SqueezeCenter through the CLI port (not the web interface). The SqueezeCenter (and SlimServer before it) then connects to the appropriate SqueezeBox and sends the necessary native commands to achieve the result required.

From your log output, it would appear that the LMCE DCE device, is #59 (the parent of the 2 actual devices, and responsible for relaying the commands, both in the LMCE schema and the SqueezeCenter "real world"), and that this DCE device believes that the CLI port is 9090.

Now I don't know if this has changed since the 0710 version I am used to, or my memory is faultly, but nothing about 9090 rings a bell. From memory, the port number is configured in the SlimServer DCE device's Device Data. If it is not correct, then either you need to update this Device Data field to reflect the correct port that SqueezeCenter is using, OR connect to SqueezeCenter on its web admin interface (http://192.168.80.1:9000) and change its CLI port configuration to be 9090. Only then can then communicate correctly. Then do a reboot.

From the logging it appears that the DCE device attempts to connect on 9090.... it doesn't explicitly say this fails, but doesn't confirm it either. Then on subsequent reattempts it appears that it may be failing because it never connected correctly and never shutdown correctly either (probably a bug), so LMCE thinks it is already running (which it is) and working/communicating fine (which it isn't).