How does the official Hue (bridge) app communicate with the Hue bridge?

Hello everyone,

I was wondering how the official Homey Hue (with bridge) app communicate with the bridge?

Is it through HomeKit? (I guess not). Is it local over ethernet (I hope so)? Does it rely on the API (and thus not local - I hope not)?

If local over ethernet, does that mean that it uses a kind of hue-bridge-specific protocol to communicate? Is it open or proprietary?

Hi,

The hue bride contains its own http server and therefore the API can be accessed locally. It is not homeKit, it is local over ethernet, but it relys on the api, which is local. It uses the hue-bride-specific API which is well documented, you can get access here:

Hi Nick,

Thanks a lot for your answer. Very clear now.

I had experience with the home bridge Hue plugin (GitHub - ebaauw/homebridge-hue: Homebridge plugin for Philips Hue) and indeed it communicates with their API locally as well. I found that this plugin was more feature rich than the official homey hue app, so that means that there would probably be room for an improved community Hue bridge app.

One more question: can the Hue bridge be also connected via Matter ? The Hue bridge is itself a Matter bridge and Homey is a Matter controller, so this could work? Just trying to understand the ecosystem.

Before creating one, ask Athom if they will actually allow it in the app store. Officially the guideline is that there should be only one app per brand and that developers are encouraged to work together by issuing PR’s against the app that already exists, but that guideline is immediately negated by Athom pretty much making all their own apps closed source.

Thanks for the heads up. I wasn’t aware of that.

I imagine we could run the app anyway and share it through Github even if it is not accepted in the App Store.

Correct, or publish it through the community app store(s).

And of course exceptions (were) (are) made

2 Likes