@afrench10

A small part of the MichMich set-Up instructions:

ℹ️ Activating the Open GL drive can also be accomplished by using the raspi-config tool by running sudo raspi-config. Go to the Advanced Options menu and select A7 GL Driver. Next, select the G1 GL (Full KMS) OpenGL desktop driver with full KMS. Note that this option will be selected in the menu even when the GL drive is not yet configured.

Unfortunately, as a result, the display_rotate=1 (see below) won't have any effect on the display. If you want to rotate the display when the Open GL driver is in use, we need to use the xrandr tool which allows us to rotate the display when in desktop mode. To do so, edit the autostart file:

nano ~/.config/lxsession/LXDE-pi/autostart

And add the following line:

@xrandr --output HDMI-1 --rotate right

That should solve your problem.

Kind Regards

Hein-Jan

I did have the same problem as @bhepler. Switching from fake KMS to full KMS solved the problem.

Hein-Jan

@kovu94

Although I did not have a problem with syncing, (actually I was not getting any call history) my logs gave a similar error.

TypeError: PythonShell is not a constructor
    at Class.loadDataFromAPI (/home/pi/MagicMirror/modules/MMM-FRITZ-Box-Callmonitor/node_helper.js:216:17)
    at Class.socketNotificationReceived (/home/pi/MagicMirror/modules/MMM-FRITZ-Box-Callmonitor/node_helper.js:69:9)
    at Socket. (/home/pi/MagicMirror/modules/node_modules/node_helper/index.js:113:11)
    at emitTwo (events.js:126:13)
    at Socket.emit (events.js:214:7)
    at /home/pi/MagicMirror/node_modules/socket.io/lib/socket.js:528:12
    at _combinedTickCallback (internal/process/next_tick.js:131:7)
    at process._tickCallback (internal/process/next_tick.js:180:9)

Looking for the error on internet I found some references to the PythonShell dependency that is being used. It seems that PythonShell is now running at version 1.0.7. Where it was running @ version 0.5.0 during development of the module.

I have reverted back to 0.5.0 and things are working like they should!

Go to cd ~/MagicMirror/modules/MMM-FRITZ-Box-Callmonitor/node_modules.
Remove the Python-shell directory and all its content:
rm python-shell -r.
Now reinstall the old version with:
npm install python-shell@0.5.0.

Restart your MagicMirror and it should work.

Al least it did for me.

Hein-Jan

@j-e-f-f ,

I am also stuck at “Loading” actually it says “Bezig met laden…” which is Dutch for “Loading”.

I ran the “git clone…”, switched to the “MMM-DarkSkyForecast” directory, and ran the NPM Install.
I do get this warning: “npm WARN mmm-darkskyforecast@1.0.0 No repository field.”, but I do not know how to act upon it.

The module is making calls to DarkSky, I see that in the Api usage.

The logs show no error.
This is the config:

		{
  			module: "MMM-DarkSkyForecast",
  			header: "Weersverwachting",
  			position: "top_right",
//  			classes: "default everyone",
  			disabled: false,
  			config: {
    				apikey: "XXXXXXXXXXXXX",
    				latitude: "51.5096192",
    				longitude: "5.6364183",      
    				iconset: "1c",
//				maxHourliesToShow: 4,
//				maxDailiesToShow: 4,
//				useAnimatedIcons: true,
    				concise: false,
//				label_timeFormat: "k[h]",
    				forecastLayout: "table"
			}
		},

I am not sure were I went wrong. Can you provide help?

Kind Regards,

Hein-Jan

Mykle1

Thanks for your reply and confirming that it is a time-zone issues.
Instead of messing around with the code, I think I will simply off-set my event deadline time.
That way I am at least robust against updates.
Thanks for the work with the CET link.

Hein-Jan

@Mykle1

It feels like the timer is not indicating the correct time. It is set for 09:00:00. Current time is 21:40. Count down says we still have 17 hrs and 19 minutes to go. I think it should be 11 hrs and 21 minutes.
I am on Central European time. Could that be a contributing factor? Does the module vector in time-zone influences?

Hein-Jan

@AxLed

Sorry it took me some time to reply. Holidays and such.

In reply to your suggestions:
1st idea: Haven’t tried, I went a different route, see underneath.
2nd idea: had tried i before; commands via the URL worked.

It decided to go another route.
Instead of using MMM-ModuleScheduler I have opted to use Cron to do the MONITORON and MONITOROFF commands.
As I was only having trouble at the MONITORON command I first tried this in Cron.
To my surpise I now had a mirror in the morning but not in the evening.
It turned out that I was sending 1 MONITOROFF with Cron (after the nightly reboot).
Actually I am not using MONITORON and MONITOROFF in Cron but vcgencmd display_power 1 and vcgencmd display_power 0.
After the vcgencmd display_power 0 I was able to use Cron to turn the monitor back on with vcgencmd display_power 1
But after MONITOROFF I was not able to turn the monitor back on with vcgencmd display_power 1.
So MONITOROFF seems to be doing something strange in combination with the FakeKMS driver.

I think I read a similar conclusion in another post:
https://forum.magicmirror.builders/topic/8556/monitor-not-waking-up-from-sleep

So my work around for all this is Cron. And it is working. And I learned something about Cron.

Hope this may also help others who are struggling.

Hein-Jan

Silvor,

As far as I understand it, only the immediate next action is scheduled, once that action has been performed, the schedule will be studied and the following action will be scheduled.
So it makes sence that you see the first upcoming Monitor On, the first upcoming Monitor Off and the first upcoming Reboot.

By the way, are the time and date correct by the time mmm-mode scheduler is running?

@paulb

Is your device listed in “whitelist”, in your config.js?

Please check forum on whitelist issues.

Hein-Jan

@bhepler

As far as I can tell the

libGL error: MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information

Is due to the Open GL driver. I am using the Fake KMS and these are mine errors. I am not using NOAA.