Hue bridge API integration VS matter bridge integration

Iā€™m getting my ducks lined up for making a whole house change for room lighting which includes rewriting all automations, moving to a new HE hub and moving from the Hue bridge legacy integration on 2.3.9. This is a once in every six years project for me and will again provide consistent lighting automation across the whole house after six years of tinkering with different rules.

I have to admit I havenā€™t gone digging too much yet, but Iā€™ve seen that the Hue bridge now can be added as a matter bridge. What Iā€™m wondering is what is the difference between the ā€œnormalā€ API integration and the matter integration. Which oneā€™s more feature rich? More stable? Future proof?

The built-in integration supports more features, including scenes and button devices, plus more features on devices, so I'd say it's more feature rich -- but Matter is sufficient for many use cases. I can't speak to stability, as both are either new or revamped recently, but if you notice any problems with either, a report here with sufficient information should be enough to figure it out. Hard to speak about "future proof," either, but it's unlikely Hue will discontinue either their local V2 API or Matter support. The API has the advantage of being self-contained and not depending on other standards (except HTTP), but it's unlikely Matter will go anywhere or get worse, likely only better. :slight_smile:

4 Likes