I took the plunge. My five year old MagicMirror ground to a halt as far as Display resolution, Rotation and DIsplay control are concerned. Everything was working great on my Raspberry Pi 3B+. An unfortunate rpi-update broke everything. I struggled to restore Bullseye, and it was a shock to realise it is not easy to find the right official image. I then tried Bookworm, the three issues continued to remain unsolved. I then decided to install Trixie. Most of the transition of MM was smooth, ofcourse with a few hicks, but getting the display resolution and rotation was the most frustrating part. I got it working finally. I have restored the Display resolution and the rotation succesfully. I will shortly upload the entire process which was not only exhausting but of great learning value. I need to recover the GPIO Notification Module which isnt working and resulting Motion control of monitor using RCWL0516.

@sdetweil Thank you for the info. However, I finally successfully migrated to Trixie with desired Monitor Resolution and Rotation. And i am using Raspberry Pi 3B+ with an Acer 27 Inch monitor. With Trixie being launched only three weeks back, there is almost no solutions avaiable. I will shortly share my process of how it was achieved. Thanks

@schlomm ## I just thoght of uploading the Summary of Attempts - All Failed. It is really getting frustrating. My Monitor was working perfectly well the desired rotation and resolution 1080x1960, and now is stuck at 1024x768. config.txt modifications:** Custom hdmi_timings for 1920x1080 Various hdmi_mode settings (82, 87) hdmi_ignore_edid=0xa5000080 Different boost levels and drive settings Result: Monitor only shows up to 1024x768 max cmdline.txt kernel parameters:** video=HDMI-A-1:1920x1080@60D Various video= parameter combinations Result: No effect on available resolutions Custom EDID firmware:** Created multiple EDID files (256 bytes, 268 bytes, 285 bytes) Placed in /lib/firmware/edid/ and /boot/firmware/edid/ Used drm.edid_firmware=HDMI-A-1:edid/1920x1080.bin Rebuilt initramfs to include EDID early Result: Kernel loads file but rejects it as “Invalid firmware EDID” Wayland/X11 rotation scripts:** wlr-randr (Wayland) - can’t set non-existent 1920x1080 mode xrandr (X11) - output name issues Result: Can only work with available modes (max 1024x768) Core Problem: Acer HA270 monitor provides NO EDID data** to the Pi Bookworm OS + Labwc Wayland compositor won’t accept forced resolutions Same monitor worked with Pi 3B + Bullseye (older firmware stack) Raspberry Pi detects only: 1024x768, 800x600, 848x480, 640x480 Current Status: Stuck at 1024x768 rotated = 768x1024 instead of desired 1080x1920. Wonder if we the Rpi OS team is aware f this issue.

@Capt-Jib and what is the error?

@sdetweil Sure noted. Thanks

@karsten13 said in ChatGpt developed Module MMM-Dockerstat: @Rags missed the -a ❯ docker ps -a --format "{{.Names}} {{.State}}" magicmirror running watchtower running traefik running Great ! Yes the command is working now but locally on the docker machine only. It needs to work from the first machine after ssh ing into docker machine. ssh .exec (‘docker ps -a --format “{{.Names}} {{.State}}”’) .on(‘error’, (err) => { console.error(Error: ${err}); this.status = ‘Error’; this.sendSocketNotification(‘STATUS_UPDATE’, { status: this.status, icon: this.offlineIcon }); })

@Rags can u send me the module_list file from the backup the package-lock.json message is noise. sadly we can’t suppress those UUID message. this is a sign that the module hasn’t been updated in a while. there is no telling what the impacts of the update might be. there are breaking changes everywhere. I strongly recommend ignoring the messages. I don’t see any issue in the pm2 setup during install. I ask it for the command IT thinks it needs to execute, and then I execute that command. same as u did manually I will get the os level u used and test, thanks. there is no good way to test for module eol, as only 1 developer uses that term lots of modules have been abandoned, but still work. on the not copied files (token.json, env…) I might have an idea there.

I recently bought an ACER HA240Y monitor (https://www.displayspecifications.com/en/model/8d8f1615) for my Magic Mirror. I wanted to install the monitor in my frame in portrait mode. However, The display settings of the Pi OS are unable to identify the monitor and i am unable to find the drivers for the monitor in the Raspberry Pi OS. I am not able to proceed further to flip the display from landscape to portrait. Is there any way in which this can be resolved. Thanks

Post the issue here https://forum.bugsounet.fr/ Good luck with him, pompous to say the least.

Hi, After recoding, main code of EXT-TelegramBot This one is now locked to my own use and exclusively to EXT Plugins And in reverse, you can’t use any EXT-TelegramBot commands in MMM-TelegramBot I confirm, i send back MMM-TelegramBot to @MMRIZE

@Rags Yeah, the only real potential downside is that smartTV’s may or may not handle Poweroff or standby requests properly, and in the event of a loss of power, may or may not come back on automatically. Other than that, they tend to be a lot cheaper than monitors but just as good. Heck, if you can find a cheap 4k tv, probably even better than typical PC monitors!

Update: found it how to export also the birthday calendar (this only works by exporting ALL your calendars at once, but not on the birthday calendar itself). And anyhow - that didn’t solve my issue - because the exported birthday calendar has each of the birthdays as 3 single events (birthday from last, current and next year), but it’s not a yearly event-series. So using this exported file once wouldn’t help much on my MM - after 2 years all the birthdary events would be gone again. I will use a workaround now: I will create a separate calendar, where I enter all the birthdays manually (as yearly events). This calendar will then have a public address, and I can include it as separate calendar in MM.

@Rags Message forwarding or relaying between bots are not allowed by spec of API. Bot doesn’t react to other bot’s message.

@sdetweil Ok Problem solved. I installed MMM-DHT-Sensor module instead of MMM-LocalTemperature module and it is working like a charm. Absolutely no issues during installation and worked the first time it was fired up. This indicates there is some issue with the MMM-Local Temperature module. I opened an issue in the Github page. Hope it can be addressed.

@Rags correct. Alexa only knows the sound of words

@sdetweil Bingo. All systems go… Thanks once again. I am doing the backup restore thing now.

@Rags You are welcome. Great if it works.

@MMRIZE u want me to add that? I can do u can incorporate. (really just copy paste from other code)