Bugzilla – Bug 4775
Off after... feature
Last modified: 2009-09-08 09:11:45 UTC
I'd like to request a feature to switch off the SqueezeBox a certain period of time (ideally user-configurable) after the alarm has switched it on. This is to prevent the player from continuing to play should the alarm have been left on and there be no-one to turn it off. See thread for more info. I'm aware this feature exists in the alarm plug-in, but it's missing in SqueezeNetwork. SlimServer consistency would obviously be nice. Thanks.
Are you sure this exists in the SlimServer alarm plugin? I recently updated SN to use the same alarm code, and don't recall seeing it.
Sorry, was referring to kdf's alarm plugin, though to be fair I've not checked it out personally myself.
server alarm: simple alarm with options for weekdays. Alarm Plugin: advanced, multiple flexible alarms with snooze, and duration options. Extended Alarm: scalable single package version of the AlarmPlugin, for 7.0(trunk) server version and higher only.
In order for this feature to make it's way to SN, we'd need to include the new features of kdf's plugin in the core SlimServer. This is an issue for Dean.
*** Bug 8236 has been marked as a duplicate of this bug. ***
Max: what do you think of this?
No problem - I can do this in the branch containing the new alarm code. How about a limit of 1 hour? Would you like it to be a preference? If so, I'd probably only expose it in the web (and controller?) ui.
1 hour would prevent the thing playing on and on. What would be really great though would be able to set an off time as well for when you leave the house, e.g. on at 7am off at 7.40am.
(In reply to comment #7) > No problem - I can do this in the branch containing the new alarm code. How > about a limit of 1 hour? Would you like it to be a preference? I would like this feature too, but for simplicity just have settings for 'Alarm On' and 'Duration' (in minutes). The range for duration could be from 1 to 600 minutes.
I've just checked this into the branch. Alarmv now time out after a default period of 1 hour. Snoozing an alarm resets this period such that the alarm then times out 1 hour after the snooze ends. The timeout period is a user preference and can be disabled completely by setting it to 0 or undef. The web ui should expose this preference.
This appears to be addressed in SqueezeCenter 7.2-22834 NOTE: Alarm Timeout must be set >= 5 minute increments. Entering any number <5 will result in 0 (nul) and any number >5 will round the time to the closest 5 minute increment.
James, does your last comment refer to the web interface? In the default skin it's set by a slider which moves in 5 minute intervals. However, if other skins just use a text box, I'd say your described behaviour is a bug that should be addressed. The underlying alarm code should allow any timeout value - I think the web ui is adding the multiple of 5 restriction.
> NOTE: Alarm Timeout must be set >= 5 minute increments. I've removed that restriction in change 22874.
(In reply to comment #12) > James, does your last comment refer to the web interface? In the default skin > it's set by a slider which moves in 5 minute intervals. However, if other > skins just use a text box, I'd say your described behaviour is a bug that > should be addressed. The underlying alarm code should allow any timeout value > - I think the web ui is adding the multiple of 5 restriction. > some feedback: I finally had the chance to test the 7.2 version with the Alarm Timeout. The alarm duration is set at 90 min. and the playlist is set to random album mix. Both settings are ignored and the receiver just selects and plays 10 random tracks then stops. Also, it would be nice to have the ability to enter durations longer than 90 minutes. On weekdays I would like to set it at 120 min and have it at 240 min. on weekends. I definitely would chose just a text box entry if it is a choice between having sliders with a fixed duration period or no slider and more flexible choices for durations. Using: SqueezeCenter Version: 7.2 - 22997 @ Tue Sep 2 02:02:58 PDT 2008 - Windows XP - EN - cp1252
This bug was originally reported with regard to SqueezeNetwork. So far as I'm aware this isn't yet available, although SqueezeCenter 7.2 does have the functionality. As reporter of the bug, for me it's not resolved. Should I re-open it? Thanks.
Coment #14 is bug 9330 and so can be disregarded in this context (not that it's not an issue, however!). Re #15: Andrew, please do re-open if this definitely isn't working with squeezenetwork in 7.2.
Created attachment 3946 [details] SN screenshot
Apologies if I'm missing something, but I can't see this functionality in SqueezeNetwork. Can't see anything about it at all - screenshot of what I'm seeing under the Alarms tab attached. Re-opened in line with Max's recommendation.
Could you please open a new bug with the right product and component, and a short summary so I don't have to go through all the comments to know what it really is about? We're not talking about SC's player UI as this bug suggests, are we?
Verified fixed in SqueezeNetwork (sv) r4682/r23371 & SC 7.2.1-23472
This bug has been fixed in the 7.3.0 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.
Reduce number of active targets for SC