before I raise an Issue or Feature Request, I'd like to get your view.
Homeassistant allows using HTTPS out of the box with a certificate since a couple of weeks. By OOTB I mean without additional "Apps" like DuckDNS. This comes with the caveat, that Homeassistant is now ONLY available via HTTPS (if configured) and no longer additionally via plain HTTP.

Now the problem:
I use a self-signed certificate.
While this works fine for the rest of my home (where I just trust it), Bambuddy now seems to have an issue to connect to Homeassistant (and the switch I want to use in Bambuddy). I assume! that this is because of my self-signed certificate. In the past this problem did not materialize, because I could direct Bambuddy to use plain HTTP. This is now no longer possible on Homeassistant side.

Question: is it possible to place my root-certificate somewhere, allowing Bambuddy to trust it? Is there a deeper issue with HTTPS?
I have a similar problem when I try to connect to MQTTS (although here i still have the unencrypted fallback on Mosquitto side.)

Thank you!
aebgit