Hi. Thanks for this. Installed flawlessly. No errors. Log looks fine. One problem I am seeing is HA does not seem to be able to track the status of a device. I can turn it on but that’s pretty much it. Am I missing something?
@TurboJones, yes, I believe I just started completely over with the bridge. Since this was the initial install, it was no big deal. IIRC, I believe you have to take the url from the 500 error page and post it into the Cert Web UI.
Thanks. It’s good to know I’m not the only one. I’ve manged to get things working for now through the SmartThings integration, but it’s a bit of a kludge, plus the HA is local (I think) which I prefer.
Once the cert files are in the ssl/lutron directory, you can uninstall.
As a note, I couldn’t get this addon to work so I did it the manual way.
As a second note, the spacing in the documentation and this post has only two spaces instead of the four that the Lutron integration has for each entry below lutron_caseta:
I updated to Release 4.0. But when I clicked the “Open Web UI”, I got an error message:
# This site can’t be reached
**myha.duckdns.org** refused to connect.
* Search Google for [myha duckdns org 5817](https://www.google.com/search?q=myha%20duckdns%20org%205817)
I have duckdns set up and I can access my Hassio (installed on Raspberry Pi) remotely. Not sure how I can make the lutron work. Do I need to set up the port forwarding for 5817 on my router? Any help would be highly appreciated!
Thanks a lot in advance,
@frenck Thanks for your prompt response and explanation. I installed the Lutron Certificate v0.4.0 and started it. In the installation section, you mentioned that Step4 is "Open the web UI for the “Lutron Certificate” add-on and follow the steps. When I clicked the “Open Web UI” on Lutron Certificate page (via Hassio -> DashBoard -> Lutron Certificate), I got the error:
# This site can’t be reached
**myha.duckdns.org** refused to connect.
* Search Google for [myha duckdns org 5817](https://www.google.com/search?q=myha%20duckdns%20org%205817)