@madscientist Switched to dtoverlay=vc4-fkms-v3d and everything seems to work fine. MM runs at a few % CPU so it looks very good, maybe even lower than with OpenGL, but I haven’t gone into details.

What command do you use to check temperature?

@madscientist Thanks! I’ll try when I get home. And the fake OpenGL drivers don’t push the CPU/temp too much?

I cannot access remote control for some reason. It has worked before, but stopped some time ago (not sure when).

Running the mirror remotely works fine:
http://192.168.1.133:8080/

But running to remote control:
http://192.168.1.133:8080/remote.html

…gives me this error message:

“If you see this message, an errror occured when loading the javascript file. Please go to the following link and see if this a known problem with your browser:”

MMM-RemoteControl is up to date. Javascript is enabled in my browser. I have tried with Chrome, IE and my Android phone, same error.

Anyone who’s seen this before?

Just updated to 2.4.0 without problems and followed these steps to enable OpenGL:

https://github.com/michmich/magicmirror/wiki/configuring-the-raspberry-pi#enable-the-open-gl-driver-to-decrease-electrons-cpu-usage

After that, my display is rotated, i.e. running in landscape mode. So I continued to follow these steps:

nano ~/.config/lxsession/LXDE-pi/autostart
@xrandr --output HDMI-1 --rotate right

Display is still rotated though. I tried to manually run xrandr over SSH and got:

warning: output HDMI-1 not found; ignoring

Maybe I cannot run that over SSH? Any hints how to proceed?

Put the API request in node_helper.js. MMM-Surf.js is run on client and node_helper.js on server. Keep in mind that there is always only one node_helper instance.

@TheVieiraAkA My trakt account was already public. But I found that I was using the default watchlist, which probably wasn’t a good idea. I created a new public list and switched the ID in the config to that one. Still no luck, same error.

@TheVieiraAkA Thanks! I have checked client_id, client_secret, username and id_lista and they are correct. And there is no token file from before.

I get this exception in .pm2/logs/mm-error-0.log:

TypeError: Error processing argument at index 1, conversion failure from 80
    at TypeError (native)
    at ClientRequest.setHeader (/home/pi/MagicMirror/node_modules/electron/dist/resources/electron.asar/browser/api/net.js:252:21)
    at ClientRequest (/home/pi/MagicMirror/node_modules/electron/dist/resources/electron.asar/browser/api/net.js:190:14)
    at Net.request (/home/pi/MagicMirror/node_modules/electron/dist/resources/electron.asar/browser/api/net.js:354:10)
    at get (/home/pi/MagicMirror/modules/MMM-MyTraktSeries/node_modules/got/index.js:49:18)
    at Immediate.setImmediate (/home/pi/MagicMirror/modules/MMM-MyTraktSeries/node_modules/got/index.js:124:3)
    at runCallback (timers.js:574:20)
    at tryOnImmediate (timers.js:554:5)
    at processImmediate [as _immediateCallback] (timers.js:533:5)

@TheVieiraAkA I’m trying out your module now, and I have set up application, API key + secret and list id. But I get this text on my mirror:

Please enter the following on https://trakt.tv/activate: undefined

It should be an 8 digit code. Any idea what is wrong?

Not my module, but for those looking for weather forecasts from SMHI (Swedish weather), I found this:

https://github.com/fbacker/MMM-Weather-SMHI

Looks great and seems to work fine. Was not mentioned anywhere here on the forum or in the wiki.

Short lived happiness it seemed… After a few minutes CPU is now back at 100% and memory use increasing. :(

Also tested after reboot of my Pi3 with the same results.

This is my config:

		{
			module: "MMM-ResRobot",
			position: "top_right",
			header: "",
			config: {
				routes: [
					{from: "740015970", to: "740015568"},
				],
				updateInterval: 2 * 60 * 1000,	// Update every second minute.
				maximumEntries: 6,  // Number of departures to show on screen
				truncateAfter: 5,   // A value > 0 will truncate direction name at first space after  characters. 0 = no truncation
				apiKey: "*******"  // Your ResRobot apiKey
			}
		},

@Alvinger Thanks for the quick fix! :)

My first test…

1. “top” without ResRobot shows about 1% CPU when idle.
2. Added ResRobot (old version): “top” shows 100% CPU all the time.
3. Updated ResRobot, removed unirest, npm install: “top” now shows 1% CPU when idle. Yay!

Looks good so far. Too early to tell anything about memory leaks, but I will keep my mirror running and check tonight. Currently electron shows 18% mem used (for the 2 electron processes).

@cyberdie said in Mirror turning black after a while:

@alvinger In my case, the problem started after last MM update.

Same here. Running the latest ResRobot.

But I think others have reported the same problem but with a different module.

@Alvinger Do you know what could be the problem with ResRobot here?

Maybe this can be the cause?

https://github.com/electron/electron/issues/11739

@cyberdie @schlachtkreuzer6 It seems to be related to a certain module. Most likely it is a memory leak you have too. Try to find out by disabling modules until it works.

It would be good to find the root cause to this though as many have problems. But that is a bit out of my expertise.

My problem was MMM-ResRobot. I deactivated it and kept all other modules and now CPU is at 2% and memory stable over time at around 10%. Not sure if the MM/electron/ResRobot update caused the problem, but it worked ok before. Strange…

@Mykle1 @cruunnerr Thanks. Nmon is a great tip. I can clearly see that I have a CPU issue beside the memory leak. CPU for electron process is at 100% all the time. Currently at 30% mem, but I guess this will increase over time. Will check later.

PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
1146 pi        20   0  700648 300408  47112 R 100.0 31.6 215:22.52 electron

I’ve read the CPU usage thread and can conclude that I use electron v1.4.15 and MM v2.2.0. Mykle1, the thread said to use an older MM version, but I guess the new one should work ok too? Since electron was forced to the older version in the new release?

Now all I have to do is check each module I run and check CPU and mem for each :)

@bimalnair Have you tried to find out which module is causing problems for you yet?

I have finally got a dev log file from the error… As it’s not timestamped, it’s hard to draw any conclusions. But this is one of the lasts logs, which presumably is when the mirror goes black:

[5966:0125/191204:FATAL:memory_linux.cc(35)] Out of memory.
#0 0x0000012a3bb0 
#1 0x0000012b4406 
#2 0x0000012c8ae6 
#3 0x000000d8bb1c 
#4 0x000000d8ba9e operator new()
#5 0x0000012b9ee0 
#6 0x0000012b94ce 
#7 0x0000012ba204 
#8 0x0000012cb2c6 
#9 0x0000012b89f6 
#10 0x000000b58d18 
#11 0x000000a34c38 
#12 0x000000a35a80 
#13 0x000000a349c2 
#14 0x00000221e2fa main
#15 0x000074c0f294 __libc_start_main

I did not check which process is eating all the memory though. That will be the next step.

Other than that I can see in the log that I lost internet connection a couple of times:

fatal: unable to access 'https://github.com/MichMich/MagicMirror.git/': Could not resolve host: github.com

Whoops! There was an uncaught exception...
TypeError: Cannot read property 'feed' of undefined
    at ClientRequest. (/home/pi/MagicMirror/modules/MMM-Skolmaten/node_helper.js:45:20)

And a lot of these logs, which I guess is ok:

Reusing 14 cached departure(s) for module: MMM-ResRobot

Any bright ideas? :)

@Henrik From what I’ve read, a collaborator has write access directly to the repo. You can push code directly as if you are the owner.

@erq @Henrik Thanks for the tip! I have made a quick solution for now… changed package.json to have dependency to rss-parser v2.12.0.

Checked the rss-parser readme and the latest version (3) has changed it’s interface (“A few minor breaking changes were made in v3…”). If I find the time, I will update my code to support the latest version.