@sdetweil

is already set to 1024

@scottwalsh

Will reimage with the 64-bit version and see if it is more stable.

I think not … but you can try it.

@scottwalsh

I gave up with Pi Zero 2W. The memory is to low.

I suspect this is your problem when removing modules results in running longer before crashing.

You maybe got a newer base OS when reimaging and the mm dependencies grows with every release (e.g. node, electron).

You did not write which OS you are using, 32-bit or 64-bit. The 32-bit is more resource-saving.

@AndyHazz said in 2.32.0 Calendar module limitDays and excludedEvents stopped working:

I can see this in the docker container logs so I reckon it’s reverting any changes I make there?

yes it overrides the default modules but you can change this behavior

@bdeelman said in Error on loading .css:

• /volume2/docker/magicmirror-1/css:/opt/magic_mirror/css

then try it with changing the above line to

- /volume2/docker/magicmirror-1/css/custom.css:/opt/magic_mirror/css/custom.css

@sdetweil

I changed the setup for css to

      - type: bind
        source: /var/services/homes/sam/magicmirror/mounts/css/custom.css
        target: /opt/magic_mirror/css/custom.css
        bind:
          create_host_path: true

It was a design mistake in the beginning to mount the whole folder instead the single file.

This is maybe not backward compatibel for all old setups.

@bdeelman

show us your setup. How did you start the container? If with the provided setup goto the magicmirror/run dir and show the output of docker compose config and output of cat .env, if with a docker run ... command show the full command.

I suspect you are using an outdated setup which mounts the whole css dir instead only custom.css file, I changed this a few months ago …

@MM_Noob

@MM_Noob said in MMM-Universal-Pir and cec-client:

OK - post the update to include the cec-utils in the build I can confirm it now works…

don’t understand, are you talking about this?

@MM_Noob said in MMM-Universal-Pir and cec-client:

I guess this update will be rolled into the latest release at some point ?

which update, which release?

@MM_Noob

I have no hardware to reproduce but maybe this helps for debugging:

Go to an empty dir and execute npm init -y, then write a file index.js with content:

const { exec } = require('node:child_process');

const onCommand = "echo 'on 0' | cec-client -s -d 1 > test.log";

console.dir(onCommand);

exec(onCommand, (error, stdout, stderr) => {
  if (error) {
    console.error(`exec error: ${error}`);
    return;
  }
  console.log(`stdout: ${stdout}`);
  console.error(`stderr: ${stderr}`);
});

Now run node index.js and look into presented output and into the file test.log. You can play with the content of onCommand, maybe you find what’s going wrong.

@mumblebaj

These are the “carbon” ads added by @MichMich, which probably still serve as a small source of income for him. I won’t turn them off without consulting him.

This ad can easily be hidden with an ad blocker in your browser or, for example, with “AdGuard Home” or similar tools.