Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
If all devices simply connect to wifi instead of the hub, then in the future there's never a need for a hub and never a need to replace the hub with a new one.

Nope. A mere WiFi connection is not enough to be HomeKit-compatible. The device that communicates with HomeKit needs to have special hardware (an encryption coprocessor). Philips solved that problem by putting all of that in the Bridge, which communicates to the bulbs via ZigBee (which is better than WiFi for this application anyway for reasons I've explained in a previous post). Even if the old Hue bulbs were directly WiFi enabled, like LIFX (which still doesn't support HomeKit--and likely can't without additional hardware...oh, and LIFX still uses a mesh network rather than WiFi for inter-bulb communication), we'd probably still need to replace all the bulbs--and probably add them individually to HomeKit, each with their own QR code, instead of doing it once for just the Bridge like you can now. I'll take the Bridge. :)

HomeKit also limits the available functionality for any device that makes use of a hub and only bridges some of the functions, though doesn't allow full integration.

Please expand on this and provide specific examples because not only do I think it's not true, I think it's actually easier with the Bridge. I only need to add the Bridge to HomeKit (once) and just change some configuration within the app if I add or remove bulbs and want to use them with HomeKit, and the only limitations are things Apple or Philips just doesn't have a good way to support yet (like grouping bulbs--which the Bridge hardware actually supports but the functionality isn't exposed in the Hue app [yet?]). This should become easily possible with software updates in the future.
 
Nope. A mere WiFi connection is not enough to be HomeKit-compatible. The device that communicates with HomeKit needs to have special hardware (an encryption coprocessor). Philips solved that problem by putting all of that in the Bridge, which communicates to the bulbs via ZigBee (which is better than WiFi for this application anyway for reasons I've explained in a previous post). Even if the old Hue bulbs were directly WiFi enabled, like LIFX (which still doesn't support HomeKit--and likely can't without additional hardware...oh, and LIFX still uses a mesh network rather than WiFi for inter-bulb communication), we'd probably still need to replace all the bulbs--and probably add them individually to HomeKit, each with their own QR code, instead of doing it once for just the Bridge like you can now. I'll take the Bridge. :)

Please expand on this and provide specific examples because not only do I think it's not true, I think it's actually easier with the Bridge. I only need to add the Bridge to HomeKit (once) and just change some configuration within the app if I add or remove bulbs and want to use them with HomeKit, and the only limitations are things Apple or Philips just doesn't have a good way to support yet (like grouping bulbs--which the Bridge hardware actually supports but the functionality isn't exposed in the Hue app [yet?]). This should become easily possible with software updates in the future.

Yes, I'm well aware that there are additional requirements outside of simply having wifi connection. My comments here aren't meant as a reference for developers as that simply isn't the audience here.

Bridged devices are limited. I won't dig into the developer docs as I simply don't have time to do so but for instance, no third-party device can be bridged (regardless of how it connects) to a HomeKit device if it allows physical access to a home. It would only work if the device had HomeKit compatibilty and the MFi license.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.