Although my original issue wasn’t identified, I am happy with the new module information provided by mumblebaj. It appears to be stable and the updates are continuing to work. I think we can close this one. Thanks!

@mumblebaj
I installed the module and it looks good! I will continue to monitor for the next while to see if the updates continue to work. Thanks!

@mumblebaj
Wow! That looks like just what I would need… What module is that? I thought that sticking to the default modules would be advantageous but maybe that is a better solution.

I seem to be having an intermittent problem with getting weather updates. I am using the default weather module, and I am aware of the issues with using some of the different providers. But I have read that using the Pirate Weather API would work. I have configured my MM to display both the current weather conditions and a second display of the weekly forecast. Initially, everything works as expected. But eventually, either my current weather display OR my weekly forecast will stop providing updated information. Whenever I reboot/restart my MM, the problem is resolved and I get the correct information.

I understand that Pirate Weather allows 10,000 API calls per month. I set the first update interval to 600,000 (every 10 minutes) and the second one to 1,800,000 (every half hour). I assume this results in 8 calls per hour or just under 6,000 calls per month. So, I don’t believe that I am exceeding the call limitation. Also, the fact that a reboot will fix the problem would indicate that this is not a call limitation issue.

I have read that others have run into problems which they resolved by offsetting the times when the call requests are sent by adjusting the ‘initialLoadDelay’ value. I have set that value to ‘5000’ on my second display (value not set on the first display).

I set my MM to restart every week (via crontab) so I can get an idea if the problem re-occurs at a specific point. I attempt to monitor the uptime whenever I see the problem. It doesn’t seem to have a pattern. It can fail after two days, or three days, four days, etc. Sometimes, it will work for the entire week, and my MM will restart and reset the uptime clock.

The failure can appear on the current conditions (ie. the displayed temperature is ‘stuck’ at the same value for days), or it can appear on the weekly forecast (ie. the days of the week will not change). It seems to be random. I know that if I just wait a few days, it will get resolved on its own, but I would prefer to get an idea on how to fix this so that the display is correct all the time. Any ideas?

Thanks in advance.

	  {
module: "weather",
position: "top_right",
config: {
  type: "current",
  weatherProvider: "pirateweather",
  apiBase: "https://api.pirateweather.net",
  weatherEndpoint: "/forecast",
  apiKey: "my API key",
  lat: "my latitude",
  lon: "my longitude",
  tableClass: "medium",
  colored: "true",
  fadePoint: "0.50",
  maxNumberOfDays: "1",
  updateInterval: "600000",
  degreeLabel: "true"
},

},

	{
module: "weather",
position: "top_right",
config: {
  type: "forecast",
  Header: "true",
  appendLocationNameToHeader: "true",
  weatherProvider: "pirateweather",
  apiBase: "https://api.pirateweather.net",
  weatherEndpoint: "/forecast",
  apiKey: "my API key",
  lat: "my latitude",
  lon: "my longitude",
  tableClass: "small",
  colored: "true",
  fadePoint: "0.50",
  maxNumberOfDays: "7",
  updateInterval: "1800000",
  degreeLabel: "true",
  initialLoadDelay: "5000"
},

},

Ah, yes. That was it. Instead of manually making the changes, I just copied the entire code and pasted. Seems to work now. Thanks!

I don’t believe that I am using pm2. Here are the logs when MM starts:

magicmirror@2.27.0 start
DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js

[2024-05-03 16:04:55.886] [LOG] Starting MagicMirror: v2.27.0
[2024-05-03 16:04:55.935] [LOG] Loading config …
[2024-05-03 16:04:55.938] [LOG] config template file not exists, no envsubst
[2024-05-03 16:04:55.957] [LOG] Loading module helpers …
[2024-05-03 16:04:55.958] [LOG] No helper found for module: alert.
[2024-05-03 16:04:56.237] [LOG] Initializing new module helper …
[2024-05-03 16:04:56.239] [LOG] Module helper loaded: updatenotification
[2024-05-03 16:04:56.240] [LOG] No helper found for module: clock.
[2024-05-03 16:04:56.402] [LOG] Initializing new module helper …
[2024-05-03 16:04:56.403] [LOG] Module helper loaded: MMM-MyCalendar
[2024-05-03 16:04:56.403] [LOG] No helper found for module: calendar_monthly.
[2024-05-03 16:04:56.414] [LOG] Initializing new module helper …
[2024-05-03 16:04:56.414] [LOG] Module helper loaded: MMM-Pir
[2024-05-03 16:04:56.462] [LOG] Initializing new module helper …
[2024-05-03 16:04:56.462] [LOG] Module helper loaded: MMM-Weather
[2024-05-03 16:04:56.543] [LOG] Initializing new module helper …
[2024-05-03 16:04:56.544] [LOG] Module helper loaded: MMM-Tools
[2024-05-03 16:04:56.673] [LOG] Initializing new module helper …
[2024-05-03 16:04:56.674] [LOG] Module helper loaded: newsfeed
[2024-05-03 16:04:56.674] [LOG] All module helpers loaded.
[2024-05-03 16:04:56.685] [LOG] Starting server on port 8080 …
[2024-05-03 16:04:58.244] [LOG] Server started …
[2024-05-03 16:04:58.247] [LOG] Connecting socket for: updatenotification
[2024-05-03 16:04:58.248] [LOG] Starting module helper: updatenotification
[2024-05-03 16:04:58.250] [LOG] Connecting socket for: MMM-MyCalendar
[2024-05-03 16:04:58.261] [LOG] Starting node helper for: MMM-MyCalendar
[2024-05-03 16:04:58.262] [LOG] Connecting socket for: MMM-Pir
[2024-05-03 16:04:58.264] [LOG] Connecting socket for: MMM-Weather
[2024-05-03 16:04:58.272] [LOG] Connecting socket for: MMM-Tools
[2024-05-03 16:04:58.284] [LOG] [Tools] MMM-Tools Version: 2.1.7
[2024-05-03 16:04:58.286] [LOG] Connecting socket for: newsfeed
[2024-05-03 16:04:58.287] [LOG] Starting node helper for: newsfeed
[2024-05-03 16:04:58.288] [LOG] Sockets connected & modules started …
WARNING: v3dv is neither a complete nor a conformant Vulkan implementation. Testing use only.
[2024-05-03 16:04:58.891] [LOG] Launching application.
[2024-05-03 16:05:02.661] [LOG] Create new calendarfetcher for url: http://www.calendarlabs.com/ical-calendar/ics/39/Canada_Holidays.ics - Interval: 300000
[2024-05-03 16:05:02.668] [ERROR] Whoops! There was an uncaught exception…
[2024-05-03 16:05:02.677] [ERROR] ReferenceError: fetcher is not defined
at fetchCalendar (/home/pi/MagicMirror/modules/MMM-MyCalendar/calendarfetcher.js:65:3)
at CalendarFetcher.startFetch (/home/pi/MagicMirror/modules/MMM-MyCalendar/calendarfetcher.js:110:3)
at Class.createFetcher (/home/pi/MagicMirror/modules/MMM-MyCalendar/node_helper.js:73:11)
at Class.socketNotificationReceived (/home/pi/MagicMirror/modules/MMM-MyCalendar/node_helper.js:21:9)
at Socket. (/home/pi/MagicMirror/js/node_helper.js:98:11)
at Socket.emit (node:events:514:28)
at Socket.emitUntyped (/home/pi/MagicMirror/node_modules/socket.io/dist/typed-events.js:69:22)
at /home/pi/MagicMirror/node_modules/socket.io/dist/socket.js:704:39
at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
[2024-05-03 16:05:02.680] [ERROR] MagicMirror² will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
[2024-05-03 16:05:02.684] [ERROR] If you think this really is an issue, please open an issue on GitHub: https://github.com/MagicMirrorOrg/MagicMirror/issues
[2024-05-03 16:05:02.686] [LOG] Create new calendarfetcher for url: https://calendar.google.com/calendar/ical/5u47rliikveghncls65jrsotkc%40group.calendar.google.com/private-7c6a117f2ae0d357b447c735373245a2/basic.ics - Interval: 300000
[2024-05-03 16:05:02.688] [ERROR] Whoops! There was an uncaught exception…
[2024-05-03 16:05:02.689] [ERROR] ReferenceError: fetcher is not defined
at fetchCalendar (/home/pi/MagicMirror/modules/MMM-MyCalendar/calendarfetcher.js:65:3)
at CalendarFetcher.startFetch (/home/pi/MagicMirror/modules/MMM-MyCalendar/calendarfetcher.js:110:3)
at Class.createFetcher (/home/pi/MagicMirror/modules/MMM-MyCalendar/node_helper.js:73:11)
at Class.socketNotificationReceived (/home/pi/MagicMirror/modules/MMM-MyCalendar/node_helper.js:21:9)
at Socket. (/home/pi/MagicMirror/js/node_helper.js:98:11)
at Socket.emit (node:events:514:28)
at Socket.emitUntyped (/home/pi/MagicMirror/node_modules/socket.io/dist/typed-events.js:69:22)
at /home/pi/MagicMirror/node_modules/socket.io/dist/socket.js:704:39
at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
[2024-05-03 16:05:02.690] [ERROR] MagicMirror² will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
[2024-05-03 16:05:02.690] [ERROR] If you think this really is an issue, please open an issue on GitHub: https://github.com/MagicMirrorOrg/MagicMirror/issues
[2024-05-03 16:05:02.790] [LOG] Create new newsfetcher for url: https://rss.cbc.ca/lineup/canada.xml - Interval: 300000
[2024-05-03 16:05:03.039] [LOG] Create new newsfetcher for url: https://rss.cbc.ca/lineup/canada-toronto.xml - Interval: 300000
[2024-05-03 16:05:03.052] [LOG] Create new newsfetcher for url: https://rss.cbc.ca/lineup/sports-nhl.xml - Interval: 300000
[2024-05-03 16:05:03.071] [LOG] [WEATHER] MMM-WEATHER Version: 1.0.6
[2024-05-03 16:05:03.112] [LOG] [MMM-Pir] Version: 1.5.1 rev: 240402
[2024-05-03 16:05:03.114] [LOG] [MMM-Pir] [LIB] [PIR] Mode 0 Selected (onoff library)
[2024-05-03 16:05:03.168] [LOG] [MMM-Pir] [LIB] [PIR] Started!
[2024-05-03 16:05:03.172] [LOG] [MMM-Pir] [LIB] [SCREEN] Mode 4: HDMI CEC
[2024-05-03 16:05:03.228] [LOG] [MMM-Pir] Started!
[2024-05-03 16:05:03.231] [INFO] updatenotification: Updater Class Loaded!
[2024-05-03 16:05:03.233] [INFO] updatenotification: Checking PM2 using…
[2024-05-03 16:05:03.239] [INFO] Checking git for module: MMM-MyCalendar
[2024-05-03 16:05:03.375] [INFO] Checking git for module: calendar_monthly
[2024-05-03 16:05:03.478] [INFO] System information:

SYSTEM: manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 4 Model B Rev 1.4; raspberry: [object Object]; virtual: false

OS: platform: linux; distro: Raspbian GNU/Linux; release: 11; arch: arm; kernel: 5.10.103-v7l+

VERSIONS: electron: 29.1.6; used node: 20.9.0; installed node: 20.4.0; npm: 9.8.1; pm2: 5.3.1

OTHER: timeZone: America/Toronto; ELECTRON_ENABLE_GPU: undefined

[2024-05-03 16:05:03.529] [INFO] Checking git for module: MMM-Pir
[2024-05-03 16:05:03.687] [INFO] updatenotification: [PM2] You are not using pm2
[2024-05-03 16:05:04.116] [INFO] Checking git for module: MMM-Weather
[2024-05-03 16:05:04.566] [INFO] Checking git for module: MMM-Tools
[2024-05-03 16:05:04.708] [INFO] Newsfeed-Fetcher: Broadcasting 18 items.
[2024-05-03 16:05:04.809] [INFO] Checking git for module: MagicMirror
[2024-05-03 16:05:04.861] [INFO] Newsfeed-Fetcher: Broadcasting 20 items.
[2024-05-03 16:05:04.874] [INFO] Newsfeed-Fetcher: Broadcasting 19 items.
[2024-05-03 16:05:14.810] [LOG] Shutting down server…
[2024-05-03 16:05:14.812] [LOG] Stopping module helper: updatenotification
[2024-05-03 16:05:14.813] [LOG] Stopping module helper: MMM-MyCalendar
[2024-05-03 16:05:14.813] [LOG] Stopping module helper: MMM-Pir
[2024-05-03 16:05:14.814] [LOG] Stopping module helper: MMM-Weather
[2024-05-03 16:05:14.814] [LOG] Stopping module helper: MMM-Tools
[2024-05-03 16:05:14.815] [LOG] Stopping module helper: newsfeed
[2024-05-03 16:05:14.816] [LOG] Node_helpers stopped …
[2024-05-03 16:05:14.891] [LOG] [MMM-Pir] [LIB] [SCREEN] See you soon !
[2024-05-03 16:05:14.893] [LOG] [MMM-Pir] [LIB] [SCREEN] @bugsounet

Not sure what happened here… You indicate that this issue is solved…? I still don’t have a calendar yet. MM launches now, but I only have an indication that the calendar is “Loading…” but it never appears.

I am running MM version 2.27.0, node v20.4, npm v9.8.1

I read that post already, which allowed me to get the MM running again. I just commented out the lines indicated.

I’ve been using the default calendar module for awhile now, and living with the incorrect date for one of my recurring events. Specifically, my event occurs on the first Thursday of each month, and the calendar seems to show the correct date for the first occurrence, but all subsequent occurrences seem to happen on the first Wednesday of each month — one day early.

I understand that one solution may be to use the MMM-MyCalendar module instead. I attempted this and discovered that my MM wouldn’t launch, and attempted a workaround shown here:

https://github.com/jclarke0000/MMM-MyCalendar/issues/40

As others have reported, MM will now launch, but the calendar never appears (always indicates ‘loading’). I can put back the original calendar module, and just live with the problem, but does anyone have any other suggestions? Thanks.

@karsten13

Success! I ran the following command:

npm install node-fetch@2

… and now it’s back up and running again! Thanks for the quick response!

@sdetweil

Ok. I went to my /home/pi/MagicMirror/modules/MMM-Weather/ folder and I ran the ‘npm install node-fetch’ command. I am getting a different error now:

pi@raspberrypi:~/MagicMirror $ npm run start

magicmirror@2.25.0 start
DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js

[03.10.2023 16:57.03.945] [LOG] Starting MagicMirror: v2.25.0
[03.10.2023 16:57.03.956] [LOG] Loading config …
[03.10.2023 16:57.03.958] [DEBUG] config template file not exists, no envsubst
[03.10.2023 16:57.03.962] [LOG] Loading module helpers …
[03.10.2023 16:57.03.964] [LOG] No helper found for module: alert.
[03.10.2023 16:57.03.998] [LOG] Initializing new module helper …
[03.10.2023 16:57.04.001] [LOG] Module helper loaded: updatenotification
[03.10.2023 16:57.04.004] [LOG] No helper found for module: clock.
[03.10.2023 16:57.04.238] [LOG] Initializing new module helper …
[03.10.2023 16:57.04.239] [LOG] Module helper loaded: calendar
[03.10.2023 16:57.04.240] [LOG] No helper found for module: calendar_monthly.
[03.10.2023 16:57.04.244] [LOG] Initializing new module helper …
[03.10.2023 16:57.04.245] [LOG] Module helper loaded: MMM-Pir
[03.10.2023 16:57.04.342] [ERROR] (node:3203) UnhandledPromiseRejectionWarning: Error [ERR_REQUIRE_ESM]: require() of ES Module /home/pi/MagicMirror/modules/MMM-Weather/node_modules/node-fetch/src/index.js from /home/pi/MagicMirror/modules/MMM-Weather/node_helper.js not supported.
Instead change the require of index.js in /home/pi/MagicMirror/modules/MMM-Weather/node_helper.js to a dynamic import() which is available in all CommonJS modules.
at Function._load (node:electron/js2c/asar_bundle:2:13327)
at Object. (/home/pi/MagicMirror/modules/MMM-Weather/node_helper.js:11:15)
at Function._load (node:electron/js2c/asar_bundle:2:13327)
at loadModule (/home/pi/MagicMirror/js/app.js:180:19)
at loadModules (/home/pi/MagicMirror/js/app.js:210:10)
at async App.start (/home/pi/MagicMirror/js/app.js:258:3)
(Use electron --trace-warnings ... to show where the warning was created)
[03.10.2023 16:57.04.342] [ERROR] (node:3203) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
WARNING: v3dv is neither a complete nor a conformant Vulkan implementation. Testing use only.
[3203:1003/165705.081300:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: org.freedesktop.portal.Error.NotFound: Requested setting not found
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
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/arm-linux-gnueabihf/dri:$${ORIGIN}/dri:/usr/lib/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/arm-linux-gnueabihf/dri:$${ORIGIN}/dri:/usr/lib/dri)
failed to load swrast driver

@sdetweil
Thanks for the reply… I’ve gone to my MagicMirror/modules folder, and I can confirm that there is no module called ‘node-fetch’. Your post indicates that to fix this, the library needs to be installed in the module folder. The procedure continues to indicate that I need to change directories to the module that is having the problem… but it doesn’t exist…? Am I reading this correctly?

I just attempted to update to the latest version of Magic Mirror, and now I can’t get it to start… Can anyone provide any suggestions? Here is what I am seeing now:

pi@raspberrypi:~/MagicMirror $ npm run start

magicmirror@2.25.0 start
DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js

[03.10.2023 12:06.38.811] [LOG] Starting MagicMirror: v2.25.0
[03.10.2023 12:06.38.822] [LOG] Loading config …
[03.10.2023 12:06.38.825] [DEBUG] config template file not exists, no envsubst
[03.10.2023 12:06.38.829] [LOG] Loading module helpers …
[03.10.2023 12:06.38.831] [LOG] No helper found for module: alert.
[03.10.2023 12:06.38.868] [LOG] Initializing new module helper …
[03.10.2023 12:06.38.870] [LOG] Module helper loaded: updatenotification
[03.10.2023 12:06.38.871] [LOG] No helper found for module: clock.
[03.10.2023 12:06.39.093] [LOG] Initializing new module helper …
[03.10.2023 12:06.39.094] [LOG] Module helper loaded: calendar
[03.10.2023 12:06.39.095] [LOG] No helper found for module: calendar_monthly.
[03.10.2023 12:06.39.099] [LOG] Initializing new module helper …
[03.10.2023 12:06.39.100] [LOG] Module helper loaded: MMM-Pir
[03.10.2023 12:06.39.104] [ERROR] (node:2935) UnhandledPromiseRejectionWarning: Error: Cannot find module ‘node-fetch’
Require stack:

• /home/pi/MagicMirror/modules/MMM-Weather/node_helper.js
• /home/pi/MagicMirror/js/app.js
• /home/pi/MagicMirror/js/electron.js
• /home/pi/MagicMirror/node_modules/electron/dist/resources/default_app.asar/main.js
• at node:internal/modules/cjs/loader:1084:15
  at Function. (node:electron/js2c/browser_init:2:117419)
  at Module._resolveFilename (/home/pi/MagicMirror/node_modules/module-alias/index.js:49:29)
  at node:internal/modules/cjs/loader:929:27
  at Function._load (node:electron/js2c/asar_bundle:2:13327)
  at Module.require (node:internal/modules/cjs/loader:1150:19)
  at require (node:internal/modules/cjs/helpers:110:18)
  at Object. (/home/pi/MagicMirror/modules/MMM-Weather/node_helper.js:11:15)
  at Module._compile (node:internal/modules/cjs/loader:1271:14)
  at Object…js (node:internal/modules/cjs/loader:1326:10)
  at Module.load (node:internal/modules/cjs/loader:1126:32)
  at node:internal/modules/cjs/loader:967:12
  at Function._load (node:electron/js2c/asar_bundle:2:13327)
  at Module.require (node:internal/modules/cjs/loader:1150:19)
  at require (node:internal/modules/cjs/helpers:110:18)
  at loadModule (/home/pi/MagicMirror/js/app.js:180:19)
  (Use electron --trace-warnings ... to show where the warning was created)
  [03.10.2023 12:06.39.104] [ERROR] (node:2935) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
  WARNING: v3dv is neither a complete nor a conformant Vulkan implementation. Testing use only.
  [2935:1003/120639.849727:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: org.freedesktop.portal.Error.NotFound: Requested setting not found
  MESA-LOADER: failed to retrieve device information
  MESA-LOADER: failed to retrieve device information
  MESA-LOADER: failed to retrieve device information
  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/arm-linux-gnueabihf/dri:$${ORIGIN}/dri:/usr/lib/dri)
  failed to load driver: kms_swrast
  MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/arm-linux-gnueabihf/dri:$${ORIGIN}/dri:/usr/lib/dri)
  failed to load swrast driver

…and it just sits there… Can anyone help me to decipher these messages? Thanks…

Beautiful. That solved the issue. Thanks for the quick response.

I recently attempted to perform an update for the MMM-Pir module and it didn’t seem to work. I attempted the ‘npm run rebuild’ command, and now I am getting the following error message:
FATAL: 1 needed library not loaded
Here is what I am seeing when I attempt the rebuild:

pi@raspberrypi:~/MagicMirror/modules/MMM-Pir $ npm run rebuild

MMM-Pir@1.0.1 rebuild
installer/rebuild.sh

Welcome to MMM-Pir rebuild script
This script will erase current build and reinstall it
Do you want to continue ? [Y/n]
Your choice: Y

Deleting: package-lock.json node_modules
Done.

Upgrading EXT-Pir…
HEAD is now at 97f6cc8 update for vulnerabilities security // add node v16.14.0 min requirement
hint: Pulling without specifying how to reconcile divergent branches is
hint: discouraged. You can squelch this message by running one of the following
hint: commands sometime before your next pull:
hint:
hint: git config pull.rebase false # merge (the default strategy)
hint: git config pull.rebase true # rebase
hint: git config pull.ff only # fast-forward only
hint:
hint: You can replace “git config” with “git config --global” to set a default
hint: preference for all repositories. You can also pass --rebase, --no-rebase,
hint: or --ff-only on the command line to override the configured default per
hint: invocation.
Already up to date.
Done.
Reinstalling MMM-Pir…
npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: @npmcli/fs@3.1.0
npm ERR! notsup Not compatible with your version of node/npm: @npmcli/fs@3.1.0
npm ERR! notsup Required: {“node”:“^14.17.0 || ^16.13.0 || >=18.0.0”}
npm ERR! notsup Actual: {“npm”:“8.5.5”,“node”:“v17.9.0”}

npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2023-07-11T23_00_51_522Z-debug-0.log
pi@raspberrypi:~/MagicMirror/modules/MMM-Pir $

What am I missing, and how can I fix this? Thanks in advance…

solution posted here:

https://forum.magicmirror.builders/topic/17813/mmm-pir-sensor-lite-modification/22

Terrific! I just installed MMM-Pir and it works properly as before. I am using mode 4 (HDMI CEC) and the monitor responds as expected. Thanks very much for the quick response! You guys are a real credit to this open source project!

I assume that I would need to re-configure the MMM-PIR-Sensor-Lite module to prevent the command from turning OFF the HDMI. How do I do that?

As I dig more into this, I am finding that there seem to be a lot of reports that some LG monitors do not support using the Standby command. I am not certain of how this was working before, but now I am beginning to suspect that the Magic Mirror app simply went hidden when the timeout occurred. Perhaps the monitor was ON all along, but the app disappeared from the screen? I don’t know if this applies in my situation, because I can’t seem to make any of the CEC commands work at all.

I attempted to turn OFF the monitor, and then issue the CEC ON command, but that also did not work. It appears to be some fundamental issue with the CEC commands that I may not be able to use. Are you aware of any modules that simply blackout the Magic Mirror app using the PIR sensor? I know that isn’t really saving as much energy, but it might be worthwhile implementing…

Here is the last portion of the debug log when I attempt to issue the standby command:

WARNING: [ 3123] FIXME: LG seems to have bugged out. resetting to ‘in transition standby to on’. the return button will not work
DEBUG: [ 3123] Recorder 1 (1): power status changed from ‘on’ to ‘in transition from standby to on’
DEBUG: [ 3123] << Recorder 1 (1) -> TV (0): in transition from standby to on
TRAFFIC: [ 3123] << 10:90:02
DEBUG: [ 3123] >> TV (0) -> Recorder 1 (1): give device power status (8F)
DEBUG: [ 3175] expected response not received (90: report power status)
DEBUG: [ 3189] CLinuxCECAdapterCommunication::Process - ioctl CEC_RECEIVE - rx_status=01 len=2 addr=01 opcode=46
DEBUG: [ 3276] CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT - tx_status=01 len=3 addr=10 opcode=90
TRAFFIC: [ 3276] << 10:8f
DEBUG: [ 3276] Recorder 1 (1): power status changed from ‘in transition from standby to on’ to ‘on’
DEBUG: [ 3366] CLinuxCECAdapterCommunication::Process - ioctl CEC_RECEIVE - rx_status=01 len=3 addr=01 opcode=89
DEBUG: [ 3428] CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT - tx_status=01 len=2 addr=10 opcode=8f
TRAFFIC: [ 3429] >> 01:90:00
DEBUG: [ 3429] TV (0): power status changed from ‘unknown’ to ‘on’
DEBUG: [ 3429] expected response received (90: report power status)
DEBUG: [ 3429] >> TV (0) -> Recorder 1 (1): report power status (90)
NOTICE: [ 3429] << putting ‘TV’ (0) in standby mode
TRAFFIC: [ 3429] << 10:36
TRAFFIC: [ 3429] >> 01:1a:01
DEBUG: [ 3429] >> TV (0) -> Recorder 1 (1): give deck status (1A)
DEBUG: [ 3494] CLinuxCECAdapterCommunication::Process - ioctl CEC_RECEIVE - rx_status=01 len=2 addr=01 opcode=46
DEBUG: [ 3557] CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT - tx_status=01 len=2 addr=10 opcode=36
DEBUG: [ 3557] unregistering all CEC clients
NOTICE: [ 3557] unregistering client: libCEC version = 6.0.2, client version = 6.0.2, firmware version = 0, logical address(es) = Recorder 1 (1) , physical address: 1.0.0.0, compiled on Linux-5.10.63-v8+ … , features: P8_USB, DRM, P8_detect, randr, RPi, Exynos, Linux, AOCEC
DEBUG: [ 3557] Recorder 1 (1): power status changed from ‘on’ to ‘unknown’
DEBUG: [ 3557] Recorder 1 (1): vendor = Unknown (000000)
DEBUG: [ 3557] Recorder 1 (1): CEC version unknown
DEBUG: [ 3557] Recorder 1 (1): osd name set to ‘Recorder 1’
DEBUG: [ 3557] Recorder 1 (1): device status changed into ‘unknown’
DEBUG: [ 3557] CLinuxCECAdapterCommunication::SetLogicalAddresses - ioctl CEC_ADAP_S_LOG_ADDRS - log_addr_mask=0000 num_log_addrs=0
DEBUG: [ 3557] CLinuxCECAdapterCommunication::SetLogicalAddresses - ioctl CEC_ADAP_S_LOG_ADDRS - log_addr_mask=0000 num_log_addrs=0
DEBUG: [ 3557] unregistering all CEC clients
TRAFFIC: [ 3557] >> 01:46
DEBUG: [ 3558] CLinuxCECAdapterCommunication::SetLogicalAddresses - ioctl CEC_ADAP_S_LOG_ADDRS - log_addr_mask=0000 num_log_addrs=0
TRAFFIC: [ 3558] >> 01:89:01
TRAFFIC: [ 3558] >> 01:46
DEBUG: [ 3558] CLinuxCECAdapterCommunication::Process - CEC_DQEVENT - CEC_EVENT_STATE_CHANGE - log_addr_mask=0000 phys_addr=1000
DEBUG: [ 3558] >> TV (0) -> Recorder 1 (1): give osd name (46)
DEBUG: [ 3558] >> TV (0) -> Recorder 1 (1): vendor command (89)
DEBUG: [ 3558] >> TV (0) -> Recorder 1 (1): give osd name (46)
DEBUG: [ 4564] CLinuxCECAdapterCommunication::Process - stopped - m_path=/dev/cec0 m_fd=4
DEBUG: [ 4564] CLinuxCECAdapterCommunication::Close - m_path=/dev/cec0 m_fd=4

This seems to indicate that it will not take the command, and returns the monitor to the ON state. But I don’t know where to look next…