Those bubble and dust are hard to avoid when applying the film. I followed this instructional film on youtube and made a huge improvement to my own mirror.

Watch the whole thing and I’m sure you’ll see a big improvement next time you try it.

@Cato yes. yes I am. Thanks. That’s it!

Hi @Cato ,

I’ve just updated with MM 2.1.0 and checked that I’m running the latest version of MMM-Ruter.

When I tried to run the module with two different stops, it crashed the config file.

´´´´javascript´´´´

{
module: ‘MMM-Ruter’,
header: ‘Ruter’,
position: ‘bottom_right’,
config: {
showPlatform: true,
maxItems: 10,
stops: [
{
stopId: “3010430”,
platforms: [ “1”, “2” ],
timetoThere: 2
}
{
stopId: “3010425”,
platforms: [ “1”, “2” ]
timetoThere: 2
}
]
}
},
´´´´javascript´´´´

It runs fine with 1 stop. But I get a config error message with 2 stops. Even if I just copy the exact same information two times.

Is there an error in the config above? Let me know!

You’re right! An area around Oslo and to the North of the city is showing an incorrect temprature on the site.

I’ve submitted an issue to them. Hopefully they’ll fix it soon.

I’m using the default Weather module and have added the api key from openweathermap.

The module is working OK, and has previously worked perfectly.

Recently, however, today’s weather has been wrong. Both on Current weather and the Weather forecast. (The week ahead is fine).

Here’s the config:

                 {
			module: 'currentweather',
			position: 'top_right',
			config: {
				location: 'Oslo',
				locationID: '3143244',  //ID from http://www.openweathermap.org
				appid: '***********************************'
			}
		},
		{
			module: 'weatherforecast',
			position: 'top_right',
			header: 'Weather Forecast',
			config: {
	            		location: 'Oslo',
				locationID: '3143244',  //ID from http://www.openweathermap.org
	            		appid: '*******************************'
			}
		},

The API key is the same. The weather is equally wrong on both Today’s Weather and Forecast modules.

Image

I’ve done the obvious and checked Openweather map website. The weather there is correct.

The weather outside is also correct.

What should I try next?

@jc21 just for closure here I found the issue. After running the python script again I realised that the PIR was always HIGH even with the sensitivty dialled right down.

So I checked the leads going into the pi and found that, despite checking it many times, I’d mixed up GND and VCC :(

The lesson for any other idiots out there when testing is, run this Python script and make sure that the PIR stops broadcasting “Motion Detected!” when you cover it with something:

from gpiozero import MotionSensor
import os

pir= MotionSensor(22) //the gpio pin PIR OUT is connected to
while True:
               if pir.motion_detected:
               print (“Motion Detected!”)

Code from this site

With some further adjustments for sensitivity it’s now working great!

Hi @Cato all good!

Default config language is “en” (english).

Here is a film demonstrating the refreshing issue:

https://www.dropbox.com/s/5n0lkx9z3lhznkn/2016-11-05 18.52.26.mp4?dl=0

I tried setting the animation speed to 10 to elimate the display flicker. It’s a simple hack, but worked fine. Now it’s barely noticeable.

:)

Hi @Cato sorry for the slow response.

I’ve pulled v 1.0.2 but haven’t changed my config file. It looks like this:

{
module: 'MMM-Ruter',
header: 'Ruter',
position: 'bottom_left',
config: {
showPlatform: false,
maxItems: 10,
stops: [
{ 
stopId: "3010430",
platforms: [ ]
}
]
}
},

In reply to your previous question: I haven’t changed the time settings on the module. The time in the default clock module is in 24 hour format. So is the Pi. Any guesses as to the reason? It’s not a big problem for me, or it wasn’t, until you pointed it out ;)

Two other comments:

The GUI visibly refreshes inconsistently (between every 5 and 20 seconds) but often. Often enough that it’s visually distracting. Not sure what is triggering the refresh - serviceReloadInterval or timeReloadInterval maybe? Have you changed these in your setup? If so maybe post the config so that I can copy those settings and see if the problem fixes.

See you have down as a point for future improvement the ability to run two instances of the module at the same time. I’d just like to second that! I’d like to have two instances running in two different corners of my mirror for the two nearest transport hubs we use. I would certainly make use of it if/when you get the time to add it.

Hope to be a bit more available in the week ahead if you have any other questions.

Great work @Cato!

Super easy install. Will look forward to playing with the config in the week ahead.

Proof: https://www.dropbox.com/s/zafm6q8k8hg8e1t/2016-10-24 23.42.24.jpg?dl=0

@jc21 hi again, thanks for your input so far.

I’ve had the sensorPIN at 22 previously. And tested it using the python script shared on a few other threads:

´´´python
from gpiozero import MotionSensor
import os

pir= MotionSensor(22)
while True:
if pir.wait_for_motion(timeout=10*60):
print(“It lives”)
else:
os.system(“/opt/vc/bin/tvservice -0”)
´´´
The result spammed “It lives”. Which I understand to mean that the sensor is working… If I change the if to “os.system(”/opt/vc/bin/tvservice -p")" the screen shutsdown.

The reason I changed it was based on the results of “gpio readall”. I currently have power in pin 1 (3.3v), ground in pin 6 and data in pin 15

gpio readall tells me that physical 15 = BCM 22 = GPIO 3 so I decided to try sensorPin: 3.

I’ve changed it back to 22 now, but the result is still the same.

Other possible vectors are:

I’m forcing HDMI output because I’m using a HDMI -> DVI converter and so it seemed like a safe choice.

With dev tools open I can see that USER_PRESENCE is not being logged anywhere in the console.

I followed this post and ran:

“Run npm rebuild --runtime=electron --target=1.3.4 --disturl=https://atom.io/download/atom-shell --abi=49”
in the MMM-PIR-Sensor folder,