-
-
Notifications
You must be signed in to change notification settings - Fork 114
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
HTTPError "404 Client Error: Not Found for url: https://****:8123/api/alexa/smart_home", #23
Comments
What version of HomeAssistant are you currently using? Thanks |
Thank you for your quick reply! I'm using Home Assistant 0.63.2 on Hassbian. |
@alekvie Can you send your configuration of Home Assistant? (It requires the Smart Home configuration for this skill now: https://home-assistant.io/components/alexa/#smart-home) |
You can even expose full domains to Alexa, if you want that:
Also, you should consider secrets (https://home-assistant.io/docs/configuration/secrets/) in Home Assistant, if you share your configuration more often (or just delete the password before sending it). Now if it is your real password in that configuration, you should change it. |
Thank you @TheJulianJES . There is nothing wrong with my configuration? |
@alekvie You will have to write:
It is the smart home option in the Alexa component, so you will always need that in your configuration. |
@TheJulianJES, ok. So as long as I have the smart_home: option in my configuration file, the error is probably caused by something else? |
@alekvie Well, I see that you also used v2 test event. Try using the new one:
|
@TheJulianJES, suddenly it works - the test and to discover new devices. Thank you so much for your help! |
I'm not sure if this is the correct way to ask for help. I used a older version of haaska by you, mike-grant, and everything were working fine. However, when I added a switch to home assistant alexa stopped finding devices (and I could not control the other devices with alexa). Thus, I tried the new updated version and now I get a error when using the following test event. Furthermore, alexa does not find any devices.
The text was updated successfully, but these errors were encountered: