So update i got the skill enabled to work, however i am getting an error that after i log into my HA login screen( it gave me the HA login screen after i enabled the skill"
"we were unable to link “my skill name” at this time.
Any ideas? I hope someone can chime in on this one.
Anyone having issues with Alexa not discovering devices lately? Using the minimal Haaska since a few years and it’s been working perfectly. I have about 250 devices exposed and now none of my media_players are discovered. Lambda discovery is working, but there is no way to validate what Alexa is expecting…
@ Redferne What version of Home Assistant?
Enabled debugging to see the discover log from HA to Alexa. https://www.home-assistant.io/integrations/alexa.smart_home/#debugging
@ochlocracy 0.105.0b4
Found the problem. For reasons unknown Alexa does not like the EqualizerController interface that Core produces for my Denon Receiver. Commented out the interface and wham! all media_players were discovered.
Could post the discovery response for your Denon Receiver with the Alexa.EqualizerController interface? There must be an issue with the json, if it’s preventing all media_player entities from being discovered.
Perhaps related to issues that others have reported. My perfectly running haaska stopped working and as part of the troubleshooting I tried to run a lambda test and it failed. Looks like the issue is on the hass.io ( 0.104.3) side?
START RequestId: ff9e08a1-8046-41d1-b6e1-659db909crre Version: $LATEST
500 Server Error: Internal Server Error for url: https://home.duckdns.org/api/alexa/smart_home: HTTPError
Traceback (most recent call last):
File "/var/task/haaska.py", line 111, in event_handler
return ha.post('alexa/smart_home', event, wait=True)
File "/var/task/haaska.py", line 66, in post
r.raise_for_status()
File "/var/task/requests/models.py", line 940, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: https://home.duckdns.org/api/alexa/smart_home
END RequestId: ff9e08a1-8046-41d1-b6e1-659db909rree
REPORT RequestId: ff9e08a1-8046-41d1-b6e1-659db909rree Duration: 825.92 ms Billed Duration: 900 ms Memory Size: 128 MB Max Memory Used: 62 MB
Ok. Looks like I found the issue. If climate component is not excluded, then this error will show up. If I exclude climate like in the code below, then all works well. Worth creating an issue on haaska github?
alexa:
smart_home:
filter:
exclude_domains:
- climate
@Robkiller1 how did you manage to fix the enabling to use not working issue?
i have the same problem
thanks
It looks OK to me, I think the problem is somewhere else, but funny enough it was only discovered if I left out the EqualizerController.
{
"configurations": {
"modes": {
"supported": [
{
"name": "MUSIC"
},
{
"name": "MOVIE"
}
]
}
},
"interface": "Alexa.EqualizerController",
"properties": {
"proactivelyReported": false,
"retrievable": false,
"supported": [
{
"name": "mode"
}
]
},
"type": "AlexaInterface",
"version": "3"
},```Thanks! Your discovery looks good. But, It lead me to find discrepancies in the Alexa documentation for the supported property. In the documentation it’s mode in the Alexa Discovery JSON schema it’s modes.
That could be the issue. I’ll report back.
I recently made a tutorial on how to add Alexa control to ANY Home Assistant device.
Check it out, I hope it’s helpful - https://www.youtube.com/watch?v=KWMDE-plRAY
Is it possible to use two different amazon accounts and share the skill between them. This is because both my wife and I have different accounts, she has a couple of alexas and I have one also. Would like all alexas to be able to accept voice commands to control HA.
Hi
has anybody figured out how to assign room to entity_id in configuration.yaml so that when we link haaska skill to alexa most entities will be created with rooms in Alexa app?
Home assistant integration to google assistant, has that capability. in Google Home app unlinking
from home assistant will also remove only devices created from Home Assistant. I’ve found there is nothing equivalent to this in Haaska, Unlinking from Haaska skill the devices stay behind. you can either click Forget 1 by 1, on a pc alexa.amazon.com portal, or you can click Forget all. Forget all though you loose everything included other smart devices not related to Home Assistant like the Amazon smart plug. Forget all you also loose custom groups you’ve created. Your Routines stay, but underlying action devices/scripts will be empty, this last part is similar in Google Assistant integration.
Wow…I was having the same problem and add exclude climate and it worked. Random. Why? Thanks for the tip.
what your asking is probably new territory, you can try in Alexa App Settings Guest connect. Your wife then give commands to your echo devices to turn on lights for instance. Don’t think she will be able to use her echo devices then turn on lights.
I’m not anywhere near an expert, and Its been a while since I’ve setup Haaska, you may have to install/configure Haaska for you wife’s amazon account (aws.amazon.com, developer.amazon.com, alexa.amazon.com) but have the URL still point to your domain, to the same HA. But this is a big maybe, Home Assistant may get confused, or may only support 1 Haaska at a time as there are keys involved.
I use push notification when someone rings my doorbell. Is there a way to make Alexa say something like “Someone’s at the door” on all my devices when someone rings my doorbell?
A suggestion would be to use the Alexa Media Player custom component.
Otherwise for Haaska, I think you should be able to set up a binary sensor template in HA that updates its state based on the doorbell being pressed, and have HA/Haaska export the binary sensor to Alexa, and have Alexa trigger a routine when the binary sensor changes state, and have an action for “Alexa Says” (although I haven’t tried this approach myself).
OK got it to work!
Almost everything is working for me up to this point. But whenever I ask Alexa about a sensor status she’ll answer with the same sentence twice (example 1). The intonation indicates that the same sentence is concatinated to itself without a period.
When I ask her to turn on the light, she’ll not answer twice (example 2).
Example 1:
Me: “Alexa, is the kitchen window open?”
Alexa: “Kitchen window is open kitchen window is open.”
Example 2:
Me: “Alexa, turn off the corridor light.”
Alexa: “OK.”
Did anybody else experience such problems before?
When you take a look in the Alexa App under Devices, what does the kitchen window sensor look like?