Problems adding Hue Smart Button and Hue Dimmer Switch V2 to HE (SOLVED)

[Wapiti]

Hello everyone,

I have recently purchased a HE to reduce the number of bridges in my setup. The key selling point for me was the new Apple HomeKit integration.

I have managed to add all my Hue light bulbs to the HE. However, when I add either the Hue Smart Button or the Hue Dimmer Switch V2 it first looks like everything is working nicely. They both get added and show up under devices. But for some reason they then go back into pairing mode (orange flashing light) and button presses don't get passed to HE.

I suspect that the initial pairing fails on the button/switch side for some reason. In both cases I'm using the designated drivers (Hue Smart Button and Philips Dimmer Button Controller V2).

Has anyone come across this problem and managed to get them added and working with HE?

I know that there is a Hue bridge integration and at least two community apps for the Hue system. However, I'm not really interested in running multiple bridges as mentioned above. That kind of defeats the purpose of the HE in my opinion. Also I want to use the HomeKit integration which shows devices that are connected via a Hue bridge as incompatible.

Any advice is much appreciated!

[Grizzlebeard]

Yes this has happened to me twice, popping the battery after pairing should fix it, as described below.

Philips hue dimmer switch v2

This one was a challenge (for my small brain), I bought a philips hue dimmer switch v2 and added it no problem, set up the buttons for lights, job done. Shortly before adding it I updated to the .123 firmware version where we seen the bugs when going to the devices page. Initially I thought this was something I had done so I restored my HE to the previous backup which was prior to me adding the new dimmer switch. Anyway, one thing led to another and I was distracted from adding it again that da…

[Wapiti]

That did the trick. Thanks so much!

I actually came across the post you linked while I was trying to solve my problem. However, I only read the first paragraph and thought it was due to firmware issues. Since the post was also more than a year old I thought that the issue was probably fixed now.

Guess I should have read to the end.

Anyways, thanks again!