Bugzilla – Bug 6976
PIN screen not offered after connecting SB Duet to SqueezeNetwork
Last modified: 2008-10-02 15:22:02 UTC
When connecting Squeezebox Duet with MP firmware to SqueezeNetwork the PIN screen is not shown after both Squeezebox Receiver and Squeezebox Controller are finished upgrading to the current firmware. Steps to reproduce: 1 Make sure both SBR and SBC have MP firmware, currently 18 and 1425, and both are in a factory reset state. 2 Delete both SBR and SBC from SqueezeCenter using the admin tool, mine were 00:04:20:1A:04:57 and 0:04:20:16:08:05. 3 Connect both SBR and SBC to your network, I used the standard wireless configuration. 4 When asked to choose a music source pick SqueezeNetwork 5 Wait for both SBR and SBC to finish updating. 6 Notice that after SBC reboots and connects to SqueezeNetowrk no PIN screen was ever offered.
Steven: What was offered on the screen at the end of this process?
(In reply to comment #1) > Steven: What was offered on the screen at the end of this process? > After SBC rebooted I was now on the home menu for "Squeezebox' and connected to SqueezeNetwork. I am able to navigate the menus as if I had entered a PIN. If I choose a premium service such as Rhapsody for example it would display "Missing or invalid SqueezeNetwork account. Please check your settings and try again." I'm sure this behavior is the result of both my SBC and SBR being connected to SN but not linked to an account. Perhaps this is by design? If I only knew where to find a PIN at this point ;)
This is probably my fault.
I've have reverted r1773. I did not think this code was required anymore after the other pin changes I made but it is needed to cover the case where Ray is connected to SN with the MP firmware. It's not possible to fully test until the new firmware is on SN, so I'm rebuilding the nightly. Steven by the time your at work this fix should be deployed. Can you test the fix and reopen the bug if it still does not work. Thanks.
Firmware has been updated on SN.
This bug has recently been fixed in the latest release of SqueezeCenter 7.0.1 Please try that version, if you still see the error, then reopen this bug. To download this version, please navigate to: http://www.slimdevices.com/su_downloads.html
In testing bug 9320 today I realized afterwards that I actually experienced this bug. After successfully connecting and updating a factory fresh Jive/Ray I was never offered a PIN. It never mentioned a PIN. When I look up my Jive or Ray's MAC on SN Admin it shows as being associated with support@slimdevices.com, indicating it's not associated with any account.
Felix: I noticed you talked about this in campfire, care to comment in the bug?
James: Not sure what you mean as this bug is about not seeing the pin, but the last campfire discussion I recall was about Jive/Ray not upgrading properly. Did you really mean me and/or this bug?
I saw some errors when connecting MP 1425/18 to Production.SN. the Ray and Jive would BOTH update at the exact same time (no delay for Jive) after the update, Ray would be assigned to the "support" account on SN and Jive would be lost. I would have to do a factory reset on both to get them attached properly to SN. Using Refresh 2063/18 the Ray would go to Blue Death when first connecting it to SN, Jive would be sitting at the "select network" screen and be non-responsive. after about 15-30 seconds I could move the selector on Jive up and down, but could not select anything.
Steven, if you would try to remember to input the version you originally saw the bug on, it would make me less confused. I'm going to assume from the bug number that you saw this with the 7.2.1 beta. So with the SBC FW that comes with 7.2.1, you can't connect the SBC to SN? That will need to get fixed for the release.
Chris, it would have been whatever SqueezeNetwork version was running on 02-05-2008 and was fixed on 02-06-2008. I don't think it actually involved SqueezeCenter at all. I have not personally looked at this bug since it was reopened by Dan on 08-28-2008.
I can connect a 7.2.1 FW Duet to SN without problem. Please re-open if there's a real bug to fix here.