I'm certain you'll disagree with me but I feel the video is a weak rebuttal.
The video (and there are
others) demonstrates using Siri to control
non-Homekit devices. Before HomeKit arrived,
SiriProxy had accomplished the same thing (until Apple released iOS7). What's important is that it does not demonstrate controlling Apple-blessed Homekit-enabled devices ("Homekit Accessories"). When that's demonstrated, then it will serve as a strong rebuttal.
I feel a claim of "supporting Homekit" should include controlling Homekit-enabled devices. The supplied video does not demonstrate this capability. I assume your claim that CastleOS will support Homekit will include the ability to control Homekit-enabled devices. Otherwise, it'll be a partial implementation that is certain to disappoint customers who will be unable to control their Homekit Accessories.
The development and demonstration of a bridge is unremarkable. The Homekit protocol is documented. Case in point, it's unlikely the engineers at Insteon had to reverse-engineer anything to design the
upcoming Insteon Hub Pro (an approved 'hardware bridge'). Unlike HomeBridge,
Insteon's press release indicates it will work with "all Homekit-enabled devices".
HomeBridge uses so-called "shims" to communicate with non-Homekit devices and it'll be interesting to see how that will work with the crypto in actual Homekit-enabled devices.
A tricky bit of business is Apple's current stance that they will not support "
software bridges" only "
hardware bridges" (like the Insteon Hub Pro). The folks at Indigo Domotics
spelled this out to their customers a few months ago. They currently cannot provide Homekit bridging because Indigo is HA software running on a Mac and would constitute a software bridge. Perhaps Apple will lift this restriction in the future (or it already has and is only known to folks who signed an NDA).
Chris, I've followed your suggestion and read many of the posts on the CastleOS forum. The following complaints speak to the charge that CastleOS's marketing may be misleading.
From the "
Wonderful ... But" thread.
"...
the system just doesn't work at the level promised, ..."
"...
I think that CastleOS is overselling itself."
"
I have been using castle os for some time now and I have to say I am generally dissapointed with the system."
Naturally there will always be customers who experience problems during the learning and implementation phases. Nevertheless, the common sentiment appears to be "overselling" and supports the position, expressed in this thread, that perhaps some of CastleOS's marketing claims may go beyond the product's actual capabilities.
I politely ask again, is there any documentation available, like a comparison chart, to support the claim that "
CastleOS integrates support for more smart devices and protocols than any other home automation system."? I assume some sort of comparative analysis was performed in order to arrive at this conclusion. There are several broad categories of devices your competitors support (alarm panels, AV equipment, irrigation systems, etc) that I don't see listed for CastleOS.