MMM-CalDAV

GregoryWest

@sdetweil DOH always the easy stuff I miss… will try tonight

GregoryWest

@gregorywest OK Put CALDAV folder inside the ~/MagicMirror folder. Still get the same error messages on the MMM screen. When I try and web browse into the ics file I get a connection refused error. Is it possible I have a firewall causing me issues?

sdetweil

@gregorywest browse from where?

the default settings in mm are only apps INSIDE the mm machine can connect

so,

change the address and ipWhitelist options in config.js

address:"0.0.0.0",
ipWhitelist:[],

this allows any computer, phone,… on your local network to connect to the mm system

also, by default, mm is NOT https enabled, so the the calendar url should be http://

GregoryWest

@gregorywest created the CALDAV folder. put in the folder a copy of my ics file. This ics file is now being displayed. the problem still remain that MMM_CalDAV does not seem to be updating the ics file at all. still have the module6 message on my screen.

sdetweil

@gregorywest ok looking at the code, I led u astray…

the module generates the file, but presents it when called at the /CALDAV/???.ics url

so, remove the CALDAV folder, but leave that url in the calendar module config

and it should work. there is a bug in the doc, as the url server is set on http, but the doc says https

GregoryWest

@sdetweil really confused now. you need the /CALDAV/ folder removed. leathe the config.js as it is?

sdetweil

@gregorywest yes, the module creates a server at /CALDAV, and when the calendar module uses that URL, this module returns an ICS file. live… (same as if you had been using a google calendar)

this is different than the other converters that dump a file in a folder.

GregoryWest

@sdetweil WOW its working!!! Thanks for your patience. Looking good. Something just occured to me. Can I do this with multiple users/calendars? The plan is for 5 calendars to be on the screen, they are all coming from the same SoGo server.

sdetweil

@gregorywest that I do not know

GregoryWest

@sdetweil I noticed a different issue now. I was updating my calendar in SoGo, but none of the updates are showing up on MMM. This is even the case after a reboot of MMM.

The problem of the multiple calendars might be a show stopper. Will keep muddling through this.

Greg

sdetweil

@gregorywest ok, for multiple cals, u use another instance of the module in config.js
his doc shows that…

update? should be the updateInterval parm… default 15 mins it says

MMRIZE

@sdetweil
Thanks your kind help. I was absent for days. So I couldn’t support this issue.

@GregoryWest
When you want to get several calendars(or accounts), just add this module again in your config.
And to refresh calendar, wait updateInterval.
And with rebooting, usually last result will be shown after reboot.(CalDAV parsing is quite slow ). Generally it will take updateInterval after reboot, the change will be displayed.

MMRIZE

@gregorywest said in MMM-CalDAV:

@sdetweil WOW its working!!! Thanks for your patience. Looking good. Something just occured to me. Can I do this with multiple users/calendars? The plan is for 5 calendars to be on the screen, they are all coming from the same SoGo server.

What you want is;

5 CalDAV calendars from one account (It has more than 5 calendars) as one iCal Calendar : Just use calendarFilter
5 CalDAV calendaras from one account as 5 iCal Calendars: Use this module 5 times with calendarFilter
5 CalDAV calendars from several accounts as one summarized iCal Calendar : Sorry, impossible with this module.
5 CalDav calendars from several accounts as 5 iCal Calendars : Use method 2.

MMRIZE

UPDATE 2.0.0

Newly rebuilt from scratch
OAUTH supported (For Google Calendar)
Multi servers/calendars in one module.
more secure and efficiently

Now, you can use Google Calendar in the default calendar module(and more).
https://github.com/MMRIZE/MMM-CalDAV

MMRIZE

@matt216
More details about your environment are needed to know what happens.

Let’s start with the concept.

Some CALDAV Providers don’t serve any public iCAL(.ics) URL to be consumed externally. You don’t need this module if your CALDAV service can host iCAL URLs. I have no idea about baikal, but I think you know whether that service would provide iCAL or not.

MMM-CALDAV can access the CALDAV server(which would not host any public iCAL URL) to get target calendar events. Then, this module converts the event data to a real iCAL file(.ics). And this module also hosts that file as a URL accessible from the default calendar module or some iCAL consuming modules with security. MMM-CALDAV will work like a private iCAL provider service.

So, to show your event on MM, you may need both MMM-CALDAV and calendar module together.

.env file is needed to connect/authenticate CALDAV server and some security features. Calendar events are very private so I want to block the security hole on working this module. You should put .env in MMM-CALDAV directory.

So, where are you stuck now? Tell me what happens.

matt216

@MMRIZE Thank you for your help, but I managed to figure out getting baikal to generate the ics file, so I don’t need this module anymore.

Thanks anyway

MMRIZE

Update 2.1.0

Birthday calendar enabled. (CardDAV implementation)
Some code refactoring.
calendars: [], is changed to targets: []. you have to reconfigure your config.js

Now you can get Birthdays calendar from iCloud or Google Contacts. (Of course, other CardDAV supported contacts services.)

Tiller

@MMRIZE

Hello I’m trying to sync my synology calendar to the MagicMirror calendar with the MMM_CalDAV module. Sadly it’s not working and I don’t know why. I tried different settings and everything I could find online.

My config.js (without the standard stuff) looks like this:

{
  module: "MMM-CalDAV", 
  config: {
    timeRangeStart: -30,
    servers: [
      { 
        envPrefix: "SYOLOGY_", 
        serverUrl: "http://192.168.xxx/caldav/",
        targets: ["family" ], 
  },
},
},


{
  module: "calendar",
  position: "top_left",
  config: {
    servers: [
      {
        symbol: "calendar-check",
        url: "http://localhost:8080/CALDAV/SYNOLOGY_family.ics",
        auth: { 
          user: 'username1',
          pass: 'password1', 
          method: 'basic'
        }
      },

The .env looks like this:

CALDAV_SERVICE_USERNAME=
CALDAV_SERVICE_USERNAME=

### For SYNOLOGY
SYNOLOGY_username=username1
SYNOLOGY_password=password1

Do you have any idea what I could try to do, to sync it?

Thank you

Tillmann

sdetweil

@Tiller can you show any of the output from
npm start

if using pm2 to autolaunch, then

pm2 logs --lines=xxxx

xxxx is the number of the most recent lines in the logs, default 15

note that the log data will have full urls for calendar , so this could expose info

MMRIZE

@Tiller said in MMM-CalDAV:

CALDAV_SERVICE_USERNAME=
CALDAV_SERVICE_USERNAME=

For SYNOLOGY

SYNOLOGY_username=username1
SYNOLOGY_password=password1

I think you may have confusing the username and password for the server and the module.

SYNOLOGY_username=username1
SYNOLOGY_password=password1

This is for your Synology Caldav Server, usually it is your account id/password to login Synology Server (Or Synology calendar account)

CALDAV_SERVICE_USERNAME=username2
CALDAV_SERVICE_PASSWORD=password2

This is a different thing. It is used for your MM calendar module. This module provide a secure calendar ics host by itself with this auth information. You should need to set your calendar config like this;

// default calendar module.
{
  module: "calendar",
  position: "top_left",
  config: {
    calendars: [
      {
        symbol: "calendar-check",
        url: "http://localhost:8080/CALDAV/SYNOLOGY_Family.ics",
        auth: { // REQUIRED
          user: 'username2', // <= used here (CALDAV_SERVICE_USERNAME)
          pass: 'password2', // <= used here (CALDAV_SERVICE_PASSWORD)
          method: 'basic'
        }
      },
...