Bugzilla – Bug 3936
Master bug for Slimserver/Squeeze Network UI integration
Last modified: 2009-07-28 20:53:23 UTC
*** Bug 1956 has been marked as a duplicate of this bug. ***
*** Bug 3269 has been marked as a duplicate of this bug. ***
Bug 4937 has an interesting issue that we should try to avoid.
*** Bug 4937 has been marked as a duplicate of this bug. ***
I'm interested in the 1956 element of this bug. I'm concerned about leaving my PC on 24x7 just to run Slimserver, so the PC now goes into Standby after 20 mins idle time and the squeezeboxes use Wake On Lan to get the PC restarted. The only problems with this setup is : - The Wake On Lan on my Transporter doesnt work properly, already logged as bug 5092 - I lose the clock and alarm features of the squeezebox, which is a shame. It would be great if the SB were to have the option to connect to Squeezenetwork if it lost the connection to Slimserver. SN could then continue the clock and alarm functions Nigel
Count me in as interested, very interested in the Bug 1956 portion of this. Having Squeezebox log on automatically to Squeezenetwork when the server goes to sleep would be wonderful.
I would also be very interested in seeing something address the "Bug 1956" part of this. 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.
*** This bug has been marked as a duplicate of bug 1956 ***
Just revisiting bugs I was interested in. This one has been marked as resolved, a duplicate of 1956. When I try and look at 1956, I see "You are not authorized to access bug #1956. " /????????