@russ Ah! No worries then. Are you able to still complete a refund as I don't intend on using the service anymore?

Many thanks

@russ I've been researching this some what. As my current PC doesn't support Windows 11 (or so it says).
There are still some things that need work arounds but hopefully they get worked out for when your 8 gig Pi arrives.

@russ said in Interface possibilities:

FYI, the agent does backup your commands.json file to commands.json.backup every time you change it, and it auto-restores the backup if you make a mistake in json formatting.

Awesome, I did see the commands.json.backup file but didn't realize it auto restored.

I don't like to use the cloud for backups, however I do for some things as well as a back up on disks.

@russ Perfect! Thanks.

@brunocunha, if you haven't done this already, please try this.

Go to here and delete all of your Smart Home devices using the Remove All button at the bottom of the page, then click the Discover button.

Check to see if your TRIGGERcmd Smart Home devices come back.

If they didn't come back, go here and disable the skill to unlink, then re-link your account.

@igo-henrique I'm like you and find it unnatural to say turn on for some things.
There actually are several words you can use for on as well as a few different words for off. These need no additional programing by you and are built into both Alexa and Googlevoice recognition.

@russ That's awesome! Thanks again for the help!

@shandra-dm You can't.

You can lock it but you can't UNlock it. It would be a gross security breach of a PC could unlock itself.

Got a lot of issues with node + brew, this one worked like a charm for me:

osascript -e 'tell application "Finder" to sleep'

@faculhps, I looked at your account and I see that you have two commands, and neither of them have the voice field value.

Please fill that field with something like "calculator" so you can say, "Alexa, turn on calculator" (or the equivalent in Spanish language).

@eliottdavidmx can you try closing your browser completely, then try again? Or try a different computer or phone? If you use a phone turn it 90 degrees because only landscape mode shows the instructions link on the left.

@russ

Sorry for the late reply, I didn't get any issues in the past few days, It seems to be completely working fine right now. Thanks for the help!

@russ Thank You Very Much!!!! Worked with chrome, the only stranger thing is whitch before worked the other 3 times. Again thank you !!!!

@andrea-carballo , thanks for the screenshot. I see the problem. You need to change the commands to foreground.

Background commands only work if you install the background service. Most people don't need it though.

@dougroyer, what OS are you running? Do you get that when you try to run triggercmdagent?

@russ, I've confirmed that the Alexa skill is working! Thanks for the rapid response!

@meet-bhagwanani, I think you're right. The agent doesn't work with the latest versions of node js. I know it works with version 14, and I think it only works with early versions of 15. It's on my list to fix at some point, but for now, I hope you don't mind downgrading.

EDIT: Correction - I just tried node version 16.13.1 and it worked.