TRIGGERcmd
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Monty
    3. Posts
    M
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 5
    • Best 1
    • Controversial 0
    • Groups 0

    Posts made by Monty

    • RE: Background Daemon Install Errors

      Well, everything seems to be working! If something is missing, I haven't run across it yet, despite those error messages. I can boot my computer and when everything is done starting, I can say "Alexa, run Sling TV" and up it pops in a Chromium (Linux) window; which was what I wanted. I haven't tried to find things that don't work yet, as I am enjoying those that do!

      As to running automatically, I simply added a command in the Linux Mint "Startup Applications" list with a 25 second delay:

      triggercmdagent

      That puts an icon on my status panel. If I right click it, I have options for:

      TriggerCMD.com
      Background Service
            Start Background Service
            Remove Background Service
      Text Command Editor
      GUI Command Editor
      Quit
      

      I have not done anything with those two Background Service controls as things appear to be working as I want them to.

      Thanks for the great support!

      Monty

      posted in General Discussion
      M
      Monty
    • Background Daemon Install Errors

      Running Linux Mint, I wanted to have everything ready to go when I booted, so assumed I needed to have the background daemon running. I checked with "systemctl status triggercmdagent" and got this msg:

      ● triggercmdagent.service - TRIGGERcmd Agent
      Loaded: loaded (/etc/systemd/system/triggercmdagent.service; enabled; vendor preset: enabled)
      Active: failed (Result: start-limit-hit) since Wed 2021-06-16 13:44:27 MST; 7min ago
      Process: 1906 ExecStart=/usr/bin/env node /usr/lib/triggercmdagent/resources/app/src/daemon.js --run /root/.TRIGGERcmdData (code=exited, status=0/SUCCESS)
      Main PID: 1906 (code=exited, status=0/SUCCESS)

      Jun 16 13:44:27 main systemd[1]: triggercmdagent.service: Scheduled restart job, restart counter is at 5.
      Jun 16 13:44:27 main systemd[1]: Stopped TRIGGERcmd Agent.
      Jun 16 13:44:27 main systemd[1]: triggercmdagent.service: Start request repeated too quickly.
      Jun 16 13:44:27 main systemd[1]: triggercmdagent.service: Failed with result 'start-limit-hit'.
      Jun 16 13:44:27 main systemd[1]: Failed to start TRIGGERcmd Agent.

      I then assumed I needed to run "installdaemon.sh". That appeared to run and install ok, but now I have two "main" computers in my computer list. Doesn't look right, LoL.

      I am really just trying to get triggercmdagent ready and willing to roll when I boot the PC w/o heading to the CLI and messing around. Do I need to start over, or is this salvageable?

      Great program but it is taking me a bit to get my head wrapped around how it works!

      Thanks,

      Monty

      posted in General Discussion
      M
      Monty
    • RE: A simple "Alexa, run text editor" works!?

      @Russ Yes, that's it! I just tried other voice commands and they work as well, ie "Alexa, run Paramount Plus" and it opens the browser and link to that site. Great! Thanks!

      But I have another issue, probably of my klutzing and just trying things, but will start a different thread.

      Again, thanks!

      Monty

      posted in General Discussion
      M
      Monty
    • A simple "Alexa, run text editor" works!?

      I am new to triggercmd, but got things started using it to control some programs and open web pages on my Linux PC.

      I started by opening Xed, the default text editor in Linux Mint 20.1. I had of set up the Linux agent, and added the Alexa skill "Trigger Command".

      I used "Text Editor" as both the trigger and the voice command, and simply "xed" in the command field.

      Then, misunderstanding how to trigger Alexa properly, I simply said "Alexa, run text editor". I immediately saw a blank document open in the xed default text editor on my desktop!

      I thought this was pretty cool. But when I tried that "Alexa, run ...." with other programs and websites, nothing worked.

      I have since figured out I need to use "Alexa, tell trigger command to open/run (whatever)". A mouthful, but it works.

      But why is xed opening with a simple "Alexa, run text editor"? It is coming from triggercmd, because when I delete the trigger entirely in the command editor, it does not work and Alexa says something about "nothing to do". So there is some kind of connection but I cannot find it.

      I mean if xed will run with a simple "run" command, why not gedit, or gnote. Tried them, but they will not work with the "run" only voice command, but will with the full "tell trigger command" trigger. Oh, the "voice response" from Alexa does NOT work when using the "run" command, but does using the normal "tell trigger command".

      It would be nice, of course, to use a simple "run" for everything I would like Alexa to control on my PC. I mean I think triggercmd is a powerful tool to enable 'voice shortcuts', and have registered for a years worth because I can use it.

      But this "run" thing for xed has me baffled. Any ideas?

      Thanks,

      Monty

      posted in General Discussion
      M
      Monty
    • Sending keyboard commands?

      Using Linux Mint 19.1 Cinnamon flavor. Looking for something I can use with my Alexa devices to control/send keyboard commands to the Linux PC.

      For example, I would like to say something like:

      "Alexa, trigger workspaces on the PC"

      and that would send the CTRL-ALT-Up Arrow (or any other desired keyboard combination I choose) to the PC.

      Can this, or something close, be done with triggercmd?

      Thanks!

      Monty

      posted in General Discussion
      M
      Monty