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.
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.