Good news!
Thanks to everyone!
Is there not any way to connect Alexa directly to Home Assistant? I really don’t want to send my data half way around the globe and then back through a port in my router when both devices are on the same local network to begin with…
Can you run the Haaska skill locally somehow and avoid using AWS? Or is there some other local API that could be used? I’m okay with coding it myself if I have to, I just need to find out what options there are
Unfortunately, all magic that Alexa provides is delivered by Amazon’s services and therefore you need to have Alexa connected to the internet. Your only other option would be to use another voice assistant solution. To my knowledge however, there are no real local-only alternatives compared to the rich set of features Alexa & Google Home currently provide.
Anyone know how to integrate haaska into code-red?
This is an error in the Login with Amazon setup… let me get the thread where we discovered this.
@anthonylavado Done y solved the problem, the url to privacy is: https://developer.amazon.com/loginwithamazon/console/site/lwa/overview.html
Anyone tried this setup?
FYI Emulated Hue stopped working properly at release 0.91.4. It no longer turns on Input _booleans and with switches lacking brightness it performs the action but then announces the device is not working. There is a patch but it hasn’t been integrated into any of the recent updates including 0.93.3. It looks like a hack in emulated hue went unnoticed. I guess I need either to look at Node Red or start using the HA Cloud. I don’t m ind the price but dislike the idea of another cloud. OTOH it looks like hacks in the older Alexa interfaces can go unnoticed/uncorrected for a while.
Whats the point of homeassistant if you cant use it to local control lights using alexa… the whole point and goal of homeassistant was to get away from relying on the cloud… most of the new alexa devices support local control now for lights and things even when your alexa goes offline but now homeassistant doesnt support local connection to alexa… is this going to be fixed so that homeassistant is true to its roots or not?
Your beef is with Alexa not HA.
This is working again in the stock 0.94 release. The “patch” was literally adding 2 characters to some Python code, so pretty easy to recover from in 0.93.
Little bumps in the road is why I usually wait a week after a release before I decided to upgrade…
same what if they just offered a free version with ads or something? I know they would make less but more people would use it then and they will make their money back.
receive this in Lambda
any clue?
{
“errorMessage”: “401 Client Error: Unauthorized for url: https://xxx.duckdns.org/api/alexa/smart_home”,
“errorType”: “HTTPError”,
“stackTrace”: [
[
“/var/task/haaska.py”,
111,
“event_handler”,
“return ha.post(‘alexa/smart_home’, event, wait=True)”
],
[
“/var/task/haaska.py”,
66,
“post”,
“r.raise_for_status()”
],
[
“/var/task/requests/models.py”,
940,
“raise_for_status”,
“raise HTTPError(http_error_msg, response=self)”
]
]
}
I use IFTTT webhooks, and integrate IFTTT and Google Home.
The same is possible with Alexa.
Of course this exposes HA to the internet, but with an API key, I fell relateively safe.
Tricky to set up (especially in a two language household) but works flawlessly, with the control (outside of voice control) kept local.
Looking forward to trying Almond integration… Have not read yet but hope that HA CLoud is not required to use it…
I have the same error 500 you had, could you help me to solve this?