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

    Raspberry Pi setup

    Raspberry Pi
    raspberry pi
    12
    40
    17.7k
    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.
    • George HatzisymeonG
      George Hatzisymeon
      last edited by George Hatzisymeon

      It looks like offCommand is never called using this PI/Debian distribution, do you have an update? Did you forget to include this functionality for Linux, it works fine on Windows.

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

        @George-Hatzisymeon, sorry I never responded to this. I just noticed it because someone upvoted it.

        I just verified that the offCommand commands.json value is supported in the current version of the Raspberry Pi agent. If you were using that version and it didn't work, then maybe you were missing this part:

        "allowParams":"true"
        

        Here's an example entry I just tested. It turns my led strip off if the parameter was off, and if the parameter was on, it turns the strip on and makes the leds green.

            {
               "trigger":"Green",
               "command":"\/root\/killrun.sh leds.py green",
               "offCommand": "\/root\/killrun.sh leds.py off",
               "ground":"background",
               "voice":"green",
               "allowParams":"true"
            },
        

        Russell VanderMey

        1 Reply Last reply Reply Quote 0
        • RussR Russ referenced this topic on
        • tuicemenT tuicemen moved this topic from Instructions on
        • tuicemenT tuicemen pinned this topic on
        • RussR Russ referenced this topic on
        • Dean McNaughtonD Dean McNaughton referenced this topic on
        • Dean McNaughtonD Dean McNaughton referenced this topic on
        • Dean McNaughtonD Dean McNaughton referenced this topic on
        • A
          Ar7hur
          last edited by

          What I did wrong? It appears:
          E: Unable to locate package https://agents.triggercmd.com
          E: Couldn't find any packageb by glob 'https://agents.triggercmd.com'
          E: Couldn't find any packageb by regex 'https://agents.triggercmd.com'

          I'm a noob, and sorry for my english.

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

            @Ar7hur, the URL to download the Raspberry Pi installer is this:

            https://agents.triggercmd.com/triggercmdagent_1.0.1_all.deb

            Does that answer your question?

            Russell VanderMey

            A 1 Reply Last reply Reply Quote 0
            • A
              Ar7hur @Russ
              last edited by

              @Russ I wrote this, but appears what I mentioned

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

                @Ar7hur, how do you get those errors? Can you please give me the command you typed, or paste a screenshot?

                Russell VanderMey

                A 1 Reply Last reply Reply Quote 0
                • A
                  Ar7hur @Russ
                  last edited by Ar7hur

                  @Russ It was my mistake. I discovered where was wrong😅 Sorry
                  How to create a trigger to turn off? and is there how to turn on the pi by voice command?

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

                    @Ar7hur, no problem. I'm glad you got it working.

                    You could create a trigger that runs shutdown --poweroff but it won't actually power the Raspberry Pi off. Raspberry Pi's also do not support wake-on-lan, so you couldn't power it on from another computer on your network like you could with a PC.

                    The only thing I can think of is you could power the Pi on/off with a relay by connecting/disconnecting the vbus on the 5volt power input with an adapter you could build with something like this, or you could use a smart plug to power it off/on. You could run a command that runs an Alexa routine that powers the smart plug on or off.

                    Russell VanderMey

                    1 Reply Last reply Reply Quote 0
                    • Jorge FuentesJ
                      Jorge Fuentes
                      last edited by

                      Hello, first of all thanks for this amazing integration/work.

                      I've a question:

                      Do you know if there's a way to add a parameter over the "commands.json" file in order to make Alexa speak when you execute the trigger? So she'll reply when you do a query. Would be great so it could be integrated with some bash scripts/ansible playbooks.

                      Thank you,
                      Kind regards.

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

                        @Jorge-Fuentes, yes, there is a way.

                        You can use the Voice Reply field to do that.

                        This article explains how.

                        Basically, put "{{result}}" in your voicereply field and run the sendresult script that the TRIGGERcmd agent installs here:

                        Windows:

                        %USERPROFILE%\.TRIGGERcmdData\sendresult.bat
                        

                        Linux / Mac:

                        ~/.TRIGGERcmdData/sendresult.sh
                        

                        I know you're on a Raspberry Pi, but I'm pasting the Windows GUI editor screenshot just to make sure the concept is clear.

                        f3d13688-7d34-434a-874d-2168e6ef7daa-image.png

                        In the runs list you can see what the "sendresult" script is sending back to the server as the "result" of the command you ran. If you include {{result]] in the Voice Reply field, The TC, TRIGGERcmd, or Trigger Command Alexa skills will say that text when you use one of those skills to trigger the command.
                        eb58845e-a91a-4835-bd03-15f7e9127f74-image.png

                        Instead of making the command in the commands.json file directly run the sendresult script, normally the commands.json would reference a script that would run the sendresult script last, and send back the value of an environment variable like this:

                        ~/.TRIGGERcmdData/sendresult.sh ${RESULT}
                        

                        The one problem with the above method is it uses one of the non-smart home TRIGGERcmd Alexa skills. Those skills are not as reliable at matching the words in the sentence pattern it uses to run the command. The TRIGGERcmd Smart Home Alexa skill does a much better job.

                        TC / TRIGGERcmd / Trigger Command Alexa skill pattern:

                        • Alexa, ask TRIGGERcmd to run Calculator

                        TRIGGERcmd Smart Home Alexa skill pattern:

                        • Alexa, turn on Calculator

                        If you want to use the TRIGGERcmd Smart Home skill to run your command, you use this method.

                        Russell VanderMey

                        Jorge FuentesJ 1 Reply Last reply Reply Quote 0
                        • Jorge FuentesJ
                          Jorge Fuentes @Russ
                          last edited by

                          That's brilliant, thank you for the information.

                          1 Reply Last reply Reply Quote 0
                          • RussR Russ referenced this topic on
                          • RussR Russ referenced this topic on
                          • First post
                            Last post