@ankonaskiff17 mm version cd ~/MagicMirror grep version package.json Wayland was introduced three Raspi OS releases ago. its ‘better’ than X11 they say WE MagicMirror don’t have any choice.

@chrga ok. Should be nothing to stop it Did you try my Module and the examples on the alert module did you add the ViewNotifications module so you could see it being broadcast The structure of the notification is exactly the same as if you were coding it in a running module

@Ronald ok, I only see pinn on sd card as a choice there On the MagicMirror topic you can use a different config.js with the MM_CONFIG_FILE environment variable So a different startup script would allow you to quickly switch between them

@videogame95 I replied to your other topic any module that wants to use OpenWeatherMap has to change the endpoint and provide the other parms AND the user needs to get a new apikey… supposedly the old 2.5 api parms still work, but OWM has told us repeatedly they are going to shut that down completely…

@videogame95 from the doc https://docs.magicmirror.builders/modules/weather.html#openweathermap-options in v3, location and locationID are not used. only lat/lon also https://forum.magicmirror.builders/topic/19323/version-2.30.0-weather-module-stuck-loading-worked-fine-before-upgrade?page=1 also, in old api we got the location back and added it to the header in 3.0 api we don’t so YOU have to set the header for the module AND set appendLocationNameToHeader:false in the weather module config

@ankonaskiff17 I dont use vnc, only ssh And dont have issues w locale

@ArnoldoB Submitted a pull request to the upstream.

@chrisfr1976 weird Upgrade log looks great. Can you change to DISPLAY=:0 npm start And try Shouldn’t matter, but such is life

@karsten13 said in Docker Watchtower container restarting and mm container errors after upgrade: I found a good documented PR in another project which explains the dbus errors in detail. Thanks for providing the link, interesting background.

@BKeyport I fixed my script to handle that

Hello together I have noticed that the excludedEvents function with the “until” parameter no longer works. The last time I used the function was version 18.3.24, when everything worked. While searching for the error, I came across this article https://forum.magicmirror.builders/topic/19767/2.32.0-calendar-module-limitdays-and-excludedevents-stopped-working?page=1 or this issue https://github.com/MagicMirrorOrg/MagicMirror/issues/3841. How was the error found (Reproducible) I want to hide a recurring event until X days before it starts. In the test case, the event is called “DailyTask”. This repeats every 2 days. I use the configuration excludedEvents: [{filterBy: 'DailyTask', until: '2 days'}] The appointments are displayed unchanged on the MM. I then only used the excludedEvents: [{filterBy: 'DailyTask''}] command. Now no events with the name “DailyTask” are displayed. Which leads me to conclude that the “until” parameter no longer works. it does not matter whether days, weeks or months are used Current Config for Calendar: { module: "calendar", header: "Kalender", position: "bottom_left", config: { excludedEvents: [{filterBy: 'DailyTask', until: '2 days'}], fade: true, fadePoint: 0.75, // Possible values: 0 (top of the list) - 1 (bottom of list) tableClass: "medium", // Possible values: xsmall, small, medium, large, xlarge. Default value: small. maximumEntries: 18, // default 10 showLocation: true, maxTitleLength: 40, // values 10-50 maxLocationTitleLength: 20, // values 10-50 // hidePrivate: false, coloredText: true, coloredSymbol: true, coloredBackground: true, calendars: [ { // Test-Kalender fetchInterval: 300000, // 5 min * 12 = 1h symbol: "calendar-plus", color: "#FFFFFF", // Dunkleres Grün #1ea30f etwas helleres Grün #43ff64d9 symbolClassName: "fa-regular fa-", bgColor: "rgba(0, 0, 0, 0.02)", name: "Test-Kalender", url: "https://calendar.google.com/calendar/ical/******************.ics" } ] } MM was reinstalled a few days ago. A Raspberry Pi 3B+ is used Operating System: Debian GNU/Linux13 (trixie) Kernel: Linux 6.12.47+rpt-rpi-v8 Architecture: arm64 MM version: v2.33.0 i use pm2 All modules with the exception of the calendar module were deactivated for the test. my solution I think I have found the problem in the calendarfetcherutils.js file. I have the following line 163: let { excluded, eventFilterUntil } = this.shouldEventBeExcluded(config, title); replaced with this code: let { excluded, until: eventFilterUntil } = this.shouldEventBeExcluded(config, title); Subsequent tests were positive for me, but I cannot judge whether the customisation has any further effects. Unfortunately I’m not a programmer, just a “nerd” =) can someone verify this and possibly open a bug? Best regards Jacky

@Keithj edit MMM-Traffic.js change these lines (79/80) self.errorMessage = payload.error.message; self.errorDescription = payload.error.description; to self.errorMessage = e.message; self.errorDescription = e.description; and restart MM let me know…

@sdetweil ok, that makes sense, caching might be an issue!

@dangerousden glad you got it working again!!

@CaptainKen no. You need to install node 22.18.0 You installed node 20

@Mr.Sponti do you have the gpu hardware enabled? If not then I think electron tries to emulate it, probably w the vlc content

@Richard238 said in Calendar failed to load - check the logs: about a minute ago If perhaps it could show the nature of the error? what does that mean? we requested the ics data from the calendar provider using the URL you provided in the config and the request failed, timeout… we don’t know why or anything more and we gave you all that in the messages we produced. And the route to the logs, because most of us have to look up where they are! ;-) you are LOOKING at the logs… so you must have found the route ---- as always — the logs IS the output of the MM start command, npm start node --run start npm runs server node --run server whatever you used now, you can do it manually in some terminal window OR you can code it into the system startup OR you can use a pgm that does that FOR you, aka pm2 WHERE that data is stored is up to that implementation as I do the install script, I use pm2, as it insulates me from the OS details… my script last lines is see the help echo please see the help for the pm2 command, pm2 --help echo pm2 status will show the running apps, and their runtime status SO… one could/should detect that the command is pm2 and so do pm2 --help and one core learning thing on linux ALL terminal commands , by agreed convention, provide a general help using the parameter --help so pm2 --help will tell you all the things it can do SOME commands ALSO provide a manual page (pm2 does not) which can be viewed with the man command man ls will show you the detailed help for the ls command Yes, there is a LOT to learn here…

@RonR ctrl-+. Should zoom in

thanks ok

@xylyn the caldav module is getting g the data from the server To create the iCal file the MagicMirror calendar module needs I don’t know how the caldav module works at that level