Bugzilla – Bug 9355
SC alarm CLI does not cover new alarm functionality
Last modified: 2008-09-15 02:20:06 UTC
1. There does not seem to be a way to set the "Fade In", "Timeout" and "Snooze Length" parameters through the CLI or at least they are not documented 2. The alarm CLI only provides an interface to set a playlist URL for an alarm. But the default web UI offers also functionality to use Favorites, Random Mixes, the current playlist and Sounds. These are not available through the CLI or at least not documented.
1) Fade in, timeout and snooze length are all preferences so can be set using the pref and playerpref commands. See Slim::Utils::Alarm for info. You want alarmfadeseconds, alarmTimeoutSeconds and alarmSnoozeSeconds. 2) All alarm playlists are now urls, so you can set any playlist through the cli that you could set using the ui. An easy way to get the urls would be to have a look at the html source for the alarm web settings ui. e.g. randomplay://track.
That helps and answers the questions regarding the fade, snooze, etc. May I suggest that when such a change is made that it be placed in the CLI document as part of the change notice. That would help a lot. I did not know where to look for the changes. A note that would have said "... the fade parameter has been removed from the alarm command and is available as part of playerprefrences along with Timeout and Snooze. See SLIM::Utils::Alarm" would have allowed a resolution with out a submission. Now where do I find "Slimm::Utilities::Alarm" so I can look at it ? That still leaves the Bug/issue that the alarms command does not return a dow value. It always returns dow: with no value. That is in bug report 9354 Thank you for your assistance
Okay I figured Slim::Utils::Alarm should be somewhere in the squeezecenter app I installed on my PC I was able to locate a Slim::Utils folder but no subfolder called alarm. I am obviously looking in the wrong place. A hint would help TIA
BTW, what do you mean by "in the appropriate settings pages"? Maybe this is a principal thing: My understanding is: the primary means of controlling SC these days is the CLI or the JSON/RPC IF. If you plan to use that, it's very inappropriate to have developer documentation in perl or html or js source files since these don't apply. Apart from source files generally not being appropriate as a means of documentation.