Hue Bridge Integration and Tasmota issue with recent HE platform updates

🧰 Built-In Apps and Drivers Built-in Apps
21

Ok problem solved. I edited the lines in below function and changed them to http instead of https. Auto discovery didn't seem to work but manual did. Thanks for your assistance

void sendBridgeInfoRequest(Map options)

Is https mandatory for genuine Hue bridges (either V1 or V2)?

I thought I might make a feature request to HE staff to add option of disabling https in built-in driver as I suspect this is the same issue that is causing their driver to not work with Tasmota either.

22

It is mandatory for API V2, which is the default API version the integration will use if the Bridge is compatible (vaguely recent firmware on the V2 Bridge; the V1 API is still available as of now -- and it's likely the version to which this endpoint belongs, though it's a bit different from the others, and I'm not sure what their plans are for it).

The next version of the built-in integration will use HTTP if the integration is configured not to use the V2 API. This is an option under "Advanced" when you initially install the integration and before you add the Bridge (or any devices). I believe that should address this case.

1 Like
23

Its curious it uses http to locate the bridge then https to discover devices.

Thanks for the info and the assistance.