@sdetweil Awefully sorry for not replying till now - didnt see the message about a new reply.

Thanks alot for adjusting the module!

@sdetweil
Okay that makes sense to stop and resume them but i am guessing i would need to somehow code the hide and show into the module as well.
Since i got no clue on coding i am not sure if that will help me unforunately

Hey everyone,

I got the MM-TomTomCalculateRouteTraffic module and it is making calls with a TomTom API - now i would like to have really high amount of calls in the morning (about once every 30s) and non after a certain time.

Is it possible to config a module to be deactivated after a certain time? e.g. run it from 7-8am and then not?

@sdetweil
Just tried it with another pin (pin 20) and the results are completly different. So i am not sure what to make out of the infos i get from the script.

Gosh this is such a bummer that the sensor for some reason decided to quit…

Guess i will have to build in a switch or something to turn on the mirror for X minutes and use the existing script for it

@sdetweil
Thanks for the links. I ran the 2nd script and it came back with constant “motion detected” and “motion stopped” while there was I wasnt moving.

Which is a bit strange as the only thing i did was reconnect the existing cable to pin 17… (the soldering came off)

Hello everyone,

I just repaired my connection of the PIR Sensor and the Pi. Doing so i thought this should be it and the sensor work again.

However: For some reason the Module is not working as intended.

Intention:
Monitor being on for 20s when movement has been registered

Current behavior:
Either being ONLY when movement is detected or CONSTANTLY on

Status Quo:
The old code i have used and worked is as follows:

{
	module: 'MMM-PIR-Sensor',
	config: {
		     sensorPin: 14,
		     powerSaving: true,
	             OffDelay: 20000,
	}

Doing so will have the monitor turned off instantly unless i move.

{
	module: 'MMM-PIR-Sensor',
	config: {
		     sensorPin: 14,
		     powerSaving: true,
	             powerSavingDelay: 15,
	}

this code will have the MM on “forever” (well i havent been standing infront of the mirror for minutes… so i cant tell if forever…) at least not after 15s

I am a bit at a loss as to what has changed… i have not updated any modules or the MM… reconecting the pin 17 to the sensor was all I did…

Any help is highly appreciated

@BKeyport
Hey Keyport - thanks for the reply.

I was just reeeeally confused since i had a connector on the first pins and that didnt make any sense.

I will def. get one of these boards for my new Mirror as that just makes it so much easier to wire it up and it looks clean!

Hello everyone,

I built my MM a couple of years ago and sadly have pulled out some pins from the Rasperberry Pi… I am now completly lost as to how to place them again…

Could someone help me figuring it out again?

The Yellow and Red one are for the Monitor itself - the Black one is for the motion sensor which, according to my config file, should be connected to the Pin 17. However the First pin row had a pin-top thing (the small black things you can slide over them).

@sdetweil
Hey there,

so as of today the module is now working . I had to remove the API Version as you mentioned and that helped. However it took another day for the module to work… no clue why it didnt work right away (despite “reboot” and “pm2 restart”)…

I am currently now trying to figure out how to get one Module working as “current” or “day forecast” so i know what the day brings and another with the “forecast”.

I am assuming i need to do multiple modules to get that done?

@sdetweil

Can you please write me the code? I am seriously going mental over “not having anything loading” to “no config file” to just partially loading things…

This is really frustrating when you got 0 clue about coding to not figure out where the heck the issue is… ._.

This code doesnt create a missing config file but doesnt load the module. If i just enter the weather module (without config) it loads but only shows the current weather, but i would like to get the forecast for my region with the current API Version which is apparently 3.0

{
   		module: "weather",
   			position: "top_right",
   				config: {
     // See 'Configuration options' for more information.
   			type: "forecast",
   			units: "metric",
   			roundTemp: true,
   			degreeLabel: true,
   			showPrecipitationProbability: true,
   			colored: true,
   			apiVersion: 3.0,
   			lat: 123123,
   			lon: 312321,
   			apiKey: "asdasdasd123123asedasd123",
   					},
 },

@sdetweil

{
   		module: "weather",
   			position: "top_right",
   				config: {
   			type: "forecast",
   			units: "metric",
   			roundTemp: "true",
   			degreeLabel: "true",
   			showPrecipitationProbability: "true",
   			colored: "true",
   			apiVersion: "3.0",
   			lat: "123.123123",
   			lon: "321.321312",
   			apiKey: "abcdefg",
   					},
 },

That still results in no display of the weather module :/

@BKeyport That one comes up with “no config file found”

Since DarkSky API is discontinued i looked for a new module.

So i wanted to go for the standard weather module which however creates a config error.

Would someone be so kind and help me out if it is a code error or if i have to download/install the weather module?

 {
			module: "weather",
    			position: "top_right",
    				config: {
      // See 'Configuration options' for more information.
				type: "forecast",
				units: "metric",
				roundTemp: "true",
				degreeLabel: "true",
				showPrecipitationProbability: "true",
				colored: "true",
				apiVersion: "3.0"
				lat: "12.123123"
				lon: "12.123123"
				apiKey: "abcdefgh"
    					}
  },

@fozi

So I reinstalled the whole module and tried to get it back to work. I swapped to the GPIO_4 but unfortunately the Sensor is now not responding at all :/

Plugin it back to GPIO_17 it instantly works .

HOWEVER - the config is still on 4 but it is accepting the pin 17…

So there is something wrong but i am inclinded to “leave it as be” … it kinda works as i want, alltough i cant “control” it as intended by the module

@fozi
After two days of the programm running it SEEMS that the program is using “minutes” instead of “seconds” for the power off…

Because it does work now for some reason but the “turn off” is masively delayed

Hello everyone,

i just updated my MM to 2.17 and also my modules. Everything works fine (finally) except the MMM-PIR-Sensor module. ( https://github.com/paviro/MMM-PIR-Sensor )

The module did detect my first motion turned on and after the set amount of time (60s) turned the screen off. The issue is, that after moving again the module does deactivate the PowerSaving anymore…
HOWEVER after some time of the MM running it did detect the motion again… Now the opossite issue happens: It is not turning “off” anymore after the 60s…

Anyone got an idea on what to do?
.

Code in use:

{
module: 'MMM-PIR-Sensor',
config: {
sensorPIN: 17,
powerSaving: true,
powerSavingDelay: 60,
},

@sdetweil
Well the issue with the Pi being stuck at the splash was already happening before the console… maybe it was multiple things?

The pi started up and forced me to log in suddenly (no clue why). That is what got me started on checking the SD card. Since i didnt get access via remote (“wrong” username) I had to swap to console, deleted files and couldnt figure out how to get back.

It works again ^^

–

Regarding the disk-space. I got a 16 gb sd card.

However it was the 3-4 previous versions of MM2 I forgot to delete from the bin.

I will keep an eye on it and hopefully never run into that problem ^^’

–

Really appreciate the help! Thanks alot and big thumbs up to the community here!

Also added the “solutions” to the first post so people may be able to find a quick solution as well.

@sdetweil Yes excatly that one shows up and didnt go anywhere.

HOWEVER - Problems resolved.

–

I am using pm2 so i went and redid the autostart file (mm.sh and so on) [the shell script?]

After that I restarted and the Pi

1. started
2. showed the splash (see above)
3. showed the desktop
   [I got that wrong apparently]
4. loaded the MagicMirror 2 app [bit slow but it loaded]

I really got no idea as to why it now works again :D

–

regarding the pm2-flush. You said that is a big issue? Any idea how i can maintain the Pi properly?

@sdetweil said in MM stuck on boot up - cant connect via remote:

@Kastore said in MM stuck on boot up - cant connect via remote:

The software MagicMirror 2 is stuck in “Booting” and has rc-services.local on the bottom right
the console is still showing and i cant exit it (The CTRL+ALT+F1)

‘booting’ is another word… that means from hardware power on…

Just quoting what it says on the screen. The Pi is starting and running (sub 5% on idle - 40% on npm installs). After restarting the 4 berries show, the starting screen shows (“desktop”) quick and then the MagicMirror 2 application launches.

The APP however displays “MagicMirror 2 - booting” and keeps being stuck in this state

(did that clear it up?)

so, it sounds like the hardware boot is failing, but u say u can access…

rc-services.local that has nothing to do with MagicMirror, it is an OS file…

Again - just citing what it shows

the console is still shown?

so, are you booting your pi in console mode? use raspi-config to change that back to Desktop mode

Aaaaaah! And I thought I need to press some fancy combinations -.-’

Went to
sudo raspi-config and changed the setting.

---

So only the “booting” issue is still active