Bug 15103 - Incorrect capabilities for signalstrength
: Incorrect capabilities for signalstrength
Status: NEW
Product: Logitech Media Server
Classification: Unclassified
Component: CLI
: 7.4.2
: PC Debian Linux
: -- minor (vote)
: Future
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-11-12 02:37 UTC by Bjørn
Modified: 2011-11-06 23:23 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 Bjørn 2009-11-12 02:37:51 UTC
I'm monitoring different aspects of the Squeezebox Server using the CLI. So as not to monitor devices with useless/invalid information (such as signal strength on a streaming http player, in this case, Rhythmbox 0.12.0) I thought I should check the capabilities first. However, it seems the capabilities for signalstrength is broken:

 # rlwrap telnet localhost 9090
 Trying 127.0.0.1...
 Connected to localhost.
 Escape character is '^]'.

 version ?
 version 7.4.2

 player count ?
 player count 3
 
 player id 0 ?
 player id 0 00%3A04%3A20%3A16%3Ad7%3Afa

 player model 0 ?
 player model 0 receiver

 can 00:04:20:16:d7:fa signalstrength ?
 can 00%3A04%3A20%3A16%3Ad7%3Afa signalstrength 0

 00:04:20:16:d7:fa signalstrength ?
 00%3A04%3A20%3A16%3Ad7%3Afa signalstrength 87
 
 player id 1 ?
 player id 1 10.10.6.10

 player model 1 ?
 player model 1 http

 can 10.10.6.10 signalstrength ?
 can 10.10.6.10 signalstrength 0

 10.10.6.10 signalstrength ?
 10.10.6.10 signalstrength 0

I would assume that "can 00:04:20:16:d7:fa signalstrength ?" should give the response '1'?

Furthermore, should "10.10.6.10 signalstrength ?" give a valid response (0)?

SqueezeboxServer version is 7.4.2~29203 (deb http://debian.slimdevices.com testing main).

Thanks.
Comment 1 Chris Owens 2009-11-16 09:18:48 UTC
This may not get good attention from our developers unless someone is trying to do something pretty cool with it.  :)

Patches are welcome as always.
Comment 2 Alan Young 2011-11-06 23:23:14 UTC
Unassigned bugs cannot have a priority.