@Russ It worked, I downgraded NodeJS to 14.9.0 and it's working perfectly. I'm still facing trouble to make foreground service run on boot, but that is less important.
Thanks for all your help and support!

@Russ said in Problem running on Manjaro KDE:

npm -v

Yeah, no problem. Here it is:

@Russ I have made the tests you asked for, here are the results:

I don't have another wifi network, but used my phone as a router to make the test:

Only have 1 PC using TRIGGERcmd, but since I have a dual boot I could test it in PopOS, and it's working fine, so manjaro should be the problem.

The command terminal:

First test was in my house network and second one in my phone network.

Websocket site:

No, using just a normal wifi connection.

Tested it again, but unfortunatelly the same happened. Actually I've tested it a few days ago, when I switched to Manjaro, and I had that same problem.

I've used TriggerCMD in Ubuntu and Pop!_OS for a long time, and it's very useful, but now I've decided switch to Manjaro KDE, but couldn't make it work.

I followed that tutorial.

When I run the command node ./src/agent.js --console, that happens:

and I can't trigger anything.

There's anything I'm doing wrong or something I can do to fix it?
Thanks for any help, and sorry for bad english.

I was facing the same problem, but solved while writing this:

If I use the old skill and say "ask trigger CMD to run terço" it works perfect, also works from pressing "trigger" in the website.
If I use the new skill and say "turn on terço" it doesn't.

What have I tried:

• Disabling and enabling the skills.
• Deleting and adding the command again.
• Removing and discovering the comands again in Alexa.
• Removing and re-installing the triggercmdagent.
• Changing voice command.

Useful info:

• Only happens to that command, all the other works fine.
• This command is a bash script that open a few chrome pages depending on week day.
• I'm using Linux (PopOS 20.04).
• I'm using it in portuguese.

Then I decide to try changing the Trigger name. I used "batata" (potato in portuguese) and it worked, then I tried "Terço" again and it didn't, then I tried "Terco", it worked. Apparently it is a problem with "ç" in the trigger name (in the voice command is working well). Since english don't have that, it's understandable. It's not a big thing or really a problem, just wanted to inform so if anyone is having the same problem, try that.