@Russ
I'll try doing what you suggested.
I will update it later.
Thank a lots.

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

@Russ could you walk me through how to do this in simple terms and lots of clear step by step instructions? I've never used these softwares before so you can imagine how confusing this is for me to understand without having any experience doing anything remotely similar to this.

obrigado pela informação

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.

@Firas-Frikha , do you have a question?

@pongsatonn-siripet, I looked the the Microsoft article you sent.

I see this on that page about the error you're getting:

Cause
This error means a Power Automate license is required for the current user to do the action

@pongsatonn-siripet are you saying you cannot get to the GUI Command Editor? That's where you should see "+ Add Command", "+ Browse Example", and "+ Computer List

You should have a TRIGGERcmd tray icon if you click the up arrow in the lower-right near your clock. Here's a screenshot where I right-clicked my TRIGGERcmd tray icon. You can see the "GUI Command Editor" in the menu.

009faa08-7913-48af-a366-c322a2f36b22-image.png

@john-lagos-ramirez, awesome.

@Viniciusmbs, de nada.

@abaratz, awesome. Thanks for confirming.

@Viniciusmbs, I'm glad you asked because I've been working on the official Home Assistant integration for TRIGGERcmd. It's almost ready. I'm just waiting for this pull request to get merged: https://github.com/home-assistant/core/pull/121268

In the meantime, you could use this method.

Awesome @Valter-Santos ! Thanks for your patience, and for showing me this bug. I'm working on the fix now.

EDIT: It should be fixed now, so it won't error even if you do have multiple triggers with the same name on the same computer.