Other than DNS/SSL is there anything special required for webhook access?

1

I’ve configured my HA to be remotely accessible via DuckDNS. Navigating to https://<my_url>.duckdns.org successfully reaches my HA instance - so I’m properly forwarding external port 443 to 8123, Let’s Encrypt is configured, etc.

However, when I try to configure the SmartThings integration, the webhook it generates returns 405 (Method not allowed)

https://<my_url>.duckdns.org/api/webhook/<unique_id>

I’ve checked the SSL cert and the only warning it gives me is:

The Certificate is not issued by DigiCert, GeoTrust, Thawte, or RapidSSL

Otherwise, it says it’s configured correctly. Is there something else I need to do to allow this /api/webook endpoint to be reachable?

-Rick

2

The request to HA must use the POST http method.

1 Like
3

@koying - I’m not sure I understand. I don’t think I have any control over how SmartThings accesses the API endpoint.

4

Ah, nevermind, overlooked you were using the HA integration.
What tells you “405”, then?

5

That’s a great question - and you’re right, this might be something different. When I go to create the SmartThings integration, I get the below dialog:

image
image1198×696 55.5 KB

My first step was to grab the webhook URL that it shows in the step immediately preceding this step and plug it into a browser, which is where I get the 405 (which, to your point, is probably because it’s defaulting to a GET).

So then I guess my question is: how can I diagnose why SmartThings is unable to reach my webhook API, despite remote access/SSL being configured properly?

6

Ah - I was using a SmartThings token that I had previously generated via HA Cloud. For some reason it didn’t like me reusing that, upon creating a new token, it works!