@Russ yes it was down for about 2 hours yesterday, now work correctly 🙂

@Noah-Nauman, I sent you your paypal email address. I see you do still have an active subscription. I can cancel it or you can.

@Richard-Rico, awesome, good job. I'll suggest that in the future. That's a simple way to fix it.

@tsanchez, I found your subscription and cancelled it.
Subscription ID : I-TGNG50GBAB0V

obrigado pela informação

@Ancar Try unplugging the device and plugging it back in. You might also want to re-sync the device in the Google Home app.

Since your PayPal’s closed, maybe try reaching out to their support team directly?

Yeah, I have been on this forum for a few hours and Russ helps everyone.

Thanks for that, helped me too.

Go into Sound settings, find your Realtek device, and disable it there if you don’t want it to play anything at all.

@iswasdoes, nice. I'm glad you figured it out.

@john-lagos-ramirez, awesome.

@abaratz, awesome. Thanks for confirming.

@mlabombarda, thank you for reporting that. I'll fix it the sorting for the "computer | trigger" setting.

I'll look into adding a way to pick a panel, then a button on it from a submenu. I think that's what you want.

In the meantime, you can use the fast-forward and rewind buttons on the Roku remote to page down and up. I figured I'd mention that feature in case you missed it. I find it helpful.

EDIT: I fixed the sort. Thanks again for reporting it.

@Lucas-Lima-Ribeiro, thank you for confirming it's working!

@Renan-J, please make sure your second computer has a "Voice Name" because if it doesn't, it won't work with the Alexa skills.

Only your default computer works with the Alexa skills without a Voice Name. Your first computer is the default computer by default.

@Gabriel-Martins you could try the new version I just released, but I don't have confidence it will solve that error.

Do you have admin access on your Windows PC? What Antivirus do you use?

@Luigi-Marco-Silvestrini, I think I fixed it but I'm not 100 percent sure because the error showed up so rarely. Please upgrade to the latest version (1.0.36), and please tell me if you ever see the error again.

@Luise-Fernandes, I'm not sure, but please try deleting this folder, then re-run the "TRIGGERcmd Agent" app.

c:\Users\luise\.TRIGGERcmdData