Mike
Thanks for your reply and trust me certainly do not take it personally as I am just a power user like you i.e. no hidden agenda. Just wanted to share some thoughts on the Keen vents and experience so far from my perspective. Apologies for the long post.
First, what do you mean you’re not using other software or hubs, have to spread your HA platform wings
I noticed that the HW (vent) has received some manufacturing changes (you can check your P/N on the back as it has had an iteration change) over the past few months. Currently it appears updates have also been made to the cloud backend due to bug feedback and in particular with the Keen app/HW integration (made possible by the comms mechanism today). The way in which comms are handled from the Keen portion (app->cloud>server>bridge>vent) allows for those tweaks on the backend without the need for pushing full blown app updates, SW side in iOS etc. An example of some of those items that I have seen fixed personally so far are issues with room additions (could not add rooms beyond a point), ghost vents, pairing discrepancies, app control and server comms to app functions etc have all been resolved quickly through that mechanism. Those can be witnessed personally using the Keen App & bridge already (I know you mentioned people here may not be using that platform but wanted to share).
I’ve seen a number of nuances with the vents that are affecting multiple platforms (Iris, ST, Keen) and those are being worked hard by their team as well to trap and isolate so all benefit from a fix regardless of platform choice. With regards to HW related issues being fixed/updated, as you mentioned there are no USB/service ports today but they do have the ability using remote server pushes to distribute FW to the vents which is a plus. The mechanism for this being possible across the other platforms (outside of the Keen infrastructure) is a question I have out there although I would think it would have to be supported due to the investment in Iris, (launch partner) and ST.
In terms of continuing platform support my understanding is an ongoing commitment across the board up to and including expansion into new areas such as HomeKit in the future, i.e a strong presence regardless of platform.
As the vents and bridges are only just getting out to the masses now (as everyone here has seen), focus appears to be switching to their growing customer base, platform support, vent installs, reported issues across platforms and backend server work as well (this last piece relating to their own Keen platform and ensuring that it is stable with their Keen Bridge and App). Taking these updates, enhancements, findings and resolutions and applying where possible/applicable across other platforms. This focus shift now being possible as attention can be moved from fulfillment of their pre-orders to development/engineering and support etc.
Staying on the topic of platforms, with regards to platform integration variances, I am referring to things like the fact that in Iris and the Keen app, pressure data is not made available to the user today (vent temperature is not in the Keen app nor is a real-time poll of device status at this time) therefore limiting what can and cannot be done there today, hence the additional work. ST on the other hand has that data being passed and also benefits from integration with ST sensors/devices that are more readily available than elsewhere currently. So although some may not agree, the ST platforms integration, community and 3rd party sensors work a lot better and allow more customization of your HA environment with the vents than for example other platforms like Iris currently IMO. The Keen app platform itself (through my experience using it) looks to be aimed more at the regular homeowner rather than the techy integrator (I don’t see this as a detriment necessarily). By that what I mean is that things are presented in a more simple, friendly way such as ‘does the room feel cold or hot etc’ and then the app driving preset vent adjustments to compensate. Occupancy scheduling in blocks of hours rather than granular to the minute or hour itself. Temp purposefully not presented to the user (which as we know is vent air flow temp not room) which could be confusing to some in its current iteration. Also, apart from things like Nest control and upcoming auto balancing (sill currently in beta) there is no option to bring sensors, rules etc into the Keen environment today. Therefore I believe this is why Keen is and will continue to support the other HA platforms and associated user base for those wanting full HA control, more granularity and deeper integration across a plethora of ‘other’ devices.
In terms of further integration directly, Keen could offer (through ST smart apps, their own infrastructure and associated app) the ability to monitor/report and action based on vent temp and pressure status to ensure the health of the system just as one example already mentioned. This has not been implemented so far to the end user (hence great individuals on here coming up with other options in ST). Another example might be extrapolating room temp algorithmically from vent temp (if possible) to expand use almost into a remote sensor/zoning type of deal (something that Nest for example should be doing with its Protect alarms IMO) or looking to integrate tighter with other options to provide the same end result and a more rich experience when pairing with a Nest or other Thermo. My understanding is that these are at least being discussed at this time.
Continuing on integration, I’m sure even more functionality will be added to the Keen app based on the backend data it has available and the streamlined way in which to control features and bug fixes through the comms mechanism I mentioned. With that said, any features that can be replicated/introduced across Iris & ST as well (HomeKit in time hopefully), I am sure would be, due to the large community and customer base along with access to sensors and devices that are not directly supported through Keens infrastructure or partner network today.
Don’t and won’t speak for Keen here at all, again I’m just a power user thats testing across 4 platforms (albeit 1 ported) with a whole house of these vents (and a number of other HA devices on other platforms) and working closely with them on anything I see issue wise. providing feedback as I go and testing any fixes that are shared.
From my own perspective, I don’t disagree that there are issues today and maybe product launch was not as smooth as anyone would like or expect, however I am seeing Keen step up to the plate to work on addressing as much as they can, as quickly as possible and seeing that commitment increase as cycles free up from the completion of the pre-order fulfillment phase.
Of course time will tell with these HA platforms, products and the companies behind them, which is why I am using multiple to see what best works for my needs and to gauge the level of continued investment in platform(s) or product(s).
Not sure if that helps Mike as again just based on my personal experience so far.
Thanks