Basically, I find that if I say "alexa fast forward" - if alexa is successfully triggered, then it picks this the spoken phrase 100% of the time and the activity node outputs the message with the "alexa fast forward" phrase in it and I can control my SkyQ box with it.
Problem is, that it doesn't recognise the wake word 100% of the time (standard alexa behaviour dur to other noises going on) so I like to do it in two stages
E.g say "alexa" then wait for blue circle on my dot - then say "fast forward"
Unfortunately - although it is awake and responds to my command and speaks my chosen Q&A completion phrase so I think it worked - the remote2 activity node doesn't actually output anything in about 50% of cases
If your running the combination of remote2 and Q&A skill - could you test this out and see what results you get?
I just tried with a simple flow with event listener and a debug.
It produced an output on msg.payload.description.summary, 10 out of 10 times and responded with Q&A skill response
Having spent a lot of time on this - I'm giving up on the remote2 node - the extra facilities that it gives over using the reliable node-red-contrib-alexa-home-skill from @hardillb isn't worth the unreliability - my family just laugh at me trying to get it to work properly
OK - it has worked "quite" well (but not yet good enough for other family members to rely upon)
Current fault is that it doesn't seem to pick up on the 1st time I use a phrase - the Alexa Q&A skill responds but no event is fired by the On Device Activity node.
But once "woken up" it then works at least 9 times out of 10
.
So I decided to trim my NR install from 110 to 18 tabs yesterday and we'll see if that improves the situation.
Just tried the Alexa app on my computer and at least that still works
but I'd stopped using that as I find it more convenient to just use a phone rather than having to press some keys on my computer while I'm developing stuff