@ldwvii https uses encryption to protect your data while traveling across the internet.
to do this, the receiving host must have registered to support that encryption.
it does this by recording it’s url and encryption type with a certificate authority ( not just anybody can be an authority), they give back a file with a key, with a specific lifetime. ( so u can’t have old sites with bad security hanging around forever)
well the authorities also have expiring rights.
in this case the authority’s certificate expired. (it’s a chain ) … and there was a bug in electron that didn’t handle it correctly
now, in your case u use an unprotected url ( no longer allowed as a standard)
no ‘s’ on http and it was redirected to secure (https)… maybe the redirect sent to the wrong place…
MMM-AlexaControl was working great changing pages of Sbatm’s MMM-Carousel but stopped a couple of months ago. The Wemo devices are present in the Alexa App and show as connected but tapping the power button or speaking the command does not result in a page change anymore. I’m using a Raspberry Pi for the Magic Mirror. Here is my MMM-AlexaControl config. I would really appreciate some help in troubleshooting this. Thanks!
In my test (with my calendars), I cannot find anything wrong.
Try self-testing more.
Remove all other modules except CX2 from config. (You can backup your original config.js), Then try again.
You have two month views on a screen. Usually, screen is not so huge to hold multi month views. Is there any special reason? Anyway try with just one month view.
Investigate the Front-end Log and Backend-log. Is there any suspicious message in both? Especially in scanning result in back log, how it shows?
[29.08.2023 08:58.32.610] [LOG] [CALEXT2] calendar:Gracie >> Scanning start with interval:60000
[29.08.2023 08:58.32.843] [LOG] [CALEXT2] calendar:Gracie >> Scanned: 18, Selected: 18
[29.08.2023 08:58.33.977] [LOG] [CALEXT2] calendar:General >> Scanning start with interval:60000
[29.08.2023 08:58.34.360] [LOG] [CALEXT2] calendar:General >> Scanned: 23, Selected: 23
[29.08.2023 08:58.34.662] [LOG] [CALEXT2] calendar:Nora >> Scanning start with interval:60000
[29.08.2023 08:58.35.435] [LOG] [CALEXT2] calendar:Nora >> Scanned: 96, Selected: 96
Were the scanned/selected results changed in close cycles? (You can test it with short scanInterval of calendar)
Without original ical data and environment, I cannot reproduce your issue. Could you send me the original config.js and custom.css privately? (firstname.lastname@example.org) I’ll drop your ical after investigation.