Read the statement by Michael Teeuw here.
Motion Detector
-
my logs without any changes:
If I put in the therminal:
/opt/vc/bin/tvservice --preferred && sudo chvt 6 && sudo chvt 7
my monitor turn on and my mirror work…
-
Was your monitor on when you were starting the magic mirror?
-
@alexyak Yes these both work via ssh
Switch off:/opt/vc/bin/tvservice -o
Switch-on:
/opt/vc/bin/tvservice --preferred && sudo chvt 6 && sudo chvt 7
When I do this:
/opt/vc/bin/tvservice -s
I get this:
state 0x12000a [HDMI CEA (16) RGB lim 16:9], 1920x1080 @ 60.00Hz, progressive
But when I start the mirror with the normal npm start and it runs until the motion sensor time then the screen goes out and won’t come back on…
Note from admin: Please use Markdown on code snippets for easier reading!
-
@cowboysdude could you please run the magic mirror from the terminal until it switches off and doesn’t switch back on, bring the monitor back with the command and post your screenshot of the terminal?
-
@alexyak Do you mean SSH or shell on the mirror?
-
Could you also run the
/opt/vc/bin/tvservice -s
when your monitor is on? -
@alexyak I did … I posted it above LOL
/opt/vc/bin/tvservice -s
I get this:
state 0x12000a [HDMI CEA (16) RGB lim 16:9], 1920x1080 @ 60.00Hz, progressive
-
@cowboysdude on the RPI.
-
@alexyak
/opt/vc/bin/tvservice -s
I get this:
state 0x12000a [HDMI CEA (16) RGB lim 16:9], 1920x1080 @ 60.00Hz, progressive
That’s where I was running it from and I still get the above
-
@cowboysdude so just to confirm, when you run the status command on the RPI you get this output, right?