PIR problem RPi 4B, Bullseye 64 bit

sdetweil

@wyovino pm2 launches a script in the
MagicMirror/installers/mm.sh

pm2 info (the pm2 app name, as shown by pm2 status)

for example
pm2 info MagicMirror
or
pm2 info 0 (if its the 1st created app in the list)

sdetweil

@wyovino sorry, I hit reject by accident, please resubmit

are you using pm2? or the manual install startup process editing a service?

did you use my install script? or the manual install?

wyovino

@sdetweil I don’t know why but my previous reply was rejected. I added my script to the mm.sh script but I believe that is legacy code that doesn’t get executed. This is the first line of that file:" # This file is still here to keep PM2 working on older installations."

Any suggestions would be appreciated.

sdetweil

@wyovino see my previous reply, I hit reject accidentally. ( I review all posts for members with reputation below 2, to keep out all the scammers, and porn posts)

anyhow, my install script uses that file with pm2 to launch MM.

so, as you are using mm as the name, the file is

~/MagicMirror/mm.sh

again, pm2 status

will show you the apps managed
pm2 info (the name or line number) will show you the detail, including the name of the thing launched

wyovino

@sdetweil I followed the instructions for the manual install and I’m using pm2. MagicMirror is working as expected, but I just can’t get my python script which stops and starts the monitor based on input from a PIR sensor to work unless I stop Magic Mirror, start my program, and then restart MagicMirror.

At this point I’m thinking of starting from scratch with the previous version of Raspberry Pi OS (Buster) which I believe works with a PIR module for Magic Mirror. That uses TVservice which does not work with Bullseye.

sdetweil

@wyovino

show me the output of

pm2 status

wyovino

@sdetweil
$ pm2 status

│ id │ name  │ mode     │ ↺   │ status    │ cpu     │ memory   
│ 0  │ mm    │ fork     │ 0   │ online    │ 0%       │ 2.8mb

sdetweil

@wyovino said in PIR problem RPi 4B, Bullseye 64 bit:

│ 0 │ mm

so the managed app name is mm
and the managed app number is 0

so, now, show me the output of pm2 info 0, or pm2 info mm


from my system
(base) sam@sams:~/MagicMirror$ pm2 info 1
 Describing process with id 1 - name MagicMirror 
┌───────────────────┬───────────────────────────────────────────┐
│ status            │ stopped                                   │
│ name              │ MagicMirror                               │
│ namespace         │ default                                   │
│ version           │ 2.15.0                                    │
│ restarts          │ 27                                        │
│ uptime            │ 0                                         │
│ script path       │ /home/sam/MagicMirror/installers/mm.sh 
..

particularly the script path

sdetweil

headed to bed, will look in in the morning

wyovino

@sdetweil pm2 info mm

 Describing process with id 0 - name mm
│ status            │ online                          │
│ name              │ mm                              │
│ namespace         │ default                         │
│ version           │ N/A                             │
│ restarts          │ 0                               │
│ uptime            │ 29m                             │
│ script path       │ /home/pi/mm.sh                  │
│ script args       │ N/A                             │
│ error log path    │ /home/pi/.pm2/logs/mm-error.log │
│ out log path      │ /home/pi/.pm2/logs/mm-out.log   │
│ pid path          │ /home/pi/.pm2/pids/mm-0.pid     │
│ interpreter       │ bash                            │
│ interpreter args  │ N/A                             │
│ script id         │ 0                               │
│ exec cwd          │ /home/pi                        │
│ exec mode         │ fork_mode                       │
│ node.js version   │ N/A                             │
│ node env          │ N/A                             │
│ watch & reload    │ ✘                               │
│ unstable restarts │ 0                               │
│ created at        │ 2023-06-28T02:47:15.904Z

I tried putting the command in /home/pi/mm.sh but it’s not working.