Closed karlc28 closed 5 months ago
@jbergler How do I fix this as every time home assistant restarts I get the webhook request
@karlc28 hello - the notification will go away once you successfully receive a webhook from the ttlock cloud. I suggest you double check that the url you have setup in the ttlock portal is reachable from the internet.
Sorry to sound stupid but how do I check that
An easy way is to open the webhook url in a web browser when you're not connected to your home internet. If it times out or says connection refused then it's not working.
I can't really provide much support for this, given there's so many little details that vary from setup to setup. If you have a nabu casa cloud subscription, their remote access provides a proxy service for webhooks that this integration will use. Otherwise I'd say look into however you have remote access to your home assistant setup.
I am using cloudflared When I go to the url it just shows a white screen The lock works correctly but the notification keeps returning
i can reach my webhook from outside my network, but don't know why the notification don't go away... the url is corrent at ttlock webhook :( and i'm using cloudflared too... anyone knows how to make a better test?
An easy way is to open the webhook url in a web browser when you're not connected to your home internet. If it times out or says connection refused then it's not working.
I can't really provide much support for this, given there's so many little details that vary from setup to setup.
If you have a nabu casa cloud subscription, their remote access provides a proxy service for webhooks that this integration will use. Otherwise I'd say look into however you have remote access to your home assistant setup.
Cannot access the webhook at all Not sure where to go from here I'm using cloudflare to access remotely and would appreciate any help
Callback url test failed:javax.net.ssl.SSLHandshakeException : sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
i see this error when click on test... but i do have ssl with this url
Callback url test failed:javax.net.ssl.SSLHandshakeException : sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
i see this error when click on test... but i do have ssl with this url
You might have some sort of access control to your CloudFlare tunnel. I had a geography based one. I'm living in the UK and the WebHook notifications were being sent from Germany. After allowing German IPs to bypass the tunnel, the notification disapeared for me.
Yeah I think I've got it.
Copy the webhook link from the notification in Home Assistant.
Login to Open.lock.com
Open the app you created.
Past that link into the Callback URL field.
Done.
Thanks everyone who chimed in with help! @karlc28 or anyone else who reported problems - are you still having issues?
I've also just spotted that there is now a "test" link over at euopen.ttlock.com
Callback url test failed:javax.net.ssl.SSLHandshakeException : sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
i see this error when click on test... but i do have ssl with this url
You might have some sort of access control to your CloudFlare tunnel. I had a geography based one. I'm living in the UK and the WebHook notifications were being sent from Germany. After allowing German IPs to bypass the tunnel, the notification disapeared for me.
How do you do that I'm on cloudflare too
An easy way is to open the webhook url in a web browser when you're not connected to your home internet. If it times out or says connection refused then it's not working.
I can't really provide much support for this, given there's so many little details that vary from setup to setup. If you have a nabu casa cloud subscription, their remote access provides a proxy service for webhooks that this integration will use. Otherwise I'd say look into however you have remote access to your home assistant setup.
Hey. I have the same webhook issue. I use duck dns to connect to HA outside of my network. I noticed that the webhook is trying to access through https://xxxxxxxx.duckdns.org:8213/api/webhook/xxxxxxxxxxxxxxxxxxxx. But i only use the duck dns url withour the port 8123. Maybe that is why i'm getting the webhook url notification. How can i resolve this and make it call https://xxxxxxxx.duckdns.org only and not :8123 at the end?
The notification only makes a guess at the url based on what home assistant knows. If you're using port 443, then you can just change the url in the ttlock portal and it should work.
The notification only makes a guess at the url based on what home assistant knows. If you're using port 443, then you can just change the url in the ttlock portal and it should work. - Jonas
I got it to work by entering it without the port number in the callback url. Thanks
Callback url test failed:javax.net.ssl.SSLHandshakeException : sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
i see this error when click on test... but i do have ssl with this url
I have the same error when I try to add the generated webhook URL on the TTLock portal. (Also using Cloudflared)
I tried configuring Cloudflare but I didn't find anything useful...
I think the webhooks on my instance of HA are exposed through Cloudflared and I haven't been successful in trying to expose them
There doesn't appear to be anything wrong with the integration here, so I'm closing this.
Describe the bug
I followed all the steps now i can access the lock in home assistant but the we hook notification keeps coming back
Expected behavior
The notification to stay away
Diagnostic info