Thanks @metablast.

I've been thinking about how I could allow other parameters. Would you want to create an HA automation that triggers the command, and do you want the properties of the device that triggered the automation to be selectable as command parameters? I think I could build a way to do that.

@Rafael-Estevam, what you say to Alexa will make more sense if you make the Voice field just computer instead of turn off computer.

The formula is, "Alexa, turn on/off [voice word]."

That's assuming you're using the TRIGGERcmd Smart Home skill.

In this example, I can say

"Alexa, turn on calculator." to open it.
"Alexa, turn off calculator." to close it.

@Al-S, do the new commands have a voice word? That's required for the skill to create devices.

@Greg-Larsen Correct. They are optional should someone want to just use the triggercmd site to set off their actions but absolutely needed for Alexa/Google integration.

@Greg-Larsen If you want to add hardware, a $5 smart plug (Aliexpress) would do the job of your $25 (+hub) suggestion. Set the BIOS to turn on when power is provided and you're done.

I have my three monitors on one smart plug so when I say Good Morning to Alexa, she fires them up. I don't really need WoL so pressing the button is fine with me.

@Al-S, the agent will restore the commands.json.backup file if it detects invalid json in the commands.json file.

If you have a valid commands.json file and the commands don't get added on the website when you add them to commands.json, the most common reason the agent is running in background mode but you've make the "ground" value equal "foreground". When you install the agent with installdamon.sh, it will run in background mode, so you should make ground=background.

Please copy/paste your commands.json file here. Maybe I can spot the issue. A common problem I've seen is a comma after the last command in the array. You can also test your json by copy/pasting it into an online json parser like this one: https://jsonparser.org

I published this Home Assistant blueprint to trigger 21 different commands, one for each button on this 21 button infrared remote control.
https://github.com/rvmey/TRIGGERcmd-Agent/blob/master/ha_blueprints/ir_remote.yaml

Install the "Mosquitto broker" Home Assistant add-on if you don't already have it.

Create a Home Assistant user for Tasmota to log into MQTT using this web page:
http://homeassistant.local:8123/config/users

Connect your ESP32 device to your PC via USB and install Tasmota firmware using this web page:
https://tasmota.github.io/install

Connect it to your wifi, open the Tasmota web interface, and enable MQTT. Point it to your Home Assistant IP address, and input the username and password for the user you just created for it.

In the Tasmota Module configuration, enable IRrecv on GPIO 15:

Add this to your Home Assistant configuration.yaml. This will make the IR receiver(s) available as entities you can select on your automation.

mqtt: 
  sensor:
  - name: "IR Receiver Blue"
    state_topic: "tele/tasmota_778254/RESULT"
    value_template: "{{ value_json.IrReceived.Data }}"
  - name: "IR Receiver White"
    state_topic: "tele/tasmota_47F4CC/RESULT"
    value_template: "{{ value_json.IrReceived.Data }}"

Modify it for your specific tasmota name(s) instead of tasmota_778254 or tasmota_47F4CC. You'll find yours on the MQTT configuration page.

Go to this page and install the blueprint with the IMPORT BLUEPRINT button.
http://homeassistant.local:8123/config/blueprint/dashboard

Click the blueprint and configure your automation with an action for each of the 21 buttons on the IR remote. Notice the automation can use multiple IR receivers if you want.

The IR remotes are cheap enough you can buy a bunch and have them all over:

https://www.amazon.com/HiLetgo-HX1838-Infrared-Wireless-Control/dp/B01HTC5JX4

https://www.amazon.com/Teyleten-Robot-ESP-WROOM-32-Development-Microcontroller/dp/B08246MCL5

Optionally, you might also want to run this command in the console to prevent it from losing its config when the power going out and back on too many times:

SetOption65 1

If you prefer a Raspberry Pi solution that uses the same IR remote, check out this post.

@metablast, sorry, at this point in time the TRIGGERcmd Home Assistant integration only supports sending the on and off parameters with the trigger.

You mentioned "Bot Replied." What bot are you talking about?

I wrote this start.sh bash script to run Home Assistant for the Youtube demo but you could also use it to try out Home Assistant and/or the TRIGGERcmd integration for it:

#!/bin/bash

mkdir -p ~/ha/config
docker run -d \
  --name homeassistant \
  --privileged \
  -e TZ=America/Detroit \
  -v ~/ha/config:/config \
  -v /run/dbus:/run/dbus:ro \
  -p 8123:8123 \
  --rm \
  ghcr.io/home-assistant/home-assistant:stable

This shows my session where I ran it, then confirmed it's running with the docker ps command:

russ@RussHP:~/ha$ cat start.sh
#!/bin/bash

mkdir -p ~/ha/config
docker run -d \
  --name homeassistant \
  --privileged \
  -e TZ=America/Detroit \
  -v ~/ha/config:/config \
  -v /run/dbus:/run/dbus:ro \
  -p 8123:8123 \
  --rm \
  ghcr.io/home-assistant/home-assistant:stable
russ@RussHP:~/ha$ ./start.sh
a32957000a3f029fda67ff1cc2d96b22d2fe4f13125536023e94723a5df2dc6f
russ@RussHP:~/ha$ docker ps
CONTAINER ID   IMAGE                                          COMMAND   CREATED       STATUS       PORTS                    NAMES
59c343cb87fa   ghcr.io/home-assistant/home-assistant:stable   "/init"   2 hours ago   Up 2 hours   0.0.0.0:8123->8123/tcp   homeassistant

After it was running, I was able to access it at http://localhost:8123

@Sxve__ , I'm glad it's working. I know, it's too bad Alexa reserves certain words. I just picked "banana" because I knew it's not one of them, but I'm sure you could come up with a better word.

About controlling Spotify, here's one approach you could consider:
https://youtu.be/5LNVrFHCKkA?si=4gCgQWv0VB4RnCIt&t=164

One thing you could add to your script is a command like this to switch to a playlist:

spotify --uri=spotify:user:1269640531:playlist:0kYOOgseBw3Jr1Sl7Yv2Pj