No Components found

[pete83n]

Hello all,

I have the issue that haaska is not finding any of my components in Home Asssistant.

I have performed test in the pi and on lambda and both provide seemingly good results, except that no devices are found. Searching for devices in Alexa app does not result in anything either.

Thanks for your support!

Peter

{ "payload": { "discoveredAppliances": [] }, "header": { "namespace": "Alexa.ConnectedHome.Discovery", "messageId": "649af9d7-8bc3-464d-a9c3-f21531060cfe", "name": "DiscoverAppliancesResponse", "payloadVersion": "2" } }

[trisk]

Check the AWS logs for your Lambda function, haaska might be having trouble communicating with your HA instance.

[pete83n]

hey,

i checked and receive the following debug log:

START RequestId: 71bdfd76-aa0e-11e7-8d93-3340856113e3 Version: $LATEST [DEBUG] 2017-10-05T20:47:47.320Z 71bdfd76-aa0e-11e7-8d93-3340856113e3 calling event handler for DiscoverAppliancesRequest, payload: {} [DEBUG] 2017-10-05T20:47:47.339Z 71bdfd76-aa0e-11e7-8d93-3340856113e3 invoking Alexa.ConnectedHome.Discovery DiscoverAppliancesRequest [DEBUG] 2017-10-05T20:47:47.341Z 71bdfd76-aa0e-11e7-8d93-3340856113e3 Starting new HTTPS connection (1): pete83n.duckdns.org [DEBUG] 2017-10-05T20:47:48.53Z 71bdfd76-aa0e-11e7-8d93-3340856113e3 https://pete83n.duckdns.org:443 "GET /api/states HTTP/1.1" 200 32252 [DEBUG] 2017-10-05T20:47:48.115Z 71bdfd76-aa0e-11e7-8d93-3340856113e3 response payload: {'discoveredAppliances': []} END RequestId: 71bdfd76-aa0e-11e7-8d93-3340856113e3 REPORT RequestId: 71bdfd76-aa0e-11e7-8d93-3340856113e3 Duration: 804.86 ms Billed Duration: 900 ms Memory Size: 128 MB Max Memory Used: 31 MB

any ideas?

[pete83n]

no ideas?

I just summarized my situation once again: i have no tried to integrate haaska for ages and for some reason it does not work on the last mile.

I have prepared Home assistant for SSL and can reach my HA directly through https://URL.duckdns.org (without port).

I have setup the Alexa skill and authentication. Everything is working ok, I have enabled the Alexa App. Issue is that it does not find any device.

I have tried many haaska configurations my current version looks like this:

{ “url”: “https://URL.duckdns.org:443/api”, “password”: “PASSWORD”, “ssl_verify”: “ca-certificates.crt”, “expose_by_default”: false, “exposed_domains”: [ “light” ], “debug”: true }

When I run the make test version of haaska i receive the following output:

{ “payload”: { “isHealthy”: true }, “header”: { “namespace”: “Alexa.ConnectedHome.System”, “messageId”: “ea3942a4-83f9-4125-b6af-34b8e66567a8”, “name”: “HealthCheckResponse”, “payloadVersion”: “2” } } true

So everything look ok. When I test the lambda function online i receive the following debug log:

START RequestId: 4a797dc2-ab32-11e7-abc4-ad2968882cca Version: $LATEST [DEBUG] 2017-10-07T07:36:54.845Z 4a797dc2-ab32-11e7-abc4-ad2968882cca calling event handler for DiscoverAppliancesRequest, payload: {} [DEBUG] 2017-10-07T07:36:54.845Z 4a797dc2-ab32-11e7-abc4-ad2968882cca invoking Alexa.ConnectedHome.Discovery DiscoverAppliancesRequest [DEBUG] 2017-10-07T07:36:54.847Z 4a797dc2-ab32-11e7-abc4-ad2968882cca Starting new HTTPS connection (1): URL.duckdns.org [DEBUG] 2017-10-07T07:37:12.43Z 4a797dc2-ab32-11e7-abc4-ad2968882cca https://URL.duckdns.org:443 “GET /api/states HTTP/1.1” 200 30948 [DEBUG] 2017-10-07T07:37:12.100Z 4a797dc2-ab32-11e7-abc4-ad2968882cca response payload: {‘discoveredAppliances’: []} END RequestId: 4a797dc2-ab32-11e7-abc4-ad2968882cca REPORT RequestId: 4a797dc2-ab32-11e7-abc4-ad2968882cca Duration: 17257.29 ms Billed Duration: 17300 ms Memory Size: 256 MB Max Memory Used: 29 MB

Even that looks ok to me.

Any ideas suggestions from the crowd?

Thanks and best Peter

[ghost]

@pete83n did you solve this? I have the same status at the moment...

//Reidar

[cbrherms]

@Reidar6 If it's a fresh setup it may be due to payload version. Haaska uses V2 and AWS is now v3 by default. There's a way to change it to v2 via inspect on chrome, think it's documented somewhere in the closes issues

[ghost]

@cbrherms its an old updated, but I changed it to v2 as it changed when I updated other info. When I run the test in lambda I don't get any error. Just no rows from HASS.

[ghost]

Found it... "expose_by_default": false in the config.json requires 'haaska_hidden': false OR 'hidden': false on all devices to be seen in Alexa :)