Voice command only works with old computer name
-
Hi,
I changed the name of my computer and did a test by changing the name of it in the triggercmd panel. I found that the voice commands do not work. What should I do to keep my computer name on the site?
Thanks.
-
@hdegenaro, you should be able to do all of these things without breaking TRIGGERcmd:
- Change your computer name locally on your computer
- Change your computer name in your TRIGGERcmd account on the website.
- Change your computer's voice word in your TRIGGERcmd account on the website.
Do your commands work if you click the green Trigger button on the website?
Also, do you use Alexa or Google Assistant? And are you using one of the Smart Home skills or one of the non-Smart Home skills? -
Hi @Russ, I followed the 3 steps described, changing my computer name and entering the word "Alexa" from my virtual assistant. After that, I clicked on the green "trigger" button for each item and everyone opened the apps and files. It works with the green button, but it doesn't work with the voice command.
-
@hdegenaro, ok good that narrows it down.
Assuming you're using the TRIGGERcmd Smart Home Alexa skill, and you say "Alexa, turn on Calculator" what happens? Also do you see a device for each command in the Alexa app or at https://alexa.amazon.com? They would be under "all devices."
-
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,
