Update: Philips retired their early FAQs on this matter in favor of a much more extensive explanation as to what’s going on. Everyone will be better for it, even Philips!
Here’s hoping Philips clarifies things and keeps at least unsupported “support” for 3rd party bulbs part of the platform. They (and I’m including myself) have invested in the platform and had high hopes it would remain open and flexible. That coupled with the fact that the customers who have attached standard 3rd party ZigBee bulbs to the Hue hub are probably some of the most faithful Hue customers. Little transparency about the change has been shared either ahead of time or after the fact.
Philips hue party software#
While Philips does have the right to change their software to meet their needs, the way this has been handled so far has been disappointing to say the least. Officially in the MeetHue developers forum Philips alluded to the change and there are a few FAQs (since removed) to the effect on the MeetHue site as well. It’s possible even the official Hue app would not likely be able to control them given mixed reports from people who have updated their hubs.
Philips hue party update#
From what we have gathered, the firmware update will block access to the Hue API for any non-approved bulbs essentially rendering them useless. Philips has not said a lot about this new development, even though the community of enthusiasts has been hammering the company online on Twitter, Facebook, Reddit, and other forums. This appears to apply to both the round v1 bridge and square v2 HomeKit-compatible bridge after the latest firmware update is applied. We’re also not sure if being “reset” means rebooted or factory reset. The recent change seems to suggest any non-Philips bulbs from manufacturers such as Cree, GE, and Osram will not be supported in many situations, whereas “Friends of Hue” branded product are. At the time of publication, it’s unclear whether 3rd party bulbs will stop working immediately after the firmware update or if they may only become inaccessible after the bridge is reset.
0 kommentar(er)
