@sdetweil

and I learned more about pi imager, the stuff it writes seems to depend on the OS, with my examples above I used fedora, now looking at a raspian pi os lite I don’t see the files.

There now is a userconf.txt with only user/password …

@sdetweil

files should be in same directory as config.txt and cmdline.txt. Maybe the OS deletes them after initial reading? So you may have to look for this files before you insert the sd-card into the pi …

example of user-data:

[mm@pi4-argon efi]$ cat user-data
#cloud-config
hostname: pi4-argon
manage_etc_hosts: true
packages:
- avahi-daemon
apt:
  conf: |
    Acquire {
      Check-Date "false";
    };

users:
- name: mm
  groups: users,adm,dialout,audio,netdev,video,plugdev,cdrom,games,input,gpio,spi,i2c,render,sudo
  shell: /bin/bash
  lock_passwd: false
  passwd: $5$wEw...
  ssh_authorized_keys:
    - ssh-rsa AAAA...
  sudo: ALL=(ALL) NOPASSWD:ALL


timezone: Europe/Berlin
keyboard:
  model: pc105
  layout: "de"

example of network-.con:

[mm@pi4-argon efi]$ cat network-.con
version: 2
wifis:
  renderer: networkd
  wlan0:
    dhcp4: true
    optional: true
    access-points:
      "k13":
        password: "cbd..."

@sdetweil

another interesting fact, if I open the settings in the imager to flash another
the password fields (user and wifi) are filled with junk text, maybe encrypted… but the values I entered are not visible

thats normal

which version of pi imager are you using? Latest which is v1.9.0?

And you are using the right user + passwd (I often forget to set the correct user)?

The pi imager writes a file user-data into the root dir of the sd-card which has yaml content, you can check the content (e.g. user) and also try to override passwd, maybe it works unencrypted, otherwise you can try to encrypt with htpasswd.

wifi has own file network-.con (yaml too).

@rkorell said in Standard Weather Module showing unwanted header:

appendLocationToHeader

read the docs, there is no property with above name …

@smegbadger

I build another new labwc image. You can revert the changes done to MM_IMAGE and the on-/offCommand in your setup.

The new karsten13/labwc:develop now runs labwc with pid=1 (I thought that was already the case) and additionally kills labwc if the wlr-randr command fails with failed to connect to display.

Now the container will restart if labwc is terminated inside the container. This does not address the root issue but should be a good workaround (hopefully).

So please do again a docker compose pull && docker compose up -d to get the latest changes …

for testing I added wlopm to the current mm-develop docker image.

So for another test use this lines in the .env file

MM_IMAGE="karsten13/magicmirror:develop"
LABWC_IMAGE="karsten13/labwc:develop"

Then change the on/off commands in the config.js

                        module: "MMM-Universal-Pir",
                        position: "top_right",
                        config: {
                                onCommand: "wlopm --on HDMI-A-1",
                                offCommand: "wlopm --off HDMI-A-1",
                        }

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

@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.