Topics created by hdegenaro

Sorry @hdegenaro, I saw this and forgot to respond.

You can say Alexa, ask TRIGGERcmd to open X if you use the TRIGGERcmd, TRIGGER command, or TC skills. This page shows the sentence format for those skills.

You can say, Alexa turn on X if you use the newer TRIGGERcmd Smart Home skill. This page shows the "Smart Home" skill sentence format.

Also, if you use an Alexa routine, you can use any word or phrase you want. For example I say, Alexa, open sesame to open my garage using a routine that translates "open sesame" to "ask TRIGGERcmd to run russ on garage" so it runs the command on my Raspberry Pi that opens my garage via the TRIGGERcmd skill.

@hdegenaro, good. Also thank you for subscribing.

Hello @Russ,

I found out what happened. First when I changed my machine name and then the name in the site's control panel, I don't know why, but the commands that were associated with Alexa's app routines lost their link. I think this is what you mentioned that could break TRIGGERcmd. Alexa interpreted the applied command, but did not open the files and applications. But there was an even bigger problem, because Alexa discovered other new commands associated with the other name I gave my machine, i.e the commands in Alexa were duplicated! I had to delete everything one by one it created. After that, I replaced a backup I had of the TRIGGERcmd commands (commands.json file) and let Alexa rediscover all the commands again. But it still couldn't figure out all the commands at once. I had to re-enable Alexa's TRIGGERcmd skill and ask it to find out the rest of the commands. So to finish, I had to reassociate all the commands again for each routine I had. Finally, with this I don't think to change my machine name anytime soon. It was a lot of work, it took me almost 2 hours to redo the process. In case it happens to someone, that can be of support so that no one gets lost at first like I was.

Regards,

@Russ Good morning, thanks for the return. The script that I put on the first line, works perfectly. It just turns off the lights on my keyboard and mouse. Can you help me?

It's just a matter of changing the command itself, mostly changing the /s to a /r.

If you type shutdown /? at the command prompt, it'll give you the full list of options.