Bug 614 - Cannot display text on squeezebox using web based URL CLI
: Cannot display text on squeezebox using web based URL CLI
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: CLI
: 5.x or older
: PC Windows (legacy)
: P2 normal (vote)
: ---
Assigned To: Blackketter Dean
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-10-08 11:05 UTC by Ian Hutt
Modified: 2008-12-18 11:52 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Hutt 2004-10-08 11:05:05 UTC
Trying to display some text on my squeezebox. I have used the given example 
from the FAQ. Also tried other combinations:

http://192.168.1.1:9000/status.txt?p0=display&p1=Firstline&p2=secondline&p3=5

Where slimserver is at 192.168.1.1.

The squeezebox displays nothing, other than what is previously displayed ie Big 
clock (in standby) or playlist etc when on and the IE6 web browser returns:

__center__Thursday, 7 October 2004
__center__11:02:01 AM

Thanks

Ian
Comment 1 KDF 2004-10-08 11:35:36 UTC
you need to also state the player=<playerid> in the url.
Comment 2 Ian Hutt 2004-10-08 11:45:06 UTC
Just upgraded to slim server 5.3.1 and problem resolved.
Comment 3 Ian Hutt 2004-10-08 12:00:24 UTC
Just rebooted machine with 5.3.1 and display does not work, even when using the 
&player=192.168.1.11 (The IP address of the squeezebox).

http://192.168.1.1:9000/xml/status.txt&p0=display&p1=Firstline&p2=secondline&p3=
40&player=192.168.1.11

Maybe this is a problem running as a Windows service? When it was working, I 
had it running locally but I am unable to reporduce it working...
Comment 4 KDF 2004-10-08 12:17:32 UTC
the id is the mac address of the squeezebox. look at player settings, at the
bottom.  Or you can usually see the pleryer=<id> in the url of most links in the
web interface. when grabbing from CLI, use player <index> id, insead of 'ip'
Comment 5 KDF 2004-10-08 12:29:43 UTC
also, you dont need the xml/ in there. it shoudln't hurt, but its not needed.
Comment 6 Ian Hutt 2004-10-08 12:43:51 UTC
The examples that I used came direct from the FAQ. No player ID is listed. 
Also, when I first installed 5.3.1, it worked without player ID, then after a 
reboot, stopped working. Both occasions coming from the same IE6 browser 
session on the same remote machine 192.168.1.12 - ie drop down url box was used 
to send exactly the same request to slim server so something changed as a 
result of the reboot.

The web interface documentation states that playerid can either be the IP 
address or the MAC address althought it does mention that this is dependant on 
the client. Further examples in this section still do not work, ie Will 
robinson/hi Mom. Additionally, the status being returned is correct for the 
single player in the system, so part of the request is correctly working. Im 
afraid, I do not see that the player id is the problem, or the slim 
documentation is incorrect.
Comment 7 Ian Hutt 2004-10-08 12:50:03 UTC
Removed /xml and used MAC address, still doesn't work:

http://192.168.1.1:9000/status.txt&p0=display&p1=Hello&p2=World&p3=50&player=00:
04:20:05:02:56

Comment 8 KDF 2004-10-08 13:09:29 UTC
with 5.3.1 on my windows machine, all of the above examples are working.  I'm
afraid I cannot reproduce this one.  Maybe Dean will have some suggestions.
I suggest you contact slimDevices support, as I suspect this isn't necessarily a
bug, but I'm no expert on the CLI and URL display commands so I can't think of
anything that might be making this not work for you. As you said, it worked once
after upgrading.  Another option is to try the latest nightly, though i do not
recall any specific fix that would have addressed this issue.
Comment 9 KDF 2004-10-08 13:32:46 UTC
you might also want to try posting to the discussion list.  Other users may be
able to confirm the problem, or point out what might be going wrong for you.
Comment 10 KDF 2005-03-05 01:40:57 UTC
now that there is a reworked CLI in 6.0a2, is this still a problem?
Comment 11 Blackketter Dean 2005-03-11 14:56:33 UTC
This appears to be fixed.  Please verify and reopen if it's still an issue.
Comment 12 Chris Owens 2006-06-16 14:40:38 UTC
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006.  I am setting them to targets of 6.2.1 to keep them from showing up in my queries.
Comment 13 Chris Owens 2008-12-18 11:52:03 UTC
Routine bug db maintenance; removing old versions which cause confusion.  I apologize for the inconvenience.