No route to host Problem

Third party integrations
1

Hi all,
I have been using haaska for a couple of months now.
Sometimes I faced the “no route to host” error when testing the lambda function but then resolved itself automatically in a couple of hours.

The problem returned yesterday morning and is continuing until now so Alexa can’t discover nothing for two days.

The error is the one below:

image
image1452×91 16.6 KB

I also tried to do a POST call to my Home assistant by using Postman.
I sent the test request payload to:
https://myhassio:443/api/alexa/smart_home

It responds correctly returning the list of all discovered entities.

Then, what can be the problem if the service call from AWS fails and from Postman works correctly?

Many thanks!

2

I would point to an IP address and see if the problem persists.

3

Hi Fanuch, the problem persists also using the IP address.
I also reach https://myhassio:443 in browser. I’m going crazy!!!

4

I finally solved the problem. I think it’s a router issue. After a series of software reboot it still doesn’t working but after an hard reboot of the router the call from AWS does.
It’s remaining the mistery! Why the call from postman worked and from AWS doesn’t? :frowning:

1 Like
5

@Pasquale I’m having this issue too! By chance, are you running a Ubiquiti router?

Everything was working great with Haaska for 2 years (including moving houses and ISP’s) and now it stopped working all of a sudden.

6

yeah I rebooted my Ubiquiti router and everything worked!