@Leonardo-Felix-dos-Santos, yea Felps does a good job on his videos.
Of course this one is my favorite.
I'm a tech enthusiast with about 30 years experience in IT. Recently I'm also a TRIGGERcmd developer.
@Lucas-Hortale, sure. You can run many commands if you create a script, and have your command run the script:
Assuming you're on Windows you could make a c:\tools\websites.bat script with these contents:
start https://www.triggercmd.com start https://www.google.com
Then make this command: c:\tools\websites.bat
Or, if you want to be lazy you could use a & between two commands like this:
I also found you can still download the Thinking Home software here, but it's not supported anymore.
I haven't tried either one myself yet.
Terminology-wise, a "batch file" is a .bat file and only works on Windows. For Mac and Linux you'd want to make a bash script (usually with a .sh extension) like this:
#!/bin/bash if [ "$1" == "off" ] then echo turn light $1 >> /tmp/on_off.log # Put your command to turn the light **off** here. else echo turn light $1 >> /tmp/on_off.log # Put your command to turn the light **on** here. fi
You'd create that file (/Users/(your user)/on_off.sh for example) then make it executable with a command like this:
chmod +x /Users/russ/on_off.sh
Enable parameters on your command so TRIGGERcmd will add a on or off parameter to the command that runs the script via the TRIGGERcmd Smart Home Alexa Skill or Google Assistant Action.
Your command would be the full path to the script, like this: /Users/russ/on_off.sh
@clarkzara, I'm glad you got it working.
There's no problem installing the agent on a VM - I've done it many times.
Connecting through a proxy is a problem though. I've tried to add support for a proxy server, but so far I haven't had much luck.
@André-Ricardo-da-Costa, have you tried uninstalling the program first? I have seen problems trying to run the installer while the program is installed. I assume you already tried the "Update Agent" option.
When you uninstall the agent, it won't delete your data files in c:\users\(your user)\.TRIGGERcmdData, but it also doesn't hurt to take a backup of that.
One more thing you could try is temporarily disable your anti-virus software while you install it. I've seen certain AV software break the install, including Avast.
@Diego-Alonso-Aldave-V, please try these two things:
Remove the · from your computer name. I saw in the log that the system is having a problem finding your computer, and I think that's why.
Delete or rename your reboot command because I see you have two of them. Maybe one got added while it was set as a background command and the background service was working.
@clarkzara, you definately could do that. Please tell me what you've tried.
It looks like you could create a command with this format:
UiRobot.exe execute [--process <Package_ID> | --file <File_Path>] [--folder <Orchestrator_Folder_ID>] [--input <Input_Parameters>]
You might need to specify the full path to the UiRobot.exe file though. Like if it's in your c:\tools folder, you'd make your command: c:\tools\UiRobot.exe execute ....
That said, what exactly are you saying to Alexa? I just said these and they both worked for me:
@mayron and I talked over chat and it's working for him now. I tested it too. We just had to press enter at that Warning prompt, then paste in the token. I'll try to get rid of that warning, but at least it works as-is.
I think one of the packages was updated to the latest version which introduced that warning message.
@mayron, thanks for reporting this.
The package.json that's in-place now might be the windows version. Please try copying the ubuntupackage.json or redhatpackage.json file over-top of package.json like this:
cp ubuntupackage.json package.json
Then try npm install again.
I don't have time right this minute to test it. I'll add a archbuild.sh file to that repo once I know which package.json works.