@h_vestbo where, which geography?

@kayakbabe - thanks for letting me know. I will keep an eye on the one I am using and if I see issues, will try the other one.

@eyesallin in the node_helper.js browsers cannot access the system directly. the node_helper is the mm solution for that

@did awesome… glad you got it working and tested the other.

@svenpisa i don’t understand… did you do the steps in the module instructions? [image: 1708006763178-snip20240215_2.png]

@nhweb Done. Update module to 1.8.1 Then, in your custom.css, append these lines. /* css/custom.css */ #CX3_POPOVER .criteriaItem.period .name::before { content: "PERIOD"; } #CX3_POPOVER .criteriaItem.location .name::before { content: "LOCATION"; } #CX3_POPOVER .criteriaItem.description .name::before { content: "DESCRIPTION"; } #CX3_POPOVER .criteriaItem.calendar .name::before { content: "CALENDAR"; } Modify as your wish.

@sdetweil yes i did but with https://github.com/thobach/MMM-MicrosoftToDo/issues/109 hope they will find a solution

@Alexjons I was just pointing to where the dialog about this problem is happening. The author knows and so far as I can read the issue, there is no general purpose solution that works for all.

@vandy2424 I have provided a ‘fix’, that will produce a message if this case happens again… hopefully next release (April 1) https://github.com/MagicMirrorOrg/MagicMirror/pull/3383 edit: the fix was accepted for next release

@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.