Well… This one kept me awake last night. I have another possible explanation… I have Amazon as integration to HA, but I do not have HA integrated to Amazon (If I did I think I would end up with even more duplicates and loops.
I also have my own domain (997DJ.net) and static IP(s) but Use DuckDNS and Ngiinx for simplicity.
I started automation over 30 years ago with X-10 and progressed from there in stages. When ADT came out with Pulse, I was right there and integrated a device or two monthly… Until I was having connection drop outs. The Tech advised me that I had too many devices connected. I purchased Wink II and was transferred almost all of my Z-Wave devices. Then Wink transitioned to a $5 month subscription… Immediately replaced with two SmartThings. The way I look at it and my expectations, is that HA becomes the ultimate server integrating the various hubs and smart devices. I will most likely always be adding more. Currently Alexa can integrate ADT, by HA integration fails and have not figured why (So it’s off the the back burner!). Additionally I had a new heater installed… To the cloud, but I have no idea how to write the API. Anyhow… Alexa also does not see virtual devices… So I may end up using extra switches to signal from Alexa to switch and HA listening for state change… It will work… at least till I figure what is up with the Auth and links. Oh! - you asked about my YAML for Alexa:
configuration.yaml:
default_config:
## Alexa Media Player Integration
alexa_media:
accounts:
- email: !secret amazon_user
password: !secret amazon_password
url: amazon.com
I think so. For Alexa to get entities from HA you need Amazon Alexa Smart Home Skill in addition to the Actionable Notifications via Alexa Media Player
Changed? Like OMG totally different! I made it all they way to ( Painful ) the very last step… Tested everything in the AWS Console using the Discovery. All works to that point and responded back with what I believe is everything she has . But as I said, and you noted Documentation was extremely outdated. So… last step, account linking in the Alexa App (Enable To Use)… , I get the login screen for HA, enter username and password, and authy security token… and I get “Unable to link Home Assistant with Alexa. We are experiencing a problem connecting with the skill to link your account. You can try linking your account again by visiting the Home Assistant Skill Page.”
Researching everything I can find leads me to believe it is directly related to the Amazon LWA OAuth server because I had the errors in my log forever, but I have no idea how to fix that…
@dbrunt
I am convinced the only way to resolve is start over… My question to you, if you recall… When you fist installed Amazon Media, did you start at HACS? All of the documentation I found is at various levels and nothing seems current. Could that be why I am having the errors?
Well, the first thing I installed was the Home Assistant Alexa custom skill integration. This is what populates your HA devices and scripts/scenes into Alexa. Next was Alexa Media Player via HACS which creates your Alexa Echo devices as media players in HA. They are two totally separate processes and are unrelated to each other. Then you need the custom skill Alexa Actionable Notifications which requires a working Alexa Media Player integration (HACS). Without re-reading the posts, I thought you were having trouble with the Home Assistant Alexa custom skill integration not giving you your HA entities in Alexa?
I did the whole process in both languages (Spanish and English) to try, I also did it with English, adding Spanish… but it doesn’t work, alexa tells me “there was an error managing the response on this device”
@dbrunt
Long time no hear (Update). I finally got the Home Skill linked from the Alexa App… Well, I have been troubleshooting since - it broke my Actionable Notifications. Now I am getting authentication errors like you would not believe I am trying everything I can think of… So far, I have completely deleted HA and built from the ground up (4th time now) Somewhere in the Actionable Notifications is an authentication section. I just don’t recall how to get back there. Wish you well, wish me luck, I will need it.Let you know how things go… Hopefully soon, as you can imagine, I am consumed with trying to get it back on line.
Everyone following this educational thread. I finally have everything solved. Amazon is a strange creature… Even stranger than trying to figure the syntax of HA . Until I very slowly followed every step, I did not realize how many keys, F2A, Two-Step, and passwords were actually active. I for one know it is all necessary, because everywhere you lurk someone is trying to disrupt or hack your existence. In authenticating one of the skills work disconnect the other and drive you nuts! The fix: In the app, disable both, Open the Developers console page Amazon Sign-In Review the steps in edit mode updating keys, long time passwords, etc. Then re-link them in the app after saving changes. It was a long and challenging journey. BUT…
Thanks to @dbrunt I can now use both amazon skills to the very fullest ability! I home to see more exciting abilities posted in the forum.
Mine is working!!! What do others do with this exciting feature?
but the automation get never triggered when alexa get no answer from me.
here is the automation for the question
service: script.activate_alexa_actionable_notification
data_template:
text: Hallo, Soll ich die Shield ausschalten?
event_id: actionable_notification_firetv_kueche_switch_off
alexa_device: media_player.echo_show_kueche
and in the script is everything correct, the ResponseYes works well.
I have the same problem, ResponseNone never seems to work. ResponseYes and ResponseNo work fine, but looking at the trace it seems like the automation just stops if no response is given and it doesn’t proceed with the ResponseNone action.
I’m using Sonos speakers with Alexa as the voice assistant. Could this be a limitation of using Sonos, or should it be able to work correctly?
I get “There was a problem with the requested skill’s response” almost constantly after not having any issues for a few years. I’ve found that sometimes rebooting works, but only sometimes.
Does anyone have any suggestions on how to resolve the “There was a problem with the requested skills response” issue?
One of the last updates changed the way the integration was configured. it is no longer in the configuration.yaml and you must you set up F2A within the configuration and your Amazon Account.
I did some digging in my AWS lambda function logs and every failure has the same error:
HTTPSConnectionPool(host='xxxxxxxxxx.ui.nabu.casa', port=443): Max retries exceeded with url: /api/alexa (Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1129)')))
Researching that error indicates it may be a proxy error. I’m not seeing any errors in my local HA logs - makes me thing this may be an issue with the Nabu Casa cloud integration?
@gjtaylor72 Boy do I ever feel your pain. I don’t use nabucasa; however I had the same issue. It was the F2A. The difficult part in my opinion is there is not one single source to get your fix. Not being sure what you have already done or what stage you are at… I will share the links and actions that got me operational…
At this stage. I noted all the passwords etc. and removed the integration, including the following from configuration.yaml
At that time, after a restart, I went back to the integration page clicking + ADD INTEGRATION and searched for Alexa Media Player. At that point I got the configuration form… However, mine, and I think you may have the same issue, would not authenticate… So I opened a trouble ticket on GitHub.
I think after you review the thread you may find your answer or at least enough to have a better understanding… Good luck, let me know if you get there
Sorry looks like I posted in the wrong thread, this has nothing to do with the Alexa Media Player integration, that is working flawlessly and always has.
Hi! Been following this thread and was able to set up the Alexa custom skill required for Actionable Notifications but I guess the issue I’m having is in the home assistant portion with the automations. You mentioned above that the user’s response is contained in the event.data.event_response. I currently have 3 automations setup. For argument’s sake I’ll call the automations “trigger”, “action1”, “action2”:
Trigger - this is the automation that triggers the script and in my case I use a motion sensor to trigger Alexa to ask me the first question.
Action1 - this automation is triggered by 1st automation and has Alexa asks me a second question if I responded yes in previous automation.
Action2 - this third automation is where the action should actually take place. My possible answers to “Action1” are neither numeric nor a yes or no so I’ve set this up as event_response_type: ResponseString and I wanted to know how I can use the value of event.data.event_response (my response from “Action1”) as field in the action section of this automation to actually trigger the response I want.
Not sure of this makes sense, hopefully someone can understand
6. ResponseSelection is the closest you’re going to get. I’ve looked at it but I’ve not tried configuring it. From what I recall it’s not for the faint of heart!
I’m waiting for ResponseDate/ResponseTime to get added but not holding my breath!
Thank you so much for your response! I will be taking a closer look going at it ResponseSelection route and will report back if I am successful. This thing has so much potential I think with some slight tweaking it can be even more powerful.