Just got an update from Hubitat that includes a native fan/light driver. Should I change to that over the user installed one? Or does it make a difference?
There are differences between the drivers, but the choice is yours. As always, Hubitat will only “officially” support the built-in drivers (custom code of any kind is on you). That being said, Hubitat staff tend to still be pretty responsive to users and Inovelli certainly is, so if any problems arise with Inovelli’s custom driver, I’d expect those to be addressed to the best of whoever’s ability.
Differences you’ll note:
- Inovelli’s driver exposes every Z-Wave parameter as an option; Hubitat chose what I’d assume they’d guess as the most “popular” options (any parameter can still be changed regardless of the driver you regularly use by switching to either Inovelli’s driver or the Basic Z-Wave Tool to make your changes, then switching back)
- Inovelli’s driver adds a few features some users like, including the ability to create preconfigured “notification child devices” as switches you can turn on/off to make use of the notification LED. This is still possible in Hubitat with the custom
setIndicator()commands (which Inovelli has in some of their other drivers to match Hubitat’s drivers but not this one at the moment) - Inovelli’s driver exposes all scenes (mutli-taps, presses, holds, and releases) as some sort of event. Hubitat’s driver does too with the exception of maxing out at double-taps (so you lose taps 3-5 in each direction). Hubitat’s button numbering and event naming makes a lot more sense, but Inovelli’s is usable once you know what corresponds to what (and, in their defense, is presumably a compromise they made since Hubitat’s button model does not natively support “quintuple tappable”)
- Hubitat’s driver makes use of standard debug logging and “info”/descriptionText logging, consistent with what you may see from other drivers (e.g., debug logging enabled for first 30 minutes after install, info logging enabled indefinitely, where info logging shows device events in the log like “switch on” or “button 1 pushed”). Inovelli’s logging is…interesting but more or less similar if you have the right settings. (Some Hubitat users care a lot about their logs. I confess I’m one.)
There are probably more
So, I guess the best advice is the usual advice on Hubitat or any similar platform: if the built-in driver meets your needs, I’d start there; if you want something only the Inovelli driver offers, I’d switch to that.
3 Likes
Thanks for the breakdown. I’ve been using the Innovelli driver since the beginning and it’s working fine.
My other question would be will only the Hubitat version get updates from now on?
Team Eric is pretty good at keeping Inovelli drivers updated or added features. Keep an eye out on github or use the Hubitat package manager to keep your driver updated.
I’m not sure any of us can speak for whether either driver will ever get updated, but I’d expect both to continue to be updated on an as-needed basis due to either platform changes, new device firmware, or (more likely with Inovelli IMHO) user feedback, based on the history of both companies. 
(Inovelli, for example, has released several updates for their Red and Black switch and dimmer drivers since their release, only some of which were to address new firmware features.)