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

    Shutdown function

    Windows
    2
    4
    1.6k
    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.
    • RobertofilhoR
      Robertofilho
      last edited by

      Hello Russ, sorry to bother you, but is the windows shutdown function working on Alexa? I haven't been able to use it for a few days, if everything is normal, I'm sorry I was in doubt

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

        @Robertofilho, I just tested Alexa and it's working for me. Are other commands working for you?

        The shutdown command requires the background service to be running. On Windows you can search for services then scroll down to TRIGGERcmdAgent.

        7485f42e-bf72-4994-83d1-7aade7b04bc0-image.png

        If you don't see it there, you haven't installed it yet. You can install it by right-clicking the TRIGGERcmd icon in your tray, then click Background Service, Install Background Service.

        622ae89f-a94b-4e90-ab4c-71e38fe458ec-image.png

        Russell VanderMey

        1 Reply Last reply Reply Quote 0
        • RobertofilhoR
          Robertofilho
          last edited by

          None of the skills are working, shutting down, blocking ... I reinstalled the program but it remains the same, I have already installed the Background Service and nothing ... the service is "stopped" is it normal Rus?

          Screenshot_29.png

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

            @Robertofilho, I think something is wrong in your TRIGGERcmd agent's configuration. Uninstalling and re-installing doesn't delete the configuration. Please try this:

            1. Delete or rename your .TRIGGERcmdData folder in C:\Users\(your user).
            2. Delete your computer from your account.
            3. Close and re-run the TRIGGERcmd Agent.
            4. It will prompt you again for the token. Copy/paste that from the Instructions page in your account.

            After that, you should be able to run commands again, and if you restart the background service it should stay running and you can run background commands.

            Russell VanderMey

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