Add HTTPS support for Home Assistant

[aherbjornsen]

Feature request

What problem does this feature solve?

The current Home Assistant support is HTTP only.

What does the proposed API look like?

How should this be implemented in your opinion?

There should be a checkbox enabling SSL/HTTPS.

Are you willing to work on this yourself?

Sorry, I do not have the necessary knowledge to do this.

[RiderCrazy]

Hello,

It could be very nice to get that little feature.

[awawa-dev]

Sorry, it does tell me completely nothing

[domotick]

Hi,

@awawa-dev It's about Home Assistant with the SSL protocol enabled.

In this case, neither the integration nor the wizard works.

It would be great to add SSL support to HyperHDR

[awawa-dev]

Hi
SSL is supported by HyperHDR out-of-box so still it's complete unclear for me what is about this issue. Keep in mind that I'm not using HA at all so it's a black box for me.

[domotick]

Hi,

This isn't when connecting to HyperHDR with SSL, but when we use the wizard to detect devices in an SSL HA instance.

Here's the line that fails

https://github.com/awawa-dev/HyperHDR/blob/master/www/js/wizard.js#L2504

Maybe you know how to fix it, I think all other "tunnels" work without SSL.

Thx!

[awawa-dev]

Thank you for pointing out the specific functionality that needs to be changed.

[mhackdo18]

Hi Anybody know how to fix it and cant add Home assistant as led hardware, I am using SSL also

[domotick]

Hi!

I dig futher... and what I get:

• HA implementation was done by @awawa-dev here following Phillips Hue model to bridge request to API (reason why error message speak of "Hue Entertainment API")
• Concerned file (server side) and modification is here
• So here is build the resquest

Problem: Wizard is only made to support IP and port to reach HA API, not SSL.
Solution: Maybe add one SSL option to force https?

I tried without SSL and devices are well detected, but advice: using zigbee device with 20ms of refresh delay is not sustainable and could dommage your light. MQTT broker is spammed with update request and only way to stop processing is to restart the broker...

[mhackdo18]

Hi!

I dig futher... and what I get:

* HA implementation was done by [@awawa-dev](https://github.com/awawa-dev) [here](https://github.com/awawa-dev/HyperHDR/pull/1014) following Phillips Hue model to bridge request to API (reason why error message speak of "Hue Entertainment API")

* Concerned file (server side) and modification is [here](https://github.com/awawa-dev/HyperHDR/pull/1014/files#diff-6bc5261ce58e373cf99e774ce556b2069ce24920540b5ccd7df575c029fe248c)

* So [here](https://github.com/awawa-dev/HyperHDR/blob/master/sources/api/HyperAPI.cpp#L1299) is build the resquest

Problem: Wizard is only made to support IP and port to reach HA API, not SSL. Solution: Maybe add one SSL option to force https?

I tried without SSL and devices are well detected, but advice: using zigbee device with 20ms of refresh delay is not sustainable and could dommage your light. MQTT broker is spammed with update request and only way to stop processing is to restart the broker...

Hi! I get away using this HA bridge,

https://community.home-assistant.io/t/use-home-assistant-lights-with-hyperion/678249

but I guess nothing better with direct integration, I wonder how to implement your build release? should i change the file or replace inside Hyperhdr and restart the app

[domotick]

hyperion-project/hyperion.ng#1886