Posts made by HALPi-Thousand

HALPi-Thousand

@sdetweil said in I changed text in a module, now I don't get the module:

NEVER edit the module source code
ALL config goes in config.js
to recover a shipped mm file do( from the mm folder)
git status

Thanks, that did the trick.

But how can I change things like the compliments text and opening greetings and such, things that aren’t in the main config file? Or am I just stuck with a very obsequious Pi?

HALPi-Thousand

So, I’ve got MM on a Pi 4b. I installed Magic Mirror, and changed a few things - measurements from Metric to Imperial, being American and behind the times, and weather locations. So far so good.

Then I went and changed the compliments (because I don’t need a computer to tell me I’m sexy), and the opening messages (because I do want it to know I’m the boss and tell me it does).

Now it doesn’t do either one. just a big blank space. I was going to just toss it and re-install it, but that would just mean it would happen again next time.

So, I think I’d like to know how to prevent it instead. Obviously, other people manage to do this, so I’d like to know where I’m getting it wrong.

I opened the xxx.js files in the desktop environment; it opened them automatically with Mousepad, which I gather is the Pi’s text editing app. Should I have used something else? Maybe open it in the Terminal, and if so, how? Or is there something else I’m missing?

Thanks, guys

HALPi-Thousand

@sdetweil

So, I tried using that install script, ran into a few problems.

First I should mention that I did have a successful install of Magic Mirror at one point recently. Found Mystic Mirror, which apparently includes Alexa, which I want, so I deleted Magic and went to install Mystic, but ran into a bit of trickiness, so I installed Magic (or thought I did) until I could work out what to do with Mystic. And that’s around when I started running into this npm problem. Might have skipped something somewhere or gotten somethign wrong, I really don’t recall.

—edit----
You were about to be wading through a ton of text copied from the Terminal, but I somehow managed to figure out the right thing to google, and realizing that node.js was the first thing it had problems with, found out how to get rid of it. That worked. I did the full Magic Mirror installation again, and it’s happy. Just thought I’d mention the solution here.

I’ll take a swing at using your install scripts in a bit, but for now the main problem is solved. Victory!

HALPi-Thousand

@sdetweil

I’m still running Buster; tried Bullseye, ran into issues. Decided to wait a few versions. Will your script work with Buster as well, or just Bullseye?

Thanks

HALPi-Thousand

@mumblebaj

I think I’ve found the cuse of the problem. it begins at the npm install part:

pi@HALpiThousand:~/MagicMirror $ npm install
npm WARN read-shrinkwrap This version of npm is compatible with **lockfileVersion@1**, but package-lock.json was generated for **lockfileVersion@2**. I'll try to do my best with it!

So, it looks like, for whatever reason, it keeps doing that, and that results in it having problems trying to use it.

So, I guess the question is, what exactly is lockfile, what’s the deal with it putting this package in V@2 instead of V@1, and how can I get it to do what it’s supposed to do with it?

HALPi-Thousand

@mumblebaj

Funny thing, after I wrote that, I deleted and reinstalled Magic Mirror, then remembered that during an earlier install, I might not have done that directory change.

So now, it may be that it’s looking in the main Pi home folder, even though I’ve installed it the right way twice or three times since then.

So, I guess the question is, how do I let it know that the file is where it should be? Is there something else I should delete from somewhere else? Something that got installed in the main home folder and is probably still there?

Also, on this last install, I got this message:

pi@HALpiThousand:~/MagicMirror $ npm install
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it

> playwright@1.17.1 install /home/pi/MagicMirror/node_modules/playwright
> node install.js

internal/util.js:220
    throw new errors.TypeError('ERR_INVALID_ARG_TYPE', 'original', 'Function');
    ^

TypeError [ERR_INVALID_ARG_TYPE]: The "original" argument must be of type Function
    at promisify (internal/util.js:220:11)
    at Object.<anonymous> (/home/pi/MagicMirror/node_modules/playwright-core/node_modules/extract-zip/index.js:11:18)
    at Module._compile (module.js:649:30)
    at Object.Module._extensions..js (module.js:660:10)
    at Module.load (module.js:561:32)
    at tryModuleLoad (module.js:501:12)
    at Function.Module._load (module.js:493:3)
    at Module.require (module.js:593:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/home/pi/MagicMirror/node_modules/playwright-core/lib/utils/browserFetcher.js:9:42)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! playwright@1.17.1 install: `node install.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the playwright@1.17.1 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2022-01-28T17_50_58_671Z-debug.log

Does this help any with that question?

Thanks

HALPi-Thousand

Hi, Guys -
I’m trying to run Magic Mirror on a Pi 4b. I followed the install instructions perfectly, but I keep getting this error:

pi@HALpiThousand:~ $ npm start
    npm ERR! **path /home/pi/package.json**
    npm ERR! code ENOENT
    npm ERR! errno -2
    npm ERR! syscall open
    npm ERR! enoent ENOENT: **no such file or directory, open '/home/pi/package.json'**
    npm ERR! enoent **This is related to npm not being able to find a file.**

So, it can’t find the file. I found the file. It’s in the Magic Mirror folder, right where it should be. For whatever reason, MM hasn’t thought to look there. Any idea on how to teach it geography?

Fair warning, I am somewhere on the opposite end of the programming spectrum from anyone who knows what they’re doing.

Thanks

HALPi-Thousand

Hi -
I’ve been trying to install Magic Mirror. I’m on a Pi 4B, running Buster because the more recent update doesn’t seem to get along too well right now.

I’ve installed it, had to delete and start again because something somewhere went wrong in the last install, or maybe somewhere along the way when I tried changing a compliment or hte weather settings or something.

ANyway, now I keep getting this error:

Failed at the playwright@1.17.1 install script

the full text looks like this:

pi@HALpiThousand:~/MagicMirror $ npm install
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!

> playwright@1.17.1 install /home/pi/MagicMirror/node_modules/playwright
> node install.js

internal/util.js:220
    throw new errors.TypeError('ERR_INVALID_ARG_TYPE', 'original', 'Function');
    ^

TypeError [ERR_INVALID_ARG_TYPE]: The "original" argument must be of type Function
    at promisify (internal/util.js:220:11)
    at Object.<anonymous> (/home/pi/MagicMirror/node_modules/playwright-core/node_modules/extract-zip/index.js:11:18)
    at Module._compile (module.js:649:30)
    at Object.Module._extensions..js (module.js:660:10)
    at Module.load (module.js:561:32)
    at tryModuleLoad (module.js:501:12)
    at Function.Module._load (module.js:493:3)
    at Module.require (module.js:593:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/home/pi/MagicMirror/node_modules/playwright-core/lib/utils/browserFetcher.js:9:42)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! playwright@1.17.1 install: `node install.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the playwright@1.17.1 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2022-01-23T22_07_13_111Z-debug.log

So, obviously something somewhere is going screwy. I don’t know what or where, and not exactly being a master coder - more on the complete opposite end of that skill scale - even if I did in some vague way, I would have no idea why probably or what to do to make it behave.

That said, I can follow directions as easily as the next above-average IQ guy, so… Does anyone have an idea of what the problem is, and how I might fix it?

thanks