Bugzilla – Bug 7254
Going from SC to SN beta, player not already added to SN is lost.
Last modified: 2009-09-08 09:27:10 UTC
Steps to Reproduce: 1. Get a Jive and a Ray that had never been added to SN(beta). 2. Connect these new Jive and Ray to wireless network, then to SC. 3. Play some songs with ShoutCast. 4. Look at the MP3Tunes Locker and thnik "Um, it sounds interesting.". 5. Click it, and message tells the user to go to "Switch to SqueezeNetwork Beta". 6. Go back to the Home page of SC and click this link. 7. The Web UI switches to the SN beta. 8. Notice the Ray has disappeared from the SC. Problem is, it is not on the SN beta either. These Ray and Jive had never been added to the SN beta. The user has no PIN for the Ray. 9. Notice Jive is not showing a PIN for the Ray to be added to SN beta. 10. The user is basically stuck.
Good point, I guess we have to not switch Rays when you click on that link. However, note that if you had entered a valid SN account in SC before you did this, the Ray would have been auto-registered to your SN account.
Can we enable this link only if you have valid SN credentials?
Fixed in 7.0 change 17677, Ray will just not switch to SN when you use the web link. The browser will still be redirected. Moving to 7.0.1 to come up with a better solution such as checking whether the Ray is linked to the user's SN account or not.
Verified to be fixed in SC 7.0.0.
Ahm... any new plans? Was working on on the server switching and came across this issue. This means we can't switch a Receiver from SC to SN using the web interface?
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
I still don't understand: you can't switch a Receiver to SN using the web interface. Is this what it should be? IMHO this is not fixed, but it's a work around to get 7.0 shipped. We should re-consider this for 7.1. Andy - is there a way to know whether a Receiver has been registered to SN or not (or some other, safe way to know whether we can switch it or not)?
Right you can't switch a Receiver because SBC needs to send a playerRegister command while moving it. But yes, if SC knew the Receiver already existed on the user's account we could support moving it from SC. In the list of players returned from SN, we could include players that are not connected. Then you could look in that list for the Receiver. Would this break the SN player display in older SC versions though?
OK I checked and it would break older versions, but we can just bump the version for that API call to /api/v2/players and have this return the full list of SN players with a flag for whether it's connected or not.
what if we returned not only the player list, but a separate "known player" list, too?
That's what the full player list would be, all players registered to your SN account.
I remembered why we did this... it's because the SBC may be registered to another SN account, and SC has no knowledge of SBC's at all. So SBC always switches the SBR to make sure it stays on the same account.
Verified fixed in Controller 7.1 r2699 Receiver r36 SB2/3 r101 Transporter r49
This bug has now been fixed in the 7.1 release version of SqueezeCenter! Please download the new version from http://www.slimdevices.com if you haven't already. If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.
Bug as written is no longer seen. Closing. Will keep eyes open for this.
Reduce number of active targets for SC