@chrisfr1976 You need to set up a Grafana Dashboard based on influx. The discussions in the evcc github (for example here) are a good starting point. Then install MMM-GrafanaChart. Config.js as described in the module documentation:

{
	 		module: 'MMM-GrafanaChart',
		 	position: 'top_left',   // This can be any of the regions.
		 	config: {
				version: "6", // Only add this line if you are using Grafana verison 6 or greater
				id: "V9usrR48j", // Only Mandartory if you are using Grafana verison 6 or greater found after /d/ in the url
				host: "solarrouter", //Mandatory. See url when displaying within grafana
				port: 3000, // Mandatory.
				dashboardname: "pv-ubersicht-mirror", // Mandatory.
				orgId: 1, // Mandatory.
				panelId: 9, // Mandatory.
				from: "now-1d", // use any of grafanas time-range-controls
				to: "now", // 
				width: "100%", // Optional. Default: 100%
				height: "100%", // Optional. Default: 100%
				scrolling: "no", // Optional. Default: no
				refreshInterval: 9000 //Optional. Default: 900 = 1/4 hour
				}
		},

@chrisfr1976 I’m using Grafana and MMM-GrafanaChart to display the data on my mirror.

@HeikoGr Thank you! Works great and saves a lot of space.

@HeikoGr , one addition: until 2023, there was a very compact layout of the module (screenshot still in the readme). Then there was this PR, and the new layout is very space consuming with more then one child/student. Maybe it’s feasible to use both layouts (old and new) by a config switch, but I’m a mechanical engineer, not a programmer… but I could test the modifications.

@HeikoGr Great, it works again. Thanks for your effort!

@karsten13 thanks for the hint, I tried several versions, the issue still persists.

@kai I used it until last year, then this issue occured. Maybe check your logs with

pm2 logs MagicMirror --lines=500

to see if you have the same issue.

@davidboisducafe Thanks. And also still running on my mirror.

@sdetweil I used your script

fixuppm2.sh

when I set up the mirror
Now I modified ~/MagicMirror/installers/mm.sh to

#!/bin/bash
# This file is still here to keep PM2 working on older installations.
cd ~/MagicMirror
source venv/bin/activate
DISPLAY=:0 npm start

but that doesn’t work, error occures again because node_helper doesn’t seem to use the venv.

@sdetweil Thanks, so it should look like this?

#!/bin/bash
# This file is still here to keep PM2 working on older installations.
cd ~/MagicMirror
export PYTHONPATH="/home/pi/venv/bin/python"
DISPLAY=:0 npm start

@xIExodusIx that’s due to changes in the handling of the python packages. I installed “fritzconnection” in a virtual environment:

python -m venv venv

source venv/bin/activate

python -m pip install fritzconnection

to make the Callmonitor use the fritzconnection, I edited the nodehelper.js (in ~/MagicMirror/modules/MMM-FritzBox-Callmonitor-py3) in line 212 to look like this (user is “pi”, must be adapted if you use another user):

pythonPath: '/home/pi/venv/bin/python',

Don’t know if it’s the best solution, but it works.

@ichel For me it also stopped working, but I’m unsure if it’s due to the module or due to a changed configuration on school’s side. Respective issue.

MMM-DWD-WarnWeather is now fixed.

Hi, there’s a module available, works fine for me.

@sdetweil Hi Sam, I deleted the package-lock.json, after that npm install still fails with the same error message. npm install electron rebuild also doesn’t help…

I wiped the module folder and reinstalled it from github, now it works.

I have the same error. Atteached the console output. Logfile can be found here.

An unhandled error occurred inside electron-rebuild
Could not detect abi for version 6.1.7 and runtime electron.  Updating "node-abi" might help solve this issue if it is a new release of electron

Error: Could not detect abi for version 6.1.7 and runtime electron.  Updating "node-abi" might help solve this issue if it is a new release of electron
    at Object.getAbi (/home/pi/MagicMirror/modules/MMM-PIR-Sensor/node_modules/node-abi/index.js:30:9)
    at new Rebuilder (/home/pi/MagicMirror/modules/MMM-PIR-Sensor/node_modules/electron-rebuild/lib/src/rebuild.js:122:28)
    at rebuildWithOptions (/home/pi/MagicMirror/modules/MMM-PIR-Sensor/node_modules/electron-rebuild/lib/src/rebuild.js:393:23)
    at Object.doRebuild [as rebuild] (/home/pi/MagicMirror/modules/MMM-PIR-Sensor/node_modules/electron-rebuild/lib/src/rebuild.js:400:16)
    at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-PIR-Sensor/node_modules/electron-rebuild/lib/src/cli.js:115:33)
    at Generator.next (<anonymous>)
    at fulfilled (/home/pi/MagicMirror/modules/MMM-PIR-Sensor/node_modules/electron-rebuild/lib/src/cli.js:5:58)
npm ERR! code ELIFECYCLE
npm ERR! errno 255
npm ERR! Magic-Mirror-Module-PIR-Sensor@1.1.0 postinstall: `electron-rebuild -e ../../node_modules/electron`
npm ERR! Exit status 255
npm ERR! 
npm ERR! Failed at the Magic-Mirror-Module-PIR-Sensor@1.1.0 postinstall 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/2020-04-02T08_25_32_202Z-debug.log
processing complete for module MMM-PIR-Sensor

@BigMan There’s another thread with your problem here. So far nobody knows a fix.

I’ve changed to MMM-TomTomTraffic which works correctly. But I’m still wondering why MMM-TomTomTrafficincidents doesn’t.

I tried the config from @Lordy (even with his API-key, many thanks Lordy), but still the same behavior (nothing shows up from the module). I reinstalled the module, double- and trible checked the config, it just doesn’t show the map. Any further ideas?

@Lordy
Thanks for your reply. I want to display

lng: 8.35,
lat: 49.08,

I’ve already tested the coordinates for New York from your example above - same behavior.

Danke für die Antwort. Ich will die oben genannten Koordinaten darstelllen. Ich habe es auch schon mit deinem New York Beispiel von oben probiert, mit dem gleichen Ergebnis. Falls ich dich irgendwie unterstützen kann, sag Bescheid.