@odolmach3
Hi,

just tried to run the latest Image of karsten13 on my Synology.
You need to make sure you add “npm run server” as “command” during the creating of the container settings.

@sifuhall Hi,

I think it might be already possible with my MMM-ValuesByNotification module.

If you need a module to fetch the data you can use a curl command with my MMM-CommandToNotification.

If you can send the data via MQTT you can use MMM-MQTTbridge.

@Jonae

Hi,

you can use my MMM-Temperature module or a combination of my two modules MMM-CommandToNotification and MMM-ValuesByNotification for this job.

@Brown19

Just released the new version 0.0.8 which (hopefully) fixes the problem.

I integrated your script, too. But i named it sht31d.

@sdetweil @Brown19
Hi,

i did some more investigation today and think i found a solution.
Although the exception looks different i think the problem is the execSync command.
The only way i was able to fix it is to use spawnSync.

But i can not say where or why the problem happens.
I tried different node versions (latest 16, 18, 20) and different electron versions (25.3.0, 25.3.2 and 25.4.0) with execSync.

I will release a new version of MMM-Temperature today which uses spawnSync instead of execSync.

@sdetweil Hi Sam, it looks like both MMM-Temperature and MMM-Tools cause the error.

@Brown19
Hi,

today i installed a new instance of MagicMirror 2.24.0 with both your node version 18 any my current used one (16).
In the installation which uses electron i can reproduce the error now. But i am pretty sure this is a problem related to the combination of the version 2.24.0 and the used electron version.
I found this thread with the same error but MMM-Tools instead in the forum of bogusnet, too.
It might be a general MagicMirror issue and not a problem of the module.

Maybe one of the core developers can have a look into it. I never had been that deep in the MagicMirror code and do not have much time to investigate the problem at the moment.

@Brown19 Do you see any errors in the development console of the browser?

@Brown19

I tried your script and the current version of the module in both of my setups (2.24.0 native and 2.25.0-develop container) and do not have any problems.

As i wrote already the problem looks like there is problem during communication between the node_helper.js and the frontend (either electron or the browser of your choice).

@ankonaskiff17 Hi,

it’s basically the same but not exactly…

• apt full-upgrade upgrades all packages and removes old versions of the packages
• apt dist-upgrade upgrades all packages and removes old versions but it tries to figure out which upgrade is more “worthful” if there are occur conflicts cause of the upgrades
• apt update updates the locally saved list of available packages by downloading the current package list of all configured repositories
• apt is the new replacement command of apt-get