@Russ Works now, thank you so much! Also, wanted to let you know that what you do is pretty awesome. Keep it up!

@Russ said in Alexa stops midway when reading long sentences:

@tigor, I cut my command down to just this, and tested.

I wasn't able to reproduce the issue. Alexa stopped listening right after she spoke that short sentence.

Actually I can't reproduce anymore.... I must have done something wrong that led me to a wrong conclusion. Thanks Russ. I'll let you know if there's a problem!

@Russ I ran your command, and observed that she stops in the middle of the third sentence. I think I found where the issue is. In my Alexa routine, I call TriggerCMD by using the following action: "ask TriggerCMD to run my_trigger", but after that, I tell her to "stop running TriggerCMD", which probably stops Alexa while she talks. The reason I do the second command, is that the first command seems to leave Alexa in a "TriggerCMD state", where she doesn't respond to queries as usual after the routine is completed, so I explicitly tell her to quit this state.

Do you have a better solution to avoid Alexa to be in this TriggerCMD state? Thanks

I try to make Alexa say long results of commands running through TriggerCMD, but I observed that she stops after a few seconds. Is it possible to have her read long sentences or is it a built-in limitation?

@Russ Works now, thank you so much! Also, wanted to let you know that what you do is pretty awesome. Keep it up!

Hello,

I'm trying to make Alexa say the result of a command but she keeps saying "no result" for {{result}}. I managed to have my command run (not easy, using the Custom Action to trigger a command is quite inconsistent, so I had to set up fancy activation words). I reduced my command to the simplest I could think of. It's basically a batch file that runs:

...\.TRIGGERcmdData\sendresult.bat "hello"

I also checked the logs of sendresult.bat, and they seem to indicate that the result is sent correctly:

{"data":[{"name":"...","voice":"tagada","voiceReply":"{{result}}","allowParams":false,"user":"...","computer":"...","switch_is_on":false,"runCount":3,"createdAt":"2024-12-07T20:04:37.550Z","updatedAt":"2024-12-07T20:14:43.334Z","lastResult":"hello","id":"6754aa5536561400146ee0ad"}],"message":"Command result updated successfully."}

Could it be a timing issue? The command runs quickly (easily under 1 second), I checked in a command prompt. Any help would be appreciated!