@Oscar-Daniel-Díaz-Carmona, Are you asking how to create a command that opens a folder? If so, please try this: [image: 1662762426130-cadc1017-a664-4d7a-9379-e56addc0843d-image.png] When I triggered that command it opened my D:\music folder in Windows Explorer. [image: 1662762373477-b7b01a6c-dcb8-4ea7-8871-d53aec1644fd-image.png]

@Russ Thank you so much! You made my day <firework emoticon>

@Marcos-Martinez-Debelluit, this is one method. I used the SoundVolumeView.exe tool from Nirsoft. SoundVolumeView.exe /SetDefault "Realtek*\Device\Speakers\Render" all SoundVolumeView.exe /SetDefault "*USB Audio Device\Device\Speakers\Render" all If I run the above commands while Spotify was playing a tune, it switches my computer's audio output from between my "3- USB Audio Device" (usb headphones) and "Realtek High Definition Audio" (speakers). Notice I shortened the device names that the GUI showed me using the * wildcard. [image: 1661132325663-ae6ca298-41ba-4ae5-969f-18e6e1ace8e7-image.png] I have Spotify set to "This Computer". [image: 1661133138406-cf86c6d7-3906-49a3-909d-765410db633e-image.png]

@Gustavo-Yrepá I just made a command with NirCMD into voicemeeter to change where the sound is going. Works pretty fine. But i'm still struggling with setting up everything to work with my Macrodroid app (I use it to automate a lot of things.

@FantasmaJF Veja esse tutorial: https://www.youtube.com/watch?v=2ybc7ObLosI Eu fiz no meu e deu certo. Geralmente, funciona melhor em Desktop. Tomara que seja de ajuda. Vlw!

@aidanjalili03, now you can setup MFA. I posted the details in this announcement.

okay thanks Russ, I was on vacation, maybe it was something to do with the wifi for the hotel, i'll let you know if it continues doing it now i'm back

@Paulo-Varjal, I see. Thank you for the screenshots. I don't know why Paypal won't authorize your cards. Have you tried all 3 of those?

@Five, you should be able to use Bixby to flip any switch in your SmartThings devices. You can use these instructions to add your TRIGGERcmd commands as virtual SmartThings switches.

@mikeh_iver After you installed the software on the other PC, copy the commands.json file from the "C:\Users*username*.TRIGGERcmdData" to the it.

...but unfortunately, Amazon has set up restrictions: "Response length – The combined total time for the entire audio response generated from the components cannot be more than 240 seconds." BUT... "Our API throttling limits will allow up to 30 calls within a 60 second window…anything above that will block subsequent requests for the next 15 minutes." So, no creating a music box isn't really doable - a text reader/TTS no problem!

@josé-david-cabañales-ramírez, sorry no, I'm only setup with Paypal at this point.

@joão-vitor-zanotto, thanks. I'll test that myself. I don't know why that would break it, but I'm glad it's working.

@aaaaa12345, if I add a 3rd version of the non-Smart Home skill, I think I'll see if TC is available. I'm curious, why are you using the old TRIGGERcmd and Trigger Command skills? Is it for the voice reply capability? I generally encourage people to use the TRIGGERcmd Smart Home skill because it matches your words to your command triggers much better. I also think "turn on calculator" is easier to say than "ask trigger command to run calculator." Also, fyi, Google is discontinuing conversational actions (Google calls it an action instead of a skill). So after June 13, 2023, I expect the Google version of the TRIGGERcmd and Trigger Command actions to go away, and you'll have to use the TRIGGERcmd Smart Home action.

@aaaaa12345, I wonder if you're using the original non-Smart Home skill. If so I'm not surprised it would often miss what you're saying. I created this "NBC" command and I'm able to say, "Alexa, turn on NBC" and it works every time. It uses the TRIGGERcmd Smart Home skill. The TRIGGERcmd Smart Home Google Action works every time too. [image: 1657734987028-a69d0fe7-1adb-4226-a9a5-b8b929aae1d9-image.png]

@aaaaa12345, this is a method you could use TRIGGERcmd to say something any time. Alexa routines can execute commands by flipping the TRIGGERcmd virtual switches that the TRIGGERcmd Smart Home skill creates for each command, but routines can also execute commands using the original TRIGGERcmd skill using the "custom" action like this: [image: 02.png] The routine will run a command using the original TRIGGERcmd skill, which allows you to use the Voice Reply field with the {{result}} placeholder that you fill using the SendResult.bat script. So if you have a long running script and you want Alexa to say something about the result, you could write your result message to a file somewhere, then trigger the Alexa routine by running a tcmd command that runs the routine by tiggering the TRIGGERcmd command you've tied to the Alexa routine. The routine would run another TRIGGERcmd command that uses the SendResult.bat script to say your message via the {{result}} placeholder in the Voice Reply field. It's complicated because it uses all these ingredients: TRIGGERcmd Alexa skill (the old original skill) to run a command and hear the result. An Alexa Routine with a custom action has Alexa say "Alexa, ask TRIGGERcmd to run result" to itself. TRIGGERcmd Smart Home Alexa skill to run the Alexa routine when you trigger a command. The tcmd command to run the command that triggers the Alexa Routine. I had another case where I couldn't use TRIGGERcmd because the purpose was to have my Echo next to my bed tell me if the TRIGGERcmd site is down. I used https://voicemonkey.io with IFTTT for that. It worked great. I have montastic.com call this endpoint which tells Alexa to have my Echo Dot speak "Trigger CMD is down" https://maker.ifttt.com/trigger/Montastic/with/key/(my IFTTT key)?value1=Trigger%20CMD%20is%20down My IFTTT applet looks like this: [image: 1657735932118-8d3a1085-a78f-471c-a202-6718a9d827fe-image.png]

@mark-hollis, last night I finally found the root cause and I'll be working on fixing it today. Basically, AWS has been throttling my server when it gets too busy. That's why it's intermittently slow. I'm going to upgrade to a different type of server today. EDIT: It's done now - AWS won't throttle the server anymore. Thanks again for reporting the problem. If you see slowness again, please let me know, but I think I got it this time.