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.

    MMM-Pir

    Scheduled Pinned Locked Moved Solved Troubleshooting
    34 Posts 5 Posters 4.1k Views 6 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.
    • P Offline
      Peter @gonzonia
      last edited by

      @gonzonia before installing did you follow all the tips mentioned by sdetweil?
      Peter

      bugsounetB G 2 Replies Last reply Reply Quote 0
      • bugsounetB Offline
        bugsounet Banned @Peter
        last edited by

        Can you check new ReadMe

        I haven’t had time to create a topic for the new release of MMM-Pir v2 yet, sorry

        G 1 Reply Last reply Reply Quote 0
        • G Offline
          gonzonia @Peter
          last edited by

          @Peter Yes. Because I was getting an error when I tried installing.

          1 Reply Last reply Reply Quote 0
          • G Offline
            gonzonia @bugsounet
            last edited by

            @bugsounet
            I installed v 2 successfully. Everything seemed to be working with my old config (posted above). I tried updating based on the new readme, but now it won’t come back on.

            I did have the wrong GPIO originally, but now it should be correct.

            {
            		  module: 'MMM-Pir',
            		  position: 'top_left',
            		  classes: 'SceneFamily SceneSam',
            		  config: {
            			debug: false,
            			Display: {
            					timeout: 2 * 60 * 1000,
            					animate: true,
            					style: 0,
            					colorFrom: "#FF0000",
            					colorTo: "#00FF00",
            					mode: 2,
            					counter: true,
            					lastPresence: false,
            					lastPresenceTimeFormat: "LL H:mm",
            					availability: false,
            					autoDimmer: false,
            					xrandrForceRotation: "left"
            				},
            				Pir: {
            					mode: 0,
            					gpio: 20
            				},
            				Cron: {
            					ON: [],
            					OFF: []
            				},
            				Touch: {
            					mode: 0
            				},
            				Governor: {
            					sleeping: 4,
            					working: 2
            				},
            				Sounds: {
            					on: 0,
            					off: 0
            				}
            			}
            		},
            
            htilburgsH 1 Reply Last reply Reply Quote 0
            • htilburgsH Offline
              htilburgs @gonzonia
              last edited by

              @gonzonia Are you using X11 or Wayland?
              Because now you’re using mode 2 and that’s for X11

              (still trying to learn JS, but not afraid to ask) ☺

              G 1 Reply Last reply Reply Quote 0
              • G Offline
                gonzonia @htilburgs
                last edited by

                @htilburgs yes. I was using mode 9 in the old version. When I looked it up I thought that’s what corresponded. Im on Pi OS 11 and Wayland is for 12 according to the read me

                G 1 Reply Last reply Reply Quote 0
                • G Offline
                  gonzonia @gonzonia
                  last edited by

                  I think I had the GPIO correct originally. Went back to that and it’s working.

                  htilburgsH 1 Reply Last reply Reply Quote 0
                  • htilburgsH Offline
                    htilburgs @gonzonia
                    last edited by

                    @gonzonia
                    Ok 👍 succes.

                    (still trying to learn JS, but not afraid to ask) ☺

                    1 Reply Last reply Reply Quote 0
                    • G Offline
                      gonzonia
                      last edited by

                      Okay, sorry to revive this. I saw there was an update available so I went to update.

                      I did a git pull and got this

                      hint: Pulling without specifying how to reconcile divergent branches is
                      hint: discouraged. You can squelch this message by running one of the following
                      hint: commands sometime before your next pull:
                      hint: 
                      hint:   git config pull.rebase false  # merge (the default strategy)
                      hint:   git config pull.rebase true   # rebase
                      hint:   git config pull.ff only       # fast-forward only
                      hint: 
                      hint: You can replace "git config" with "git config --global" to set a default
                      hint: preference for all repositories. You can also pass --rebase, --no-rebase,
                      hint: or --ff-only on the command line to override the configured default per
                      hint: invocation.
                      From https://github.com/bugsounet/MMM-Pir
                         3a5bcdb..1fee537  master     -> origin/master
                         fc5b3f6..658a322  dev        -> origin/dev
                      Updating 3a5bcdb..1fee537
                      error: Your local changes to the following files would be overwritten by merge:
                      	MMM-Pir.js
                      	components/cronJob.js
                      	components/governorLib.js
                      	components/motion.js
                      	components/motionLib.js
                      	components/pirLib.js
                      	components/screenDisplayer.js
                      	components/screenLib.js
                      	components/screenTouch.js
                      	node_helper.js
                      Please commit your changes or stash them before you merge.
                      Aborting
                      
                      

                      The thing is, I know I have made NO CHANGES to any of those files.
                      Should I run a pull.rebase? Would that fix it ?

                      G 1 Reply Last reply Reply Quote 0
                      • G Offline
                        gonzonia @gonzonia
                        last edited by

                        I just did a reinstall for now, but I would like to know what I should do to fix this in the future

                        S 1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 3
                        • 4
                        • 4 / 4
                        • 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