@smegbadger

unfortunately that change did not prevent the display from dropping

I expected this already …

can you post the exact error message of wlr-randr when it fails?

Other point: What happens if you disable MMM-Universal-Pir for a test? Are you still getting the errors or does mm runs correctly over night?

@sdetweil

this was already done with release v2.28.0 (openmeteo as default weather provider in config.js.sample)

@karsten13 said in I cannot disable screen blanking with MagicMirrorOS:

I will try to build a labwc container which executes wlr-randr e.g. every 30min. so we can see if this helps.

you can now test with a new labwc container which does the wlr-randr call every 15min. but I’m not sure this helps …

For testing change this line in the .env file

LABWC_IMAGE="karsten13/labwc:develop"

and then do a docker compose pull && docker compose up -d

@smegbadger said in I cannot disable screen blanking with MagicMirrorOS:

I can get it back with docker rm -f labwc && docker compose up -d

so restarting only the labwc container solves the problem …

I will try to build a labwc container which executes wlr-randr e.g. every 30min. so we can see if this helps.

@smegbadger

the 4 objects are o.k., one network and 3 containers (init is only for setting correct permissions in the mount folders, it runs for a very short time, you can disable it in the .env file if wanted).

Question: When the failed to connect to display occurs, how do you get the screen back working? Is a docker rm -f labwc && docker compose up -d sufficient or a docker compose up -d --force-recreate? Or do you have do reboot? Or do you switch the monitor off and on?

Other idea is to implement a wlr-randr call every 30min. in the labwc container.

@sdetweil

the setup is “Raspberry Pi OS Lite” with the normal docker setup and an additional labwc container

@smegbadger

I have no idea what is happening. Sounds like the monitor totally cuts the connection to the pi after a while.

Maybe this post contains something helpful.

What is your wlr-randr command for waking up?

see https://github.com/ianperrin/MMM-Strava

@plainbroke

see e.g. https://www.baeldung.com/linux/clean-zombie-process

fixed now, you can restart the pi (it will need some time to pull the new image before working) or

cd /opt/mm/run
docker compose pull
docker compose up -d

@scottwalsh

Thanks for the finding.

The labwc image is built weekly and after a first look in the logs (comparing to the week before) it seams seatd is not installed anymore.

Have to dig deeper …

@scottwalsh

on OS boot

@scottwalsh

the script /opt/mm/install/install.sh is executed with every reboot.

As workaround you could add

sleep 10s
docker compose up -d --force-recreate

at the end (where you have to play with the sleep seconds).

mmos is critical with pi zero 2w, I had a user who gave up, but it depends on installed modules and quality of used sd-card.

CONF_SWAPSIZE=1024 (if not changed by user)

@sdetweil

well, I did not promote it because the image base was to old (beside other problems) but in 2024 I decided to do a complete refactor so now the image build (iso, not docker) is done by me with gitlab based on the current raspian bookworm os lite.

@sdetweil

from the beginning

@scottwalsh said in MagicMirrorOS build intermittently not starting mm container (Version 2.30):

However, I am finding if power cycle it, sometimes the calendar does not load up and just have a blank screen.

I don’t know if this is related to the docker setup but I think not. I have encountered similar problems depending on slow hardware and/or heavy load on start due to many modules starting in parallel or starting after fresh boot.

So you could try to change the start order of the modules (order in config.js), e.g. put the calendar as first.

@sdetweil said in MagicMirrorOS build intermittently not starting mm container (Version 2.30):

@scottwalsh that is not MagicMirrorOS
that is karstens docker container

mmos uses my docker setup

https://khassel.gitlab.io/magicmirror/docs/faq.html#error-cannot-find-module-request

@plainbroke

you can do cron restart with pm2 too, see https://pm2.keymetrics.io/docs/usage/restart-strategies/

@morangen said in Calendar Recurring events on wrong day:

I’ll have to make sure it is actually updating and or pulling the latest version in.

yes, not everyone wants auto updating if a new image is available.

For this you can use tools like watchtower (as @sdetweil already mentioned).

The docker image is updated weekly (for getting updates of the underlying debian) but because mm only releases every 3 months there are no mm changes inside.

So beside auto updating you could do a manual docker pull ... every 3 months to get the new mm release …

@wswenson said in MMM-Flights:

I would like to see a configuration option to filter

now implemented with this commit

Thanks for the suggestion!