Bug 1956 - auto connect to squeezenetwork when slim server offline
: auto connect to squeezenetwork when slim server offline
Status: CLOSED FIXED
Product: SqueezePlay
Classification: Unclassified
Component: Networking
: unspecified
: PC Windows (legacy)
: P1 enhancement (vote)
: 7.4.0
Assigned To: Wadzinski Tom
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-08-09 20:02 UTC by jtahlborn
Modified: 2009-10-05 14:36 UTC (History)
9 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jtahlborn 2005-08-09 20:02:55 UTC
don't know if this is already in the works, but the whole squeezenetwork thing
is way cool, except for the fact that it requires manual intervention. the ideal
scenario for me would be that when the slim server goes offline (i turn off the
computer), the sb2 automatically connects to the squeezenetwork. when the slim
server comes back online, the sb2 switches back. obviously, some people may not
want that behavior so ideally it would be configurable. just a thought...
Comment 1 Blackketter Dean 2005-08-09 20:20:42 UTC
This is a feature of the player and a good idea.
Comment 2 Christian 2006-01-27 11:42:33 UTC
This feature sounds really great! It would dramatically increase the number of SqueezeNetwork users, I think.
Comment 3 Michel 2006-05-16 20:49:56 UTC
Requested on the "french forum" by

Jean-Claude
France - Saint Amour
http://www.fmprod.fr

and 
Michel
mftech@videotron.ca

This is an excellent idea.
Comment 4 Marc Auslander 2006-05-17 16:22:49 UTC
Let me cast a negative vote - or at least a plea for configurability.

My slim server is normally up all the time.  We don't use squeezenetwork.

So I'm not home.  My wife reboots our PC.  If the SB connects to the squeezenetwork, she is just going to be confused.

In fact, its already happened to me through inadvertent key presses (or maybe is was the key press queuing problem) and it took a bit for me to figure out what was going on.
Comment 5 Dan Sully 2006-08-04 17:29:26 UTC
Untargetting for post 6.5 assessment.
Comment 6 Chris Owens 2006-08-16 19:07:42 UTC

*** This bug has been marked as a duplicate of 3936 ***
Comment 7 Jon Pawley 2008-03-29 23:22:37 UTC
I would love to be able to turn off my SqueezeCenter server, and have my Squeezebox automatically try to connect to the SqueezeNetwork, in order to maintain the clock and alarms. Then, if my server was later powered up, it would be great to have the Squeezebox disconnect/sign-out/whatever... from SqueezeNetwork and connect to the local server again.
Comment 8 Chris Owens 2008-06-02 11:30:40 UTC
We need to define some things about this.  What if you are playing something on SN and the local SC comes back?  Are there items that will confuse the user about where they're connected.
Comment 9 Chris Owens 2008-06-02 12:03:14 UTC
*** Bug 3936 has been marked as a duplicate of this bug. ***
Comment 10 Blackketter Dean 2008-06-19 17:19:01 UTC
Waiting on feedback from mdilley
Comment 11 Blackketter Dean 2008-08-04 12:38:24 UTC
Not going to make it into 7.2.  Mike, please update...
Comment 12 Blackketter Dean 2008-10-14 20:43:48 UTC
*** Bug 9478 has been marked as a duplicate of this bug. ***
Comment 13 Mickey Gee 2008-11-17 10:52:44 UTC
Not going to make it into 7.3 -- Mike D still working on it.
Comment 14 Blackketter Dean 2008-11-17 11:55:32 UTC
Let's get some UI thinking on this for the 8.0 release.
Comment 15 Weldon Matt 2009-01-22 10:24:22 UTC
As part of the Liberace design, the user will not be asked to choose between connecting to "SqueezeCenter" and connecting to "SqueezeNetwork."  Instead, which service the Squeezebox connects to should be a function of what the user chooses to listen to (streaming from a PC/Mac will connect to that machine's SqueezeCenter; playing files from an SD card on a Fab4 will utilize the built-in version of SqueezeCenter, and playing music from an internet radio station or music service will connect the Squeezebox to SqueezeNetwork).
Comment 16 Jim McAtee 2009-01-23 04:01:49 UTC
I have an SqueezeNetwork account but use it very rarely.  If this is implemented, then it _must_ be a player option.  I do NOT want any player to ever connect to SqueezeNetwork on its own unless I've set the option.
Comment 17 Blackketter Dean 2009-02-25 16:57:05 UTC
JJ: why is that?  If your SC went away you'd want to be able to listen to internet radio, etc, right?
Comment 18 Jim McAtee 2009-05-28 11:34:57 UTC
(In reply to comment #17)
> JJ: why is that?  If your SC went away you'd want to be able to listen to
> internet radio, etc, right?

No, I would not.
Comment 19 Weldon Matt 2009-05-28 13:19:26 UTC
Jim: please elaborate.  I can't do anything with an "I don't want to listen to internet radio without SC" type comment.  What's your real issue with Squeezenetwork?
Comment 20 Weldon Matt 2009-05-28 13:57:18 UTC
Marc just sent me an email about this, so I will respond to his bug comment.

Marc said: "My slim server is normally up all the time.  We don't use squeezenetwork."

With the changes we've made, the device is connecting to SN out of the box (we're not calling it that anymore, but that's the deal).  As part of setup you create a "mysqueezebox account" (this is an SN account), or log in to your current one.  As far as most users are concerned, this won't be optional.  You just put in an email address and a password. Done, you're logged in. 

So the "I don't use squeezenetwork" case isn't going to apply to most people (yes, I know it applies to you, but I'd call you an "expert user.")

Marc said: "So I'm not home.  My wife reboots our PC.  If the SB connects to the
squeezenetwork, she is just going to be confused."

No.  She won't know the difference.  That's the point.  The switch will be entirely transparent and automatic.  The word "squeezenetwork" won't show up anywhere, she won't have to log in to anything, the menu structure won't change, the settings on the device won't change.  She won't have to do anything special at all to use the device differently.

the only change in the UI will be the fact that your local music library won't be available under "my music" until the server is turned back on.

That's it. Done.  Keep in mind that we're not totally done with this and are still working out a lot of kinks in terms of behavior and performance.
Comment 21 Richard Titmuss 2009-07-27 01:12:52 UTC
Reset priority before triage.
Comment 22 Jon Pawley 2009-07-27 15:26:52 UTC
Hi. Is there any chance of a Squeezebox issuing a WOL magic packet when it attempts to switch from SqueezeNetwork to SqueezeCenter? The use case I see here is (based on 7.3):

- machine running SqueezeCenter is shutdown to save power, using the SrvrPowerControl plugin (http://code.google.com/p/srvrpowerctrl/).
- at a later stage user "turns on" the Squeezebox, and chooses to "Connect to SqueezeCenter"
- Squeezebox issues WOL packet and waits for SqueezeCenter to respond.

(Should I open a seperate bug about this?)
Comment 23 Wadzinski Tom 2009-07-30 04:27:54 UTC
Autoswitching has been in place for a while. There are a few bugs related to it 
that are addressed in other bugs.
Comment 24 James Richardson 2009-10-05 14:36:16 UTC
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.