MMM-CalendarExt2

sdetweil

@jdfraser really no javascript , just stuff in config…

you have for Ext2 a config section
which has

scenes: {
     [
         { name:  "scene1",
             viewes: ["view1", "view2"]
         },
         { name:  "scene2",            // < --- make secodn scene that looks like the 1st
             viewes: ["view1", "view2"]
         },
    ]
}
Views: {
     [
         { name:  "view1"
         },
         {  name: "view2"
         }
     ]
}

Clubjack

I think there’s a little misunderstanding.
I would like to create several pages with mmm-pages and control them via alexa. Therefore I have to specify in the configs of mmm-pages which modules should be there on the pages.

Example:
Page 1: mmm-clock, mmm-calendarext2
Page 2: mmm-waether, mmm-calendarext2

How should I insert different scenes or views there?

A Former User

@Clubjack
MMM-CalendarExt should exist on all the pages. And give it an order to change scenes by notification from whatever(mmm-pages?)

A Former User

@Clubjack
I just looked inside MMM-Pages(edward-shen/MMM-pages) shortly, It has no feature to emit notifications about current page sequence to other modules. It has PAGE_NUMBER_IS but it is only as the response of QUERY_PAGE_NUMBER. So there is no way to recognize which page at that moment. So CalendarExt2 cannot know what scene to show.
My previous answers are somewhat confused because MMM-Page-Selector(Veldrovive/MMM-Page-Selector) has PAGE_CHANGED to inform the current page when page is changed.

cskenney

Hi @Sean
After the syntax corrections you highlighted my MM was working fine. Today I added an entry into one calendar and it did not show up on my MM. I looked at the log and the [CALEXT2] tasks are not showing up to query any calendars.

I went and looked at my mm-out.log file and found some strange messages.

[CALEXT2] calendar:BOPA >> Scanning start with interval:60000
[CALEXT2] calendar:BOPA >> Scanned: 7, Selected: 7
[CALEXT2] calendar:Chris >> Scanning start with interval:60000
[CALEXT2] calendar:Chris >> getaddrinfo EAI_AGAIN calendar.google.com calendar.google.com:443
[CALEXT2] calendar:Kim >> Scanning start with interval:60000
[CALEXT2] calendar:Kim >> getaddrinfo EAI_AGAIN calendar.google.com calendar.google.com:443
[CALEXT2] calendar:BOPA >> Scanning start with interval:60000
[CALEXT2] calendar:BOPA >> Scanned: 7, Selected: 7
[CALEXT2] calendar:BOPA >> Scanning start with interval:60000
[CALEXT2] calendar:BOPA >> Scanned: 7, Selected: 7

It appears that when the getaddrinfo… messages appear that the calendar is no longer accessible to the module and it is no longer scanned. Above I show the message for 2 calendars but eventually every calendar I have programmed gets this error message.

What is happening and is there a way to automatically recover from this error?

Note: it looks like this may be a Google issue but I am wondering if there is a way to elegantly handle the error or get a notification that an error occurred? It also happened to different calendars at different times so I don’t think it was an issue with my network.

Edit: further inspection this may be a local network issue. Would still like to know if there is a way to recover from these errors.

MJhere

I have a calendar showing week view. But cannot get event text to overflow. Help would be appreciated. TIA

JRB1988

I’m having trouble getting MMM-CalendarExtTimeline to populate. The CalendarExt2 is filled in. Here is what I have in my configuration (with my personal info blocked out) and what I am seeing on my screen. Any ideas?

BKeyport

hey, @Sean Did you happen to miss this?

I’m trying to add an ICS file, but it’s throwing an error, but other calendars accepts it.

The url is http://www.tax.gov/calendar/employer/calendar.ics

Log from PM2 LOGS shows this error:

[CALEXT2] calendar:irs >> invalid date-time value: “2016-12-30T::”

Is it the US Government not knowing what’s going on, or is it a bug in the code?

Thanks!

A Former User

@JRB1988

type: "dyanmic",

seems wrong.

A Former User

@BKeyport
Sorry for the late answer. I was hospitalized due to my broken ankle, so I couldn’t inspect.
The issue looks like invalid format of ics. Unfortunately, iCAL format is not so strict (despite of standard rule, RFC-5545, RFC-5546 and so many standards), some iCAL could have ambiguous formats. Well, my parser cannot understand yours. At this moment, I have no time to fix it. (Or, … I’m not sure it should be fixed.) Sorry.