Originally Posted by HDTVNYC
Haven't had a chance to pick one up yet, but planning on it. They've been very responsive with support for Lutron. One item I'm looking forward to is being able to select the dimming based on either daylight level outside or time of day. So when you turn on a room, at nighttime instead of 100% it might only go to 65%. If this works out well, it'll help reduce the amount of buttons needed (Evening, Day vs Room On)
I'm a new forum member, and not the Bill mentioned above, but I do use Hubitat with my RadioRA 2 system. It's a good match for me.
A few points on the platform:
1) The company is only about 18 months old, so there's a fair amount of continuous change going on. New builds 1-2 times a month.
2) One of the founders has RadioRA 2 in his house, so functionality and use cases are familiar to developers
3) The developers are really responsive to issues and (frequently) user enhancement requests
4) If you go to the community forums you will see hub lock-up issues. Almost all are due to user-developed code that is used for complex or non-base functionality use cases. If all you need is to extend a RadioRA 2 system these problems won't be an issue.
As to RadioRA 2 extension cases:
1) Like HDTVNYC noted, it's really easy to make a keypad button do different things based on conditions. Conditions can be almost anything, but for lighting will usually be a mode (which can be based on time of day). The process is:
a) set a "base" scene in Lutron software for the button. So if the Hubitat is offline from the local network (note that operation is all local, does not need Internet for Lutron) the lights will come on to a reasonable state.
b) set your other mode-based scenes up as phantom buttons. This is not technically necessary as Hubitat has its own scenes, but it prevents any popcorning of Lutron devices especially if using Pico controls.
c) in Hubitat set up the keypad in Hubitat's button controller app and choose settings per mode. Program the physical button push then virtually push the mode-based phantom button.
d) The only thing you lose is the indicator light on the keypad. It's lit only for the times that the scene in a) is active.
e) I have mine set up so that the lights automatically adjust themselves if the mode changes. This is optional.
f) Pushing that scene button in the Connect phone app will also trigger the Hubitat actions.
2) Another real easy use case is to add Philips Hue lights to a Lutron scene. In the same Hubitat Button Controller app add your Hue settings. In my house for a Movie scene the Lutron controlled lights go off and the Hue lights change from 3000K a dim blue.
3) After these simpler configurations you are likely adding devices to the system and adding complexity. The issues with the devices is that they are generally Zigbee or Z-Wave devices. So the performance issues generally become related to mesh communications problems as opposed to platform issues. A couple easy use cases for use with a Lutron system 1) if humidity increases by x% then turn on the bathroom fan (needs a humidity sensor), or 2) if leak is detected then flash the lights (needs a water sensor).
4) Another use case - it's a viable way for people to combine a Caseta system (Pro bridge required) with RadioRA 2. Hubitat becomes the "glue" between the systems.
In summary, the Hubitat platform works well with Lutron. IMO, it's probably the easiest for even most mid-complexity use cases and at about $100 certainly the most cost effective. It's at least worth trying out.