bdonohoe

I'm pleased to announce that the production version of the Varietas Software Homebridge Driver is ready for download and is now listed at HouseLogix here.  
A sincere thank you to all my beta testers and folks who have helped me test out support for various devices.  The Homebridge Network Appliance is also ready for production.  For anyone that wants to buy the ready-made device, please feel free to PM me.

For those following along at home, the last beta driver is scheduled to expire the day after tomorrow (the 15th).  I have put together an updated driver that is functional until April 1.  Scary, but arbitrary date.  This new version auto-detects the Clipsal drivers that some folks have used for "generic programming".  It also should auto-detect a few new dimmers (as dimmers) and locks.
Yes I still need to add thermostats and blinds.
I also updated the driver so that it *will not* output duplicate names during configuration import.  This was causing lots of confusion and the appliance to not be detected by HomeKit.  I still need to update the firmware in the appliance to disallow duplicates, and your can still manually rename devices to be duplicates, but if you just import the config from the director, any duplicates in Composer will now be auto-renamed with "Device 2", "Device 3", etc.
The latest driver is here -> https://dl.dropboxusercontent.com/u/13324724/homebridge.c4z

OK folks.  The latest copy of the driver is available here -> https://dl.dropboxusercontent.com/u/13324724/homebridge.c4z
This version plays nicely with my soon-to-be-released hardware appliance, and also extends the expiration date to 02/15/17.  At that point, my hardware should be finalized for production release, and I should have the production driver available on HouseLogix.

For those following along at home, I've updated the copy of the driver located here -> https://dl.dropboxusercontent.com/u/13324724/homebridge.c4z
This new version extends the beta timeout from 12/15/16 to 1/15/17.  It also includes support for a few new C4 drivers (several new ones that use the light proxy) and has updated documentation to identify which C4 drivers are currently supported.  

I haven't heard from too many people who are trying this out yet, but the homebridge-control4 plugin has been installed nearly 200 times.  I have been in touch with one person who is successfully using this driver in his project... so far so good.
I have a pre-configured homebridge appliance nearly ready to go on sale.  This will be a drop-in network appliance that comes pre-configured with everything needed to get the Homebridge driver running with HomeKit, and which supports a super-easy web-based configuration.  Plug it in, enter a few settings, and everything should "just work."  It will even auto-import the device configuration from your Control4 system.   Here's a little sneak-peek.  MSRP for the hardware box will be about $225.

Thought I'd show you guys a little of what I've been working with.  So far, it's been very snappy and stable.

I've been working on developing a homebridge plugin to fully enable HomeKit control/reporting of various Control4 devices.  Initially I'm supporting lights, dimmers, door contact sensors, window contact sensors, generic contact sensors, motion sensors and security systems (because that's what I have in my home).  I'm also working on a Control4 driver that will communicate with the homebridge plugin for all system devices without additional programming needed.
This will give the benefit of:
* Direct control of Control4 systems via HomeKit w/ Siri voice control
* Remote access (if you have home hubs such as Apple TV 4 or iPad) without 4Sight needed
* Direct integration of "favorite" devices into the iOS control center views
* Control of all Control4 devices via Apple Watch
SO....a few questions:
1) Does anybody out there have interest in such a thing?  
2) Are there folks out there that might want to beta test?

I wrote a blog post about doing exactly that kind of thing a while back: http://www.c4cookbook.com/recipes/2015/9/20/setting-lower-light-levels-at-night
The gist of it, for your purposes, is you set the preset level to what you want, then any time the light itself turns on, you change the preset level to 100%. When it turns off, you reset it to 25% (or whatever). Those changes are tied to the light on/off events, so that it doesn't matter how the light is turned on. I then combine that with variables for different levels at different times of day and get lights that always turn on at an appropriate level and can always be turned up to 100% with a second tap.

Thanks for your kind words, Kevin. My first name is Brendan. I've got a short list of articles I've been planning to write since I wrote that first one. Just need to find the time!
One small note I need to add to that article: when the schedule runs to change the light levels between day/night mode, I check to see if the light is already on. If it is, I don't change the level. That leaves it set so the next tap will go to 100%, but turning the light off will still reset it to the lower level. It's a little thing, but it makes the behavior work the same 100% of the time.

I wrote a blog post about doing exactly that kind of thing a while back: http://www.c4cookbook.com/recipes/2015/9/20/setting-lower-light-levels-at-night
The gist of it, for your purposes, is you set the preset level to what you want, then any time the light itself turns on, you change the preset level to 100%. When it turns off, you reset it to 25% (or whatever). Those changes are tied to the light on/off events, so that it doesn't matter how the light is turned on. I then combine that with variables for different levels at different times of day and get lights that always turn on at an appropriate level and can always be turned up to 100% with a second tap.