I think I kept the npm wiring-pi on there as well… There’s probably some other stuff in there that makes it work in mm.

So I think as wiring-pi is the npm specific version the reason it didn’t work was because they haven’t compiled it to work with the pi3 chip.

Try http://wiringpi.com/download-and-install/

@MadScientist said in {HowTo} turn on/off your monitor (Time based, PIR/Button, App):

Hmm, I get

Unable to determine hardware version. I see: Hardware   : BCM2835
,
 - expecting BCM2708 or BCM2709. Please report this to projects@drogon.net

when I run gpio -g write 27 1 .

I had the same issue. I just followed the instructions on the wiring pi site to install. Don’t have my notes but there was a different version depending if you use wiringpi or wiring-pi. I’ll see if I can find the right one.

Wish there was an easier workflow for me to use?

I installed samba on my pi & shared my home directory.

You can then just browse to it from a windows machine & directly open your config.js, edit (notepad++ is the best choice imo) & then use putty to send a pm2 restart command.

Google rpi samba as there’s plenty good info out there

For bonus ease you could then access the mirror in a Web browser on the pc using for example 192.168.1.100:8080 (sub in your mm ip). You will first need to set the ‘interface’ parameter in your config.js to 0.0.0.0 and set the access list to include pc ip or subnet. This is how I do it so I don’t have to go & stand in front of the mirror while I’m making changes to it.

Sorry, should say you combine with the remote control module to send screen off notifications.

For simple time based screen on & off check https://github.com/ianperrin/MMM-ModuleScheduler

Just looked at the install notes… The manual installation step is right after the auto install script so is probably why you did it (that’s my excuse anyway!)

Your screenshot of the pm2 output shows 2 instances of magic mirror. One called mm & the other MagicMirror.

I think if you follow the install guide it tells you to run install script (which I believe now sets up the MagicMirror instance) & then tells you to manually set up another called mm. I think the install guide might need updated.

Could it be 2 instances running & causing issues? If so get rid of one & restart & see if that solves it.

Got some feedback from the transaport api people today… seems they have figured out & resolved the back end data feed issue…it was related to stanox station code data dropping leading zeros for some stations (of which mine was one)… this caused their data to include trains which had already departed as they weren’t being seen to have passed through the station.

I’ve reverted back to the original version of your code it is working fine again.

On another note, I’ve tried swapping to using chromium to display the MM… I notice it does render other elements a lot better so maybe wont have the same problem with the train data stopping updating… time will tell.

Have you set it to autologin to GUI? Looks like you’ve got it set to login to console instead.

sudo raspi-config then go to boot options.

Text there is suggesting you change your password as well. Default user is pi with password raspberry