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

    Now you can get the result of a remote command in your API response.

    Announcements
    1
    1
    331
    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
      last edited by Russ

      Here's a Youtube video to demonstrate: https://youtu.be/q0Uu4SNFKFY

      You can use the https://www.triggercmd.com/api/run/triggerSave API or the tcmd tool to see the result of the remote command. The Youtube video shows me using the tcmd utility to call the API.

      Send the result back to the server using the SendResult.bat (or .sh) script in the .TRIGGERcmdData subfolder of your user's home folder.

      The script only has about 4 seconds to send the result.

      The SendResult script has to run in the context of a running remote command - generally as the last command in a script.

      Your command's "Voice Reply" field has to have {{result}} in it because that's the result's placeholder in the voiceReply field the API returns.

      EDIT 6/18/22: You can no longer get the result via the /api/run/triggerSave api. You can only get it via Alexa or Google Assistant. If you want it back in the api response, let me know.

      EDIT 9/15/23: Now you can get the result via the API again. Your response will look like this: Trigger sent. Result was: YourResult

      Russell VanderMey

      1 Reply Last reply Reply Quote 0
      • First post
        Last post