Ok, this might be a stupid question but, do I need to keep the add on running after I generate the certificates? (which worked flawlessly)
Thanks for anyones advice
-Bob
Ok, this might be a stupid question but, do I need to keep the add on running after I generate the certificates? (which worked flawlessly)
Thanks for anyones advice
-Bob
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:
Removed - Updated below.
This is a maintenance release and does not have breaking changes.
Questions? Join our Discord server! https://discord.me/hassioaddons
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,
@chenghs You do not need this add-on to be forwarded to the outside world.
This add-on is a one-time run / needed one time only type of add-on.
It only provides a tool to obtain a certificate easily. After obtaining it, you wonāt need it anymore.
So Iām not sure what you question or issue is at this point.
@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)
This is a maintenance release and does not have breaking changes.
Questions? Join our Discord server! https://discord.me/hassioaddons
this is so easy to use!! thank you !
Does anyone else have the issue of the fan control missing the medium_high option?
Howd you make out here? Im facing the exact same issue and havenāt found a resolve yet.
oi. if anyone else start losing their mind trying to figure out why their caseta component isnāt working, i solved it by providing the complete vs relative path in the config.
mazel.
Iām running home assistant as a Docker image on macOS. As such, I donāt have access to the Home Assistant Community Add-on store that is used to load this app. I saw mention of a manual way to do so. Can I use this app with my set up and, if so, how?
I currently have access to my Caseta devices via a SmartThings integration. I no longer use SmartThings to control the devices so my thinking would be to delete them from SmartThings and then add in this integration. Would I then have to redo all my automations referring to the Caseta devices? Iām hoping, given that the device names wouldnāt change, that I wouldnāt. If not, if wouldnāt be a huge amount of work to redo them. The reason I ask is directly accessing the Lutron hub instead of going through the SmartThings hub much of an improvement? I still need to access the SmartThings hub to get to my SmartThings motion sensors.
Hey, thanks for making this an easy integration.
Is there a possibility to add more than one bridge to an instance?
I also noticed the following mentioned in the log;
How stable is the build? Is it safe to use in a business environment (small restaurant, retail outlet, etc?)
Hey, thanks so much for providing this. Unfortunately, even thought the web ui tells me that everything was succesful, I am not seeing the cert files being generated. Any chance it is an obvious mistake I am making?