Roon Extension: Alarm Clock v0.9.0

embarrassed to say I was typing npm . so now node . is working…but I’m still not able to get an auto startup shortcut to work as per above

Would this help you in any way ?

Thats what I used… but its not working… at least not when I try to run it from the startup folder - the GIT one works so maybe Ill just use that

should I expect the window to be open and constant scrolling of the pings?


Are you sure you actalluy have the correct path. Maybe you have one more folder ?
Can you please browse in your file manager to verify.

If yes, you may start looking if you actually have used the correct startup menu. Add another program to test.

I tried to make my guide “bullet proof” so if there is anything that can be misunderstood in my explanation, please let me know.

Well the same extension works for git but not for the node shortcut. I’m following the same start menu select the cmd and then open location I think it was…I’m in bed now as it’s 2:40 am and trying to see if the fade will work on this API and then in the morning wake me up…then I have to try to make it WAF friendly…that could be a challenge despite my wife being pretty techie when she wants to be.

Yes, this is how it works at the moment. In case you forget to preselect something, a track from your play history will be picked. There is some more information about this in the Limitations section in the first post.

Sleep well, I hope your wake alarm isn’t too early :wink:

1 Like

Well it stopped after fading out I think…let’s see if it wakes me up too :slightly_smiling_face:

And it woke up too…but at the end of the playlist…must remember to turn radio on after that…maybe add an option for the alarm clock to ensure there is something to play after if the last song stops things?

Now how long before we get to see some easier way to have all this built into roon for adding an extension?

Seriously all this git and node install is going to be well outside the capabilities of most roon owners. I consider myself pretty handy with computers and support clients operation, but this was a traumatic episode even for me :sweat_smile:

Perhaps node . >> null is something better than a scrolling window…I’m trying that now. Seems to be visible in the extensions list still so thats a start.

What exactly is being spouted out … seems to be like status or something…of what roon is doing? or is this some debug info perhaps??

<- CONTINUE 2 Changed {"zones_changed":[{"zone_id":"16019b784a4fb4bf41dc49c3b531be3f6285","display_name":"RPi VinShine R2R","outputs":[{"output_id":"17019b784a4fb4bf41dc49c3b531be3f6285","zone_id":"16019b784a4fb4bf41dc49c3b531be3f6285","can_group_with_output_ids":["170115ae610ee4caebb6215cb7227e8e47bb","1701b0400b378f02d27eccd35be57cde8b5c","17019b784a4fb4bf41dc49c3b531be3f6285","1701c2202a6fe585b95f0608f49390aa1557","17015b93fe7f28b656c2ac2f94a30f025b5e","17014f5e47990bb90567b700ab8f3fbe30cf","17015023f7a8356317107ebfdf407aa2d202","1701664d34b604c47ea6e7516c271add0a9d","1701680e87dd4a8cc782826adc5613b93b16"],"display_name":"RPi VinShine R2R"}],"state":"playing","is_next_allowed":true,"is_previous_allowed":true,"is_pause_allowed":true,"is_play_allowed":false,"is_seek_allowed":true,"settings":{"loop":"disabled","shuffle":false,"auto_radio":false},"now_playing":{"seek_position":122,"length":221,"one_line":{"line1":"Ay Ay Ay - Mew"},"two_line":{"line1":"Ay Ay Ay","line2":"Mew"},"three_line":{"line1":"Ay Ay Ay","line2":"Mew","line3":"Visuals"},"image_key":"51669bcff404b53a9deb3ae199f33a10007dae7348f1d78d17164c24e65a786381d563e099b631e0042b962b674ec35f1f217dfae3fc88103322206a1323cba0caf18e2bc13238e8dc23f62b5376542adf9962d3486bf9c083123d1c03b99072"}}]}

@R1200CL seems your command line is wrong as removing the & plus the internal "'s using this worked

Now my command looks like

C:\Windows\System32\cmd.exe /k “C:\Program Files\nodejs\nodevars.bat cd C:\Users\ladmin\roon-extension-alarm-clock & node . >> null”

This works well and I also set it to start as minimised

So a combination of several different sources of info to get this all working in the end… :confounded:

Haven’t thought about that. Maybe the radio should be a more generic fallback, not only for the case that there is nothing to play. Food for thought…

This is the information the Roon Core provides to the extension. It tells the play state, playing time, active modes etc.

Would it be possible to control Alarm Clock by using iOS workflow ?

(If anyone did the effort)

Implemented ‘Track Boundary’ transition (v0.5.0)

The functionality to adjust a stop alarm to a track boundary, as described previously, is now available in the v0.5.0 release.

To install, step 3 till 7 of the installation guide have to be repeated (overwrite the files of the previous install). See the first post for the link.

Note: I no longer have the possibility to edit the first post, so I have to find another way to provide up to date information.

@Jan_Koudijs, Small bug… When entering the time lets say the wake up time is 05:30AM under the status of the extension it interprets 5:30AM as 5:20AM.


and looks like:

Perhaps it’s indicating the start of the fade time

I thought Fade was measure in seconds not in minutes?
Maybe I just don’t know what it means :stuck_out_tongue:

Hi @Tech_Whisky_Lab,

@wizardofoz is right. The status screen shows when fading starts, the time you enter is when the set volume is reached. Since this leads to confusion I will align the two in the next release.

The fade time is in minutes, I will add units to make this more clear.

Thanks for the feedback.

@Jan_Koudijs Got it. Thanks!

@Jan_Koudijs, thank you very much for the alarm extension. One idea for additional functionality would be the ability to reload the queue (using a pre-defined playlist) and play randomly from that. This would allow a “set and forget” alarm that didn’t require priming or resetting the queue after use at other times. Is this something that is technically possible?

This is a great initiative and exactly what I need but I just installed ROCK so what is the best way to install this extension now? Thanks for the support