I'm facing a weird issue when pairing a "GE Enbrighten Z-Wave Smart Dimmer" with Hubitat:
Whenever I dim over 38%, it starts flickering (the higher, the faster)
This dimmer was initially paired with a Honeywell Lyrics hub and there was no flickering issue.
(As a matter of fact, I did unpair from Hubitat and pair it again with Lyric and the flickering issue disappeared but as soon I pair it again with Hubitat, it starts flickering again)
I also (electrically) unplugged Hubitat to operate the dimmer manually but here as well the flickering occurred.
Is there any known issue with this combination (GE + Hubitat)? any fix?
When you unpaired the dimmer from your other hub it reset the settings within the dimmer and that is why the issue exists now when controlled from Hubitat and not. Do you remember if you had any specific settings for the device in your other hub? Usually you get a flickering bulb when a dimmer is too low, not when it is too high. so, if your dimmer is at 20%, you get no flickering at all?
There was no specific setting in that other hub that I'm aware of. When I'm paring again with that hub again, I only "include" the device and it works.
Now regarding the flickering: from 1% to 38% no problem at all. Above 38% and up to 100%, the more I increase the brightness, the faster it flickers.
One additional test I did: unpairing from hubitat and not pairing it back with Lyric: no flickering either.
That is very bizarre and extremely unlikely. Local control for the switch should not depend on the Hubitat. The HE hub should be able to be plugged in or not and local control should function regardless.
The only thing that I can think of that would affect local functionality would be if the Lyric hub passed certain configuration parameters on pairing that the HE hub does not pass.
What model of GE dimmer is it really? There are several models of the "Smart" dimmer because they rebranded the 14XXX series halfway through and then released a new line also called Enbrighten. Also, what driver are you using? Maybe some driver is passing a parameter to alter the steps or step length incorrectly. I think those dimmers support both number of steps and step length. Maybe. I didn't fact check just now.
I'm not sure if it helps but here are some additional observations:
I paired again (for the 6th time) with HE and now the flicker starts above 55% (previously it was always around 36 - 38%)
When paired with HE, Interferences (e.g. microwave) will trigger the flicker when above a certain value (30% in my previous attempts, 46% in the last one). In other words, when using the microwave, the threshold at which the flicker starts is 10% less. - Note that when paired with Lyric, there is no flicker at any value, microwave or not.
Some refactoring was performed in 2.1.9, but no functional changes and nothing like these issues were noted when those updates were tested with the actual dimmer.
I know this doesn't help, but I have >150 GE/Jasco z-wave dimmers between 3 houses, and I've never seen any configuration setting that can make a bulb flicker/not flicker.
That doesn't mean you are wrong, as sometimes things happen that I don't understand. But I know every published configuration parameter and I can't think of a single one that could possibly do what you are describing.
I have no idea how to explain this situation.
I have moved the HE in different place in the house, including just next to the dimmer and still have the issue.
I have replaced the dimmer with a Zooz one and no flicker either.
Putting back the GE dimmer, the flicker happens again.
It drives me crazy ...
I don't think so.
I have 3 GE dimmers and 2 Zooz dimmers.
I had them all paired with Lyric first (as the GE were already) and no issue.
Then I moved everything to HE and this is when I started to have the flicker issue on the GE
Would the attributed device_id matter ? (aka, the order in which I pair them)
The embrighten driver uses exactly two configuration parameters, both of which default to the device defaults, and both of which are exposed as preference settings, and both of which are published on the alliance site.
No other configuration parameters are sent to the device.
Association group 1 is added during inclusion, and that's it for configuration...