Unsolved Motion Detection Becomes Unresponsive After Being Idle For A Few Hours
-
Thanks again for all of your help! The motion detection works great after rebooting for a few hours. However, when I leave it alone and don’t return for several hours after, motion detection stops working and all I have is blank screen of hidden modules. This issue is intermittent, so it’s difficult to understand what is causing it. Clicking on the screen to wake (unhide) the modules also doesn’t work. It’s as if the entire display becomes disabled.
System:
32-bit Bookworm running on Pi5 with X11
Linux ClientV5 6.1.0-rpi8-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.73-1+rpt1 (2024-01-25) aarch64 GNU/Linux
Linux version 6.1.0-rpi8-rpi-v8 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT Debian 1:6.1.73-1+rpt1 (2024-01-25)Node v20.8.0
npm v10.1.0
MM Version: 2.26.0{
disabled: false,
module: ‘EXT-Screen’,
classes: “hide”,
position: ‘top_left’,
animateIn: “flipInX”,
animateOut: “flipOutX”,
config: {
debug: false,
animateBody: true,
autoDimmer: false,
delay: 20 * 60 * 1000,
mode: 0,
xrandrForceRotation: “normal”,
wrandrForceRotation: “normal”,
wrandrForceMode: null,
displayCounter: true,
displayBar: true,
displayStyle: “Text”,
displayLastPresence: false,
lastPresenceTimeFormat: “LL H:mm”,
displayAvailability: false,
detectorSleeping: false,
gpio: 18,
clearGpioValue: true,
sound: false,
touchMode: 0,
ON: [],
OFF: []
}
},{
disabled: false,
module: ‘EXT-Pir’,
classes: “hide”,
config: {
debug: false,
gpio: 18,
mode: 2
}
}, -
Clicking on the screen to wake (unhide) the modules also doesn’t work
It’s seams to be an MM² engine crash or an module crash
try to open dev tools when happen (in remote with CTRL+MAJ+I)
inspect red lines (error) and what module can do that