@bwente thanks… fix pushed a drop down, with no default set, when not present took the first entry… oops… in the module folder git pull for the fix… that means you didn’t use the config.js.sample as your base, and then didn’t use my installer script, which copies it…

Here is a shot of my MagicMirror layout. I wanted to get as much daily info into one screen as I could but also display photos at a size that was nice. Here is my module list; calendars - directory for iCloud calendar sync MMM-AirQuality MMM-DailyBibleVerse MMM-iCloudPhotos - syncs iCloud Photos Album to my Pi MMM-ImagesPhotos MMM-MoonPhase MMM-Pinfo MMM-PWSWeather - Provider for default weather module MMM-UpliftingNews - An RSS reader with links to positive news. (Not in the list of 3rd Party Modules) MMM-WordOfTheDay Simon’s Simple[image: screenshot.png]

@Snille Please take a look at the private message…

Description MMM-TempestWeather is a MagicMirror² weather module for owners of a WeatherFlow Tempest personal weather station. It combines real-time observations from your Tempest with current conditions and a five-day forecast. The display includes: Current temperature and conditions Wind speed and direction Relative humidity Barometric pressure and pressure trend Precipitation probability and daily accumulation Five-day forecast with weather icons Automatic WebSocket reconnection and connection monitoring Real-time observations are received through the WeatherFlow WebSocket service. Forecast and current-condition information comes from the WeatherFlow Better Forecast service. The module uses the standard MagicMirror frontend/node_helper architecture and requires no additional npm packages on supported Node.js versions. A WeatherFlow Tempest station, personal access token, device ID, and station ID are required. Screenshots [image: MMM-TempestWeather] Download https://github.com/dwburger/MMM-TempestWeather Installation and configuration instructions are provided in the README. Version 1.2 Added configurable imperial and metric unit support Added the units configuration option (imperial or metric) Imperial displays °F, MPH, inHg, and inches Metric displays °C, km/h, hPa, and mm Imperial remains the default for backward compatibility Better Forecast requests now use the selected unit system Version 1.1 Moved WeatherFlow WebSocket communication to node_helper.js Moved Better Forecast REST requests to node_helper.js Added WebSocket reconnection and connection watchdog Added forecast request timeout and overlap protection No additional npm packages required Version 1.0 Initial standalone release

@sdetweil The comma, it’s always the comma. Thank you.

The current version of electron we use is version 43, This version actually downloads the binary for the matching runtime at startup. Help from others added a script to my scripts package to help cleanup the growing disk consumption Anyhow, version 43 is no longer supported after this year Version 44 does NOT provide support for arm32, armhf systems. Node 24 also has the same limitation. We will move to electron 44 in the October release. And will document a workaround: after install or upgrade, manually install electron 43 before running (I’ll update the install/upgrade scripts to do the hack while it works) We don’t know how long this hack will work. Soooo, for those of you running on 32bit os for smaller memory, pi0-2w or pi3, you need to start making plans Freeze upgrades on that system Upgrade, possibly the hardware too, to a 64 bit os We have added the electron 44 to the next release, aka develop, branch If you have time or interest you can start reviewing its impacts by installing the develop branch. See my post in troubleshooting about testing changes for how to get the develop branch

I was having issues with getting rtsp streams from my Frigate NVR to reliably show as I wanted them so I decided to let AI create a module for me that uses WebRTC and it’s much simpler. I’m using it only to show a birdseye view from Frigate rather than multiple individual cameras but it’s working well for me so far but wanted to share. https://github.com/maxbethge/MMM-WebRTC

@1a2a3a For the latest Wayland on off I use the new adjusted scripts. mon.sh #!/bin/bash export WAYLAND_DISPLAY=wayland-0 export XDG_RUNTIME_DIR=/run/user/1000 /usr/bin/wlr-randr --output HDMI-A-1 --on --mode 1920x1080@60Hz --transform 270 mof.sh #!/bin/bash export WAYLAND_DISPLAY=wayland-0 export XDG_RUNTIME_DIR=/run/user/1000 /usr/bin/wlr-randr --output HDMI-A-1 --off This works pretty well for me. The screen eventually times out as there is no input and it turns off. In addition to these I have these cron entries to call the scripts. Turns the screen on at 6am and off at 9pm. 00 06 * * * /home/pi/mon.sh >> /home/pi/mon.log 2>&1 00 21 * * * /home/pi/mof.sh >> /home/pi/mof.log 2>&1

@1a2a3a not my intent to DO … was trying to get him to help…

@LaeHarr yes, if you are vnc connected, you have the browser menu and developers support

@Beginner_123 what was the ‘fix’ ? open a new window?

Would MMM-EmbedURL do what you need?

Got it working. MMM-iCloudPhotos Still testing with MMM-ImagesPhotos to see what update interval works for me.

@noeknl Hi and sorry for the late reply… Don’t know why I had overseen the post. There is a example at https://github.com/Tom-Hirschberger/MMM-EmbedURL/tree/main/doc/configs I think it contains everything you need to move the content and hide parts.

@sdetweil Sorry for the late answer. I was a bit busy. I will have a look to your Subtraction Code at the Weekend. Thanks

another user posted upcoming updates https://forum.magicmirror.builders/topic/20337/upcoming-enviromment-canada-changes

@sdetweil Everything’s fine – that’s what I thought. That’s why I’ve set out my changes as clearly as possible. Thank you very much!

@braijuvrou thanks… and the MMM-Config user doesn’t know, or need to know, how all this was constructed…

Withdrawn. The MagicMirror maintainer kindly pointed out that this is already covered by the built-in per-module animationSpeed: 0 config option — it gives an instant, blink-free content swap for any module that passes it through. Where a module hardcodes its fade duration, the correct fix is in that module (expose animationSpeed), not a separate global module. I’ve corrected that in my own modules and withdrawn MMM-NoFade. TL;DR: to stop a module from fading on updates, just set animationSpeed: 0 in that module’s config.

All, not sure if this was just me but after upgrading my Pi 5B to OS 13.6 my fan stopped working. The fix was to add the following line in /boot/firmware/config.txt. I put it near the top. dtoverlay=cooling_fan