tw99 wrote:
> Hi Greg.
>
> It's not password protected, and I am using Material Skin. The problem
> is very reproduceable, so I got a wireshark capture by leaving wireshark
> running as I suspended and re-awoke the PC. From looking at the capture
> and trying to surmise what it's doing, there are a few different HTTP
> interactions, but looking at the key one (stream 25) it seems to do the
> following:
>
> POST REQUEST WITH PARAMETERS:
> {\"ID\":0,\"METHOD\":\"SLIM.REQUEST\",\"PARAMS\":[\"\",[\"SERVERSTATUS\",0,100]]}
>
> This gets a response that lists among other things all the connected
> players *but NOT the squeezelite-X player itself*.
>
> POST REQUEST WITH PARAMETERS
> {\"DATA\":{\"RESPONSE\":\"/C9ED997C/SLIM/SERVERPREFS\",\"REQUEST\":[[\"PREFSET\"]]},\"ID\":\"38\",\"CHANNEL\":\"/SLIM/SUBSCRIBE\",\"CLIENTID\":\"C9ED997C\"}
>
> This gets a success response.
>
> POST REQUEST WITH PARAMETERS
> {\"ID\":0,\"METHOD\":\"SLIM.REQUEST\",\"PARAMS\":[\"CC:CC:09:E2:4B:D0\",[\"STATUS\",0,500,\"TAGS:CDEGILQTYSAKNS\"]]}
>
> This gets a success response with a bunch of details about the player
> with the MAC address cc:cc:..... which is the player that it always
> incorrectly picks, which is NOT the squeezelite-X player.
>
> So it looks to me like it's what I had suggested previously, at the
> point where the server is queried for the list of active players, the
> Squeexelite-X player has not yet been registered. So it can't be chosen,
> and it ends up picking the first one in the list instead.
>
> There's another stream (stream 22) as well, which looks like it might be
> the one that is actually registering the local player. That seems to get
> a failure, it then retries and gets a success, and then sends a few more
> "subscribe" requests.
>
> I've attached the full decodes as text files on the assumption they'll
> mean more to you (or mherger) than me !
>
>
> 31833
> 31834
Wow, I love folks like you that know what you are doing, thanks for the
info. The odd thing is that SLX will not attempt to load the URL until
after it receives a message from the LMS server that the squeezelite
player has connected ("client connect" or "client reconnect". If I have
just received a "client connect" message from the server, then I would
think the server could select that player.
I took a quick look at those streams, which appear to show requests to
the server coming from the skin as opposed to SLX itself. That gives me
an idea that when SLX wakes up, its browser (material skin) starts doing
its own thing before I am really ready for it to. So, even though Isay
I am not loading the url, the browser/skin actually is doing stuff
beforehand. To prevent that I thinking I need to make sure I set the
browser url to nothing on sleep, so when it wakes the browser does not
try interacting with the server until I call LoadUrl after the player is
registered.
Again, thanks!
R Greg Dawson
Squeezelite-X
------------------------------------------------------------------------
rgdawson's Profile: http://forums.slimdevices.com/member.php?userid=65236
View this thread: http://forums.slimdevices.com/showthread.php?t=108550
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins
