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

@Getinthegames awesome!!! thanks for the feedback

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

@sdetweil That does work. Looking back, I did try that, but I wonder if maybe I had a typo in the region name or something. Makes things side-by-side as you say (for my usage with upper_third region): .region.upper.third .container { flex-direction: row; } Thanks, as always, for all the hard work and all the kind help!

@KristjanESPERANTO I’m using https://globe.airplanes.live/ and they have a RainViewer Layer which still works when zooming in - maybe they use a license key … [image: 1770852609766-c3f43f6d-acdd-4c96-873b-b565e57b5ccd-grafik.png] Another approach I played with is using german dwd data (problem: germany only), tested this in my MMM-Flights module: [image: 1770852815628-mmm-flights-radar.png]

@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

@lif Thank you very much, I didn’t think of such a solution, even though I work a lot with Gemini. It generated a module, but I can’t test it until tomorrow!Thank you very much, I didn’t think of such a solution, even though I work a lot with Gemini. It generated a module, but I can’t test it until tomorrow!

@htilburgs and you can erase the core files

@hahawoooooo it’s amazing what our minds see, even when it’s wrong! Glad you found it!!

@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

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

@Racing88 as I said, not module developer. That’s how I would have made them different

@Racing88 awesome!!!

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

@ArnoldoB Submitted a pull request to the upstream.

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

@plainbroke not too many, but that’s the hard way Define known page names Page1 Page2 Mom’ Dad Billy Sue Stocks Weather Family Anyhow Then at each module in your config Add a classes:"…..", After the module: line Where …… is the list of the pages you want this module to show on. Space separated Fox modules that should show all the time Use whatever name you set next to the pages fixed definition Sorry, no idea where Waldo is

@Mati_93 This sort of thing happens to others from time to time as well. It would be really interesting to know how you came across the old version 🕵️. We have the module list, which refers to the fork from shabatm since a while. Did you come across the old version in the forum?

@Queasy Great to hear that. As I am using Debian 12 at the moment I am optimistic it is working for older installations, too. I think the topic is solved then.

@dangerousden glad you got it working again!!