@karsten13 my apologies, I see the transform is not needed as you have taken the rotation into account
Read the statement by Michael Teeuw here.
Posts
-
RE: I cannot disable screen blanking with MagicMirrorOS
-
RE: I cannot disable screen blanking with MagicMirrorOS
@karsten13 I left it running overnight with the MMM-Universal-Pir config lines commented out and the monitor physically switched off and this morning MM was still working fine when I switched the monitor back on again. When I looked at
docker logs labwc
thewlr-randr
command was failing (still being triggered every fifteen mins) which suggests the connection between theMMM-Universal-Pir
and the display driver is the issue rather than the display actually going off. I will try your new build today although i will have to add--transform 90
to theonCommand
to get my screen rotation.magicm@magicmirror:/opt/mm/mounts/config $ docker logs labwc HDMI-A-1 "Raspberry PI RPI MON156 81005568472 (HDMI-A-1)" Make: Raspberry PI Model: RPI MON156 Serial: 81005568472 Physical size: 350x190 mm Enabled: yes Modes: 1920x1080 px, 60.000000 Hz (preferred, current) 1920x1080 px, 60.000000 Hz 1920x1080 px, 59.939999 Hz 1920x1080 px, 50.000000 Hz 1920x1080 px, 48.000000 Hz 1920x1080 px, 47.952000 Hz 1280x720 px, 60.000000 Hz 1280x720 px, 60.000000 Hz 1280x720 px, 59.939999 Hz 1280x720 px, 50.000000 Hz 1280x720 px, 48.000000 Hz 1280x720 px, 47.952000 Hz 720x576 px, 50.000000 Hz 720x480 px, 60.000000 Hz 720x480 px, 59.939999 Hz 640x480 px, 60.000000 Hz 640x480 px, 59.939999 Hz 640x480 px, 59.939999 Hz Position: 0,0 Transform: 90 Scale: 1.000000 Adaptive Sync: disabled failed to connect to display failed to connect to display failed to connect to display failed to connect to display failed to connect to display failed to connect to display failed to connect to display failed to connect to display failed to connect to display failed to connect to display failed to connect to display failed to connect to display failed to connect to display failed to connect to display failed to connect to display failed to connect to display failed to connect to display failed to connect to display failed to connect to display failed to connect to display magicm@magicmirror:/opt/mm/mounts/config $ docker exec -it labwc bash pi@c7c64f70849e:/$ wlr-randr failed to connect to display pi@c7c64f70849e:/$
Steve
-
RE: I cannot disable screen blanking with MagicMirrorOS
@karsten13 unfortunately that change did not prevent the display from dropping. There’s no time timestamp in the docker logs for
labwc
but when i looked this morning there were some 40 calls towlr-randr
that had failed. If they are every 15mins that’s about 10:00 it failed. I will make a more accurate observation tonight -
RE: I cannot disable screen blanking with MagicMirrorOS
@karsten13 i have disabled the
init
container as suggested.When the display fails I can get it back with
docker rm -f labwc && docker compose up -d
(docker compose up -d --force-recreate
also works butdocker compose up -d
on it’s own doesn’t). I am running it today with theMMM-Universal-Pir
module disabled as another test (although when sitting at a login prompt it never went off).Note that the display fails after a few hours of no PIR trigger, it doesn’t have to be overnight.
Steve
-
RE: I cannot disable screen blanking with MagicMirrorOS
@sdetweil I stopped docker at 9:30 last night with
docker compose down
leaving the screen at the magicmirror login prompt. This morning the screen was still showing the login prompt . MM was reinstated perfectly withdocker compose up -d --force-recreate
. @karsten13 I notice there are now four objects that start:[+] Running 4/4 ✔ Network magicmirror_default Created 0.1s ✔ Container mm Started 0.9s ✔ Container init Started 1.0s ✔ Container labwc Started 1.0s
Steve
-
RE: I cannot disable screen blanking with MagicMirrorOS
Hi
I don’t know where that would be. The RPi boots to a login prompt. Then docker takes over and launches MM in electron. There is no GUI for me to fiddle with
Steve
-
I cannot disable screen blanking with MagicMirrorOS
Hi
I am running MM via MagicMirrorOS on a RPi4B with an RPi monitor in portrait. I use MMM-Universal-Pir to turn the screen on and off during the day (with
wlr-randr
commands) which works great but the screen switches off for good overnight, the PIR cannot wake it up. I have disabled Screen Blanking withraspi-config
but that makes no difference.If I run
wlr-randr
in thelabwc
container (access viadocker exec -it labwc bash
) I normally get (some resolutions removed for brevity):HDMI-A-1 "Raspberry PI RPI MON156 81005568472 (HDMI-A-1)" Make: Raspberry PI Model: RPI MON156 Serial: xxxxxxxxxxxx Physical size: 350x190 mm Enabled: yes Modes: 1920x1080 px, 60.000000 Hz (preferred, current) ... 640x480 px, 59.939999 Hz Position: 0,0 Transform: 90 Scale: 1.000000 Adaptive Sync: disabled
However, once the display has gone to sleep that same
wlr-randr
command givesfailed to connect to display
this make me feel it is something in the docker set up but i see nothing in the docker logs
Note that I also have
RANDR_PARAMS="--output HDMI-A-1 --transform 90"
in the.env
file to rotate the display at boot.Cheers
Steve -
RE: Getting MMM-CalendarExt3Agenda to show more than 10 days out
Hi
I’ve discovered the CSS for the agenda module has a hard height limit
.CX3A .agenda { max-height: 600px; }
increasing that to
1325px
fills the screen height . I can’t tell if that was the problem all along as the patch is in place now!overriding the font and width as follows has given me the size of agenda I wanted.
.CX3A { font-size: 30px; max-width: 600px; } .CX3A .event .headline.useSymbol .symbol { font-size: 25px; }
many thanks for your help
-
RE: Getting MMM-CalendarExt3Agenda to show more than 10 days out
Hi
I ran
npm run install-mm
in the docker container as the above commands and rebooted. The agenda is still truncatedSteve
-
RE: Getting MMM-CalendarExt3Agenda to show more than 10 days out
Hi
following the same process that i used to install MMM-CalendarExt3Agenda in the fiirst place i ran the git inside the docker but it hasn’t changed the display. Have i done it incorrectly?
magicm@magicmirror:/opt/mm/run $ docker exec -it mm bash node@magicmirror:/opt/magic_mirror$ ls CHANGELOG.md clientonly entrypoint.sh js mount_ori serveronly Collaboration.md config eslint.config.mjs jsconfig.json node_modules tests LICENSE.md create_restore_script.sh fonts mm2.png package-lock.json translations README.md cspell.config.json index.html module-types.ts package.json vendor build.info css jest.config.js modules prettier.config.mjs node@magicmirror:/opt/magic_mirror$ git fetch origin pull/3679/head:_fix_clipping remote: Enumerating objects: 27479, done. remote: Counting objects: 100% (27479/27479), done. remote: Compressing objects: 100% (9077/9077), done. remote: Total 27158 (delta 17476), reused 26718 (delta 17037), pack-reused 0 (from 0) Receiving objects: 100% (27158/27158), 22.64 MiB | 12.11 MiB/s, done. Resolving deltas: 100% (17476/17476), completed with 228 local objects. From https://github.com/MagicMirrorOrg/MagicMirror * [new ref] refs/pull/3679/head -> _fix_clipping * [new tag] v2.0.0 -> v2.0.0 * [new tag] v2.0.1 -> v2.0.1 * [new tag] v2.0.2 -> v2.0.2 * [new tag] v2.0.3 -> v2.0.3 * [new tag] v2.0.4 -> v2.0.4 * [new tag] v2.0.5 -> v2.0.5 * [new tag] v2.1.0 -> v2.1.0 * [new tag] v2.1.1 -> v2.1.1 * [new tag] v2.1.2 -> v2.1.2 * [new tag] v2.1.3 -> v2.1.3 * [new tag] v2.10.0 -> v2.10.0 * [new tag] v2.10.1 -> v2.10.1 * [new tag] v2.11.0 -> v2.11.0 * [new tag] v2.12.0 -> v2.12.0 * [new tag] v2.13.0 -> v2.13.0 * [new tag] v2.14.0 -> v2.14.0 * [new tag] v2.15.0 -> v2.15.0 * [new tag] v2.16.0 -> v2.16.0 * [new tag] v2.17.0 -> v2.17.0 * [new tag] v2.17.1 -> v2.17.1 * [new tag] v2.18.0 -> v2.18.0 * [new tag] v2.19.0 -> v2.19.0 * [new tag] v2.2.0 -> v2.2.0 * [new tag] v2.2.1 -> v2.2.1 * [new tag] v2.2.2 -> v2.2.2 * [new tag] v2.20.0 -> v2.20.0 * [new tag] v2.21.0 -> v2.21.0 * [new tag] v2.22.0 -> v2.22.0 * [new tag] v2.23.0 -> v2.23.0 * [new tag] v2.24.0 -> v2.24.0 * [new tag] v2.25.0 -> v2.25.0 * [new tag] v2.26.0 -> v2.26.0 * [new tag] v2.27.0 -> v2.27.0 * [new tag] v2.28.0 -> v2.28.0 * [new tag] v2.29.0 -> v2.29.0 * [new tag] v2.3.0 -> v2.3.0 * [new tag] v2.3.1 -> v2.3.1 * [new tag] v2.4.0 -> v2.4.0 * [new tag] v2.4.1 -> v2.4.1 * [new tag] v2.5.0 -> v2.5.0 * [new tag] v2.6.0 -> v2.6.0 * [new tag] v2.7.0 -> v2.7.0 * [new tag] v2.7.1 -> v2.7.1 * [new tag] v2.8.0 -> v2.8.0 * [new tag] v2.9.0 -> v2.9.0 node@magicmirror:/opt/magic_mirror$ git switch _fix_clipping error: Your local changes to the following files would be overwritten by checkout: package-lock.json package.json Please commit your changes or stash them before you switch branches. Aborting node@magicmirror:/opt/magic_mirror$ rm package-lock.json node@magicmirror:/opt/magic_mirror$ rm package.json node@magicmirror:/opt/magic_mirror$ git switch _fix_clipping D config/config.js.sample Previous HEAD position was c24de64d Release 2.30.0 (#3673) Switched to branch '_fix_clipping' node@magicmirror:/opt/magic_mirror$ ls CHANGELOG.md clientonly entrypoint.sh js mount_ori serveronly Collaboration.md config eslint.config.mjs jsconfig.json node_modules tests LICENSE.md create_restore_script.sh fonts mm2.png package-lock.json translations README.md cspell.config.json index.html module-types.ts package.json vendor build.info css jest.config.js modules prettier.config.mjs node@magicmirror:/opt/magic_mirror$ exit exit magicm@magicmirror:/opt/mm/run $