forked from 586837r/node-red-contrib-alexa-remote2
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On Device activity #7
Comments
Works for me... UK emea based account. PS hi watch your YT :) |
Oh Hi!
I'm on the UK settings too. I get the media queue changes but I cannot get
the information about the voice commands or routines triggered.
I'm triggering from mobile Alexa app.
Innit is ok as other things were fine.
I also had issues passing speech to Alexa devices with screens. No speech
occurred.
…On Thu, 11 Mar 2021, 11:32 Peter Stevenson, ***@***.***> wrote:
Works for me...
Just tested and routine execution returns msg with msg.payload.success
true ok
And separate on device activity returns payload with details of the action
the routine just took.
Sure it’s initialised ok when you are testing?
UK emea based account.
PS hi watch your YT :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#7 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKDRL26GMSGXUDABCUXVXFDTDCS3LANCNFSM4ZABDHXA>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The node returns no information from AWS servers for routine execution or voice queries
The text was updated successfully, but these errors were encountered: