TRIGGERcmd
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    PS4-Waker troubleshooting

    Mac
    5
    11
    887
    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.
    • RussR
      Russ @BetoFuenzalida
      last edited by Russ

      @BetoFuenzalida, did you install ps4-waker using a -g like this?

      npm i -g ps4-waker
      

      That should allow you to run ps4-waker from any directory so you don't have to worry about specifying the full path.

      Also, if you want to add a log file so you can see any errors, you can make your command something like this (this will capture stdout and stderr):

      ps4-waker 1> c:\logs\ps4-waker.log 2>&1
      

      Russell VanderMey

      1 Reply Last reply Reply Quote 0
      • R
        Rafa
        last edited by Rafa

        Hi @Russ , how are you?

        I'm having the same issue.

        How this log command looks like in macOS?

        RussR 1 Reply Last reply Reply Quote 0
        • RussR
          Russ @Rafa
          last edited by Russ

          @Rafa, on a mac you can do this:

          On my mac I typed: which ps4-waker
          I saw this output: /usr/local/bin/ps4-waker
          Then I ran this: ls -al /usr/local/bin/ps4-waker
          And I saw something like this: /usr/local/bin/ps4-waker -> ../lib/node_modules/ps4-waker/dist/cli.js
          So I knew the path for ps4-waker's cli.js file is /usr/local/lib/node_modules/ps4-waker/dist/cli.js
          I typed this to find my Node JS executable: which node
          It showed me this path: /Users/russ/.nvm/versions/node/v8.17.0/bin/node

          I made ps4-waker my command in the TRIGGERcmd GUI editor this:
          /Users/russ/.nvm/versions/node/v8.17.0/bin/node /usr/local/lib/node_modules/ps4-waker/dist/cli.js > ~/Desktop/ps4-waker.log 2>&1

          This part is meant to log the output of the ps4-waker command: > ~/Desktop/ps4-waker.log 2>&1

          When I looked at the log I saw this:
          Could not detect any matching PS4 device

          Your paths will likely be different depending on the output of your which commands.

          Another way to find the path to your cli.js file is this command: find / | grep ps4-waker/dist/cli.js

          Russell VanderMey

          1 Reply Last reply Reply Quote 0
          • Bráulio BetônicoB
            Bráulio Betônico
            last edited by Bráulio Betônico

            @Russ

            if I type in the terminal, the system runs normally, I still linked the triggnercmd on Alexa Amazon, it recognizes the APP, she (Alexa) says she recognized a new APP, but it doesn't trigger the PS4. But, when I go to the terminal and type ps4-waker turns on, and ps4 waker standby it goes to sleep, but by the triggercmd command, it doesn't work, I've uninstalled it several times, I redid all the configuration and nothing. Anyone to help?alt textalt textalt textalt textalt textalt textalt text

            RussR 1 Reply Last reply Reply Quote 0
            • RussR
              Russ @Bráulio Betônico
              last edited by

              @Bráulio-Betônico, please show me the output of this command:

              which node
              

              If it shows something like /Users/russ/.nvm/versions/node/v8.17.0/bin/node, then your full command should be:

              /Users/russ/.nvm/versions/node/v8.17.0/bin/node /usr/local/lib/node_modules/ps4-waker/dist/cli.js
              

              Russell VanderMey

              1 Reply Last reply Reply Quote 0
              • Bráulio BetônicoB
                Bráulio Betônico
                last edited by

                alt text @Russ

                1 Reply Last reply Reply Quote 0
                • Bráulio BetônicoB
                  Bráulio Betônico
                  last edited by

                  @Russ It worked out! I love you!

                  1 Reply Last reply Reply Quote 0
                  • Bráulio BetônicoB
                    Bráulio Betônico
                    last edited by

                    @Russ Thank you very, very much! I am really happy! Would you have a command to put it to sleep?

                    RussR 1 Reply Last reply Reply Quote 0
                    • RussR
                      Russ @Bráulio Betônico
                      last edited by

                      @Bráulio-Betônico, awesome. I'm glad that worked.

                      I looked up the documentation here and I see this is the command to put the PS4 on standby:

                      ps4-waker standby
                      

                      So in your case:

                      /usr/local/bin/node /usr/local/lib/node_modules/ps4-waker/dist/cli.js standby
                      

                      Russell VanderMey

                      1 Reply Last reply Reply Quote 0
                      • Bráulio BetônicoB
                        Bráulio Betônico
                        last edited by

                        @Russ said in PS4-Waker troubleshooting:

                        /usr/local/bin/node /usr/local/lib/node_modules/ps4-waker/dist/cli.js standby

                        Thank you very much. worked correctly.

                        1 Reply Last reply Reply Quote 1
                        • tuicemenT tuicemen referenced this topic on
                        • First post
                          Last post