Can you use an http endpoint instead of an https endpoint?

Of course, as the Home Assistant server is local I can have it be accessible over HTTP. I may look into allowing both HTTP and HTTPS traffic to the server on different ports then only use HTTP for things like Flic.

Https with a non-trusted certificate is kind of insecure anyway.

Sure, it is more about wanting to make sure that all traffic is encrypted within the network. Even if that certificate isn't trusted by a browsers (or a CA) having some encryption is better than none.

The middle ground here would be to set up a DNS server and then have a trusted certificated issued from a known CA.

I was simply hoping that I could either tell the HTTP Module to ignore certificate errors, or add my certificate to a trusted list. Sounds like that is currently not the case, can you confirm?

I am using the this module to connect my Flic Hub with a Home Assistant instance running locally on a Raspberry Pi 5. I recently added a self-signed TLS certificate to my Home Assistant instance and am now getting a TlsFailure error fom the http_class used within the module.

I am hoping there is a way to disable the TLS check, Home Assistant provides the verify_ssl: false option. I am looking for something similar to curl --insecure / -k but within the HTTP Class.

Upstream issue: https://github.com/blunan/flic-hub-home-assistant-module/issues/10

Hi there,

Is there a public changelog for the Flic Hub Firmware available?

Looking for this for two reasons:

1. Curiosity and transparency
2. to know when Matter will be supported

Thanks!