@m3iaz Hi,

the Reolink cams provide a fluent and a high quality stream.
You can select three different stream types in the Surveillance Station. The MJPEG stream is generated of the one for reduced speed which in my setup is the fluent stream of the Reolink cam.
I can select a 640x stream in my Reolink but it may depend of the camera.

I do not have much time to program at the moment but you may checkout my EmbedURL module. It is able to embed images and a refresh rate can be configured. Some people use it to embed JPEG of public webcams already.

@MMRIZE
Or https://github.com/Tom-Hirschberger/MMM-Notification-To-Command

@Jimmy1502
You will need to comment the try, too. Additionally the indention of the code needs to be changed.
The file will be look like this then:

#!/bin/python3
#Install Dependencies:
#  pip3 install adafruit-circuitpython-dht
#  sudo apt-get install libgpiod2
import time
import board
import adafruit_dht
import json
import sys

gpio_nr = 4
if len(sys.argv) > 1:
    gpio_nr = int(sys.argv[1])


# Initial the dht device, with data pin connected to:
dhtDevice = adafruit_dht.DHT22(getattr(board, "D%d"%gpio_nr))

result = {}
result["temperature_c"] = dhtDevice.temperature
result["humidity"] = dhtDevice.humidity
result["temperature_f"] = (result["temperature_c"]*1.8) + 32
result["error"] = False

print(json.dumps(result))

@Jimmy1502 As the reuseCount is set to 100 the wrong value need to be caused by the script sending them.
It only sends 0.0 if a error occurs.

You may remove the except block in the script and fire it very quickly on the shell to see what causes the error.

@Jimmy1502 I think the problem with the temperature is caused by the json path. The script outputs temperature_c and temperature_f but the json path causes the module to search for temperature only.

The problem with the humidity may be caused by the interval you query the sponsor values. 10 seconds is very short for the dht sensor. Maybe you can try a bigger interval.

@Jimmy1502
The script uses GPIO 4 in default but accepts any GPIO number as first argument.
At least GPIO 25 has no double function on raspberries and should work.

You can call the script directly in the shell and check the output for debug purposes.
And make sure to check the comments in the first lines of the script if you need to. install any dependencies.

Edit: Looks like you use GPIO 12 in your config which should work, too

@Jimmy1502 Hi and thanks to @sdetweil for trying to help.

I will try to update the readme of the module in the next days.

The timeout is set in milliseconds. Your config looks like it is set to 5ms. The script will not be able to respond in this time.
Please increase it to a value much higher especially for the dht sensor. Let’s say something like 1000ms.

@Hanimani As sdetweil suggested you can access the page of MagicMirror in your browser to do development. The only problem with this approach is that there are multiple instances of the page. This can cause some modules to behave strange (like sending notifications twice, etc.).

As an alternative you can enable VNC on the MagicMirror machine and connect to it remotely. You than can hit CTRL+R and access the Web development tools.

@h_vestbo Hi, my MMM-ValuesByNotification module is able to select single values in Json structures by JsonPath so does my MMM-MQTTbridge module.
You can receive the MQTT message with my MMM-MQTTbridge module, trigger a notification and display it with the MMM-ValuesByNotification module.

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

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