If the real value was in the hub, and these other lights were getting a free ride on it, then the opportunity would be to charge more for the hub.
What is far more likely to be the case is that the support costs around problems caused by random third party components messing with the Zigbee network were exceeding the value of providing that support, particularly when you factor in that the customers they really wanted to grow wouldn't be using anything other than Hue's.
So, while blocking out 3rd party devices decreases the perceived value of the hub, the drop in perceived value is far exceeded by the drop in support costs. Easy win.
It's still hostile, but to a distinct use case, rather than their entire customer base.
Even they have elevated support costs, Philips's made their bed by offering compatibility in the first place for many years. If they want to remove it, they really should introduce a new model ("Introducing Hue 2.0: Now with less bulb compatibility!") and leave the existing customers unaffected.
Last year, Shimano (the bikes-and-fishing people) released a firmware update for their electronic shifting system which prevents 2012 (10-speed) parts from working with 2014 (11-speed) gear mechanisms. Literally, if you upgraded your bike from 10 speeds to 11, it worked when the hardware was released, but not after you installed the (irreversible) firmware update. This is with everything coming from a single brand!
You can read a little about that here: http://fitwerx.com/converting-shimano-ultegra-6770-di2-to-11...
...unless they ran a wire up the the controls to carry power :)
I'd be surprised if they did. A dynamo adds a noticeable load on the bike, and the people buying this are already optimising for small improvements. Adding a dynamo to power it would probably be a net negative for performance.
I run a dynamo generator for lights on my bike. The datasheet says it steals about 7 watts of power. I'm a relatively weak cyclist, but I can put out 230W continuously for an hour. The dynamo doesn't matter unless you're racing.
That said I still have good-old-classic 10 speed mechanical shifting. It works so well I don't see the need to add another computer-based gadget to my life.
How much power would that really generate? You can't make them too stiff, since part of the reason people like electronic shifting is that it's easy to do when your hands are numb from cold.
In general, being more compatible increases the value of a device. When it doesn't, you've got some bad market forces at play.
Put another way, if your analysis is correct, it presents a fundamental weakness in any standardized architecture that relies on a central managing device, which could prevent the development of a robust ecosystem with many vendors.
There will always be bad actors. Often you design a system to handle them in ways that minimize support costs.
Consider the case of 802.11 or USB or ZigBee. In general, most of the value of providing a device that works with any of those is a function of how well it works with any other device. The support costs are also a function of how well the device interoperates with other devices.
That pretty much kills the value of making a device that only works with a manufacturers own devices, and provides strong incentives to work with as many as possible as well as possible.
I'm amazed at the level of belief in Philips' honest motives after such a move. They just saw a large market of 3rd party bulbs emerging and saw potential profits for themselves, that's the most likely explanation with the available information. If anyone has financial details to back up claims of "need" for such a move by Philips, please provide them.
Philips has been investigated and fined for antitrust violations repeatedly. They don't really deserve benefits of doubt regarding predatory/unfair business practices without need at this point.
Light Link - "Smart, easy-to-use lighting control designed for consumers." http://www.zigbee.org/zigbee-for-developers/applicationstand...
Building Automation - "Innovative, efficient and money-saving workplaces." http://www.zigbee.org/zigbee-for-developers/applicationstand...
It's conceivable that they could carry the Hue brand into other markets, but the existing Hue Bridge that just lost compatibility is definitely not that product.
Much to the rest of the industry's chagrin, CK holds a couple of fundamental patents on colored lighting by mixing red, green, and blue. Not that color mixing or PWM were new in 1997, but I guess they smushed together enough ideas that the patent office thought it was novel.
As far as I know, they do have some competitors (Lumenpulse comes to mind) but aren't under any significant threats in that market because every competitor pays them royalties anyway.
That makes this choice of Philips worse: they implement a standard, but then choose to ignore devices based on (probably) identifiers (and probably introducing incompatibilities). It's toxic to the whole ecosystem.
I think that some of their marketing material stated that they were ZigBee-compatible. So, I guess I can now (theoretically) sue them as a customer.
FTFY
After that, the same Boss would hope they should allowed their app to control third party bulbs, since that way at least they would have a brand presence, and by that way that would have allowed them to sell their bulbs better than others.
If the company looks at the employee like a tissue to be used and thrown, why is it so surprising to receive the same treatment back.
Currently, I'm using home assistant (https://home-assistant.io/) for controlling the lights, and if I ever buy other lights, they'd be controlled from there as well.
What should be interesting now is to wait and see if they lock down the API as well...
1. The costs they're incurring supporting non-hue compatibility might very well increase. Lighting is something people think they universally understand -- if it doesn't work when they expect it to, they call. In the rest of the "lighting world", people expect the lamp won't have problems working with whatever switch they plug it into. I still hear people confused about CFLs that don't work with their dimmers.
2. The large enough part of the market that they control might be large when that market is limited to "extremely early adopters of this kind of brand-new technology". The market will grow in many stages over the next few years and this is way to early to start giving people another reason to avoid your products.
I'm usually an early adopter of technologies like this, however, I've held off because there were only a handful of implementations out there and the use cases for them was still a "that'd be neat, but not worth the money". I've recently become very interested and will be buying something in the next 6-months, though this is making me reconsider that now.
I know I'm a future customer of this segment of technology -- not just lighting but upgrading my existing home automation system -- and I'm starting with lighting. I'm not, yet, a customer because I haven't found a good mix of "good product", "good interoperability", yet. So they've gained lock-in of all of their early adopters -- a very short-term investment[1] -- and caused the second wave of (in this case, also) early adopters to look elsewhere. They're nowhere close to the market that even high-end, non-smart bulbs command and they won't see much of it this way. People complain today about having to buy special bulbs for their dimmer switches; this is a whole other level -- you can't even use the lamp you just bought. No way someone like my dad is going to be a customer.
I can see how this might improve sales in the very short-term. It also might not. It will increase support calls. It will hurt their ability to get future customers and might even delay the next wave of adoption as people wait for fear of buying something that will become obsolete. These are all the things I'm thinking about as a person who really wants this technology, has the money to buy it, but doesn't have the money to do it twice. And I can live without it for a bit longer.
[1] Short-term because the people who are buying these for the most part have a lot of disposable income or a very small deployment, so switching to something else isn't necessarily as much of a lock-in as they'd like. And this product in particular, the primary consumer is tech folks -- they'll hack together the interoperability eventually, defeating the purpose.
Hue PM: Hue is profitable, but only marginally so. Our strategy of making up the initial investment on $60 per bulb hardware is being undermined by cheap 3rd party lighting fixtures. Plus we're incurring costs responding to all of these non-hue connectivity and reliability issues.
Boss: We control a large enough market share now and most of the market is already heavily invested in our ecosystem. Cut off hub connectivity for these 3rd party products. People should not be using non-Hue approved hardware with our software. We're a for-profit company, not a government or a charity.
Hue PM: That won't go over well with the early adopters and the tech community.
Boss: I've already run the cost/benefit analysis. The tech community might be mad for a little while, but we've got our sights set on industrial and commercial contracts now that we've proved Hue's viability in the consumer market. Do it.