I’ve had Magic Mirror running on a Pi Zero 2W for about 8 months and it is behind a few versions. I tried to update to the latest version but get the 'Unsupported engine" NodeJs and NPM version error.
As far as I’ve seen, newer versions of NodeJs don’t support the Zero 2. Is that true? Is there a workaround so I can update my Mirror?
I’d like to increase the size of the start time for an upcoming game. Which element in the CSS file would that be?
@nnvv3344 Unfortunately, the module MMM-Jast requires Node above 18, so I can do that.
I can no longer edit this post so here is some additional information.
I removed the config line that requests stock “AAPL” but all of the error messages still show unable to retrieve AAPL. Also note that all modules before and after MMM-JAST in the config file are working fine.
[15.06.2024 21:29.13.803] [WARN] API request for ^DJI failed: Unsupported redirect to https://finance.yahoo.com/quote/AAPL/, please report.
[15.06.2024 21:29.13.806] [WARN] API request for ^IXIC failed: Unsupported redirect to https://finance.yahoo.com/quote/AAPL/, please report.
[15.06.2024 21:29.13.809] [WARN] API request for GOOG failed: Unsupported redirect to https://finance.yahoo.com/quote/AAPL/, please report.
[15.06.2024 21:29.13.813] [WARN] API request for AMZN failed: Unsupported redirect to https://finance.yahoo.com/quote/AAPL/, please report.
[15.06.2024 21:29.13.817] [WARN] API request for META failed: Unsupported redirect to https://finance.yahoo.com/quote/AAPL/, please report.
[15.06.2024 21:29.13.819] [WARN] API request for TSLA failed: Unsupported redirect to https://finance.yahoo.com/quote/AAPL/, please report.
[15.06.2024 21:29.13.820] [WARN] API request for UA failed: Unsupported redirect to https://finance.yahoo.com/quote/AAPL/, please report.
I’m running the latest version of MMM-JAST and it stopped working yesterday. The rest of the modules are working properly. The error log shows “[WARN] API request for GOOG failed: Unsupported redirect to https://finance.yahoo.com/quote/AAPL/, please report.”
I’m getting a similar message for every ticker symbol. And all reference “AAPL”, which is strange.
If I go to that link in a browser, it successfully brings up that data. Here is my configuration:
module: "MMM-Jast",
position: "bottom_left",
config: {
currencyStyle: "code", // One of ["code", "symbol", "name"]
fadeSpeedInSeconds: 200,
lastUpdateFormat: "HH:mm",
maxChangeAge: 1 * 24 * 60 * 60 * 1000,
maxWidth: "100%",
numberDecimalsPercentages: 1,
numberDecimalsValues: 2,
scroll: "horizontal", // One of ["none", "vertical", "horizontal"]
showColors: true,
showCurrency: false,
showChangePercent: false,
showChangeValue: true,
showChangeValueCurrency: false,
showHiddenStocks: false,
showLastUpdate: false,
showPortfolioValue: false,
showPortfolioGrowthPercent: false,
showPortfolioGrowth: false,
updateIntervalInSeconds: 300,
useGrouping: false,
virtualHorizontalMultiplier: 2,
stocks: [
{ name: "DJI", symbol: "^DJI", quantity: 10 },
{ name: "NASDQ", symbol: "^IXIC", quantity: 15 },
{ name: "APPL", symbol: "AAPL" },
{ name: "GOOG", symbol: "GOOG"},
{ name: "AMZN", symbol: "AMZN"},
{ name: "META", symbol: "META"},
{ name: "TSLA", symbol: "TSLA"},
{ name: "UA", symbol: "UA"}
]
}
}
I would like to make the game time font larger but keeping everything else the same. I’m using Large Logos.
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/
@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
@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?
@sdetweil I appreciate your help in this as it’s obvious this is an environmental issue, not a Magic Mirror issue.