Calendar shows incorrect time for a single changed event in a series

KristjanESPERANTO

@sdetweil Just out of curiosity: Is the library moment.js?

sdetweil

it expects only local date/times
node-ical converts all to utc based times…

so we get some events that have todays date with tomorrows UTC time… Nov 6 -01:30 UTC -8

for LosAngeles that makes the event date yesterday… Nov 5- 17:30… oops…

but we in MM don’t ever look at the text in the ICS, so we have NO way of knowing of the mishmash date/time… and it seems to happen MOST with ByDay (only on thrusday or friday) …

AND EVEN if we DID look at the ICS, we wouldn’t see this, as its a recurring date event, calculated by RRULE. from start and the rules… so unless WE recode RRULE, we would never ever know

sdetweil

@Hinge @KristjanESPERANTO node-ical has just release a new version (0.17.0) which removes the luxon library which causes all the localdate/time issues…

want to give it a try ? do

cd ~/MagicMirror
npm install node-ical@latest

then start mm as usual

gelaw

@sdetweil said in Calendar shows incorrect time for a single changed event in a series:

@Hinge @KristjanESPERANTO node-ical has just release a new version (0.17.0) which removes the luxon library which causes all the localdate/time issues…

want to give it a try ? do
cd ~/MagicMirror
npm install node-ical@latest
then start mm as usual

I have the same problem.
Did this fix work?
Thanks

sdetweil

@gelaw do

cd ~/MagicMirror 
 npm install node-ical@0.16.1

gelaw

@sdetweil Thanks!
This worked in my first tests. Is this now the official version? or still in work?

sdetweil

@gelaw this is the version from prior release…

we’ll see what happens by April 1.(next mm release)