Bugzilla – Bug 15178
fab4 doesn't connect to its own TinySC instance, if libraryname is changed
Last modified: 2010-04-08 17:26:00 UTC
TinySC is configured to use the device's name as the "libraryname". Renamed fab4 to "Squeezebox Touch3", which triggered setting libraryname to the same value. This lead the device to no longer connect to its own TinySC instance. Looking at its configuration files I found the following: /etc/squeezeplay/userpath/settings/SlimDiscovery.lua: settings = { playerId="00:04:20:22:01:0c", serverUuid="73ef8617-43a0-4071-85ed-4cadd11acd2d", currentPlayer="00:04:20:22:01:0c", serverInit={ip="192.168.0.2",}, squeezeNetwork=false, playerInit={name="Squeezebox Touch",model="fab4",}, serverName="Squeezebox Touch", } /etc/squeezeplay/userpath/settings/Playback.lua: settings = { enableAudio=1, squeezeNetwork=false, serverUuid="73ef8617-43a0-4071-85ed-4cadd11acd2d", powerState="on", volume=93, serverInit={ip="192.168.0.2",}, serverName="Squeezebox Touch", playerInit={name="Squeezebox Touch3",model="fab4",}, captureVolume=40, } serverName in both cases still is the old value, playerInit.name isn't the same for both... I haven't been able to easily reproduce this. It happened after I switche back and forth between different servers. But it never happened when changing a full SBS' libraryname value.
Ok, this seems to be related to my recent changes to sync libraryname to playername: switching to some other server, then back to TinySC triggers something which changes the playername back to the old name, which in turn renames the libraryname back again. This means that while it's trying to connect to "SBT3", this latter is being renamed to "SBT"
difficult to estimate since it's not an easily reproduced bug. budgeting a half day
Ben - the real bug is that SP based players don't keep their name. They always accept whatever name was stored on the server it's connecting to, instead of telling the server its new name. I just switched between three different server (2x SBS and TinySC), and every time it changed its name. I'll file a new bug for this issue. We'll then probably be able to close this one in five minutes.
This issue was triggered by bug 15179. Now that it's fixed, this issue is gone as well. Let's keep fingers crossed.
This bug has been marked fixed in a released version of Squeezebox Server or the accompanying firmware or mysqueezebox.com release. If you are still seeing this issue, please let us know!