Bugzilla – Bug 5437
Add "Controller Info" to Server Settings (in Slimserver 7)
Last modified: 2011-01-14 12:23:45 UTC
(putting this in Jive Software so I can make it private, but it belongs in Slimserver) --- Request from Support to help diagnose issues --- In Slimserver 7 can we add a section to the bottom of Server Settings > Basic Settings, below "Version Info", similar to this... Player Info Player Firmware: XX Player IP address: xxx.xxx.xxx.xxx Player connection: [wireless or ethernet] Player MAC address: <MAC> Controller Info: Controller Firmware: XX Controller IP address: xxx.xxx.xxx.xxx Controller MAC address: <MAC>
Is there more information you are going to add to this bug about upcoming products that merits its secrecy? I see nothing here that anyone who reads the forums doesn't already know.
You're right. Moving this to where it belongs.
There is already a Player info section in player settings. Not sure that player info belongs in "server settings" as they are not player specific. What about the case of multiple players, multiple controllers?? Perhaps a "Network Info" page might be more appropriate, which could then list server config info, all players and info, all controllers and info. It should be possible to borrow a fair bit of code from the existing Information.pm player ui module.
Very good points. Now that we have a third device that is connected to SlimServer, I guess my goal is a centralized information page we can point a customer to in order to gather what relevant info we need.
Trouble with getting jive info...I don't think the server gets any aside from the requests.
Created attachment 2180 [details] Slim/Web/Settings/Server/Status.pm initial server module. This has no support for Jive as there is currently no info that the server has about jive.
Created attachment 2181 [details] HTML/EN/settings/server/status/html web page for viewing server status. not a complete list yet, but that should be fleshed out so that Player UI, Web UI and Jive UI show the same things. Information screen on Player UI shows plugins installed, which might also be useful (albeit best switched to third-party plugins only).
All of the strings used are existing, save for these two: SERVER_STATUS EN SqueezeCenter Status SERVER_STATUS_DESC EN This is a complete listing of the details of your SqueezeCenter and all devices connected to it.
added initial workup to trunk at change 13349. Please feel free to let me know what you think. url to access the page is http://serverip:9000/settings/server/status.html
Finally getting around to comment on the new "Status" tab... KDF-- it looks great! I love that it includes info on the Library and also the last music scan. Is there really no way to include information on Jive or a "Controller"?
No way yet. The controller currently only makes requests and subscribes to event notices. There is a UUID used to establish the connection, but not much else.
KDF should we keep this bug open?
yes, if you eventually want controller info shown on SC web interface :) but I think it has to be moved to a future enhancement.
Created attachment 2791 [details] jive info so far this is a ui for what I can extract so far. It parses the active connections from cometd to get the jive client ID and version.
dunno why I'm assigned. I've already shown that there is nothing I can do. Please add some info packet that can be returned from Controller if you want the changes. The patch I have above is useless without something relevant. Dean, can you maybe decide on what should be available. Dan, I assume your initial request is the wish list, but speak up if you want more. I suppose it then needs to go to Richard or Ben in order to get the right info sent form Controller. I don't know the protocol well enough, nor will I have the kind of time to ride the learning curve. Sorry guys, but for my own sanity I've changed priorities for a while. Far too pissed off at general tones these days to continue to give up every spare minute.
I'm an innocent user who found this before asking for it as an enhancement. So - users (at least one) would like this nicety. But - for this, and i think in general, you will want to start naming the controllers. As another example, my router "knows" the name of the receiver, but the controller doesn't have a name. Obviously, all this is way down on my list of wants.
As controllers can also be players in 7.2, I think this is best moved to that release. We'll know a bunch about the device as a player, but we'll need to add some additional info for the controller part (version numbers, etc...) Ben: can you take a look at this?
punting to 7.3
Michael: is your new info screen fixing this?
No, not yet. This bug is about Controller information being available in web/player UIs. We've been discussing this topic in the weekly meeting. It doesn't make sense adding this now, as it should be available anyway as soon as SBC is a slimproto player.
*** Bug 9731 has been marked as a duplicate of this bug. ***
Ben - assigning to you. We've already got some information in the menus now, but we need to add some slimproto goodness to the Controller side.
Michael, I'm still unsure what it is I'm to do for this bug. I'll try to ping you in campfire about it this week...
sending the controller info is a tricky part of this bug. That part of it won't get done for 7.3. capture of chat on the issue... Michael H. How can I "go" to an applet from within my own menu? Ben K. "go" to an applet from within my own menu...you mean you want an SC plugin menu to call a native jive applet? Michael H. There's the NetTest applet which can launch tests on any player. It just needs to know which one. Right now it always tests the one the Controller is controlling but from within the System/Information menu we'd like to be able to test any player available Ben K. I see. That's a tough one...callbacks of items from SC-delivered items are right now by definition cli commands that come back to SC so I think the API for that needs writing Michael H. as for your question: we wanted to have information like signal strength etc. in the player information. Richard mentioned that this was part of slimproto (not sure). But this is not available unless SqueezPlay is running. So... do we need to add some CLI command to give SC some status information about Controller? Richard T. i wonder if we should punt on that feature for 7.3, instead of adding some half baked solution in. Michael H. will SP always be on on SBC? Richard T. well SP is the gui + audio playback. so yes. Richard T. i seems kind of messy right now as we have two connections comet+slimproto when the controller is running as a player. it leads to some strange interactions when we have connection problems. Michael H. enhancement request: "I don't want to see my Controller in the player list" Richard T. i'm not tackling that for 7.3, but it needs some thought for later. Michael H. bet it'll be filed? Michael H. fine with me and I guess Ben won't be disappointed neither Ben K. okay, now I'm confused. Is there something I need to do yet for 7.3 and this feature? Michael H. I don't think so. Unless you come up with a great idea for my applet launching problem Ben K. that I'd like to have a separate bug for. I'll go ahead and open it and cc: you
with only these exceptions, my bug list is being retargetted for 8.0 for 7.3.2 (very soon): https://bugs-archive.lyrion.org/show_bug.cgi?id=7186 Browse albums/artists/genres/ years should remember previous state for 7.3.3 (later, but before 8.0): https://bugs-archive.lyrion.org/show_bug.cgi?id=7139 Add editable "Network Settings" page https://bugs-archive.lyrion.org/show_bug.cgi?id=7502 Add setup mode to set Static IPs (even if DHCP is present) https://bugs-archive.lyrion.org/show_bug.cgi?id=7829 Jive menu broken if BLOCK_SIZE == list count + 1 and "Pla... https://bugs-archive.lyrion.org/show_bug.cgi?id=8878 Party Mode https://bugs-archive.lyrion.org/show_bug.cgi?id=10064 SqueezeCenter doesn't always auto-generate playerstatus w... (which will fix 8300) https://bugs-archive.lyrion.org/show_bug.cgi?id=6334 add applet for network diagnostics (currently assigned to Tom)
this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.
Michael, I'm not really sure what needs doing here...can you comment and then if I should be the one doing the work assign back to me?
Ben - in the player infos we have nice information about the players as requested by Dan: Player-Modell: fab4 Firmware: 7.4.1-r7822 IP-Adresse des Players: 192.168.0.71 MAC-Adresse des Players: 00:04:20:22:00:5b Stärke des drahtlosen Signals: 20% (you'll get the German, I'm sure ;-)) But that same information is lacking for Controller if it's not a player, as the above is all handled through slimproto negotiation I'd assume. If Controller will be a player 7.5.0 by default, then this will be resolved automatically. Otherwise I don't know.