@SymmetriC what url did u provide?

if using the mm web server

http://localhost:8080/modules/MMM-Text/filename 

for reading from filename in the module folder

if some other file NOT using the mm web server

file:///full_path_to_filename

and of course if on some server someplace else

http{s}://server name/path?parms_if_any

@buzzkc Use my new scripts. Search for fixuppm2

@ZiggidyZ the pm2 error in remote control is a module packaging problem

it demands the library to be able to do the job, but didn’t install it (see package json does not list it as a dependency

do this
change to the module folder and do

npm install pm2

then restart mm and try again

@crisvdn there are really a list of issues here

most importantly, most modules are created by someone for their own use, and shared
but then they go on to other life things

maybe for a while they hang around and take issues and PRs.

but life goes on.

some modules haven’t been updated in 5-6 years. mm has been active for 10.

I would guess that 99% of the authors are not programmers, and have other day jobs. never experiencing the details , or life cycle.

as this is open source, there is no commitment to maintain a module.

we get waves of new authors maybe 5-6 a year.

without fork, there is no way to ‘fix’ an abandoned module.

now we are at the 'where do I find modules ’ problem. there is one voluntary list. others are trying to improve the usability of the list, but it’s still voluntary.

we keep up the core with issues and PRs and changelog and test cycles. but not any of the 3rd party modules.

I’m a moderator here, never a professional programmer. I do it all for for fun. I keep my stuff up to date. but I don’t list my modules in the 3rd party list.

I don’t use the Developer or Contributor tags on my ID cause I show my support thru my actions. I don’t need an outside label to differentiate myself… I’m no better than anyone else here.

@roooooony
can you do

ls /usr/lib/arm-linux-gnueabihf/libnss3.so -laF
and
ls /lib/arm-linux-gnueabihf/libdbus-1.so.3 -laF

mine are dated aug 22 and Jun 9 (libdbus-1.so.3.19.11) respectively

and a thing to test out
rename the ~/MagicMirror/node_modules/electron folder to some other name
then do

cd ~/MagicMirror
npm install electron@6.0.12

then try to start MagicMirror

@ahmed245275111 your node/npm level is below the required for this module

mm 2.26 requires node version 18 or above

if you used my mm install or upgrade scripts it would have handled that for you.

see
https://github.com/sdetweil/MagicMirror_scripts

I deleted the duplicate topic

@crisvdn here is a link to the list work
https://forum.magicmirror.builders/topic/18092/automatic-checking-of-all-magicmirror-modules?_=1704465730999

i’ve just pinned it to the top of the Development section so it won’t get lost
(I couldn’t find it when I mentioned it the first time)

@davidkmcw said in Was working fine, now just a blank screen:

Error: Cannot find module 'node_helper

that thing again

do

cd ~/MagicMirror
git checkout  modules/node_modules/node_helper/index.js

this was caused by doing an npm install in a folder that did NOT have a package.json file

@james1787 fantastic! 2fer… fixes and like more

hopefully this will help us all work on quicker responsiveness and shorter

get this
what did you do last

cycles…

but there is a side effect.,… the automated build process failed (on master, which itself hasn’t changed)… oops… and our banner shows the build failed…
on code and doc sites…

just to let you know, we know and are working on it.

conversation about the templates here