Alarm Clock not starting - possible Spotify issue

Hi Guys,

I’ve been dealing with this issue for a couple of days and I can’t seem to get it to work.

Setup:
Raspberry Pi 3
Volumio version previous to 2.344 :slight_smile: (I just noticed a new one was released on Sat)
Ethernet connection

I’ve setup the correct timezone Europe/Sofia and enabled NTP

Added Alarm with Playlist I created using tracks from my Spotify Premium acc.

Below are some of my experiments and results.

  1. Before setting up correct timezone:
  • If I setup alarm after 8 hours it won’t start
  • If I setup alarm after 5 minutes it will start
  1. Setting up correct timezone with ntp off
  • If I setup alarm after 1 hour it won’t start
  • If I setup alarm after 5 minutes it will start
  1. Setting up correct timezone with ntp on
  • If I setup alarm after 8 hours it won’t start
  • If I setup alarm after 5 minutes it won’t start

Attached is the latest log from when I set the alarm to wake me up this morning and nothing happened.
Seems that is having trouble with Spotify.

[spoiler]2017-12-19T05:55:00.054Z - info: [1513662900053] Play playlist Wakey Wakey
2017-12-19T05:55:00.065Z - info: CoreCommandRouter::volumioClearQueue
2017-12-19T05:55:00.067Z - info: [1513662900065] CoreStateMachine::ClearQueue
2017-12-19T05:55:00.069Z - info: [1513662900068] CoreStateMachine::stop
2017-12-19T05:55:00.075Z - info: [1513662900070] CoreStateMachine::setConsumeUpd ateService undefined
2017-12-19T05:55:00.079Z - info: [1513662900077] CorePlayQueue::clearPlayQueue
2017-12-19T05:55:00.081Z - info: [1513662900079] CorePlayQueue::saveQueue
2017-12-19T05:55:00.085Z - info: [1513662900084] CoreStateMachine::pushEmptyStat e
2017-12-19T05:55:00.088Z - info: CoreCommandRouter::volumioPushState
2017-12-19T05:55:00.089Z - info: CoreCommandRouter::executeOnPlugin: volumiodisc overy , saveDeviceInfo
2017-12-19T05:55:00.096Z - info: [1513662900094] interfaceApi::pushState
2017-12-19T05:55:00.098Z - info: [1513662900096] InterfaceWebUI::pushState
2017-12-19T05:55:00.117Z - info: CoreCommandRouter::volumioPushQueue
2017-12-19T05:55:00.120Z - info: [1513662900118] interfaceApi::pushQueue
2017-12-19T05:55:00.122Z - info: [1513662900120] InterfaceWebUI::pushQueue
2017-12-19T05:55:00.127Z - info: CoreCommandRouter::volumioAddQueueItems
2017-12-19T05:55:00.129Z - info: [1513662900127] CoreStateMachine::addQueueItems
2017-12-19T05:55:00.132Z - info: [1513662900130] CorePlayQueue::addQueueItems
2017-12-19T05:55:00.134Z - info: Adding Item to queue: spotify:track:54RaEDwHbCJ KMdDq68EyKE
2017-12-19T05:55:00.136Z - info: Exploding uri spotify:track:54RaEDwHbCJKMdDq68E yKE in service spop
2017-12-19T05:55:00.193Z - info: Adding Item to queue: spotify:track:48ZqiKc9qMh rOTMctjwYOw
2017-12-19T05:55:00.195Z - info: Exploding uri spotify:track:48ZqiKc9qMhrOTMctjw YOw in service spop
2017-12-19T05:55:00.208Z - info: Adding Item to queue: spotify:track:1Ucei7fOEhs kfRcAJnMdOB
2017-12-19T05:55:00.210Z - info: Exploding uri spotify:track:1Ucei7fOEhskfRcAJnM dOB in service spop
2017-12-19T05:55:00.215Z - info: Adding Item to queue: spotify:track:2L7m3LthS3l sfbQVMQj0rJ
2017-12-19T05:55:00.216Z - info: Exploding uri spotify:track:2L7m3LthS3lsfbQVMQj 0rJ in service spop
2017-12-19T05:55:00.221Z - info: Adding Item to queue: spotify:track:43l8AyJQhHd Ptq6vx4cKml
2017-12-19T05:55:00.223Z - info: Exploding uri spotify:track:43l8AyJQhHdPtq6vx4c Kml in service spop
2017-12-19T05:55:00.230Z - info: Adding Item to queue: spotify:track:5zDrHQnESOe 2nTElS6xORi
2017-12-19T05:55:00.232Z - info: Exploding uri spotify:track:5zDrHQnESOe2nTElS6x ORi in service spop
2017-12-19T05:55:00.236Z - info: Adding Item to queue: spotify:track:0ceXqD5uJPw 6s0pTfgLV5j
2017-12-19T05:55:00.239Z - info: Exploding uri spotify:track:0ceXqD5uJPw6s0pTfgL V5j in service spop
2017-12-19T05:55:00.297Z - info: CoreCommandRouter::executeOnPlugin: mpd , getCo nfigParam
2017-12-19T05:55:00.300Z - info: Pushing Favourites {“service”:“mpd”,“uri”:"",“f avourite”:false}
2017-12-19T05:55:00.642Z - info: Spotify access token expires at 1513666500223
2017-12-19T05:55:00.644Z - info: Spotify access token is BQBIlIVsRSydfqRF_2OEUOp SWlnLhRZYT3oCX3GOZONr_8ZzpYNqWFwc3fyxw-f7ITLlRUdnt0i61OcUsb4
2017-12-19T05:55:00.646Z - info: Refreshed Spotify access token
2017-12-19T05:55:00.652Z - info: Spotify access token expires at 1513666500239
2017-12-19T05:55:00.654Z - info: Spotify access token is BQCmAfIM-vzpQtOPKZFJKv8 HXY7bR7ijajJhdcXzC6SG02CmPqpg6UKcM_PBvsK72kJHbnrcCeR8sLeU2D4
2017-12-19T05:55:00.655Z - info: Refreshed Spotify access token
2017-12-19T05:55:00.660Z - info: Spotify access token expires at 1513666500232
2017-12-19T05:55:00.661Z - info: Spotify access token is BQD_DTRxteToHhjtDzjNZn5 wG3yAbvWsnKiGRRFFdkv7uO-Tv0AUgztoco_ohCOy4kNRVxSgeEi540swm70
2017-12-19T05:55:00.663Z - info: Refreshed Spotify access token
2017-12-19T05:55:00.688Z - info: Spotify access token expires at 1513666500139
2017-12-19T05:55:00.688Z - info: Spotify access token is BQD100jS_ClL_VS26IQAWvy ljPsv9-uZ4yTPcdSDcDYsDhyYxgCk9YRIxMPyczjplUiR62lEeTJYYnGbVZ4
2017-12-19T05:55:00.689Z - info: Refreshed Spotify access token
2017-12-19T05:55:00.724Z - info: Spotify access token expires at 1513666500196
2017-12-19T05:55:00.724Z - info: Spotify access token is BQBo4vEuY3F7tp9z_ibIJpW 7V29xkzbEWn-lUym91gNJz7LMuW-T3qhsWgMERIHSMZR71wi4VABCw7fwYig
2017-12-19T05:55:00.725Z - info: Refreshed Spotify access token
2017-12-19T05:55:00.726Z - info: Spotify access token expires at 1513666500217
2017-12-19T05:55:00.727Z - info: Spotify access token is BQBCmnng1huzjBdjO2ofLqo WQT6Qd42znMFoktWOsVjCeXOwb2tRCDyE4iqPoI0Nkel7O1zLGn1iLuYdW-4
2017-12-19T05:55:00.727Z - info: Refreshed Spotify access token
2017-12-19T05:55:00.731Z - info: Spotify access token expires at 1513666500210
2017-12-19T05:55:00.732Z - info: Spotify access token is BQBobvpJLdzkvrobth47QAu -K7_DVLANgv78DC0QquPQ-lE5Whoe0NS4AFeJk2VPrrmrOjNspUddRK1X8YE
2017-12-19T05:55:00.732Z - info: Refreshed Spotify access token[/spoiler]

I tried to have the queue with playlist tracks loaded but in the morning it was deleted.

Any ideas what might be causing this?

Thanks in advance.

Old post but I face exactly the same problems with latest volumio on odroid c1+. Any thoughts?

If you reset your time settings via command line, the alarm functionality will not work

Good evening,

This is what I did:

sudo nano /etc/default/crda (REGDOMAIN=GR)
timedatectl set-ntp true
sudo dpkg-reconfigure tzdata (chose Europe/Athens)

still the same problems.

Is there another way to do it right?

Same problem with Volumio on Intel NUK kit de3815tykh0e. Hardware clock in bios is correct.

Just don’t set time.

The way we set up the clock is:

  • We know the time in your browser, and we calculate the difference from your browser time and linux time
  • We set up the time accordingly
    So, if you change your timezone or your time in Linux, this calculation will be then wrong

Thank you for your help michelangelo,

I’ve tried everything (change/not change time/zone), new installations on both platforms I own (Odroid C1+ and Intel NUC x86) but I always end up with the same result: If I set the alarm on close intervals (minutes or 1 to 2hrs from the moment I create an alarm) then it starts. But after a long time (6+ hrs) it won’t!

Today I will try with local playlist and see if there’s difference.

Update:

Last three days I tried the alarm function with three different playlists, one with songs in local (internal ssd) folder, one in NAS and one in Spotify. Time and area settings were configured as I described above. Every alarm went off every morning at 7:30 on all occasions. The only difference is that with Spotify it played only the first song in the playlist.

My setup is Volumio 2.255 x86 on Intel NUC DE3815