@strawberry-3.141 I have a feeling that the camera is not properly captured from the client side js code. I am going to create a dev branch with a lot more logging soon.

It’s logging in the terminal window that you use to start the mirror with npm start. You can also start the mirror with “npm start dev” with dev tools and there will be the output from the chromium.

@cowboysdude so just to confirm, when you run the status command on the RPI you get this output, right?

@cowboysdude on the RPI.

Could you also run the /opt/vc/bin/tvservice -s when your monitor is on?

@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?

Was your monitor on when you were starting the magic mirror?

Ok, the next step let’s check whether the off state is detected correctly. After you switched off the monitor with the first command try to execute this in the ssh term:

/opt/vc/bin/tvservice -s

and let me know which output you see.

I am sorry to hear about your issues. Trying to think of the best way to troubleshoot that. The module doesn’t do anything fancy. It just executes these in the node_helper to switch on/of the output on HDMI:

Switch off:

/opt/vc/bin/tvservice -o

Switch-on:

/opt/vc/bin/tvservice --preferred && sudo chvt 6 && sudo chvt 7

As a first step, could you please try to execute these commands in the ssh terminal?

---

Note from admin: Please use Markdown on code snippets for easier reading!

@Ryroro could you try run the MM with dev tools and check the console out for errors.

npm start dev