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
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
@sdetweil said in MM stuck on boot up - cant connect via remote:
@Kastore said in MM stuck on boot up - cant connect via remote:
Not really sure how that connect to the problem with the remote? (just being curious)
there are two remote access…
you can ssh to the console, independent of any app
and u can connect to an app (MagicMirror), independent of using ssh.I was responding to this statement
The mirror is however still not accessable via remote and the MM is also stuck on the booting.
there are two things there that aren’t quite clear
mirror and MM
Sorry for causing a confussion. What I meant was: I want to remotly access the Raspberry Pi via the remotedestop app from w10.
That issue has been resolved since - of course - the problem sat infront of the keyboard… like ever other problem always does ^^’
I now got access to the Pi again.
Did that clear it up?
I just worked on my pi4 which had hung, and would not boot to the graphical desktop
I had run out of space. I could ssh and boot to the commandline (console mode)
I did the same and plugged in my keyboard to the Pi directly. Pressed CTRL ALT F2 and logged in there. That is how I gained access and realized that the SD card was full.
That issue has also been resolved. I had the bin still full and the pm2 flush command.
So the remaining two are
~~
@Kastore can u show us the address: value in config.js, there was a security fix which changed the default
address: “” means localhost, ONLY stuff ON the same machine(localhost) can access the mirror app
u need to change to
address:“0.0.0.0” (or some other specific address if u want tighter control (this means anyone, and was the accidental default before)
Not really sure how that connect to the problem with the remote? (just being curious)
The Pi is included in the network and I access it via the remotedesktop app from Windows. Just entering the name of the Pi and then name + password.
For some reason I now got access to the remote again… Not really sure why. BUT I may have entered the user name in capital letters and not lower case. ._.
Well… one problem down at least
if u got enough storage from pm2 flush, you are in big trouble. you should examine and clear whatever u don’t need.
Well I think I never cleared the logs in about 2y time or so. So… that was a bit of a problem. Plus i had 3 previous versions of the MM in the trashbin… those where the bigger problem. The pm2 flush made about 2gb, the trash-empty about 6gb
if u have modules installed that contain a ‘package.json’ file, then THEY TOO need
an npm install done in each such module folder…
But the problem had already been even prior to updating anything. (MM being stuck on booting)
Hello everyone,
as a heads up. This post contains 3 UPDATE: 2 Update: no problems which I am not sure if they are connected or not. Thus I decided to just make one post - if these should be seperated please let me know.
I am also completly new to coding. So please bear with me if some “stupid” questions arise or I cant follow along right away.
The Problems:
I am currently stuck with my MM. Since a couple of days the mirror forced me to “log in” while showing the main desktop.
I tried connecting via remote (name and pw are correct [direct console loggin works]) but couldnt get any access Update: I forgot the case sensivity… remote works
:::
connecting to sesman ip 127.0.0.1 port 3550
sesman connect ok~~
sending login info to session manager, please wait ...
login failed for display 0
:::
After some research the SD card was said to be the issue.
I plugged my keyboard into the Pi and ran the CTRL+ALT+F2 to enter the console, logged in (name/pw work!), checked if my SD card was full (… it was) and ran:
pm2 flush
trash-empty
That solved the storage issue.
The screen now just showed the mirror (update: the splash screen) being stuck on “booting” and the bottom left had “rc-local.service” on display. Other modules are however working (such as MMM-PIRSensor).
The mirror is however still not accessable via remote and the MM is also stuck on the booting.
So I ran updates via the commands, restarted and hoped it would work
git pull
npm install
The mirror is still stuck on the same spot and still not accessable.
So my three issues are
1) Getting the mirror running again
Solution: dont know what fixed it.
First: My SD card was full and I cleared some space via “pm2 flush” and “trash-empty”.
Second: I ran the “git pull” - “npm install”
Third: After having remote access again I did “npm install” in the modules folders
Fourth: I entered “pm2 list” in the console and saw no instance of the mm.sh. So I redid the pm2 shell script, restarted and it worked. The Pi now goes past the splash screen, shows the desktop and then starts the MM2.
2) Getting the remote access back
Solution: apparently I entered the user wrong… Classic case of "the problem is in front of the keyboard.
3) exiting the console display (CTRL+ALT+F1)?
Solution: It wasnt the key-combination. I changed the “sudo raspi-config”. Swaped it back to console and the display went