Project Sponsors group

wishmaster270

@Queasy
Great to hear that. As I am using Debian 12 at the moment I am optimistic it is working for older installations, too.

I think the topic is solved then.

wishmaster270

@Queasy
Hi and sorry for the late reply.

I released a new version of the module a couple of minutes ago which should fix the problem.

It uses the new version of the lib for newer operation systems and changes to a other branch if it is a old debian otherwise.

As expected the api of the lib changed and i needed to do a small change in the modules node_helper.js.

bhepler

@mmmallday - I don’t know why I’m not getting notifications from the forum but I’m just now seeing these replies to the thread.

Thank you for your work in updating the module. I’ve merged your pull request into the baseline. I encourage everyone to update the module and check out the new features.

wishmaster270

@Queasy Hi,

I will try to take a closer look at the problem in the next days.
I do not have a setup with Debian 13 at the moment and it will take me some time.
Did not test 2.x of open gpio yet. Maybe the api changed.

Make sure you set up the pull-up/pull-down resistor like described in this description

https://www.raspberrypi.com/documentation/computers/config_txt.html#gpio-control

wishmaster270

If you change line 25 in my dht11 script from except: to finally: you should see the whole error.

But make sure to revert the change after the problem is fixed.

wishmaster270

@com1cedric
Hi. No problem. If I have time it try to help.

It looks like there will installed two additional python libs in the venv in the tutorial you shared.
Maybe one of the libs is missing in the virtual environment my script creates.

You can add them to the venv with:

cd ~/MagicMirror/modules/MMM-Temperature/scripts
./venvWrapper.py --venv-name py-venv --install-libs lgpio RPi.GPIO

wishmaster270

@com1cedric

Hi,

I do not use a DHT11 at the moment but my MMM-Temperature should still work

https://github.com/Tom-Hirschberger/MMM-Temperature

Just checked the install process on a Debian Bookworm and it works fine.

evroom

@ge

A pity it does not work for you.
Strange that is only happens after a several hours
But mplayer is rather old, perhaps that is the primary issue.

Still, I tried it on my Pi 3b with 1Gb RAM and it runs well.
It is 3 to 5 seconds lagging.
Like the stream on my P4b with 8Gb.
It also does not seem very memory hungry.

Pi 3b is steaming now for over 2 hours, so I will need to look later again to see if it got messed up.
The Pi 4b is streaming for 2 weeks straight now, without issues.

To me it looks more like a camera issue, but if you say that other players have no issues …
Somehow mplayer does not like your rtsp stream, or it is a combination of factors.

I have found that there is a config file, where you can set options.
Try out some options (need to restart MagicMirror after every change).
For example try nocache first.
Then try cache=65536.
The option nosound is always good (can be set in the MMM-Mplayer options too, if not already done so).
The bandwidth option is just a shot in the dark.

$ vi ~/.mplayer/config
# Write your default config options here!

# No cache
nocache=yes

# Cache size in kBytes (4MB / 8MB / 16MB / 64MB)
# cache=4096
# cache=8192
# cache=16384
# cache=65536

# Do not play/encode sound
nosound=yes

# Bandwidth (10MB / 100MB / 1000MB)
# bandwidth=80000000
bandwidth=100000000
# bandwidth=1000000000

What also can be the case, is that the windowSize is not matching your stream resolution.
This can cause issues as it needs to recode this portion.
Try:

windowSize: { width: 960, height: 540 },

for a 1920x1080 (16:9) stream.

That is all I can think of.
Good luck.

mumblebaj

@ge You can possibly raise a new feature request on the modules Github page. Module was last updated 2 years ago though. You can clone the module and make the additions yourself as well. 😉

mumblebaj

@plainbroke Afternoon. What I was saying was that instead of sending your current output to a blackhole, >/dev/null >2&1, i meant sending it to a log file:
30 07 * * 6,0 /usr/local/bin/pm2 start mm >> /home/pi/mon.log 2>&1. This will send the output of the command /usr/local/bin/ pm2 start mm to a log file residing at /home/pi/mof.log. You can then interrogate this log file to see if there were any errors when the command was executed.

So, by pipe I meant redirect the output to somewhere.

M	MichMich
S	synint
X	xinximoni
C	Chazzer
S	sharmstr
I	Imnotme
R	Ricand
J	jrettsch
G	goldyfruit
W	wageck
D	Dresch360
B	bacon_bosch
S	scozzy
S	Saabman
N	negrito
C	CF76's
M	MaXi-XCeL
Y	ysz0507
O	orayoflighto
F	Fubd

Project Sponsors

Posts

Member List