I'm a tech enthusiast with about 30 years experience in IT. Recently I'm also a TRIGGERcmd developer.
@oloryn, I haven't made any recent changes to the Google Assistant integration, and it's still working for me.
One thing you could try is changing your computer's voice word to something simpler for Google to interpret. "Fili" isn't a common word, so I wonder if Google is hearing that as some other word.
@km, you could reduce the amount of vocal output if you put a space in the Voice Reply field for the command.
I don't think it's possible to remove the "here's trigger cmd" part. I've researched it and couldn't find a way.
I'm glad you told me it works with the original commands. These are the original commands:
[
{"trigger":"Reboot","command":"shutdown -r","ground":"background","voice":"reboot","allowParams": "false"},
{"trigger":"Gnome Editor","command":"gedit","ground":"foreground","voice":"edit","allowParams": "false"},
{"trigger":"yum update","command":"yum -y update","ground":"background","voice":"yum update","allowParams": "false"},
{"trigger":"apt update","command":"apt-get -y update","ground":"background","voice":"update","allowParams": "false"}
]
Can you paste your commands.json file here?
If the Reboot command works, then could you just try changing that to shutdown now instead of shutdown -r
Also - just to make sure you know - you need a comma at the end of any line except the last one.
@gabi92a, I found out why Fiddler wasn't working. For NodeJS apps like the TRIGGERcmd agent, you have to set these environment variables before you run the node src\agent.js --console command:
set https_proxy=http://127.0.0.1:8888
set http_proxy=http://127.0.0.1:8888
set NODE_TLS_REJECT_UNAUTHORIZED=0
That tells the NodeJS app to use Fiddler as a proxy server.
I found that here: https://weblogs.asp.net/dixin/use-fiddler-with-node-js
Can you try that? Maybe that will give us a clue.
Also, you could try running it after setting this variable to get a bunch of debug output:
set NODE_DEBUG=*
One thing you should know - the agent uses a websocket to connect to the server, and that connection doesn't use the https_proxy variable so Fiddler won't pick that up. The request that's giving us this error doesn't use websockets though, so that shouldn't matter for this troubleshooting.
Thanks @gabi92a, that's helpful, but I should have added some debugging output.
I added these lines:
console.log("Response from server:");
console.log(response);
console.log("Error from request:");
console.log(error);
Please try this updated code with these steps:
Also, it looks like you ran node install.js instead of npm install. What does that do?
@alvaro-gutierrez-romero, are you in Spain? @gabi92a is having the same problem and he's in Spain. I don't know yet if it's the location or something about spanish Windows computers. @gabi92a is a developer in Barcelona, so I'm hoping he can help me figure this out.
You can see our progress here:
https://www.triggercmd.com/forum/topic/461/unable-to-access-to-the-aplication/13
@gabi92a, thank you for testing. That narrows it down. I created a branch with updated dependencies for you to test (if you're willing). I'm hoping this solves the problem.
If that works, then I believe I can produce a new version that will work on spanish Windows computers.
@gabi92a, would you be willing to try this? This will run the agent without the GUI. I suspect the bug is in the GUI.
@da-panda, sorry. It's on my todo list, but no not yet.
@gabi92a, that's a good idea. It could be the Spanish language on the computer. If so I'm sure I can solve that because I should be able to reproduce it by switching my computer to Spanish. Thanks for that idea.
EDIT: I tried it - I installed Spanish language on my Windows 10 box and set my region to Spain. Unfortunately it still works for me.
Are you using Windows 10?
BTW, I appreciate you not giving up. I really want to solve this. Like you said, I'm loosing money.