@Hannibal said in Error while installing the triggercmdagent:

Notice: Download is performed unsandboxed as root as file '/home/hannibal/downloads/triggercmdagent_1.0.1_all.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)

Copy/paste that into ChatGPT to know why, but you can safely ignore that "Notice". Basically it means the _apt user doesn't have access to your user's home directory where the .deb file is, so it's using root to access it instead.

It looks like the agent is installed now, so you can move on to the next step:

node /usr/lib/triggercmdagent/resources/app/src/agent.js --console

It should prompt you for a token which you can copy/paste from the Instructions page while logged in at https://www.triggercmd.com

@Hannibal, thank you for reporting it! I tested it and ran into the same problem at first, but it's fixed now. Please download it again and try the install again.

@Matthew-Mason, it's a good use case that I should not disable, so I'm glad you caught it.

@Matthew-Mason, thank you for reporting this.

I was trying to avoid a loop that one user created, so I disabled the Alexa smart home "doorbell" press when the trigger source was an Alexa Smart Home device trigger.

It was intentional, but in hindsight it was the wrong way to fix it so I reverted the change. It should work now.

I'll find a better way to avoid the loop.

@Christopher-Foote, sorry about the issue. I'm not sure what happened, but I enabled your subscription.

@Sreehari-J, I see your subscription in Paypal. Do you want me to cancel it?