@fischi87 Sorry, do not know where I read iobroker but Home Assistant has a MQTT integration, too.

@fischi87 Hi and sorry. I use node red instead of iobroker and do not have a glue of it.
You will need a MQTT integration in iobroker, a MQTT broker and the MQTT module in the mirror.
If the device changes state iobroker gets notice of it and sends a message to a MQTT topic.
You can subscribe to this topic with the MQTT module in the mirror and initiate a notification with it.
The alert module can display the message in the notification in the result.

@fischi87 Hi, you could i.e. connect the mirror to iobroker with my MMM-MQTTbridge module and send a notification to the alert module depending of the state change.

@jedilkeme Hi, I do not have time to provide examples at the moment but I am pretty sure you can use my MMM-CommandToNotification module to call your script and my MMM-ValuesByNotification to display the information.

It seems that dbus is the only way to get the information.

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