MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.

    I cannot disable screen blanking with MagicMirrorOS

    Scheduled Pinned Locked Moved Unsolved Troubleshooting
    27 Posts 3 Posters 1.1k Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • karsten13K Offline
      karsten13 @sdetweil
      last edited by

      @sdetweil

      the setup is “Raspberry Pi OS Lite” with the normal docker setup and an additional labwc container

      @smegbadger

      I have no idea what is happening. Sounds like the monitor totally cuts the connection to the pi after a while.

      Maybe this post contains something helpful.

      What is your wlr-randr command for waking up?

      1 Reply Last reply Reply Quote 0
      • S Away
        sdetweil @smegbadger
        last edited by

        @smegbadger if you stop mmos does the screen still turn off overnight?

        Sam

        How to add modules

        learning how to use browser developers window for css changes

        1 Reply Last reply Reply Quote 1
        • S Offline
          smegbadger
          last edited by

          @sdetweil I stopped docker at 9:30 last night with docker compose down leaving the screen at the magicmirror login prompt. This morning the screen was still showing the login prompt . MM was reinstated perfectly with docker compose up -d --force-recreate. @karsten13 I notice there are now four objects that start:

          [+] Running 4/4
           ✔ Network magicmirror_default  Created                                                                            0.1s
           ✔ Container mm                 Started                                                                            0.9s
           ✔ Container init               Started                                                                            1.0s
           ✔ Container labwc              Started                                                                            1.0s
          

          Steve

          karsten13K 1 Reply Last reply Reply Quote 0
          • karsten13K Offline
            karsten13 @smegbadger
            last edited by

            @smegbadger

            the 4 objects are o.k., one network and 3 containers (init is only for setting correct permissions in the mount folders, it runs for a very short time, you can disable it in the .env file if wanted).

            Question: When the failed to connect to display occurs, how do you get the screen back working? Is a docker rm -f labwc && docker compose up -d sufficient or a docker compose up -d --force-recreate? Or do you have do reboot? Or do you switch the monitor off and on?

            Other idea is to implement a wlr-randr call every 30min. in the labwc container.

            1 Reply Last reply Reply Quote 0
            • S Offline
              smegbadger
              last edited by

              @karsten13 i have disabled the init container as suggested.

              When the display fails I can get it back with docker rm -f labwc && docker compose up -d (docker compose up -d --force-recreate also works but docker compose up -d on it’s own doesn’t). I am running it today with the MMM-Universal-Pir module disabled as another test (although when sitting at a login prompt it never went off).

              Note that the display fails after a few hours of no PIR trigger, it doesn’t have to be overnight.

              Steve

              karsten13K 1 Reply Last reply Reply Quote 0
              • karsten13K Offline
                karsten13 @smegbadger
                last edited by

                @smegbadger said in I cannot disable screen blanking with MagicMirrorOS:

                I can get it back with docker rm -f labwc && docker compose up -d

                so restarting only the labwc container solves the problem …

                I will try to build a labwc container which executes wlr-randr e.g. every 30min. so we can see if this helps.

                karsten13K 1 Reply Last reply Reply Quote 0
                • karsten13K Offline
                  karsten13 @karsten13
                  last edited by

                  @karsten13 said in I cannot disable screen blanking with MagicMirrorOS:

                  I will try to build a labwc container which executes wlr-randr e.g. every 30min. so we can see if this helps.

                  you can now test with a new labwc container which does the wlr-randr call every 15min. but I’m not sure this helps …

                  For testing change this line in the .env file

                  LABWC_IMAGE="karsten13/labwc:develop"
                  

                  and then do a docker compose pull && docker compose up -d

                  1 Reply Last reply Reply Quote 0
                  • S Offline
                    smegbadger
                    last edited by

                    @karsten13 unfortunately that change did not prevent the display from dropping. There’s no time timestamp in the docker logs for labwc but when i looked this morning there were some 40 calls to wlr-randr that had failed. If they are every 15mins that’s about 10:00 it failed. I will make a more accurate observation tonight

                    karsten13K 1 Reply Last reply Reply Quote 0
                    • karsten13K Offline
                      karsten13 @smegbadger
                      last edited by

                      @smegbadger

                      unfortunately that change did not prevent the display from dropping

                      I expected this already …

                      can you post the exact error message of wlr-randr when it fails?

                      Other point: What happens if you disable MMM-Universal-Pir for a test? Are you still getting the errors or does mm runs correctly over night?

                      karsten13K 1 Reply Last reply Reply Quote 0
                      • karsten13K Offline
                        karsten13 @karsten13
                        last edited by

                        for testing I added wlopm to the current mm-develop docker image.

                        So for another test use this lines in the .env file

                        MM_IMAGE="karsten13/magicmirror:develop"
                        LABWC_IMAGE="karsten13/labwc:develop"
                        

                        Then change the on/off commands in the config.js

                                                module: "MMM-Universal-Pir",
                                                position: "top_right",
                                                config: {
                                                        onCommand: "wlopm --on HDMI-A-1",
                                                        offCommand: "wlopm --off HDMI-A-1",
                                                }
                        

                        and then do a docker compose pull && docker compose up -d

                        1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 3
                        • 1 / 3
                        • First post
                          Last post
                        Enjoying MagicMirror? Please consider a donation!
                        MagicMirror created by Michael Teeuw.
                        Forum managed by Sam, technical setup by Karsten.
                        This forum is using NodeBB as its core | Contributors
                        Contact | Privacy Policy