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-PythonPrint customisation

    Scheduled Pinned Locked Moved Solved Troubleshooting
    46 Posts 5 Posters 17.4k Views 5 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.
    • R Offline
      RobCee @sdetweil
      last edited by RobCee

      @sdetweil I haven’t managed to get it running yet.
      I did have some success (I had it printing Hello on the screen), but then the wheels came off and I have been unable to get it working again.

      I have reverted to the default configuration from your Github page to try and wiork out what is going on, but I am seeing the following in the logs:

      [11.04.2022 16:30.34.903] [LOG]   Connecting socket for: MMM-PythonPrint
      [11.04.2022 16:30.34.907] [LOG]   Starting module helper: MMM-PythonPrint
      [11.04.2022 16:30.43.341] [LOG]   MMM-PythonPrint received a socket notification: CONFIG - Payload: [object Object]
      [11.04.2022 16:30.43.346] [LOG]   PythonPrint spawning /opt/magic_mirror/modules/MMM-PythonPrint/printitonce.py
      [11.04.2022 16:30.43.531] [ERROR] Whoops! There was an uncaught exception...
      [11.04.2022 16:30.43.556] [ERROR] ReferenceError: data is not defined
          at ChildProcess.<anonymous> (/opt/magic_mirror/modules/MMM-PythonPrint/node_helper.js:20:65)
          at ChildProcess.emit (node:events:390:28)
          at Process.ChildProcess._handle.onexit (node:internal/child_process:288:12)
          at onErrorNT (node:internal/child_process:477:16)
          at processTicksAndRejections (node:internal/process/task_queues:83:21)
      

      Which seems to be the same error as before, but now I am not using any 3rd party modules, just the sample code.

      S 1 Reply Last reply Reply Quote 0
      • S Do not disturb
        sdetweil @RobCee
        last edited by

        @RobCee said in MMM-PythonPrint customisation:

        ReferenceError: data is not defined

        are u launching ‘python’ or python3?

        the default
        const python=‘python’

        Sam

        How to add modules

        learning how to use browser developers window for css changes

        R 1 Reply Last reply Reply Quote 0
        • R Offline
          RobCee @sdetweil
          last edited by

          @sdetweil I am using python3 and I have updated the two references to ‘python’ -> ‘python3’ to reflect this

          S 1 Reply Last reply Reply Quote 0
          • S Do not disturb
            sdetweil @RobCee
            last edited by

            @RobCee right, you don’t have to change the code, just use the config.js setting

            { 
            module:
                 config: {  
                     pythonName:'python3',
                }
            }
            

            Sam

            How to add modules

            learning how to use browser developers window for css changes

            R 1 Reply Last reply Reply Quote 0
            • R Offline
              RobCee @sdetweil
              last edited by

              @sdetweil ok, I will try it there then and see what happens.
              Tracking down errors in this MM OS is fun…

              S 1 Reply Last reply Reply Quote 0
              • S Do not disturb
                sdetweil @RobCee
                last edited by sdetweil

                @RobCee o, I see that I have a potential bug… if the command: is not configured,
                it defaults to “”… oops…

                I just pushed an update got that

                git pull in the module folder

                to debug

                add debug: true

                and then look where u start MM… (this doing npm start )

                [11.04.2022 10:55.13.087] [LOG]   MMM-PythonPrint received a socket notification: CONFIG - Payload: [object Object]
                [11.04.2022 10:55.13.087] [LOG]   PythonPrint spawning modules/MMM-PythonPrint/printit.py
                .
                .
                .
                .
                [11.04.2022 10:55.18.114] [LOG]   PythonPrint sending program output=hello
                

                Sam

                How to add modules

                learning how to use browser developers window for css changes

                R 1 Reply Last reply Reply Quote 0
                • R Offline
                  RobCee @sdetweil
                  last edited by

                  @sdetweil I will have a go with that, but I think I have a slightly different problem of my own making.

                  S 1 Reply Last reply Reply Quote 0
                  • S Do not disturb
                    sdetweil @RobCee
                    last edited by sdetweil

                    @RobCee ok, I also fixed the use of the pythonName and added it to the debug message

                    [11.04.2022 11:04.20.218] [LOG]   PythonPrint spawning modules/MMM-PythonPrint/printit.py using python3
                    .
                    .
                    .
                    .
                    [11.04.2022 11:04.25.244] [LOG]   PythonPrint sending program output=hello
                    

                    Sam

                    How to add modules

                    learning how to use browser developers window for css changes

                    1 Reply Last reply Reply Quote 0
                    • R Offline
                      RobCee
                      last edited by

                      I’m not sure why, as I did manage to get it working at one point, but I think the issue is that I am using the MM OS Docker image to run all this.
                      I think this means that the path expectations are different from the assumptions that I am making.
                      I may have to give in and just build the whole thing manually - it will probably be quicker than trying to fault find the install, given it’s obfuscation.

                      S 1 Reply Last reply Reply Quote 0
                      • S Do not disturb
                        sdetweil @RobCee
                        last edited by

                        @RobCee yes, docker paths and if OUTSIDE the MM tree, then YOU have to add new volume statements to the docker setup to map them

                        Sam

                        How to add modules

                        learning how to use browser developers window for css changes

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