That error is actually a ‘safety feature’ of the newer Raspberry Pi OS. Since they started protecting the system Python environment, you can’t just use pip install globally anymore. The easiest way around this is to use pipx. Try running these two commands- sudo apt install pipx pipx install mmpm This installs MMPM in its own little ‘bubble’ so it doesn’t mess with the rest of your Pi’s system.

@smegbadger said in MMM-Universal-PIR - ‘GPIOcommand exited with error!': It never occurred to me the container would update things unannounced! the container does not update things on your host, but the container itself is running debian and (if you are using karsten13/magicmirror:latest) the debian version of the container image switched from bookworm to trixie …

@sdetweil resolved in less than 24 hours :-) This is “responsive” ! Thanks again! Ralf

@Getinthegames awesome!!! thanks for the feedback

@karsten13 Thank you for your advice. To my shame, I must admit that I did not read the readme.md file. Yes, after reinstalling I am using Trixie and I have to use the gpiomon V2 So with gpiomon -e rising -c 0 17" it works Thank you again

@htilburgs and you can erase the core files

I think I found the issue, the scenes section for MMM-CalendarExt2 had an error. I discovered it by explicitly looking at errors in the console (and ignoring the many warnings).

@ArnoldoB if you use the classes approach vs the module name approach . I could never remember the module name approach , always looking up and down, and figuring how to configure for multiple instances of the same module I like to use the classname “all_pages” for fixed, makes more sense

@chrga awesome!!

ok, thank you for you advice. I will use a new card .

@Mathes75 can you find the message that best explains the fix, click the 3 dots to the right and select Mark this post as the correct answer

@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.