-
Notifications
You must be signed in to change notification settings - Fork 176
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
Respond to Alexa #36
Comments
Hi, I ran into the same issue with Alexa. The current implementation does not respond to the Status request from Alexa. Apparently the response to it became mandatory with some update weeks ago. So, I copied and modified the SetBinaryState code to handle the GetBinaryState request, copied the GetBinaryStateResponse body from mattenoble and decided that an action_handler must now also implement a status-method (return True = "ON" or False = "OFF") and done. Not so pretty but maybe it helps somebody and Alexa is satisfied again. EDIT: Just saw it too late. There is already a pull request addressing the issue: link |
Just a thank you for this. Solved my misbehaving Alexa/Fauxmo setup. I had been seeing intermittent operation with "device unavailable" in the Alexa app and the Echo saying it was not responding. in just the past week or two. Applying your GetBinaryState patch worked! |
Hi,
I have setted everything up, so that i can controll the pin, and it words perfectly fine.
The issue i have is: everytime i tell alexa to turn a GPIO on or off, she does it fine, but after that she tells me every time, that the device is not online. Do alexa need a response from the pi to stop saying this? What do i have to do to send this response? what else can i do?
sry for bad englisch
The text was updated successfully, but these errors were encountered: