Posts made by Russ

@Grzegorz-Musialik, yes, it still works. Please tell me more. Where are you getting stuck?

@Mittal-Makwana, nice, what command does that?

@Erik-Dominguez, I didn't even know Microsoft had added an ssh command to Windows. That's awesome!

Please try prefixing your ssh command with start, like this:

start ssh user@10.1.2.3

It worked for me.

@al-mastro, awesome. You're welcome. I'm glad that worked.

@al-mastro, please try this:

calc & "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" "http://192.168.0.229:3480/data_request?id=action&output_format=json&serviceId=urn:micasaverde-com:serviceId:HomeAutomationGateway1&action=RunScene&SceneNum=2"

For me it opened calculator and a Chrome tab with that full URL in it.

@ccd, awesome, I'm glad you got it working. Sounds like this is the command that worked:

su - pi -c 'pm2 start mm'

@benzil, I switched to a computer where Groove is my default mp3 player, and it worked for me to use the quoted full path to he mp3 file, but then I googled and found this page that suggested this command line:

cmd /c start "explorer.exe shell:C:\Program Files\WindowsApps\Microsoft.ZuneMusic_3.6.25021.0_x64__8wekyb3d8bbwe!Microsoft.ZuneMusic" "C:\Users\Russ\Music\03 - Take a Chance on Me.mp3"

@ccd, your triggercmdagent daemon is running as root, but I think you want that pm2 command to run as pi, so please try changing your command to this:

su - pi -c 'pm2 start mm'

That su command will run as root, then it will run the pm2 command as the pi user.

@Atmosphere, I'm going to try to make it so when you link your Google account to your TRIGGERcmd account it doesn't replace the link, it adds a link. That way you could have her link her Google account to TRIGGERcmd in the Home app, and you'll both be able to use the same TRIGGERcmd account.

Please confirm that would work for you.

Sorry this is taking forever. It's a difficult thing to do, but I'll make it a priority now. Your feedback helps.

EDIT: I started looking at the code and it's not going to be practical to allow multiple Google accounts to link to the same TRIGGERcmd account, so now I'm looking into the idea of being able to share a computer with another TRIGGERcmd user.

In the meantime, you could use her IFTTT account to trigger your TRIGGERcmd commands. I know it's a relative pain to set that up though.

EDIT2: I'm making progress on the ability to share your computers with other TRIGGERcmd users. @Atmosphere, when it's ready, you'll be able to share your computers with your wife's TRIGGERcmd account, and she'll be able to link her Google Home account to her TRIGGERcmd account.

EDIT3: I'm very close. I have a system for sharing your computer so another user can trigger your commands. So far the commands on the shared computer can only be triggered via the website though. I'll update the live system when I test it more and I get Google Assistant working.

@al-mastro, can I see your full command text or the batch file you're using? Also, are you using curl?

@benzil, try this. Just put the full path of the .mp3 file in quotes in the Command field, like this:

That worked for me.

@MarkW, awesome. I'm glad that worked.

@MarkW, for some reason it seems to be trying to use the old computer's ID, not the new one. I tried to reproduce this issue and I couldn't, but I'm running the latest version of the agent. Maybe that's the difference.

When you re-ran triggercmdagent, did you run this first?

sudo su - 

That would make sure you're root and your home dir is /root.

Also I suggest trying this:

1. Stop the agent again.
2. Delete the computer from the website again
3. Run sudo su -
4. Backup your commands.json file.
5. Delete your whole /root/.TRIGGERcmdData folder (including computerid.cfg)
6. Run triggercmdagent and paste in your token.
7. Start the agent.
8. Profit (hopefully)

@jaysimhb, I'm sorry, for security reasons, I built TRIGGERcmd to never store the actual commands in the cloud, so you would need access to your old laptop.
For the future, you'll want to keep a backup of this file:

%USERPROFILE%\.TRIGGERcmdData\commands.json

For example:
c:\Users\russ\.TRIGGERcmdData\commands.json

@Fernando-Mateos, now I understand your question. I hope this answers it:

https://assistant.google.com/services/a/uid/000000c97192e061?hl=es

You can use this format to execute commands in Spanish:

Preguntar a Ejecuta Comando que ejecute la calculadora

@MarkW, I'm confused because you said you edited the commands.json, but the one you cat'ed out has the default commands in it.

Here's one thing that could be wrong. I don't know if you know you need to "escape" any forward slashes with backslashes.
Here's an example for when the script is /root/t.sh:

  {"trigger":"touch","command":"\/root\/t.sh","ground":"background","voice":"t","allowParams": "false"},

You could try adding some debug output in the code block that executes when you get that "Failed while trying to add a trigger." error.
If you want to try that, edit the addCmd function in the /usr/share/triggercmdagent/app/src/agent.js file and add the two lines I added below (I marked them with <--- Add this line).

function addCmd(trigger,voice,voiceReply,allowParams,token,userid,computerid) {
  // Configure the request

  headers.Authorization = 'Bearer ' + token;
  options.headers = headers;
  options.url = urlprefix + '/api/command/save';
  options.method = 'POST';
  options.form = {'name': trigger, 'computer': computerid, 'voice': voice, 'voiceReply': voiceReply, 'allowParams': allowParams };

  // Start the request
  request(options, function (error, response, body) {
    if (!error && response.statusCode == 200) {
      // var computerid = JSON.parse(body).data.id;
      console.log('Added ' + trigger);
    } else {
      console.log(error);                                     <--- Add this line
      console.log(JSON.parse(body));                          <--- Add this line
      console.log('Failed while trying add a trigger.');
    }
  })
}

Then run systemctl restart triggercmdagent to pick up your change.
Then run journalctl -u triggercmdagent to view the full output.

I upgraded the forum from NodeBB 1.7.2 to 1.12.2 tonight. I had to take it down for a few minutes to do the upgrade. Sorry for the outage if you were trying to use it at the time.

@markw, if you bare with me, we'll figure this out. I my theory is you might be editing commands.json in your /home/pi/.TRIGGERcmdData folder but the background agent is using the /root/.TRIGGERcmdData folder. Can you check that?

When you run systemctl status triggercmdagent, it should give you output like this. Notice it's running with /root/.TRIGGERcmdData as a parameter. That means it's using the commands.json from that folder too.

root@garagepi:~/.TRIGGERcmdData# systemctl status triggercmdagent
● triggercmdagent.service - TRIGGERcmd Agent
   Loaded: loaded (/etc/systemd/system/triggercmdagent.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2019-09-20 16:17:03 UTC; 2 weeks 0 days ago
 Main PID: 273 (node)
   CGroup: /system.slice/triggercmdagent.service
           └─273 node /usr/share/triggercmdagent/app/src/daemon.js --run /root/.TRIGGERcmdData

@hellomiakoda, how can you tell it's timing out? Is that what it says in your %userprofile%\.TRIGGERcmdData\debug.log file?

Can you confirm you're running Windows 10 and the latest version of the TRIGGERcmd agent?

TRIGGERcmd is working fine for me, and a lot of other people. I've updated my Windows 10 PC to the latest updates. I'm also using the latest version of the TRIGGERcmd Windows agent.

These are a couple things you could try:

1. You could try removing and re-installing the agent.
2. Some antivirus software breaks the TRIGGERcmd agent. You could try disabling it temporarily to see if that makes it work.
3. You could reset your data with these steps:
   a. Rename your %userprofile%\.TRIGGERcmdData folder
   b. Go to this page https://www.triggercmd.com/user/computer/list and delete your computer.
   c. Right-click your TRIGGERcmd agent tray icon and click Quit
   d. Re-run the TRIGGERcmd Agent and log it in.
   e. Copy your commands.json file from your backed up .TRIGGERcmdData folder to your new .TRIGGERcmdData folder to restore your commands.