"unable to connect, check uri and config" when using https about hass.agent HOT 5 CLOSED

Hey @bverkron,

When you open HASS.Agent, go to Configuration and then click Home Assistant API on the left:

Here you can set your own certificate, and if it's installed in your pc you can try checking use automatic client certificate selection.

Let me know if that helps.

from hass.agent.

I misspoke a bit in my description, was tired when I wrote the issue. I don't actually have a self signed certificate but rather my cert is for the duckdns url that I was using before switching to Nabu Casa. IIRC connecting via https but using the IP on the LAN will throw this kind of error for any https cert you have because they're for internet domains / urls and not local IPs.

I rectified the issue by using my Nabu Casa url instead of my local IP for now.

from hass.agent.

Yep, you need to use the duckdns url and open a port in your WAN firewall, so not ideal. You don't need to provide a cert for duckdns though (as you can tell in my screenshot, I use duckdns for my testing environment).

But using the Nabu Casa url is safer :)

from hass.agent.

as far as I understand, an external URL is unusable while your internet connection is down. it would be nicer to use local IP while keeping HTTPS and use no certificate. could you implement an option to do so?

from hass.agent.

Hi @ALERTua,

If you enable https, home assistant (by default) won't listen to local non-ssl connections anymore. If you want to use both local and ssl connections, I wrote a short manual on how to achieve that:

https://hassagent.readthedocs.io/en/latest/notifications/notification-debugging-ssl/

Note that this only works with duckdns and other custom ssl solutions. You don't need to do this for nabu casa; in that case you can just the local ip.

from hass.agent.