PIR wake up automatically!

Sceetch

Hi,
im using the MMM-Pir module.
I set the timer on 30 second. If i move in front of the sensor the time resets itself and starts the countdown for new.
so far so good!

if the sensor does not detect any movement the screen disappears and the monitor switch off into standby mode.

so far so good!

but after another 30 seconds in Standby mode the Screen turns on automatically without any movement.

I have already taped over the sensor that im sure there is no movement possible. Same problem again.
it seems to be on a endless loop.

Does anybody know this problem??

wishmaster270

@Sceetch
Hi, a user of my Screensave module reported a similar problem a couple of days ago and worked out a solution.
Maybe take a look at the troubleshooting section at the end of my readme under
https://github.com/Tom-Hirschberger/MMM-Screen-Powersave-Notification

Sceetch

@wishmaster270

Hi,
Thx for your answer.
I saw your Information on the end.
But I can’t find the related .txt file under path
/boot/firmware/cmdline.txt

There is not a folder firmware inside.
Do you have perhaps another solution??

Thanks in advance

wishmaster270

@Sceetch
Hi,

on older OS Versions (i.e. Bullseye) the file is located under /boot/cmdline.txt

Sceetch

@wishmaster270

Hi,
I saw this file, but there is no vc4.force_hotplug Parameter listet.
Should I easily add it?

wishmaster270

@Sceetch Hi, yes, you will need to add it to the end of the single line that is in the file

sdetweil

@Sceetch did you resolve this?

Sceetch

@sdetweil
Hi,

Sorry for answering so late.
The problem already exists.☹️

To modify the Text file doesen’t solve the problem.
I have actually no solution.

Do u have another hint?

sdetweil

@Sceetch can you tell us the OS level you are on?

at the endof the startup messages with the latest version of MM is a list of the info we need
from my desktop system for example

[2024-10-15 01:09:31.337] [INFO]  System information:
### SYSTEM:   manufacturer: System manufacturer; model: System Product Name; virtual: false
### OS:       platform: linux; distro: Ubuntu; release: 22.04.4 LTS; arch: x64; kernel: 5.15.0-122-generic
### VERSIONS: electron: 31.6.0; used node: 20.17.0; installed node: 22.9.0; npm: 10.8.3; pm2: 5.4.2
### OTHER:    timeZone: Australia/Sydney; ELECTRON_ENABLE_GPU: undefined

on Bookworm,(latest) the PIM modes changed

Sceetch

@sdetweil
thx for help.
for me its not clear where i can find the information?

Is it on the booting sequence for raspberry?

sdetweil

@Sceetch this info is provided in the startup message of MagicMirror

if you are using pm2 to auto launch MagicMirror, then the pm2 command

pm2 logs --lines=xxx

where xxx is the number of most recent lines to display, and defaults to 15

siujd2001

I am having the same issue, which just started happening yesterday. It seems like the loop is 3 minutes or less, with the MMM-PIR timer set at 60 seconds to turn off screen.

I’m not running MM automatically via pm2.

I have added “vc4.force_hotplug=1” to the end of /boot/cmdline.txt

Raspbian ver 11 bullseye
MagicMirror version 2.29.0

Sceetch

@sdetweil

if i do your code, i get these datas:

PM2 | 2024-10-15T20:29:52: PM2 log: Node.js version : 20.8.0
PM2 | 2024-10-15T20:29:52: PM2 log: Current arch : arm
PM2 | 2024-10-15T20:29:52: PM2 log: PM2 home : /home/pi/.pm2
PM2 | 2024-10-15T20:29:52: PM2 log: PM2 PID file : /home/pi/.pm2/pm2.pid
PM2 | 2024-10-15T20:29:52: PM2 log: RPC socket file : /home/pi/.pm2/rpc.sock
PM2 | 2024-10-15T20:29:52: PM2 log: BUS socket file : /home/pi/.pm2/pub.sock
PM2 | 2024-10-15T20:29:52: PM2 log: Application log path : /home/pi/.pm2/logs
PM2 | 2024-10-15T20:29:52: PM2 log: Worker Interval : 30000
PM2 | 2024-10-15T20:29:52: PM2 log: Process dump file : /home/pi/.pm2/dump.pm2
PM2 | 2024-10-15T20:29:52: PM2 log: Concurrent actions : 2
PM2 | 2024-10-15T20:29:52: PM2 log: SIGTERM timeout : 1600
PM2 | 2024-10-15T20:29:52: PM2 log: ===============================================================================
PM2 | 2024-10-15T20:29:52: PM2 log: [Watch] Start watching MagicMirror
PM2 | 2024-10-15T20:29:52: PM2 log: App [MagicMirror:0] starting in -fork mode-
PM2 | 2024-10-15T20:29:52: PM2 log: App [MagicMirror:0] online

/home/pi/.pm2/logs/MagicMirror-out.log last 15 lines:
0|MagicMir | [2024-10-15 20:30:10.964] [LOG] Create new calendarfetcher for url:. Edited: moderator - Interval: 604800000
0|MagicMir | [2024-10-15 20:30:11.292] [LOG] requesting:https://opendata.dwd.de/climate_environment/health/alerts/s31fg.json
0|MagicMir | [2024-10-15 20:30:11.331] [LOG] [MMM-Pir] Version: 1.5.3 rev: 240701
0|MagicMir | [2024-10-15 20:30:11.333] [LOG] [MMM-Pir] [LIB] [PIR] Mode 0 Selected (onoff library)
0|MagicMir | [2024-10-15 20:30:11.446] [LOG] [MMM-Pir] [LIB] [PIR] Started!
0|MagicMir | [2024-10-15 20:30:11.449] [LOG] [MMM-Pir] [LIB] [SCREEN] Mode 9: xrandr (primary display) – Rotation: left
0|MagicMir | [2024-10-15 20:30:11.473] [LOG] [MMM-Pir] Started!
0|MagicMir | [2024-10-15 20:30:11.900] [LOG] MMM-DWD-Pollen: Success loading
0|MagicMir | [2024-10-15 20:30:11.931] [LOG] [MMM-OpenWeatherForecast] 15-Oct-24 20:30 ** ERROR ** Error: Request failed with status code 401
0|MagicMir | [2024-10-15 20:30:12.086] [INFO] System information:
0|MagicMir | ### SYSTEM: manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 4 Model B Rev 1.2; raspberry: [object Object]; virtual: false
0|MagicMir | ### OS: platform: linux; distro: Raspbian GNU/Linux; release: 11; arch: arm; kernel: 6.1.21-v8+
0|MagicMir | ### VERSIONS: electron: 29.4.2; used node: 20.9.0; installed node: 20.8.0; npm: 10.1.0; pm2: 5.4.1
0|MagicMir | ### OTHER: timeZone: Europe/Berlin; ELECTRON_ENABLE_GPU: undefined
0|MagicMir | [2024-10-18 19:33:19.104] [INFO] Calendar-Fetcher: Broadcasting 209 events from. Edited: moderator
/home/pi/.pm2/logs/MagicMirror-error.log last 15 lines:
0|MagicMir | [1441:1015/203007.468295:ERROR:gbm_wrapper.cc(76)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
0|MagicMir | [1441:1015/203007.469114:ERROR:gbm_wrapper.cc(259)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
0|MagicMir | [1441:1015/203007.469703:ERROR:gbm_wrapper.cc(76)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
0|MagicMir | [1441:1015/203007.470376:ERROR:gbm_wrapper.cc(259)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
0|MagicMir | [1441:1015/203007.470857:ERROR:gbm_wrapper.cc(76)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
0|MagicMir | [1441:1015/203007.471246:ERROR:gbm_wrapper.cc(259)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
0|MagicMir | [1441:1015/203007.471864:ERROR:gbm_wrapper.cc(76)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
0|MagicMir | [1441:1015/203007.472289:ERROR:gbm_wrapper.cc(259)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
0|MagicMir | [1441:1015/203007.473545:ERROR:gbm_wrapper.cc(76)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
0|MagicMir | [1441:1015/203007.473975:ERROR:gbm_wrapper.cc(259)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
0|MagicMir | [1441:1015/203007.474361:ERROR:gbm_wrapper.cc(76)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
0|MagicMir | [1441:1015/203007.474628:ERROR:gbm_wrapper.cc(259)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
0|MagicMir | [1039:1018/193452.138762:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion ‘GDK_IS_MONITOR (monitor)’ failed
0|MagicMir | [1039:1018/193452.146069:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion ‘GDK_IS_MONITOR (monitor)’ failed
0|MagicMir | [1039:1018/193452.150739:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion ‘GDK_IS_MONITOR (monitor)’ failed

0|MagicMirror | [1039:1018/193549.175898:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion ‘GDK_IS_MONITOR (monitor)’ failed
0|MagicMirror | [1039:1018/193549.241698:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion ‘GDK_IS_MONITOR (monitor)’ failed
0|MagicMirror | [1039:1018/193549.246287:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion ‘GDK_IS_MONITOR (monitor)’ failed
0|MagicMirror | [1039:1018/193634.176330:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion ‘GDK_IS_MONITOR (monitor)’ failed
0|MagicMirror | [1039:1018/193634.183421:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion ‘GDK_IS_MONITOR (monitor)’ failed
0|MagicMirror | [1039:1018/193634.186706:ERROR:browser_main_loop.cc(278)] Gdk: gdk_monitor_get_scale_factor: assertion ‘GDK_IS_MONITOR (monitor)’ failed

sdetweil

@Sceetch said in PIR wake up automatically!:

[MMM-Pir] [LIB] [PIR] Mode 0 Selected (onoff library)

I have seen troubles reported with mode zero.
i dont use this myself