@Russ It makes sense, thank you again. I will try this as soon as possible but I'm hopeful it'll finally work as I intended

@Russ this was incredibly helpful. I didn't pay the attention I should have, because I had simply put a

/usr/bin/steam > /tmp/steam.log 

while debugging, assuming the > operator without specifying 1 or 2 before would redirect both stout and stderr to the file, and I predictably didn't get any error in the output this way..

either way, even getting the correct error log, I wouldn't have been able to resolve the issue without your help so thank you again. One more issue that I hope you might know how to fix is that I can now launch all my apps, but they have no audio. This time there is actually no error indication but maybe there's some additional configuration I need to do, would you know anything about it? I hope I am not pestering the forum with dumb questions but I truly can't manage to find a solution elsewhere

Hello, I am having an issue with the triggercmd agent on Arch Linux (I have sort of a custom installation, I built the project from the GitHub source, then created two systemd units, for both background and foreground services).
I am trying to run applications saying "Alexa, turn on steam" for example. I have thus inserted into commands.json:

{"trigger": "steam", "command": "/usr/bin/steam", "ground": "foreground", "voice": "steam", "allowParams": "false"}

when I ask Alexa to run the command and check the logs via systemctl status, I get that the command ran

this is consistent with the fact that simpler background commands like shutting down or rebooting the pc work as intended and show up as well.

Am I missing something?