@Russ Thanks for the tip!
I removed the triggerCMD and performed a new installation using the root user.
Initially, he had problems when I made changes to the commands.json file using nano.
Using the ne everything went well.

Re: Raspberry Pi setup

When editing the /root/.TRIGGERcmdData/commands.json file
The Site does not display the new triggers. After executing the command /usr/share/triggercmdagent/app/src/installdaemon.sh the system shows the output:

root @ SPI-00: ~ / .TRIGGERcmdData # /usr/share/triggercmdagent/app/src/installdaemon.sh
Daemon install: true
No token exists. Login to request one.
● triggercmdagent.service - TRIGGERcmd Agent
Loaded: loaded (/etc/systemd/system/triggercmdagent.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2020-08-22 23:22:17 -03; 7s ago
Main PID: 8900 (node)
Tasks: 7 (limit: 2065)
CGroup: /system.slice/triggercmdagent.service
└─8900 node /usr/share/triggercmdagent/app/src/daemon.js --run /root/.TRIGGERcmdData

Aug 22 23:22:17 SPI-00 systemd [1]: Started TRIGGERcmd Agent.

I edited the commands.json file but the only trigger presented on the site is the Gnome editor. Even after I removed it from the file.