The Haaska Super Thread

[jrlambs]

Hi, I managed to get Haaska up and running pretty easily. I’m able to ask alexa to turn devices on and off and it works great. I was trying to set up some alexa automations based on device state though it they never ran… It seems like this automation does not support pushing device state back to alexa when it changes, but I can’t find anywhere where it says it does or does not support this… and it could easily me just having something configured wrong… like I need to enable that option or something.

Does this project currently support sending device states back to alexa or is it only available for if alexa queries the device status?

[kerryland]

I believe you need to install an alternative script which added pushing back device state.

I have not installed it and can’t help with support

[Bacara]

Just a small detail did all the difference. Well done man. Thx very much for your tip. Just that and my problem was solved. had to come to say thx. regards

[LinkX (Ricardo Fidalgo)]

Hello,

When I make a lambda test. Say “succeed” but appear this error. Anybody have solutions?

Thanks

{
  "event": {
    "payload": {
      "type": "INTERNAL_ERROR",
      "message": "404: Not Found"
    }
  }
}

[Underknowledge]

I would guess that your URL to your instance is off

What is 404 error and how to fix it?

[LinkX (Ricardo Fidalgo)]

I solve this with new instalation. Thanks

[debianlinux (debian)]

I have the same 404 issue with my lambda tests. I am assuming that if I plug my base_url into an average web browser and it successfully brings up my home assistant interface/login from anywhere that the url is in fact correct. LinkX suggested a new installation worked but that sounds like a very broad solution that I don’t know what exactly he did to fix it.

[debianlinux (debian)]

okay, mine was a yaml indentation issue. only after reviewing it in a proper code editor that highlighted the code blocks could i see it because it was otherwise a valid yaml file

[huu]

Is there a way to monitor if haaska is down in uptime robot?
eg we can monitor https://myhassio.duckdns.org:8123

So is there a way to know if haaska down and if it is how do we reset it?

[Augspurger (M.Augspurger)]

How do you solve the Problem I have the same error while i try to setup Alexa to Home
Assistant.I did everything as it is disrcibed in the youtube Channel everything Smart Home.

[Ralfale (Ralf)]

Hi,

Did anyone face this error when doing the haaska function setup and test? Tried reloading the zip file but nothing works. I am on the latest HA OS and version.

{
“errorMessage”: “Unable to import module ‘hasska’”
}

START RequestId: 58ace516-e7ac-4de2-86f1-f4a6d710394e Version: $LATEST
Unable to import module ‘hasska’: No module named ‘hasska’

END RequestId: 58ace516-e7ac-4de2-86f1-f4a6d710394e
REPORT RequestId: 58ace516-e7ac-4de2-86f1-f4a6d710394e Duration: 1.10 ms Billed Duration: 2 ms Memory Size: 128 MB Max Memory Used: 42 MB

[wmaker (Tommy Long)]

Don’t know if this will help, but take a look earlier in this thread:

The Haaska Super Thread

i have set up all as in the wiki. when I test I get the error message: { "errorMessage": "Unable to import module 'haaska'" } my config.json: { "url": "https://sub.domain.de/api", "bearer_token": "XXX", "debug": false, "ssl_verify": true, "ssl_client": [] }

[Ralfale (Ralf)]

Yep, i tried reloading the zip. Still got back the same error code. Any possible areas you feel i can check?

I also found another thread mentioned about missing Request folder. Did a check on mine and its there.

Home Assistant Cloud Alternatives

@wmaker, Now has other vision [imagen] hope will work! test now says ok! [imagen]

[Craig01988]

I am also getting:
{
“errorMessage”: “Unable to import module ‘lambda_function’”
}

and I cant seem to find a way to resolve it?

[ggrw1011]

Getting this error and cannot figure out the issue:

{
“errorMessage”: “401 Client Error: Unauthorized for url: https://_______.duckdns.org/api/alexa/smart_home”,
“errorType”: “HTTPError”,
“requestId”: “d4a39a89-f0c7-4613-8f75-93d4e2cbadca”,
“stackTrace”: [
" File “/var/task/haaska.py”, line 111, in event_handler\n return ha.post(‘alexa/smart_home’, event, wait=True)\n",
" File “/var/task/haaska.py”, line 66, in post\n r.raise_for_status()\n",
" File “/var/task/requests/models.py”, line 940, in raise_for_status\n raise HTTPError(http_error_msg, response=self)\n"
]
}

[wmaker (Tommy Long)]

Seems to indicate HA is failing the request from Haaska due to not being authorized. Take a look at your config.json in Haaska. Above is a post from me that points to yet another post in this thread that gives an example of what the config.json should look like.

[wmaker (Tommy Long)]

I came across this thread…

Haaska Unable to import module 'lambda_function'

I had the same issue. While I am still having other issues, I was able to resolve the issue you described. I was getting the same error because the Handler was not updated. While the haaska directions are GREAT there have been some changes to AWS. Try scrolling down to the Runtime Settings and change the handler to haaska.event_handler. That resolved the issue for me.

[nenonano (Stefano)]

Hi all… today I received this email from AWS:
SBJ: [Action Required] AWS Lambda end of support for Python 3.6
ello,

We are contacting you as we have identified that your AWS Account currently has one or more Lambda functions using Python 3.6 runtime.

We are ending support for Python 3.6 in AWS Lambda. This follows Python 3.6 End-Of-Life (EOL) reached on December 23, 2021 [1].

As described in the Lambda runtime support policy [2], end of support for language runtimes in Lambda happens in two stages. Starting July 18, 2022, Lambda will no longer apply security patches and other updates to the Python 3.6 runtime used by Lambda functions, and functions using Python 3.6 will no longer be eligible for technical support. In addition, you will no longer be able to create new Lambda functions using the Python 3.6 runtime. Starting August 17, 2022, you will no longer be able to update existing functions using the Python 3.6 runtime.

We recommend that you upgrade your existing Python 3.6 functions to Python 3.9 before August 17, 2022.

End of support does not impact function execution. Your functions will continue to run. However, they will be running on an unsupported runtime which is no longer maintained or patched by the AWS Lambda team.

The following command shows how to use the AWS CLI [3] to list all functions in a specific region using Python 3.6. To find all such functions in your account, repeat this command for each region:

aws lambda list-functions --function-version ALL --region us-east-1 --output text --query “Functions[?Runtime==‘python3.6’].FunctionArn”

If you have any concerns or require further assistance, please contact AWS Support [4].

[1] PEP 494 – Python 3.6 Release Schedule | peps.python.org
[2] Runtime support policy - AWS Lambda
[3] AWS Command Line Interface
[4] https://aws.amazon.com/support

is it something I’d be concerned to?
TIA

[RamblinMan86 (Jordan)]

I got the same email and am hesitant to upgrade for fear it breaks everything, and I honestly struggled to get it to work in the first place and fear losing this functionality that I use quite often. Hopefully a braver and smarter soul than me can bring some clarity to this situation.

[simocyz (Simone)]

I tried to upgrade Python version from 3.6 to 3.9 editing runtime settings in AWS, under Haaska layers.
Saved, tried to “test” but it fails. Funny that my Alexa commands still work, I don’t know if they will stop working now or then, so I will wait for someone able to clarify too

as explained below, there was an old domain in haaska config.json on AWS.