The Haaska Super Thread

Third party integrations
247

Super thanks for your help!

Unfortunately HA is not reachable annymore after loading the latest snapshot (which also holds the latest working Haaska config). Not with the static IP of the PI and not with the DuckDNS adress.

The green LED of the PI is still flickering after loading the latest snapshot, so seems it started up somehow.

Is it possible this has something to do with the latest HA version? I believe it changed something in the external link settings. I tried to try flash an older version of HA on the SD card, but HA keeps updating to the newest version while installing the newly prepared SD card.

Or is there a way to retrieve the .yaml files (and so my settings) from the snapshot .zip?

248

I’ve managed to restore my latest snapshot, and reach the files using SAMBA in combination with the static IP adress of the RPI. This opened the file folder with the backup folder and the config folder etc. of the Home Assisstant configuration.

I was able to back up the yaml files here, just in case. And to comment out the Haaska settings in the configuration.yaml file and save it. I was then able to reach the Home Assisstant configuration with the static IP again after restart. So guess something got broken with the Haaska or DuckDNS configuration.

I will save my snapshots without password protection from now on!

249

I never logged in into AWS etc.annymore after configuring Haaska. It worked for over a year without problems. So settings should be still the same as back then. But now something suddenly broke :expressionless:

I’ve tried to get a new long-lived acces token in Home Assisstant and configure it also into AWS again. But it still doesn’t fix annything. I’m able to run a test there, and this test also somhow fails.

Maybe it has something to do with an Home Assisstant update? I know that there was an recent update concerning external links?

But guess more Haaska users would have encountered the same problem then, right?

:woozy_face:

250

Hello guys,

I’m getting this error when i run the test of haaska.

I really can’t understand what I wronged. The file config.json is on the configuration screen of AWS and I already modified it with mu url and token…

{
  "errorMessage": "[Errno 2] No such file or directory: 'config.json'",
  "errorType": "FileNotFoundError",
  "stackTrace": [
    [
      "/var/task/haaska.py",
      106,
      "event_handler",
      "config = Configuration('config.json')"
    ],
    [
      "/var/task/haaska.py",
      79,
      "__init__",
      "with open(filename) as f:"
    ]
  ]
}
251

For a comparison, in my setup…further down the AWS configuration screen, you should see a panel “Function code” with an “Environment” side tab which contains a list of files and folders. The high level folder is haaska and under it are several other folders (such as bin, certifi, chardet, requests, etc) plus the two main files of interest here: config.json and haaska.py. If yours looks like this, then hmmmm hard to say what is wrong.

252

I’m reconfiguring Haaskaat the moment. Just started over from scratch with also a brand new HASS installation.
But got stuck at the DuckDNS setup. I believe to had port forwarding configured in my router but somehow the list of port-forwarding was empty now. I recently updated my router firmware (AsusWRT), and it’s quite possible that this was in the same period when my Haaska config stoped working. So seems it was all about the router firmware update… Configured port forwarding again to port 8123, and DuckDNS is redirecting to my HASS config again.

Wasn’t expecting that the router update could be the issue here… :frowning:

253

Is there a way to scan for new devices? I’ve had Haaska up and running for a while but just added some new lights to my system and don’t want to unlink and re-add everything.

254

You can do that via the Alexa app. Switch to the “Devices” tab and click the plus icon at the top right corner. Select “Add device”. Select the type of the device that’s missing (but I think it will find and add any type of device anyway). Select “Other” when being asked for the brand. Now click on “Search devices”. After a couple of seconds/minutes it should be done and the devices should be visible in the devices tab.

Another possibility to search for new devices is using the Alexa SPA: https://alexa.amazon.de/spa/index.html?#appliances
Scroll to the bottom and click “Search”. This will trigger adding new devices from Home Assistant the same way the Alexa app does.

255

Just got this set up, and everything has gone smoothly. However, when I get to the step in the Alexa app to “scan for new devices,” nothing shows up. Not sure what I"m doing wrong at this point. Did I miss a step?

256

UPDATE: Another try: successful , no fault at all
Mine failure log (testing haaka) here, but I am unsure the reason,
Can someone help me?

START RequestId: dc76b347-5a5c-4461-911f-4a93d84d103a Version: $LATEST
[DEBUG]	2020-08-12T03:02:24.843Z	dc76b347-5a5c-4461-911f-4a93d84d103a	calling alexa/smart_home with {'directive': {'header': {'namespace': 'Alexa.Discovery', 'name': 'Discover', 'payloadVersion': '3', 'messageId': '1bd5d003-31b9-476f-ad03-71d471922820'}, 'payload': {'scope': {'type': 'BearerToken', 'token': 'access-token-from-skill'}}}}
[DEBUG]	2020-08-12T03:02:24.856Z	dc76b347-5a5c-4461-911f-4a93d84d103a	Starting new HTTPS connection (1): MY-ADDRESS.duckdns.org:443
[DEBUG]	2020-08-12T03:02:27.312Z	dc76b347-5a5c-4461-911f-4a93d84d103a	https://MY-ADDRESS.duckdns.org:443 "POST /api/alexa/smart_home HTTP/1.1" 200 162028
END RequestId: dc76b347-5a5c-4461-911f-4a93d84d103a
REPORT RequestId: dc76b347-5a5c-4461-911f-4a93d84d103a	Duration: 3003.27 ms	Billed Duration: 3000 ms	Memory Size: 128 MB	Max Memory Used: 51 MB	Init Duration: 230.01 ms	
2020-08-12T03:02:27.845Z dc76b347-5a5c-4461-911f-4a93d84d103a Task timed out after 3.00 seconds
257

Hard to say…it appears that Haaska made a successful https POST call (it says it got 200 “OK” returned), but looks like no data was returned from HA. A guess is that there is something in your HA config that’s not allowing anything to be returned.

258

Hello,
I’m having an issue with discovering devices, when I ran the test on AWS it was successful and devices also detected, but when I try it on Alexa app, no devices are detected.

While installing, Alexa Smart Home option wasn’t available in my region, so I switched everything to US, and also my echo devices language too US English.But that doesn’t help either. Has anyone else faced a similar issue?

259

Did you choose the region according to this table?

Unfortunately I don’t know what you have to do if you have another skill language as listed in the table.

260

I selected the language as per the table (US English) and selected region as US English everywhere during the setup.

I’m in India, but the region doesn’t have Alexa Smart Home option during setup

261

You could try to choose language English (IN) and Lambda function region EU (Ireland).

262

Tried Again, still no luck - same thing - getting success on test, but no devices discovered on Alexa.
Used ENglish (IN) & EU (Ireland this time)

263

Hey… didn’t work when I tried Ireland region at forst but 3 days later Alexa automatically discovered all devices from home assistant! Don’t know what happened there :sweat_smile:

264

Sorry to push this up, but I continue to have this issue. My region should be US (Virginia) (In fact, I live in Atlanta, Georgia, USA). No devices continue to be found. Any advice?

266

I am successfully configured haaska , but I am unable to link the skill with home assistant account

Screenshot_2020-08-26_11-13-50
Screenshot_2020-08-26_11-13-501366×768 62.4 KB

please, someone help me

267

Oh boy. But nice to hear that it’s working now! :raised_hands:

1 Like