@rgr66, I found your paypal transactions. I sent you a private message via chat.

@schmuttis, I know the Wyze cameras can trigger Alexa routines, but it requires a subscription to do that.

No problem at all @Smart-Communities. I'm glad you asked.

@Ricardo-Ferreira, I see you cancelled already. I'll send you your paypal email address.

@João-Pedro-Vital, sorry it didn't work out.

@Benny-Grahn, would you mind sharing your solution? Did you use a bookmark URL?

@David-Hess awesome. Thank you!

@Russ Yes it worked, thank you very much

@Russ Thanks Russ

@armando-martinez, you have to delete your token.tkn file, then close and open the TRIGGERcmd agent. It will prompt you for a new token. Your token.tkn file is here: C:\Users\(username)\.TRIGGERcmdData\token.tkn Uninstalling the agent will not delete the token file.

@FoxxxDie, you can find the Subscribe button at the bottom of the Instructions page.

@Russ , I did a bit more playing with routines and follow up mode. You can't run another routine after one or activate a device after with out saying Alexa first, but you can run a routine after a device trigger. If in a routine you add a say command asking "do you wish anything else?" then you can say "yes, Alexa, run....." or "no, Alexa, thank you" and she will respond to both. Doing this you could make it seem more like Alexa is interacting.

@Dimo-Ninov, which TriggerCMD skill are you using? Both the TriggerCMD and Trigger Command, require the "Alexa, ask Trigger CMD to....." The Triggercmd Smart Home skill does not. You simply say "Alexa, turn on(off) ...." Russ created a forth skill called TC to simplify things but the original TriggerCMD and Trigger Command still remain in the Alexa skills list.

@Smart-Communities, I moved that "Trigger sent. Refresh page to send again." message up to the top. Keep the requests coming. They help. I still plan to update the agent soon with the ability to name the computer during install. BTW, I noticed bookmark URL's weren't running the Alexa routine I had associated with my command. I fixed that too.

@Smart-Communities, I know this isn't exactly what you were thinking, but I'm using your IP address placeholder idea in this video as an example of one way to share scripts with placeholders for things like IP address you'd store in config files. You could run a command like this remotely or locally to configure the IP: roku ip 192.168.1.10 Then a command like this to simulate the down button on your roku remote: roku keypress down This article give a list names of other roku buttons. @rem roku.bat @echo off echo %1 %2 %3 %4 if "%1"=="ip" goto :configip if "%1"=="keypress" goto :keypress if "%1"=="0" goto :findremote if "%1"=="off" goto :findremote goto :done :configip echo|set /p="%2" > c:\tools\rokuip.config goto :done :keypress set /p IP= < c:\tools\rokuip.config curl -XPOST http://%IP%:8060/keypress/%2 goto :done :findremote set /p IP= < c:\tools\rokuip.config curl -XPOST http://%IP%:8060/keypress/FindRemote goto :done :done echo Done. This video shows that, and shows how to pass a number from 0 to 100 with Alexa using the TRIGGERcmd Smart Home skill by saying: Alexa, roku on tv zero. That works because Alexa interprets that as setting the dim level to 0 for the "roku on tv" device because roku is the command's voice word and tv is the computer's voice word. Be aware if you use Google Assistant, when you say 0 it sends off as the parameter because it figures if you're setting the dim level to 0 percent, that's off. That's why I added this line after I recorded that video: if "%1"=="off" goto :findremote In hindsight 0 / off seems pretty arbitrary to assign to the making your Roku remote start beeping. Also I acknowledge this a script so it's coding, so it doesn't solve the problem in the original post.

@Smart-NET I personally haven't done this with mine, but what I'd recommend you do is upload a copy of the config file to a git repository. You could pull it down automatically, then