Topics created by Atmosphere

@Atmosphere, I just found out this problem was on my end. There was a bug in my logic that triggered in cases when Google sent the computer word along with the trigger voice word. I'm sorry! Anyway I fixed it, so you might need to switch back to using pool instead of poo or pooll.

Also, thank you for reporting it. I feel bad that I blamed this on Google when it was my fault.

@atmosphere, wow, I'm glad that was it because I had no idea what I could do about that.

@atmosphere, I'm sorry but right now the TRIGGERcmd installer only supports one TRIGGERcmd account per Raspberry Pi.

But, theoretically you could maybe run two instances of the TRIGGERcmd agent on the Pi, as two separate Linux users, and give those two users sudo access if they need to run things as root.

If you run triggercmdagent --console it will run in foreground mode like so, and store two separate commands.json files in the .TRIGGERcmdData subfolder of their respective home folders:

pi@raspberrypi:~ $ triggercmdagent --console Run installdaemon.sh to install the triggercmdagent daemon so it runs during boot Daemon install: false No token exists. Login to request one. prompt: token:

The trick would be in getting the two agents to run after a reboot.