Alexa doesn't find the commands
-
@buzz, please confirm you're using the TRIGGERcmd Smart Home Alexa skill, not the TRIGGERcmd or TRIGGER command skill.
https://www.triggercmd.com/forum/topic/30/list-of-ways-to-trigger-your-commands
If you're not using the Smart Home skill, that would explain why you can't find your commands when you scan for devices.
-
you got it right, I didn't have the TRIGGERcmd Smart Home skin installed, the one that was active was the other two you mentioned. Now it worked, thank you very much.
-
@buzz, awesome. I'm glad that worked.
-
Hi! I began installed TRIGGERcmd Smart Home skin on Alexa (Portuguese Brasil). I installed in my Windows 10 app, signed the account, add commands "Shutdown", "Reboot" in GUI Commands. When I had vinculed the TRIGGERcmd Smart Home skin with Amazon Count to active skill, it doesn't find the devices "Shutdown" and other commands like device on Alexa app.
I tryed many times to desactivated and active the skill but continues doesn't find! Sorry by my english.... But please help-me here to can help others people in Brazil to avoid them complain that skill it's bad here. -
@gtrento Amigo: Eu sou brasileiro também e posso te dar alguma ajuda. Faça assim, crie uma rotina no app Alexa e coloque desligar Pc ou algo de sua preferência. Na ação adicione o dispositivo "shut down" e clique em salvar. Para achar qualquer comando do Trigger CMD procure por dispositivo de casa inteligente em "todos os dispositivos" O meu ficou assim nesse caso. Se você criar o comando no Trigger em português a Alexa vai reconhecer e não necessariamente vai precisar criar uma rotina para cada comando do Trigger. E mais para os comandos em inglês que o Trigger já tem pré-configurado
-
@André-Ricardo-da-Costa , muito obrigado pela atenção. O que acontecia, era que não aparecia os comandos adicionados do Agente instalado no windows 10 nos dispositivos de casa inteligente no app Alexa no celular. Mas aí eu descobri que quando fazia um Update no agente, ele atualizava no Alexa. Consegui criar rotinas para desligar e dar reboot no PC. Agora estou apanhando para fazer ligar com o comando wakeonlan {mac address}. Consegui fazer funcionar com um app de android no celular, mas por esse Triggercmd Smart Home, tá dificil!
-
@gtrento No meu deu certo de ligar o PC por meio da WAKE ON LAN, seguindo o passo a passo do vídeo https://www.youtube.com/watch?v=UCyC-LjA9p8 e além disso, precisei fazer um passo a mais para funcionar, foi fazer o seguinte: Painel de Controle-> Hardware e Sons->Opções de Energia -> Escolher a função dos botões de energia -> configuração de desligamento -> desmarcar a primeira opção "ligar inicialização rápida". Outra coisa a se fazer é atualizar a placa de rede. Espero que dê certo. vlw.
-
@gtrento Cara, estou com esse mesmo problema, como você fez para que os comandos aparecessem na Alexa?
-
@Igor-Sales, you probably used the wrong Alexa skill. You want the "TRIGGERcmd Smart Home" skill:
https://www.amazon.com.br/VanderMey-Consulting-LLC-TRIGGERcmd-Smart/dp/B07P1MMFRP
-
@André-Ricardo-da-Costa rapaz, to com problema pra conseguir fazer ela desligar o pc. Primeiro pq a versão do meu windows 7 home é 32bit, então já foi díficil dar os comandos pelo bloco de notas, mas no fim a alexa conseguiu reconhecer apenas 2 comandos, o padrão de abrir o bloco de notas e também identificou o de desligar, porém quando dou o comando de voz, a Alexa entede, mas não desliga. Sabe o que pode ser?
-
@pedromatos_rj said in Alexa doesn't find the commands:
rapaz, to com problema pra conseguir fazer ela desligar o pc. Primeiro pq a versão do meu windows 7 home é 32bit, então já foi díficil dar os comandos pelo bloco de notas, mas no fim a alexa conseguiu reconhecer apenas 2 comandos, o padrão de abrir o bloco de notas e também identificou o de desligar, porém quando dou o comando de voz, a Alexa entede, mas não desliga. Sabe o que pode ser?
Assuming you're using the "TRIGGERcmd Smart Home" skill, please tell me if you see your commands as devices on this page:
https://alexa.amazon.com/spa/index.html#appliances
If they don't show up there even after you click Remove All, then Discover on that page, then I suspect your computer isn't setup as your default computer in your account profile, or maybe you didn't fill in the voice field for the computer.
-
Caras, também estou tendo problemas.
Tenho dois computadores, um Windows e um Macbook. Nenhum dos dois está sincronizando os comandos com a Alexa.Eu estou usando o TRIGGERcmd Smart Home e ele funcionou nos primeiros minutos, mas parece que os dois computadores pararam de se comunicar com a Alexa e o TriggerCMD Web, pq agora nenhum comando funciona nem é adicionado a Alexa. Dicas?
EDIT 1: Aparentemente um dos comandos no Macbook era para Windows. Imagino que por isso não estava sincronizando, pq quando adicionei um de Macbook este foi sincronizado com a Alexa. Ainda assim, os comandos não estão funcionando na Alexa.
EDIT 2: O Macbook realmente está sincronizando, mas não posso dizer o mesmo do Windows. Não importa o que eu faça, os comandos do Windows não aparecem na Alexa, e nenhum comando funciona em nenhum dos PCs.
EDIT 3: Eu desinstalei o TriggerCMD e removi as pastas dele de AppData/Roaming e AppData/Local. Reinstalei, não funcionou. Atualizei, não funcionou. Instalei o serviço de background, também não funcionou.
EDIT 4: Depois de colocar um nome de voz no Windows ele passou a sincronizar. Mas nenhuma comando funciona ainda.
Hey guys, I've been having some problems.
I have two computers, a Windows and a Macbook. Neither of them is syncing its commands with Alexa.I'm using TRIGGERcmd Smart Home and it worked during the first minutes, but it seems both computers stopped syncing with Alexa and TriggerCMD, because no command is working and neither is being added to Alexa. Any ideas?
EDIT 1: Apparently one of the Macbook commands was a Windows command. I guess that's why it was not syncing because when I added a new Macbook command it actually synced with Alexa. Still, the commands are not working on Alexa.
EDIT 2: Macbook is actually syncing. But Windows is not. It doesn't matter what I do, Windows commands are not synced to Alexa and neither PC actually receives commands from Alexa.
EDIT 3: I uninstalled TriggerCMD and removed its folders from AppData/Roaming and AppData/Local, then reinstalled, but it didn't work. Updated it and it didn't work. Installed background service and it didn't work.
EDIT 4: After putting a voice name on Windows it actually synced. But no command actually works from Alexa.
-
@Guilherme-Tassinari said in Alexa doesn't find the commands:
EDIT 4: After putting a voice name on Windows it actually synced. But no command actually works from Alexa.
That makes sense - for TRIGGERcmd Smart Home to sync commands with a computer's commands, the computer has to have the voice field filled in.
The only exception is your default computer. The first computer you add to your TRIGGERcmd account is automatically set to be your default computer, but you can change it to a different computer. If you do change your default computer, you'll want to manually re-sync your commands using the Remove All button, then the Discover button at https://alexa.amazon.com/spa/index.html#appliances.
There are some other cases when you'd want to Remove All then Discover to get your commands to sync, so if you have trouble, I recommend trying that.
-
Hello friend, I installed everything correctly, created the commands, but the Alexa app does not recognize them as devices, what do I do?
I installed only the skill TRIGGERcmd Smart Home. -
@Mau-Rios, that's strange. Don't give up though, I know we can make this work.
You tried "Remove All" then "Discover" right, and you still don't see your commands as devices?
If so, please try disabling and re-enabling the TRIGGERcmd Smart Home skill here:
https://alexa.amazon.com/spa/index.html#skills/dp/B07P1MMFRPAlso, please go into your user profile and make sure your computer is your default computer:
-
@Russ said in Alexa doesn't find the commands:
@Mau-Rios, that's strange. Don't give up though, I know we can make this work.
You tried "Remove All" then "Discover" right, and you still don't see your commands as devices?
If so, please try disabling and re-enabling the TRIGGERcmd Smart Home skill here:
https://alexa.amazon.com/spa/index.html#skills/dp/B07P1MMFRPAlso, please go into your user profile and make sure your computer is your default computer:
Friend is there any way for me to communicate with you by email?
I think it would be better for me to send you some prints to help solve my problem. -
@Mau-Rios, I just sent you an email.
-
Hello everyone, I had the same problem with the commands created on the pc. For me it worked filling the "Voice" field and the Ground field as foreground. In a few seconds, Echo found the device. I don't know if this is a feature of the software or if it's a bug. If it is a characteristic, I believe it is necessary to specify that these fields must be filled in this way.
-
@Hey-Artur, yea for Alexa or Google Assistant to find your commands, you have to fill in the command's Voice field.
Maybe I should change this to say, "Required for Alexa and Google Assistant":
-
Alguem pode me ajudar?
Eu formatei meu pc recentemente é quando voltei a instalar o app, minhas rotinas aviam sumido tive que refazê-las, mas ao refazê-las sumiu do alexa, tentei reconectar com a conta do TRIGGERcmd Smart Home, saindo e entrando da conta que fiz, mas simplesmente não resolve, elas não aparecem ou atualizam
