Closed blhoward2 closed 3 years ago
I believe this feature is unintentionally locking people out of zwavejs2mqtt that didn't know it was more involved than "check this box" as seen here https://github.com/hassio-addons/addon-zwavejs2mqtt/issues/309
I think this issue is caused by a few things outside our control. It appears the addon lacks openssl in the image. It also looks like ingress modifications may break this. And there is no way in the addon to specify the pem files. These are all things @frenck would need to look at.
With ingress HTTPS is provided by Home Assistant. Not zwavejs2mqtt or the addon.
I edited my comment. I agree but the issue seems to be that we have a UI option for other installs to allow https. I'm not sure that we could fix that at all on our end.
Maybe we could detect we're running in your docker and then disable the setting. I'm not sure what modifications you make. Is there a file or something inside the container that is unique that we could look for to know we're in your docker and not ours?
I'm not sure what modifications you make.
None.
Ok. Do you build your own docker image? If so, can you touch a file inside the container for us to check for? I'm not sure how else to distinguish your image vs ours.
Presently, you can enable https only via an environment variable. Addon users cannot set the environment variable, though, and https is likely to be of greater interest to support cameras for SmartStart.
I think that we should add options to enable https, and to specify the SSL cert/key (to enable central certificates to be used) to the Settings UI.
If a user clicks to use the camera and we aren't running https, we should consider displaying a message to the user explaining that limitation.