Newsfeeder is going way to fast when showing news

[sdetweil]

@fribse could you do a quick test for me.

open the developers window, sources tab,
in the left nav,
expand modules, default, newsfeed,
select the newsfeed.js
source will appear on right window

scroll the source down, til line 298 is in view, and click the line number so it looks like this

then hit f5 (will reload MM)

and it will stop at line 298

then use you mouse to hover over the this.config.updateInterval

like this

and then tell me what node/npm version u are using

u can do the debug using chrome, firefox or edge on your pc, if u have address:“0.0.0.0” and ipWhitelist:[] set in the mm config on the pi.

[fribse]

Like this:

?

pi@bathmirror:~ $ npm --version
7.6.3

[sdetweil]

@fribse yes, thanks… so its got the right number for interval.

[fribse]

@sdetweil Currently it shows the news in a proper speed, not sure what starts the problem?

[sek_is_back]

i got exact the same strange behavior. one day after my last post, the newsfeed worked like expected for 2 weeks. today the updateInterval seems to be ignored.
After a pm2 restart everything is fine again.

Now i wrote a cron to restart the Mirror every Night at 2am. will see if this will help.

[Jalibu]

I can confirm this error. Same on my MagicMirror:
It worked for weeks and then out of a sudden the speed changed to turbo-mode during runtime

[Fozi]

Same here. This behaviour started about 2 weeks ago. Some times the feeds cycle as expected, but then all of a sudden they rush through.

[fribse]

Yup, I saw it again this morning, odd.

[fribse]

@sdetweil Ok, I finally got it tested again.
If I go to my computer and open the webpage via remote it shows the right interval (this was what I did earlier), and the news cycles slowly as it should.
But on the raspberry pi, it still races through the news.
I haven’t restarted the Rpi just to keep the problem, but for me it’s not an easy test on the RPi itself, as the RPi is of course behind the mirror and headless.

[Jalibu]

I assume that for some reason some intervals are going crazy during runtime. The problem is gone, if you refresh the page, but it may come again after an uncertain time.