@dr2man no rush… whenever you get appropriate time. thanks for the update

This module is abandoned. In issue 14 you can read that the API stopped working. Try MMM-Flights instead.

@KristjanESPERANTO ah ok, then I took it the wrong way. Sorry and thanks

@Kelemvor To make things simpler, Let’s clear the condition; What is your expectation? Are there missing events which have to be shown but not? For example, there had to be 3 events on today but only 2 events shown? on which day it happens? everyday? or some specific day? on which calendar does it happen? randomly? or some specific calendar? Or any suspicious symptoms or evidence of those missed events? Are you suspecting hidden(not missing) events or days at the end(bottom) of the module’s view? You expect 10 days but only 7 days are shown…?

I’ve created a PR to fix this :-)

@carefreepineappl note that the default fetch delay for the default calendar is quite long… 7 days… because all the mm systems polling the calendar labs urls were causing them problems

@schwarem That’s not your or your RPI’s fault. :) With your previous log image, at least 7 calendars had to be parsed. The first calendar (12 events) was fetched on 11:06:27, and the last calendar(93 events) was fetched on 11:06:40. These 7 calendars need almost 13 seconds to parse completely. But CX3* would appear after 5 seconds(by default) from the first fetching. Nobody can’t foresee when the last calendar will finish the fetching (or even whether it is complete or not). So CX3* will wait a few seconds and then show only the events from the current aggregated regardless of whether some unfetched calendars remain. CX2 parsed events of the calendar by itself so it could know whether all events were fetched or not.(At least I made so), but CX3 doesn’t parse the calendar, only using the feed from another module. That’s the difference. No worry. Until the next cycle(defined by refreshInterval), the unfetched calendars would be fetched until then. In the following refreshInterval, your missing events will be shown adequately. Or, increase waitFetch to wait more seconds for more calendars to fetch.

@timwool no , sorry

@jonnyollet the default calendar module does not get the Google calendar event colors in the ICS data. it is not part of the interchange standards. so the only thing we can send is the URL configured colors. the custom event config colors are not used until display time so they are not available when the broadcast is done

Please mark this topic as solved. The only thing I can figure is that it too some time to propagate maybe ? I haven’t changed anything yet this morning it was able to generate the token without any issues Thank you for the help :)

That did the trick, thank you.

Shares bought and now ok with MM. Thanks for your help,

@MMRIZE the default fetchInterval is set to 7 days…

@nhweb /* MMM-CalendarExt3 config in config/config.js */ ... config: { eventTransformer: (event) => { if (event.calendarName === 'test' && event.description) { // If event is from 'test' calendar and has description, event.title = event.description } return event; } ... 9:00 PM event was originally titled as ‘Singleday Event’ [image: 1706611641608-f6e47e7f-7994-4b6d-8071-4a97658aee7f-image.png]

@KristjanESPERANTO just wanna say thanks it works

@gelaw this is the version from prior release… we’ll see what happens by April 1.(next mm release)

Any way off changing colors with states off sensors? Is it possible to round decimals like in home assistant itselfe? I hate having temps with 2 decimals and/or watts.

Thank you @KristjanESPERANTO for providing a fix for it.

@MMRIZE we have this problem in general… mm used to display on TV’s and ipads/ android tablets… but as we’ve moved to ES6 level js, they no longer work… I find this a sad state for MM… (but I like the new ES6 support)

@csongor-varga-0 For the multilines events; not naturally. It is designed so intentionally. I know it is probably possible with heavy CSS tweak but I will not do or try it by myself. For the (+1) : There might be hidden(skipped) events. (You’ve set skipDuplicated: true)