[APP][Pro] IcalCalendar

v3.1.0 is relased and will have the Full day event token on all triggers

working!

I’m using version 3.1.0. After adding a second calendar, the app keeps crashing. When I delete the added calendar, everything works fine again. Anyone else experiencing this issue?

added a gmail calendar after the update, have multiple calendars, no crashing on my side

This has been asked about before, and is (as far as i can tell) different from Homey to Homey based on the over all load of the system. Homey core gives each app a chunk of RAM to use. The more apps you have installed, the more devices you have added etc, the over all system load increases and the RAM chunck each app gets is eaten up.

As stated in the following issues ( Bug: Crashes after short while Ā· Issue #607 Ā· runely/calendar-homey Ā· GitHub , CPU Warning Limit Reached Ā· Issue #651 Ā· runely/calendar-homey Ā· GitHub) this isn’t reproducible and is out of my hands.

Hi @runely , question again for adding an event into the agenda. I use the card, but that is to add an event locally:

How can I get this event to turn up in my gmail-agenda (I added a calendar there, that I named homey calendar). Or is it not possible to write in the agenda?

There’s a reason the card is called `Create local event…`.

It is documented in the first post in this thread here and on the GitHub repo here that a local event will NOT interact with your calendar externally. It’s even documented when you hover over the information button (i) on the card

That is indeed what I saw, but didn’t fully understand. with that, wanted to understand, the card cannot interact externally, your app can’t or it is not possible at all with Homey?

thanks

IcalCalendar only reads the calendar through the ICS url’s used in the settings. No write possible at all.

Based on an app called ORTEC, which handles my shifts, I can export the calendar to an ICS url. When trying to enter this url in iCal i get an ā€˜400 bad request error: request at /app/node_modules/node-ical/node-ical.js:127:17 at processTicksAndRejectrions (node:internal/process/task_qeues:103:5)’

Hopefully someone can troubleshoot this.

To troubleshoot i need a diagnostics report

Of course.

e6423610-395e-4814-90eb-d71b53ef29d8

Thank you!

400 Bad Request is sent back from the workforce-ess.ortecapps.com server for the calendar Rooster Meggie. If you try to visit the url you are using in the IcalCalendar settings, in a browser and preferrably in an incognito window, you will see that you don’t get the ics content back, instead you get an ERR_INVALID_RESPONSE error back.

Thank you very much for this plugin! It is so useful! Do you know why it keeps crashing with SIGTERM and constantly make my flow broken?

logs c60e1101-1df5-4bdd-8042-4814a58b2c94

Hi @runely , thank you so much for this wonderful app! It works great.

But I have a strange issue with some events that are put from mail into my iCloud agenda.
When I look at the agenda via iOS or MacOS, the events start at 9:00, which is right.

All events I import get the right time, except these imported events. The imported events start at 11:00, which is two hours too late. When I import via the HomeyScript it’s also 11:00.

Maybe there’s a not well processed time zone in the calendar item? I don’t know, I do miss technical insights for this.

It would be nice if this can be solved, but I got a little used to this :slight_smile:

Please follow the steps in the Any other problems section

I hope I did it right, no experience with GitHub before.

Hi! Done! Bug: App keep crashing with SIGABRT and restoring 5 mins after Ā· Issue #688 Ā· runely/calendar-homey Ā· GitHub

I have released a new test version which has these two improvements included. I would be very happy if people try out the new test version and report any findings.

  • GC optimization by nullifying variables when not needed anymore
  • Filter the raw ics content before parsing it through node-ical to only work on relevant events, to minimize the RAM and CPU usage

Just installed it. After installation, RAM usage is down by about 30–35 MB.

I’ll keep an eye on it.