For the record: I rolled back the default calendar plugin to the previous release (April) an the problem is solved. There seems to be something wrong with the latest release

Dear all

The calendar plugin shows items on wrong date. The problem appears with multiple caldav calendars from different sources. An Item which is scheduled for tomorrow appears to be due for the day after tomorrow. All other plugins like the clock are showing correct date + time

I did some more digging and changed the timeFormat to “date headers” interestingly the plugin shows actually a wrong date. For example a item which is in the ical file for the 9th appears to be due on the 10th.

This problem occurred once I updated the installation. Previously I was running a version dating back to April. Problem occurred without touching the config.js

I also added a bug report on git

It would be great if someone could help me out getting this fixed

a workaroudn to solve this problem was identified here:

https://github.com/eouia/MMM-AVStock/issues/7#event-2257397757

Dear all,

I currently use two modules in my setup which for some unknown reason are cross-interacting in a unwanted way:

• MMM-PIR

• MMM-AVStocks

My config.js looks like this:

		{
		    module: 'MMM-PIR',
		    position: 'bottom_center',
		    config: {
		        sensorPin: 4,
		        delay: 30000,
		        turnOffDisplay: true,
		        showCountdown: true,
		        callbackScripts: ["callback.py"]
		    }
		},

		{
		  module: "MMM-AVStock",
		  header: "Stocks",
		  position: "top_right", //"bottom_bar" is better for `mode:ticker`
		  config: {
		    apiKey : "XXXXXXXXXX", // https://www.alphavantage.co/
		    timeFormat: "DD-MM-YYYY HH:mm:ss",
		    symbols : ["aapl", "GOOGL", "AMZN"],
		    alias: ["Apple", "Google", "Amazon"], 
		    tickerDuration: 60, 
		    chartDays: 90,
		    poolInterval : 1000*15, 
		    mode : "table", // "table", "ticker", "series"
		    decimals: 2, 
		    candleSticks : false, 
		    coloredCandles : false, 
		    premiumAccount: false, 
		  }
		},

Now comes the peculiar thing: if I set

showCountdown: false,

in MMM-PIR the on screen countdown of this module disappears as intended but so does also the list of the AVStock. In fact the header of AVStocks is still there but the actual list does not appear. Also if I change the

mode : "table", // "table", "ticker", "series"

nothing happens. This behavior is fully reversible and reproducible. It would be great if someone could help me out on this.

@sdetweil said in MMM-PIR-Sensor not working with latest release - display does not turn off:

node_modules/.bin/electron-rebuild

Holy SHIT that worked. I’m now using the MMM-PIR instead of the MMM-PIR-Sensor

thanks you so much!!!

EDIT:

for the record: there are two PIR modules avaliable: Initially I intended to go with MMM-PIR-Sensors as I’ve been using this in the past. Unfortunately I couldn’t get it to work with the newly installed setup. Hence I choose MMM-PIR.

Besides the suggestion from @sdetweil I also modified the displayOff.sh and displayON.sh from

tvservice -o

to

vcgencmd display_power 0

so the module works with the full KMS OpenGL driver.

actually I checked the pm2 logs and found loots of this messages:

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2019-04-03T22_01_36_315Z-debug.log
/home/pi/MagicMirror/node_modules/electron/dist/electron js/electron.js: symbol lookup error: /home/pi/MagicMirror/modules/MMM-PIR/node_modules/epoll/build/Release/epoll.node: undefined symbol: _ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorENS_14SideEffectTypeE
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! magicmirror@2.7.1 start: `sh run-start.sh`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the magicmirror@2.7.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

does anybody know how to fix this?

Yes, I did. to my best knowledge the tcservice does not work with the KMS driver.

Also looking into the details at GitHub I thought that MMM-PIR-Sensor actually uses the vcgencmd

Dear all,

I’ve been using MM for over 1,5 years now. Unfortunately my SD card died yesterday so I took the opportunity to start from scratch.

I installed the latest release 2.7.1 on my RBPi 3. using the “Full KMS” OpenGl driver. Unfortunately my PIR Sensor does not work anymore as my display stays on all the time. Interestingly I’m able to turn the display on an off manually via SSH using

vcgencmd display_power 0

vcgencmd display_power 1

I already checked the wiring (which I actually did not change from my setup which was working for a long time) and I also checked the signal line of the PIR Sensor. Both are ok.

My configuration looks like this:

		{
			module: 'MMM-PIR-Sensor',
			config: {
				sensorPIN: 23,
				powerSavingDelay: 15
			}
		},

It would be great if someone could help me out as I’m clearly missing something…

First of all thanks a lot for this great plugin! I have it running on my RBPi based MM.

in my scenario it listens to my home assistant which publishes some sensor stats about my home.

I’m running three instances of this plugin, each listening to a different sensor . If I freshly boot the MM it works until suddenly it freezes and does stop updating the stats. At this point all the other MM plugins continue to work as intended. I checked and the broker actually keeps broadcasting updates values. Hence, I suspect that something with this plugin does not work. In order to get everything working again I need to restart the magic mirror.

It would be great if someone could help me to fix this.

sorry for digging this up again but my problem ist still unsolved.

yes, both events are on the same ics!

i just realized that the mirrow shows me the full day events as if they were starting just at midnight. somhow it is not recognized that these are full day events which need to be shown throughout the whole day

its still very confusing, i had an event in my calendar yesterday which worked just perfect, the whole day long it appread as “today”. Then, i have a identical event today which dissapeared.

i do not get why some events behave different than others.

thanks for the info. Actually the “today” message does appear but the entire event dissapears in the afternoon. Could it be that there is a 12h offset?.

Dear all,

i have the following problem:
I set up my MM with the default calendar module wich is connected to my icloud calendar. So far the connecton works nice an all the events are showing up. However, the indicated time seems to be off. Specifically i have a calendar which only hold birthdays (each fullday events). Lets assume that today is the 11th and a friends birthday is on the 15th. My MM would tell me that the birthday is in 3 days which seems odd. Moreover, on the 15th the event would dissapear entirely. It would be great if someone could help me to fix this.

I already checked and my raspberry is set to the correct time zone just to rule out the obvious :-)

ok, thanks a lot, this was quite helpfull!

That is odd, my current config.js was working with my API keys for both actual weather and weather forecast modules brilliantly with the most recent mm version (the slow one)

With 2.10/1.4.15 the actual weather module still works but the weather forecast modules simply does not show up on the screen although it’s fully setup in the config file including the proper API key

@Mykle1: that seems to have worked. I just entered the MagicMirror folder and ran the command! thanks a lot! the animations are a lot better now!

However, now i have another problem: it seems that the weather forecast module does not work. All other modules work as expected but the forecast does not show up. I double checked all the settings in the config.js and they seem ok.

@Mr-Sponti: thanks for the input but it seems that simply installing 1.4.15 over the 1.7.9 seems to have already working

Could it be that the weatherforecast plugin comming with MM 2.10 is the problem?

@Mr.Sponti

I tried your precise instructions but my system still installed electron 1.7.9

i started with a fresh jessy install on my raspberry pi 3. i then installed the latest version of node.js and copied the MM 2.10 folder to my pi. I then modified the dependancy for electron to 1.4.15 in the package.json and run the installation. However i still ended up with electron 1.7.9 which runns really bad…

it would be great if someone could help me

Hi everyone,
i just set up MM on a fresh installed and updated Raspberry Pi3. unfortuately the performance of MM is very slow. Animated content looks as it runs with 10frames per second. Sometimes even the second indicator of the clock just stops and then updates a few seconds at once. The CPU seems not to be loeaded or anything and the actual GUI of the OS runs smooth.

Any idears how to solve this?