Sync private iCloud calendar with MagicMirror
@Beh I’m sure I have installed it in the right directory, I followed :curl https://raw.githubusercontent.com/pimutils/vdirsyncer/master/contrib/vdirsyncer.timer | sudo tee /etc/systemd/user/vdirsyncer.timer firstly under the MagicMirror Directory. Then activating using systemctl --user enable vdirsyncer.timer.
When looking at the status I get : Warning: The unit file, source configuration file or drop-ins of vdirsyncer.timer changed on disk. Run ‘systemctl --user daemon-reload’ to rel
● vdirsyncer.timer - Synchronize vdirs
Loaded: loaded (/etc/systemd/user/vdirsyncer.timer; enabled; vendor preset: enabled)
Active: inactive (dead)
Hi mate. I have the exact same issue. I have everything now up and running. I managed to have two private ical calendars showing up in the mirror. If I sync manually and reload it works fine. Unfortunately I dont manage the damn thing to do it automatically, ideally triggered on an event or at least all few minutes. My settings in the timer are 1min, 2min, 3min. Just because Beh said to avoid all 1min settings. Any Idea?
This post is deleted!
Feedy88 last edited by
- Files are in
/etc/systemd/user/(vdirsyncer.service & vdirsyncer.timer)
systemctl --user enable vdirsyncer.timer?(no error or any other feedback in Terminal)
jorunalctl --user -u vdirsyncerwith the result:
No journal files were found. -- No Entries --
I even went forward and tried to sync using a cronjob but this is unfortuately also not working:
error: Unknown error occured for iCloud_to_MagicMirror/9*******-****-****-****-************D: HTTPSConnectionPool(host='p65-caldav.icloud.com', port=443): Max retries exceeded with url: /1355377534/calendars/9*******-****-****-****-************D/ (Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')])"))) error: Use `-vdebug` to see the full traceback. error: 1 out of 2 tasks failed. Syncing iCloud_to_MagicMirror/9*******-****-****-****-************D
Anyone has an Idea?
- Files are in
Feedy88 last edited by
- Create Shell script
First we need to create the script which is actually executed by the cronjob. To do this we open a terminal and type
Within the editor we just write a one-liner:
vdirsyncer -vinfo sync
Close by CTRL+X and save by confirming with Y
- Make script executable.
Within terminal type
chmod +x ~/MagicMirror/modules/calendars/vdirsyncer.sh
- Test the script
Run a test if your script works. Within terminal type
If working as intended you should receive the feedback
- Checking/Changing the Version of vdirsyncer
This was actually my biggest issue. I could sync successfully when running the script manually but the actual cronjob failed. Looking into Debug-Logs I found that the manual run used Version 0.16.8 of vdirsyncer while the cronjob used 0.16.7. After manually chaning the versioning if worked as inteded. To ensue you are not running into that issue, let’s check the versioning from the get-go. Within Terminal type
sudo nano /usr/bin/vdirsyncer
An editor will show you the following code:
#!/usr/bin/python3 # EASY-INSTALL-ENTRY-SCRIPT: 'vdirsyncer==0.16.7','console_scripts','vdirsyncer' __requires__ = 'vdirsyncer==0.16.7' import re import sys from pkg_resources import load_entry_point if __name__ == '__main__': sys.argv = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv) sys.exit( load_entry_point('vdirsyncer= q=0.16.7', 'console_scripts', 'vdirsyncer')() )
Change all three instances of
0.16.8, close via CTRL+X and save with Y.
- Create the Cronjob
Cronjobs are a great thing. It is pre-installed with UNIX based systems, therefore also with our Raspberry Pi. More information about Cronjobs can be found here. To set up a new cronjob, within Terminal type
The result will be the following code:
# Edit this file to introduce tasks to be run by cron. # # Each task to run has to be defined through a single line # indicating with different fields when the task will be run # and what command to run for the task # # To define the time you can provide concrete values for # minute (m), hour (h), day of month (dom), month (mon), # and day of week (dow) or use '*' in these fields (for 'any'). # # Notice that tasks will be started based on the cron's system # daemon's notion of time and timezones. # # Output of the crontab jobs (including errors) is sent through # email to the user the crontab file belongs to (unless redirected). # # For example, you can run a backup of all your user accounts # at 5 a.m every week with: # 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/ # # For more information see the manual pages of crontab(5) and cron(8) # # m h dom mon dow command
Type a new line at the bottom with the cron syntax. Here is an overview for the timings:
# ┌───────────── minute (0 - 59) # │ ┌───────────── hour (0 - 23) # │ │ ┌───────────── day of the month (1 - 31) # │ │ │ ┌───────────── month (1 - 12) # │ │ │ │ ┌───────────── day of the week (0 - 6) (Sunday to Saturday; # │ │ │ │ │ 7 is also Sunday on some systems) # │ │ │ │ │ # │ │ │ │ │ # * * * * * <command to execute>
As for us it makes senst to run vdirsyncer every X minutes (I am going with 5 minutes in my case) the syntax looks as follows:
*/5 * * * *
followed by the script to execute:
bash ~/MagicMirror/modules/calendars/vdirsyncer.sh >> ~/vdirsyncer.log 2>&1
The first part should be familiar to you. What follows after the
>>is a log we are creating. This will be helpful in case anything does not work as inteded. The full cronjob should look as follows:
# Edit this file to introduce tasks to be run by cron. # # Each task to run has to be defined through a single line # indicating with different fields when the task will be run # and what command to run for the task # # To define the time you can provide concrete values for # minute (m), hour (h), day of month (dom), month (mon), # and day of week (dow) or use '*' in these fields (for 'any'). # # Notice that tasks will be started based on the cron's system # daemon's notion of time and timezones. # # Output of the crontab jobs (including errors) is sent through # email to the user the crontab file belongs to (unless redirected). # # For example, you can run a backup of all your user accounts # at 5 a.m every week with: # 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/ # # For more information see the manual pages of crontab(5) and cron(8) # # m h dom mon dow command */5 * * * * bash ~/MagicMirror/modules/calendars/vdirsyncer.sh >> ~/vdirsyncer.log 2>&1
Close again by CTRL+X. You are now ready and have everything set up. The cronjob will start automatically on every startup and run the sync in the interval you have set it up.
@Feedy88 and if u edit your script and make the 1st line
when the script is invoked it will launch the script using bash so all the bash symbols, redirection etc can be moved into the script, and you just use the script and to.launch it
also, cron typically executes commands as root, so ~/filename will try to write to /root/filename, but not where u intended. so use the full path
Feedy88 last edited by Feedy88
@sdetweil Thanks for the notes, but can you explain a bit more into detail. You mean, if I add
#!/bin/bashas first line to the script, I can also add the logging part and remove it from the cron?
To be honest, I’m quite a noob to Linux based systems and scripts. Nonetheless, hope my answer will help some people to get the sync going who have issues with the timer service from vdirsyncer.
@Feedy88 yes, if you use the exec command in the script you can capture stdout & stderr and pipe them to a file
Open standard out at
This has the effect
Redirect standard error to standard out such that
standard error ends up going to wherever standard
out goes (the file).
normal rest of your script
I’m fairly new to the whole Raspberry Pi Thing.
I got the whole Calendar up and running. My only problem is, that it is not syncing automatically…
Do you guys know any fix for this problem?
The fix from @Feedy88 didn’t work for me unfortunately.
@jlnxaer did u create a cron job entry?
@jlnxaer what does the pm2 log show? Are error messages displayed at the log?
I also had this phenomenon recently, as the calendar did not syncronize automatically. I had an error message in the log. I no longer know the exact wording of the report.
For me it helped to delete and recreate the files under
/home/pi/.vdirsyncer/statusand the created
* .icsfiles. after creating the data again with “vdirsyncer sync”, everything now runs automatically as described in the instructions.