Bugzilla – Bug 9796
firmware messages not shown on Boom if power off brightness is set to 0 (Dark)
Last modified: 2009-09-08 09:24:29 UTC
I would like to have access to the network configuration menu directly from a turned off SB/Boom/Transporter/Receiver. If my SB3 is turned off and set to SC mode and I wantto connect to SqueezeNetwork instead I now have to first turn it on, connect to SC and then switch it to SN. This takes some time (and also it wakes up my NAS). I think that it would be better if I could acces the config menu (holding down the left arror on the remote) directly from a turned off unit. Alternatively, holding down left button on a turned off unit could show a new menu with just the two options: 1. SqueezeNetwork 2. SqueezeCenter Maybe there are some downsides to this? But I think it would be a very useful feature that I would use a lot.
can't you just press LEFT on the remote to get into that menu?
I have tried holding the left button down, this works when turned on but nothing happened when sb was turned off via remote.
Dean: can you please review and target
press-and-hold left has nothing to do with "power" state. The player is always powered, even when setting to "off" via the remote. The firmware takes over for long holds of the button, dropping back into setup mode. Even if SC is not running at the time, the button work for me (except on SBG and earlier).
Well I have SC uo and running and when I turn the unit off (after beeing connected to SC), then holding left button down does not wake my sb3 up.
I just tested switching them both to SN instead and same behaviour - holding left works when turned on but not when off.
I can't make this work as you describe, Simon. You have to hold the left arrow button for about 5 seconds, to escape out to setup. Is that what you are doing? QA: Please work with Simon to reproduce.
Yes, that is what I am doing. I think it micht have worked like you describe some time ago. Bu tI tried it with moth my SB3's and it does not work. Nothing happens when holding left down for 5 seconds.
Simon: what version of SC are you running? what version of Firmware is on your SB3? I just checked with SC 7.2.1 & SB3 r113 SC running > SB in 'off' state > press and hold LEFT 5 seconds takes me to the setup menu SC running > SB in 'off' state > SC stopped > SB goes blank > press and hold LEFT 1 seconds takes me to the setup menu SC running > SB in 'on' state > press and hold LEFT 5 seconds takes me to the setup menu SC running > SB in 'on' state > SC stopped > SB goes blank > press and hold LEFT 1 seconds takes me to the setup menu Please re-test with SC 7.2.1. SB3 r113
I did some more testing and it seems there are several issues here: Issue 1: Holding left down locked my SB3:s, power button also did not work after this, I had to unplug to get it working again. I also tried pressing the light button and that showed me the network config menu! It seems that there is a light level for that menu - and I had the light setting to off, so I did not see the network config menu. So, the menu was there all the time, I just did not see it. Why is there a special light level setting for the network config menu..? Issue 2: My SBs were already set to SN, but bringing up the network config menu woke up my NAS - I would prefer if that menu did not scan the network for SC unless really neccesary, could that be possible?
(In reply to comment #10) > I did some more testing and it seems there are several issues here: > > Issue 1: > > Holding left down locked my SB3:s, power button also did not work after this, I > had to unplug to get it working again. > > I also tried pressing the light button and that showed me the network config > menu! It seems that there is a light level for that menu - and I had the light > setting to off, so I did not see the network config menu. So, the menu was > there all the time, I just did not see it. > > Why is there a special light level setting for the network config menu..? > > Issue 2: > > My SBs were already set to SN, but bringing up the network config menu woke up > my NAS - I would prefer if that menu did not scan the network for SC unless > really neccesary, could that be possible? > Hi again, I have tried this further now and regarding my Issue 2 it woke up my NAS once only, I have tried for times since and my NAS did not wake up. Issue 1 is still there though, since there is an off-setting for the display, where it will not show the network config menu.
Simon: Please retest with SC 7.2.1 and firmware SB3 r113 I am still unable to reproduce this error as described in comment #10
(In reply to comment #12) > Simon: Please retest with SC 7.2.1 and firmware SB3 r113 > > I am still unable to reproduce this error as described in comment #10 > Hello, It has worked fine since I hit the brightness button during network config. The same had happened on both my SB3's, so it must have had to do with a setting from the web ui I guess. I think somehow my players got into the dim-level 0 (off) for the network config menu (and maybe other). So, I can no longer reproduce this behaviour.
(In reply to comment #13) > (In reply to comment #12) > > Simon: Please retest with SC 7.2.1 and firmware SB3 r113 > > > > I am still unable to reproduce this error as described in comment #10 > > > > Hello, > > It has worked fine since I hit the brightness button during network config. > The same had happened on both my SB3's, so it must have had to do with a > setting from the web ui I guess. > I think somehow my players got into the dim-level 0 (off) for the network > config menu (and maybe other). > > So, I can no longer reproduce this behaviour. > Hi again, An update: It seems that it is when connected to SC, that this happens. My SB3 is connected SC when turning it off. Then, pressing left for >5 sec will not bring up the network config menu, but then the brightness menu will. It must be besause I have set the level to 0 when off. Since I know the workaround now, I will not bother with any upgrades just for this. My setup is: 2* Squeezebox 3 with Audioengine 5 speakers 1* QNAP TS-109, Version 2.1.0 build 0624T Seagate ES 500GB flipflip's SlimServer On TurboStation Release 3.14 mrhyde's USB swap util several of erland's plugins SqueezeCenter Version: 7.2 - 22900 @ Tue Aug 26 10:59:02 PDT 2008 - Linux - EN - utf8
(In reply to comment #14) > (In reply to comment #13) > > (In reply to comment #12) > > > Simon: Please retest with SC 7.2.1 and firmware SB3 r113 > > > > > > I am still unable to reproduce this error as described in comment #10 > > > > > > > Hello, > > > > It has worked fine since I hit the brightness button during network config. > > The same had happened on both my SB3's, so it must have had to do with a > > setting from the web ui I guess. > > I think somehow my players got into the dim-level 0 (off) for the network > > config menu (and maybe other). > > > > So, I can no longer reproduce this behaviour. > > > > Hi again, > > An update: It seems that it is when connected to SC, that this happens. > My SB3 is connected SC when turning it off. > Then, pressing left for >5 sec will not bring up the network config menu, but > then the brightness menu will. It must be besause I have set the level to 0 > when off. > > Since I know the workaround now, I will not bother with any upgrades just for > this. > > My setup is: > > 2* Squeezebox 3 with Audioengine 5 speakers > > 1* QNAP TS-109, Version 2.1.0 build 0624T > Seagate ES 500GB > flipflip's SlimServer On TurboStation Release 3.14 > mrhyde's USB swap util > several of erland's plugins > SqueezeCenter Version: 7.2 - 22900 @ Tue Aug 26 10:59:02 PDT 2008 - Linux - EN > - utf8 > Ooops, now I'm getting it when connected to SN also. Seems to reappear for some reason. "Player Firmware Version: 112" Maybe it's fixed in verison 113..
Felix: can you verify that the firmware will bring the player out of brightness =0 whenever going into setup mode?
There is code in firmware taking care of this case (i.e. making sure brightness isn't set to 0 when the user goes into setup mode), but it seems to be broken due to a change I added for SBB. Do you suggest fixing it for 7.3 or should I wait until 7.3.1?
*** Bug 10071 has been marked as a duplicate of this bug. ***
there is a work around, so lets target it for 7.3.1
Fixed in rev5255, will be in SB3 fw 122, TR fw 72 and SBB fw 42.
This bug has been fixed in the 7.3.1 release version of SqueezeCenter! Please download the new version from http://www.slimdevices.com/su_downloads.html 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.
http://svn.slimdevices.com/repos/slim/7.3/trunk/server/Changelog7.html says that v7.3.1 has Boom firmware v41 but this is fixed in v42. Do you know which is correct? Thanks.
Not in v7.3.1, so status should be changed to RESOLVED?
Thanks Nigel, you are correct. This bug has been fixed in firmware as stated in comment #20, but was not included in SC 7.3.1.
Verified fixed in SqueezeCenter 7.3.2 r24679 Controller 7.3 r3852 SqueezePlay 7.3 r3753 Receiver r58 SB2/3 r123 Transporter r73 Boom r43
Fixed - Closed Message (SC) This bug has been fixed in the 7.3.3 release version of SqueezeCenter! Please download the new version from http://www.slimdevices.com/su_downloads.html 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.
Correction: SqueezeCenter version is 7.3.2