PIR problem RPi 4B, Bullseye 64 bit

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

[sdetweil]

@wyovino maybe python needs some path info, env setup

[wyovino]

@sdetweil It’s running the program but the commands to control the monitor are ignored, The program is logging the activity. Here is the scenario that works:

Boot the Pi
Connect via SSH and issue command “pm2 stop mm”
Connect directly to the Pi using a connected keyboard and start my PIR program, then enter “pm2 start mm”

This works but is obviously inconvenient as I need to have a keyboard connected to the Magic Mirror. I’m going to see if I can run my program from crontab under the “pi” account. Maybe that’s the issue.

[sdetweil]

@wyovino what do the pm2 logs show?

stop mm via pm2
pm2 stop all
pm2 flush – clear old logs

pm2 start 0

pm2 logs --lines=50

[wyovino]

@sdetweil
pm2 logs --lines=50
[TAILING] Tailing last 50 lines for [all] processes (change the value with --lines option)
/home/pi/.pm2/pm2.log last 50 lines:
PM2 | 2023-07-06T10:26:31: PM2 log: App [mm:0] starting in -fork mode-
PM2 | 2023-07-06T10:26:31: PM2 log: App [mm:0] online

/home/pi/.pm2/logs/mm-out.log last 50 lines:
0|mm |
0|mm | > magicmirror@2.23.0 start
0|mm | > DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js
0|mm |
0|mm | [06.07.2023 10:26.34.272] [LOG] Starting MagicMirror: v2.23.0
0|mm | [06.07.2023 10:26.34.280] [LOG] Loading config …
0|mm | [06.07.2023 10:26.34.284] [DEBUG] config template file not exists, no envsubst
0|mm | [06.07.2023 10:26.34.290] [LOG] Loading module helpers …
0|mm | [06.07.2023 10:26.34.292] [LOG] No helper found for module: alert.
0|mm | [06.07.2023 10:26.34.309] [LOG] Initializing new module helper …
0|mm | [06.07.2023 10:26.34.310] [LOG] Module helper loaded: updatenotification
0|mm | [06.07.2023 10:26.34.311] [LOG] No helper found for module: clock.
0|mm | [06.07.2023 10:26.34.318] [LOG] Initializing new module helper …
0|mm | [06.07.2023 10:26.34.319] [LOG] Module helper loaded: MMM-MyScoreboard
0|mm | [06.07.2023 10:26.34.550] [LOG] Initializing new module helper …
0|mm | [06.07.2023 10:26.34.553] [LOG] Module helper loaded: calendar
0|mm | [06.07.2023 10:26.34.555] [LOG] No helper found for module: weather.
0|mm | [06.07.2023 10:26.34.592] [LOG] Initializing new module helper …
0|mm | [06.07.2023 10:26.34.593] [LOG] Module helper loaded: newsfeed
0|mm | [06.07.2023 10:26.35.237] [LOG] Initializing new module helper …
0|mm | [06.07.2023 10:26.35.238] [LOG] Module helper loaded: MMM-Jast
0|mm | [06.07.2023 10:26.35.238] [LOG] All module helpers loaded.
0|mm | [06.07.2023 10:26.35.252] [LOG] Starting server on port 8080 …
0|mm | [06.07.2023 10:26.35.462] [LOG] Server started …
0|mm | [06.07.2023 10:26.35.463] [LOG] Connecting socket for: updatenotification
0|mm | [06.07.2023 10:26.35.466] [LOG] Starting module helper: updatenotification
0|mm | [06.07.2023 10:26.35.467] [LOG] Connecting socket for: MMM-MyScoreboard
0|mm | [06.07.2023 10:26.35.468] [LOG] Starting node_helper for module [MMM-MyScoreboard]
0|mm | [06.07.2023 10:26.35.831] [LOG] Connecting socket for: calendar
0|mm | [06.07.2023 10:26.35.831] [LOG] Starting node helper for: calendar
0|mm | [06.07.2023 10:26.35.832] [LOG] Connecting socket for: newsfeed
0|mm | [06.07.2023 10:26.35.833] [LOG] Starting node helper for: newsfeed
0|mm | [06.07.2023 10:26.35.834] [LOG] Connecting socket for: MMM-Jast
0|mm | [06.07.2023 10:26.35.834] [LOG] MMM-Jast helper method started…
0|mm | [06.07.2023 10:26.35.836] [LOG] Sockets connected & modules started …
0|mm | [06.07.2023 10:26.35.876] [LOG] Launching application.
0|mm | [06.07.2023 10:26.38.724] [LOG] Create new calendarfetcher for url: https://calendar.google.com/calendar/ical/wyovino%40gmail.com/private-b71db2843aaff911c63405db3b5da429/basic.ics - Interval: 300000
0|mm | [06.07.2023 10:26.38.762] [LOG] Create new newsfetcher for url: https://www.yahoo.com/news/rss - Interval: 300000
0|mm | [06.07.2023 10:26.38.769] [LOG] Create new newsfetcher for url: https://www.mlb.com/mets/feeds/news/rss.xml?_gl=1*1hyw7gs*_gcl_au*MTM2MjI0OTI5My4xNjgyMzQ1ODU3 - Interval: 300000
0|mm | [06.07.2023 10:26.38.773] [LOG] Create new newsfetcher for url: https://api.foxsports.com/v2/content/optimized-rss?partnerKey=MB0Wehpmuj2lUhuRhQaafhBjAJqaPU244mlTDK1i&aggregateId=7f83e8ca-6701-5ea0-96ee-072636b67336 - Interval: 300000
0|mm | [06.07.2023 10:26.40.378] [INFO] Newsfeed-Fetcher: Broadcasting 50 items.
0|mm | [06.07.2023 10:26.40.491] [INFO] Newsfeed-Fetcher: reloadInterval set to ttl=10800000 for url https://api.foxsports.com/v2/content/optimized-rss?partnerKey=MB0Wehpmuj2lUhuRhQaafhBjAJqaPU244mlTDK1i&aggregateId=7f83e8ca-6701-5ea0-96ee-072636b67336
0|mm | [06.07.2023 10:26.40.517] [INFO] Newsfeed-Fetcher: Broadcasting 25 items.
0|mm | [06.07.2023 10:26.40.779] [INFO] Checking git for module: MMM-MyScoreboard
0|mm | [06.07.2023 10:26.40.846] [INFO] Newsfeed-Fetcher: Broadcasting 75 items.
0|mm | [06.07.2023 10:26.40.861] [INFO] Checking git for module: MMM-Jast
0|mm | [06.07.2023 10:26.40.891] [INFO] Checking git for module: MagicMirror
0|mm | [06.07.2023 10:26.41.016] [INFO] Calendar-Fetcher: Broadcasting 1 events.

/home/pi/.pm2/logs/mm-error.log last 50 lines:
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to open kms_swrast: /usr/lib/dri/kms_swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/aarch64-linux-gnu/dri:$${ORIGIN}/dri:/usr/lib/dri)
0|mm | failed to load driver: kms_swrast
0|mm | MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/aarch64-linux-gnu/dri:$${ORIGIN}/dri:/usr/lib/dri)
0|mm | failed to load swrast driver
0|mm | [06.07.2023 10:26.41.236] [WARN] API request for IXIC failed: Quote not found for ticker symbol: IXIC
0|mm | [06.07.2023 10:26.43.980] [ERROR] Failed to retrieve repo info for MagicMirror: Error: Command failed: cd /home/pi/MagicMirror/ && git fetch -n --dry-run
0|mm | error: object file .git/objects/94/aeda9d76a88f9691fbebf7f4f50a39887c626e is empty
0|mm | fatal: loose object 94aeda9d76a88f9691fbebf7f4f50a39887c626e (stored in .git/objects/94/aeda9d76a88f9691fbebf7f4f50a39887c626e) is corrupt
0|mm | fatal: unpack-objects failed
0|mm |

[wyovino]

@sdetweil I appreciate your help in this as it’s obvious this is an environmental issue, not a Magic Mirror issue.

[sdetweil]

@wyovino I don’t see anything related to python there

to get rid of the mesa errors, add

export ELRCTRON_DISABLE_GPU=1

in the mm.sh in front of the npm start

[htilburgs]

I had issues that look the same. After a system crash (defect SD card after 6 years) I could fallback on a backup, but I decided to do a fresh install wih the latest rPi OS. After that my PIR didn’t function anymore. Screen didn’t went of and back on again.

In my case the solution to put the GL driver back to legacy.

• sudo raspi-config
• advanced options
• GL driver
• Legacy

After that my Python script and the PIR worked as they should.p

[wyovino]

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

I had issues that look the same. After a system crash (defect SD card after 6 years) I could fallback on a backup, but I decided to do a fresh install wih the latest rPi OS. After that my PIR didn’t function anymore. Screen didn’t went of and back on again.

In my case the solution to put the GL driver back to legacy.

• sudo raspi-config
• advanced options
• GL driver
• Legacy

After that my Python script and the PIR worked as they should.p

Interesting. Are you using the MMM-PIR-Sensor module?

[htilburgs]

@wyovino No, I’m not using MMM-PIR.
I’ve documented it on my website, but it is in Dutch ;-)

https://magicmirror.tilburgs.com/pir-configuratie/

[sdetweil]

@htilburgs easy to translate these days

nice write up

[wyovino]

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

I had issues that look the same. After a system crash (defect SD card after 6 years) I could fallback on a backup, but I decided to do a fresh install wih the latest rPi OS. After that my PIR didn’t function anymore. Screen didn’t went of and back on again.

In my case the solution to put the GL driver back to legacy.

• sudo raspi-config
• advanced options
• GL driver
• Legacy

After that my Python script and the PIR worked as they should.p

My Advanced Options menu doesn’t contain a reference to GL Driver

[wyovino]

Update. I started fresh with Buster instead of Bullseye and followed these instructions to get MMM-PIR-SENSOR working.

https://www.reddit.com/r/MagicMirror/comments/u1eq9u/problem_setting_up_pirsensor_with_magicmirror/