I just enabled HTTPS on Z Wave JS and don’t have it connected to any certs, and I’m now getting an error 502 “Bad Gateway” whenever I try to open the Z Wave JS config page. Is there a way to reverse this setting now that I can’t access the config page? I can’t find the config files for it anywhere.
Also, the reason I was enabling this in the first place was that the devices list on the Z Wave JS 2 MQTT page wouldn’t populate when I accessed it through my https reverse proxy. It shows the rest of the UI but the list of devices is empty. Once I get my UI back, is there a way around this so I don’t have to get at it through homeassistant.local?
The zwavejs2mqtt add-on does not support enabling HTTPS within z2m. Once you do that, the add-on is hosed. You’ll have to restore from a backup, or manually edit the zwavejs2mqtt configuration files inside the add-on container as describe in this workaround. Basically, the container for the add-on is not built with the required libraries and so it fails when you enable the functionality. Also, I think the add-on natively supports HTTPS via the Ingress functionality, but I’m not entirely sure how that works.
Also, the reason I was enabling this in the first place was that the devices list on the Z Wave JS 2 MQTT page wouldn’t populate when I accessed it through my https reverse proxy. It shows the rest of the UI but the list of devices is empty. Once I get my UI back, is there a way around this so I don’t have to get at it through homeassistant.local?
I doubt this has anything to do with the z2m HTTPS setting, and more to do with your proxy configuration. I use zwavejs2mqtt behind Traefik (standalone docker), and don’t need to enable HTTPS in z2m.
Thanks, I ended up just going with option 1 and restoring from the last backup. Awesome to have the workaround, but I think I’ve done enough damage playing with stuff I don’t understand.