Ha-bridge: Home Assistant Discovery can't use SSL?

[scottdalton]

It appears that the Home Assistant device discovery is http:// only and SSL fails to work?

[notoriousbdg]

Looks like I've hit this issue too. The code does look to have http hardcoded. Could you add optional support for https?

[jbardi]

Just curious, are these home assistant instances remote? If not, why not use the local ip address without SSL, unless there is a reason you would need SSL on a local network.

[scottdalton]

If you've set up home assistant directly with an SSL certificate, it only responds via SSL AFAIK. There's no way to access it via IP directly.

FWIW, I ended up just setting up a reverse proxy with SSL to local subdomains and getting rid of Home Assistant's built in use of certificates. I'd run into a few other headaches like this which seemed to necessitate this.

But if you're trying to use the tools Home Assistant provides, it will be a stumbling block, so it still seems like it may be a worthwhile feature for a lot of folks.

I look forward to using HA-Bridge now that I can get it talking directly to my HAss setup. Appreciate the fast and good work on it!

[noodlemctwoodle]

Same issue as previously posted. I'm using my own wildcard SSL cert and I'm unable to access any Home Assistant entities with SSL enabled via Home Assistant config.

[notoriousbdg]

After upgrading to 4.1.0 and importimg the cert chain for my cert into the java keystone, I'm able to discover my home assistant devices. Thanks @bwssytems.

sudo keytool -trustcacerts -keystore /usr/lib/jvm/jdk-8-oracle-arm32-vfp-hflt/jre/lib/security/cacerts -storepass changeit -noprompt -importcert -file /etc/letsencrypt/live/blah.com/chain.pem