Philips changes support for 3rd party lamps from Hue, twice.

It seems a firmware update for the Hue bridge and Hue bridge 2 has removed compatibility to 3rd party lamps, that version of the firmware will only work with “Friends of Hue” lamps and no longer support generic Zigbee Light Link lamps.

There was a lot of backlash on this as it can make existing, working, setups useless and raised questions about Philips still effectively being a  member of the  TCLA and if Hue bridges are still Zigbee complaint ?

So, Philips have announced they will (or have) reverse(d) the update on twitter and on meethue.

One sore point seems to remain : Apple HomeKit certification apparently not only applies to the Hue bridge but also to the lamps connected to the Hue Bridge :

Before the 1.11 software update, a bug in the Philips Hue system allowed some non-Apple HomeKit certified lights to work with Apple HomeKit. Our 1.11 software update removed the bug with the result that non-Apple HomeKit certified lights no longer work with Apple HomeKit. This remains the case.

(from meethue). Welcome to the long arm of Apple‘s Walled Garden.

 

 

The discovery and confirmation of the update that removed support :
iPhone-Ticker : http://www.iphone-ticker.de/firmware-update-fuer-philips-hue-verhindert-das-einbinden-von-osram-lightify-90450/
Meethue on Twitter : https://twitter.com/tweethue/status/674248181425774592

The announcement of the reversal :
Meethue : http://www2.meethue.com/en-us/update
Twitter : https://twitter.com/tweethue/status/677597933638955008

LivingColors / LivingWhites adapter starter set part 1 : remote

Here is what is inside the LivingAmbiance / SmartLink / LivingWhites (they should really use less of these trademarks) remote

 

LivingWhites remote pcb
LivingWhites remote pcb

 

On the left : a TI CC2530 a “Second Generation System-on-Chip Solution for 2.4 GHz IEEE 802.15.4 / RF4CE / ZigBee”

On the right :  a Cypress CY8C2044624 a CapSense controller.

The CC2530 has the 2.4 GHz transmitter and reciever and a microcontroller for the wireless protocol. The Cypress chip handles the buttons and probably the LED’s and speaker (the big square on the right). The UX logic can be in any two of the chips.

The PCB has some capsense buttons that are not on the faceplate. I assume the same PCB is used for both the LivingWhites and LivingColors remotes.

Livingcolors Gen 2 WILL work with Livingcolors SmartLink

 

Correction :

Die hard nerds know this all along : don’t trust the manual. I tried this out in a big store and Rde in the comments pointed this out as well.

In a previous post this was still unclear, now it’s sort of confirmed : the Gen2 remote wil work just fine with the SmartLink lamps and adapters and the Livingwhites Smartlink remote will work with the plain Gen2.

So now it’s clear there are only two generations and protocols : The Gen1 and the SmartLink.

The picture in the manual for the LivingWhites Starterpack adapters  is still pretty confusing:

LivingColors remotes, Gen2 no Smartlink
LivingColors remotes, Gen2 no Smartlink

The one on the right could be the Gen2 remote but also the Gen1 remote.

Philips redesigns LivingColors, breaks compatibility

Philips has recently introduced a new generation of the LivingColors lamps called “LivingColors 2nd Generation“. These lamps are incompatible with existing remotes and the new remotes cannot be used with “old” lamps (as described in the manual on page 3).

This also means kits like the CC2500 Arduino shield can not control the new “LivingColors 2nd Generation”.

The exterior and user interface of the LivingColors has not been changed as far as I can see. Internally, a lot has changed.

Instead of the CC2500 + MSP430 combo (shown here) :

Philips has used a CC2530 which is a 8051-alike and a IEEE 802.15.4 RF :

Notes: 2

(you can see the PCB here)

The CC2500 and CC2530 are entirely different devices.