Roon Extension: Alarm Clock v0.7.4

(Jan Koudijs) #211

Are you running the Docker image of the Extension Manager in QNAP ContainerStation?

If you do so, it is important that you set the correct timezone for the container by setting the TZ environment variable. More information about getting the settings right is in this thread:

(Paul Hermans) #212

My bad. My core is on QNAP, but I have in between dietpi endpoints where I installed the extension manager and the alarm clock extension and this dietpi had the wrong time.

1 Like
(Jan Koudijs) #213

Alarm Clock v0.7.0 is now available

This version includes source selection for Play alarms!

You can read more about it in the feature thread:

I hope you like it, suggestions are welcome.

How to install / update

The recommended way to install or update is via the Roon Extension Manager .

If the manager has auto update enabled then the changes will be pulled in the next time the update is performed. It is also possible to update manually via the Settings dialog, select the Alarm Clock from the Playback category and perform the update action.

7 Likes
(Rémi) #214

Many thanks Jan! You nailed it!

2 Likes
(J. V.) #215

Mad props to @Jan_Koudijs

for this update!

Works like a charm

2 Likes
(Jan Koudijs) #216

Alarm Clock v0.7.4 is now available

This is a bug fix release.

The bug that is fixed is the one reported by @Bart_Maguire in this thread:

How to install / update

The recommended way to install or update is via the Roon Extension Manager .

If the manager has auto update enabled then the changes will be pulled in the next time the update is performed. It is also possible to update manually via the Settings dialog, select the Alarm Clock from the Playback category and perform the update action.

1 Like
(John Webb) #218

Hi @Adam_Goodfellow - I get the “this.moo.close()” error using a different extension. I think I have the latest version of the extension installed. I think it happens when I haven’t been using Roon for a while; though I can’t reproduce it by putting the computer to sleep. Can you offer any insights what the error might mean?

#219

Thank you for your work on this!

I have installed and I can set alarms. I am trying a simple, instant shut off. All looks ok, but the player doesn’t shut off. I have selected the correct zone, etc. I do have TZ variable set.

Perhaps it is my setup. I have Roon core on a SonicTransporter and have installed Alarm Clock on my Synology NAS via Docker. I use an Android Tablet for control. Does Alarm Clock have to be installed on the same device as the core, by any chance? If so, is it possible to install on the SonicTransporter (Sonicorbiter OS - a Linux variant)?

(Nathan Wilkes) #220

No, it doesn’t.

In my case, the problems I had having music turn off were related (it seems) to network issues. Essentially, once I wired every node my problems largely went away.

(Jan Koudijs) #221

Can you post a screenshot of the configured alarm?

#222

Will do tonight, after work. Thanks for the reply!

#223

Thanks. All is wired with the exception of the tablet that has the control app.

#224

Here it is:

I went into settings => extensions last night and it was empty. Logged into NAS and found Docker running but needing an update. Updated, set the alarm you see. Waited a minute past the set time with music not stopping.

Hopefully the extension disappearing was an anomaly.

(Jan Koudijs) #225

Did the time that was displayed in the status line of the extension after pressing the Save button match the 07:13 setting?

Can you check the log of the container for errors? If you can upload it somewhere then I will have a look.

#226

Following up a remark by @Anthony_Cimino I found out about this strange behaviour:
grafik

grafik
Core running on a QNAP-NAS with proper time-zone setup; Extension is running in a Docker image on Core with time-zone information set; Roon Remote is on Windows.

Alarm goes off at the Time (15:55) in the status line. My TZ is GMT +1.

#227

Hi Jan,

Sent a link to the log file by PM.

The times you asked about did match. Something funny with time though. If I choose “once” the result is Wed (tomorrow) instead of today.

I tried two containers for TZ setting. One with “Alaska”, the other with " UTC−09:00". Didn’t work either way. You may see one alarm with 06:42 instead of 18:42 in the log. I realized and tried again with the right time.

I hope using “Alaska” as TZ is good, particularly if it automatically accounts for DST time changes.

Thanks for taking a look! …Pete

(Jan Koudijs) #228

If you open a console on the container and enter the date command, do you get the expected time?

I don’t know if a console is available via the QNAP interface. If you have an ssh connection then you can use a command like this:

docker exec -it roon-extension-alarm-clock sh
#229
~/.RoonExtensions/lib # date
Wed Mar 13 16:55:06 GMT 2019

Which is correct (GMT time) but not my local time.

#230

It seemed that my image was outdated. I deleted my old Docker container, pulled a new image and setup a new container. I also updated my Docker Compose configuration in the other thread. Now all works as expected. :crossed_fingers:

1 Like
(Jan Koudijs) #231

There was a timezone bug fixed in version 0.3.2 of the Extension Manager image, so if you were running an older version then that explains.

1 Like