Bugzilla – Bug 14056
getModel() returns incorrect value on Fab4 and Baby
Last modified: 2009-10-05 14:31:12 UTC
Doing a getModel() on a local player on Fab4 or Baby returns 'controller' when connected to SN. If connected to SC getModel() correctly returns 'fab4' or 'baby'.
That's an SP method right?
(In reply to comment #1) > That's an SP method right? Yes. Generally SP gets it from server status. I did a test on desktop to see what SN is sending back on it's serverstatus: { --[[table: 0x162a5720]] uuid = "0333befe7a09e5674decd6521d66a1df", isplayer = 1, displaytype = "graphic-320x32", ip = "71.195.51.91", name = "Squeezebox Toucha", model = "controller", power = "1", connected = 1, playerid = "00:04:20:22:01:0b", }, { --[[table: 0x162a5740]] uuid = "26577041704a1861484a805bdec0415e", isplayer = 1, displaytype = "graphic-320x32", ip = "71.195.51.91", name = "Squeezebox Radio", model = "controller", power = "1", connected = 1, playerid = "00:04:20:26:01:50", }, Is showing "controller" for baby and touch. I confirmed baby is sending "baby" as the model in the slimproto heloPacket: 20090915 13:49:49.012 ERROR net.slimproto - SlimProto.lua:342 model: baby Andy, your move.
OK, and SN is using the slimproto deviceid to determine the model (always 9 for these). I need to update this code to use the model value.
== Auto-comment from SVN commit #7344 to the network repo by andy == == https://svn.slimdevices.com/network?view=revision&revision=7344 == Fixed bug 14056, use model value in serverstatus when available
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server! * SqueezeCenter: 28672 * Squeezebox 2 and 3: 130 * Transporter: 80 * Receiver: 65 * Boom: 50 * Controller: 7790 * Radio: 7790 Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.