MMM-CalendarExt3 stopped working

[sdetweil]

@redink could you try the test fix here

https://github.com/MagicMirrorOrg/MagicMirror/issues/3329#issuecomment-1874330142

[MMRIZE]

@redink It seems not related to the CX3 module, rather than deep, the default calendar fetch issue.

[redink]

@sdetweil I must be missing something, I don’t see what file this code should go in.

[sdetweil]

@redink doah! I updated post there

calendarfetcher.js

[redink]

@sdetweil Thank you, but that didn’t seem to help. I use this script to update MM https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh

So, I wonder if something isn’t getting updated.

[sdetweil]

@redink can u send me the ~/MagicMirror/installers/upgrade.log

ny userid at gmail

[redink]

@sdetweil thanks for taking the time. It’s sent.

[sdetweil]

@redink so, the upgrade went perfectly. no issues.

not sure what is going on yet.

can you show output of

ip addr

[redink]

@sdetweil

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether b8:27:eb:ee:09:64 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:0f:60:04:20:d4 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.100/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0
       valid_lft 45176sec preferred_lft 34376sec
    inet6 fe80::3e7d:5421:775:6ad0/64 scope link
       valid_lft forever preferred_lft forever

[sdetweil]

@redink can you use the Raspi os config to turn off ipv6 addressing for this adapter?

inet6 fe80::3e7d:5421:775:6ad0/64 scope link

one of the workarounds deals with incorrectly picking the network address to connect with given the client network…