Read the statement by Michael Teeuw here.
MMM-CalendarExt3 stopped working
-
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
-
@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…
-
@sdetweil while messing with raspi-config over ssh, magicmirror lost connection to my wifi. I had to connect a keyboard and reconnect. But, before going back to your last suggestion I did two other things. I updated pm2 (as suggested by some other post). And in the browser console I noticed that I had an error about not being able to locate “CX3_shared.mjs”. I checked the MMM-CalendarExt3 repo, and found that file CX3_Shared/CX3_shared.mjs, which for some reason wasn’t getting pulled by a git pull. I manually copied it in, and the calendar sort of started working.
I should have paid better attention to the documentation, because I would have seen that I needed to run
git submodule update --init --recursive
to update the submodule.The reason I say “sort of” is because my family calendar doesn’t show some repeating events, but I need to dig deeper into that.
I really appreciate all your help.
-
@redink the submodule problem is because you didn’t run npm install on the Ext3 module.
ext3 gets its events from the default calendar.
-
@sdetweil yeah, i probably just did a
git pull