Read the statement by Michael Teeuw here.
Calendar not updating
-
@sdetweil said in Calendar not updating:
I think you have the wrong calendar url , you need the ical format url, not the embed url
mine is likeYou mean the public one? Because for some reason, 3 of the 5 calendars work just fine with the private ICal Format address.
-
@sdetweil I think you are potentially right. For baikal I have followed such advice as here: https://forum.magicmirror.builders/topic/434/caldav/4?_=1704811423495 where it was advised just adding ?export to the end of the cal URL to generate the ics file, but it is not an actual ics link.
I shall work along those lines… -
@matt216 i test others problems by building an ics FILE and using the url
http://localhost:mirror_port/modules/default/calendar/????.ics
so it doesn’t have to be ON a ‘server’… just has to be an ICS format file.
linking to google, the url returns that data when the calendar does a get request
same as for the local file. BUT we depend on the data changing…
the cal module does not know that ‘this’ fetch was or was not different than the last fetch.
we don’t keep a diff… we just get the current data and present it.if it didn’t change then nothing changes
-
@sdetweil Trying this.
Steps:- add new test event scheduled tomorrow
- verify event on another device, proving calendar server sync
- curl .ics file from server, find test event
- set calendar module as described in your post above
Result:
calendar loads successfully, but still does not show new event.Event as shown in ics file:
BEGIN:VEVENT CREATED:20240109T161646Z DTEND;TZID=Europe/London:20240110T170000 DTSTAMP:20240109T161647Z DTSTART;TZID=Europe/London:20240110T160000 LAST-MODIFIED:20240109T161646Z SEQUENCE:0 SUMMARY:test54321 TRANSP:OPAQUE UID:156ED8F1-9BDA-43D2-BE7C-DDEFE18E95EF URL;VALUE=URI: X-APPLE-CREATOR-IDENTITY:com.apple.mobilecal X-APPLE-CREATOR-TEAM-IDENTITY:0000000000 END:VEVENT
I think MagicMirror does not like the baikal server - no events created since I migrated from iCloud to self-hosted baikal are showing. Can you see anything unusual in the ics event above @sdetweil ?
-
@sdetweil so I’ve just spun up a radicale calendar server and added a few test events, then some more - works perfectly!
Looks like a problem with baikal integration
-
@matt216 no. i created an ics and ran mm against it
[09.01.2024 10:42.53.207] [LOG] Create new calendarfetcher for url: http://localhost:8090/modules/default/calendar/testbalkan.ics - Interval: 604800000 ... [09.01.2024 10:42.53.336] [DEBUG] parsed data={"156ED8F1-9BDA-43D2-BE7C-DDEFE18E95EF":{"type":"VEVENT","params":[],"created":"2024-01-09T16:16:46.000Z","end":"2024-01-10T17:00:00.000Z","dtstamp":"2024-01-09T16:16:47.000Z","start":"2024-01-10T16:00:00.000Z","datetype":"date-time","lastmodified":"2024-01-09T16:16:46.000Z","sequence":"0","summary":"test54321","transparency":"OPAQUE","uid":"156ED8F1-9BDA-43D2-BE7C-DDEFE18E95EF","url":{"params":{"VALUE":"URI"},"val":""},"APPLE-CREATOR-IDENTITY":"com.apple.mobilecal","APPLE-CREATOR-TEAM-IDENTITY":"0000000000"},"vcalendar":{"type":"VCALENDAR"}} [09.01.2024 10:42.53.337] [DEBUG] There are 2 calendar entries. [09.01.2024 10:42.53.338] [DEBUG] Processing entry... [09.01.2024 10:42.53.339] [DEBUG] Event: {"type":"VEVENT","params":[],"created":"2024-01-09T16:16:46.000Z","end":"2024-01-10T17:00:00.000Z","dtstamp":"2024-01-09T16:16:47.000Z","start":"2024-01-10T16:00:00.000Z","datetype":"date-time","lastmodified":"2024-01-09T16:16:46.000Z","sequence":"0","summary":"test54321","transparency":"OPAQUE","uid":"156ED8F1-9BDA-43D2-BE7C-DDEFE18E95EF","url":{"params":{"VALUE":"URI"},"val":""},"APPLE-CREATOR-IDENTITY":"com.apple.mobilecal","APPLE-CREATOR-TEAM-IDENTITY":"0000000000"} [09.01.2024 10:42.53.339] [DEBUG] start: Wed Jan 10 2024 10:00:00 GMT-0600 (Central Standard Time) [09.01.2024 10:42.53.339] [DEBUG] end:: Wed Jan 10 2024 11:00:00 GMT-0600 (Central Standard Time) [09.01.2024 10:42.53.339] [DEBUG] duration: 3600000 [09.01.2024 10:42.53.340] [DEBUG] title: test54321 [09.01.2024 10:42.53.340] [DEBUG] full day event =false [09.01.2024 10:42.53.340] [DEBUG] initial tz=Europe/London [09.01.2024 10:42.53.340] [DEBUG] corrected tz=Europe/London [09.01.2024 10:42.53.341] [DEBUG] start date/time=Wed Jan 10 2024 10:00:00 GMT-0600 (Central Standard Time) [09.01.2024 10:42.53.341] [DEBUG] start offset=0 [09.01.2024 10:42.53.341] [DEBUG] start date/time w tz =Wed Jan 10 2024 10:00:00 GMT-0600 (Central Standard Time) [09.01.2024 10:42.53.342] [DEBUG] event date=Wed Jan 10 2024 10:00:00 GMT-0600 (Central Standard Time) [09.01.2024 10:42.53.342] [DEBUG] event offset=0 hour=16 event date=Wed Jan 10 2024 10:00:00 GMT-0600 (Central Standard Time) [09.01.2024 10:42.53.342] [DEBUG] adjustHours=0 [09.01.2024 10:42.53.342] [DEBUG] saving event: test54321 [09.01.2024 10:42.53.342] [DEBUG] Processing entry... [09.01.2024 10:42.53.342] [INFO] Calendar-Fetcher: Broadcasting 1 events from http://localhost:8090/modules/default/calendar/testbalkan.ics.
-
@matt216 can u send me the curl ics from the baikal server where the events don’t show??
(if you are willing)
rename to .txt -
@sdetweil this is from the curl’d ics file, showing one of the events that will not display on the mirror display:
BEGIN:VEVENT CREATED:20240109T161646Z DTEND;TZID=Europe/London:20240110T170000 DTSTAMP:20240109T161647Z DTSTART;TZID=Europe/London:20240110T160000 LAST-MODIFIED:20240109T161646Z SEQUENCE:0 SUMMARY:test54321 TRANSP:OPAQUE UID:156ED8F1-9BDA-43D2-BE7C-DDEFE18E95EF URL;VALUE=URI: X-APPLE-CREATOR-IDENTITY:com.apple.mobilecal X-APPLE-CREATOR-TEAM-IDENTITY:0000000000 END:VEVENT
I’d be happy to send over the contents of the ics file before events start, if that would be helpful? Far too much personal family info to send the whole thing, Im afraid (again, no offence intended)!
-
@matt216 I used that event in an ICS and it displays just fine.
so I think this is not the events but some communications problem.
the fact that you have it working with another local hosting server tells me it’s something other than the data
-
Initial testing with the apache version of the baikal container looks promising (I’m currently having problems with the nginx version). Will continue testing along these lines…