@stalker401 for the future, all u need to do is add

disabled: true,

To the module definition

@whoremoan the code does

initial calc

 tickerBody.style.animationDuration = Math.round(this.config.updateInterval / 1000) + "s";

this one u can change in config

then using the actuals it does

                function calcSpeed(speed) {
                    // Time = Distance/Speed
                    var spanSelector = document.querySelectorAll("headline"),
                        i;
                    for (i = 0; i < spanSelector.length; i++) {
                        var spanLength = spanSelector[i].offsetWidth,
                            timeTaken = spanLength / speed;
                        spanSelector[i].style.animationDuration = timeTaken + "s";
                    }
                }
                calcSpeed(100);

so, it calculates seconds in characters divided by 100/second,

this second one for me is suspect, as until getDom() returns the 1st time, there are NO spans with headline class IN the dom.
then on each other pass, there is the old one being replaced

so THIS new (about to be shown headline is a fixed rate. regardless of content size

probably the bigger problem is that the end of animation calls

  scheduleUpdateInterval: function() {
        var self = this;

        self.updateDom(self.config.animationSpeed);

        timer = setInterval(function() {
            self.activeItem++;
            self.updateDom(self.config.animationSpeed);
        }, this.config.updateInterval);
    },

which refreshes the content AND starts a repeating time that does that too… on a fixed schedule.
but it keeps starting new timers, on top of prior timers…

@mcnahum MMOS is good for what it does, but a lot of the instructions you will find here and other places won’t work as MM is running inside a docker container… so all the maintenance work will be different

for migrate…

I wrote a little backup/restore

which saves config.js, and custom.css and the links to the modules you have installed

and then restore reads that info and reinstalls modules to a new MM install (previously completed, maybe with the automated install script, see https://github.com/sdetweil/MagicMirror_scripts) …

my idea is that you would use git to hold the info from the backup (really small as just 2 files and links)
(so you are not backing up gigabytes for stuff)

and then clone it and restore from there

https://github.com/sdetweil/MagicMirror-backup-restore

the commands have help --help will display that

i have just created a script for pm2 setup only…

bash -c  "$(curl -sL  https://www.dropbox.com/s/cy2z7lbkpifcbrk/fixuppm2.sh?dl=0)"

this will remove any current MM definition and create a new one
install pm2 if need be, and set it up for restart on boot…

I also replicated this code in the installer to fix the problems there

all these scripts (raspberry.sh, update-script.sh and fixuppm2.sh) now create log files of their processing

let me know how it goes…

@earnestrichards openweathermap says their forecast is updated every 3 hours, so at 9pm they would be forecasting for tomorrow…

current weather is different than forecast

see
https://www.raspberrypi.com/news/raspberry-pi-os-64-bit/

note the issues w 64 bit chromium in the text

@sdetweil said in new script to install/fix PM2 config for start on boot:

bash -c “$(curl -sL https://www.dropbox.com/s/cy2z7lbkpifcbrk/fixuppm2.sh?dl=0)”

i added a couple fixes in case pm2 was already installed but didn’t work…

@johans see this issue comment

https://github.com/MichMich/MagicMirror/issues/2779#issuecomment-1011124060

in an attempt to limit spammers from registering and posting goo, we have enabled a higher level of reputation required to fill out the ‘About me’ and signature fields in the use profile.

edit: and the website and picture content as well
no more free advertising

sorry. I know this will be trouble for some

@everybodyfloats try my updated installer.

Rename the MagicMirror folder out of the way first

https://forum.magicmirror.builders/topic/10171/anyone-want-to-try-updated-installer

@spospordo yeh, the change was a year ago… but I understand…

thats why I post and pin resolutions to known problems at the top of the troubleshooting section.

@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