Posts

• RE: DHT22 with Debian 12 Bookworm

  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.

  posted in Requests

  W

  wishmaster270
  
• RE: DHT22 with Debian 12 Bookworm

  @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
  

  posted in Requests

  W

  wishmaster270
  
• RE: DHT22 with Debian 12 Bookworm

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

  posted in Requests

  W

  wishmaster270
  
• RE: MMM-Mplayer video issues

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

  posted in Troubleshooting

  E

  evroom
  
• RE: MMM-MailMessage feature

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

  posted in Feature Requests

  M

  mumblebaj
  
• RE: pm2 doesnt work with crontab

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

  posted in Troubleshooting

  M

  mumblebaj
  
• RE: pm2 doesnt work with crontab

  @plainbroke said in pm2 doesnt work with crontab:

  @evroom,
  I get that nothing is found, when I run either of your suggestions.

  The journalctl -f shows the current activities.
  Simular to tail -f <filename>.
  So when there are none, you will see none.
  Use that when you know that a cron job is going to occur anytime soon.
  The --since "1 hour ago" searches for activities in the last hour.
  Change to, for example --since "24 hours ago" for activities in the last 24 hours.
  When nothing comes out, then indeed nothing happened (during the time period you are searching in).

  Other --since options:

  "today"
  "00:20"
  "2025-11-12"
  "2025-11-12 07:30:00"
  

  posted in Troubleshooting

  E

  evroom
  
• RE: pm2 doesnt work with crontab

  About /var/log/syslog.
  Debian does not use that anymore, already since a while.
  As far as I understand it, you will need to get familiar with journalctl.
  For cron jobs try this:

  $ journalctl --since "1 hour ago" --unit cron.service
  
  $ journalctl -f -u cron.service
  

  Happy hunting.

  posted in Troubleshooting

  E

  evroom
  
• RE: pm2 doesnt work with crontab

  @plainbroke Instead of piping the output to a blackhole, maybe pipe it to a logfile which you can interrogate to see why the pm2 start is not working?

  posted in Troubleshooting

  M

  mumblebaj
  
• RE: MMM-Hoymiles-Wifi

  @Jose1701

  No, sorry, no idea.
  What Sam says, but that needs knowledge.
  But I opened an issue/request, so let’s see if it will be granted:
  https://github.com/CuddlyCow/MMM-HoymilesPVMonitor/issues

  posted in Development

  E

  evroom