@eyesallin yes it´s an “issue” with the pi5 as the os is now using wayland as graphical environment instead of x11 which was used forever, a lot of tools are written for it and now need to be updated to work with wayland. You will find a lot of scenarios where there is no updated tool or alternative for the pi5 atm. The switch was done end of 2023 so it´s very new.
Read the statement by Michael Teeuw here.
Latest posts made by schris88
-
RE: Issues with MMM-PIR
-
RE: Issues with MMM-PIR
your config looks good thus far, if you´re not getting it to run you can try my solution which is currently running like a charm
I installed it with MMM-Pir-Sensor-light and changed the code to use wayland,
to toggle the display on Pi5 this is working on a fresh OS installWAYLAND_DISPLAY=“wayland-1” wlr-randr --output HDMI-A-1 --off
WAYLAND_DISPLAY=“wayland-1” wlr-randr --output HDMI-A-1 --onpossible outputs HDMI-A-1 (the one right next to usb-c), HDMI-A-2
If you monitor turns back on by itself after ~10 secs add “vc4.force_hotplug=1”(1=hmdi1 / 2=hdmi2 / 3=both) to the end of your /boot/firmware/cmdline.txt without creating a new line
All I did was change the command in activate and deactivate display function in the node_helper.js and added the cmdline parameter (dont forget to reboot)
-
RE: suddenly the screen can't turn on
I was just trying to get a PIR Sensor running to toggle the display on Pi5 and this was the way to go on a fresh OS install, maybe it´ll help you out too
WAYLAND_DISPLAY=“wayland-1” wlr-randr --output HDMI-A-1 --off
WAYLAND_DISPLAY=“wayland-1” wlr-randr --output HDMI-A-1 --onIf you monitor turns back on by itself after ~10 secs add vc4.force_hotplug=1 (1=hmdi1 / 2=hdmi2 / 3=both) to the end of your /boot/firmware/cmdline.txt
if you´re running rotated you can add that as --transform 90 (more options see wlr-randr --help)
vcgencmd, xrandr and xset were not working anymore for me
-
RE: MMM-OpenWeatherMapForecast stuck on Loading....
I just got it working after struggling with it myself for quite a while. Currently, only the 3.0 API is available for onecall, while forecast, etc., still uses version 2.5. That’s why the default weather with forecast is still functioning.
For the MMM-OpenWeatherMapForecast module, you need to subscribe to the onecall 3.0 API, which is now part of a paid subscription. However, 1000 per month remain free, and you can specify the number of API calls per day allowed in your subscription.
In the node_helper.js file of the modules, I updated the API endpoint to the specified 3.0 API from the OpenWeather API: “https://api.openweathermap.org/data/3.0/onecall”.
Hint: The activation of the API may take a few minutes. You can check its status by calling the API in a browser. If you haven’t subscribed yet, the error message will indicate “invalid API key.” While it’s getting activated, it will display “bla bla for onecall 3.0, there is a separate subscription… see prices.”