Hey Eric thanks for the reply!
Super weird, I tried all the settings and neutral definitely makes a difference the rest do not. My install is tied into a neutral. When I switch to non-neutral (param 21, value 0) the dimming actually seems to go back to what it was.
Basically, with the lights on in neutral. All I do is set it to non-neutral. Then hold the dimmer up and it will jump up ~15% immediately and then dim up like normal. The exact opposite happens when going from non-neutral to neutral. This 15% gap puts most of my lights at full off with minimum set at 45.
If I remember right, before this firmware update switching from non-neutral to neutral and then back did not seem to have any affect on dimming thresholds.
Unless the parameter values have flipped, Iād assume you wouldnāt recommend using non-neutral as a work around for this issue? Not sure if there is a way to prove out visually if itās actually using neutral or not (to double check the parameter values didnāt flip)? Thanks!
Iāve ācalibratedā all my LZW31-SNās bulbs by finding the minimum value where the bulbs turn on and setting the minimum value accordingly. I have also set the max values per my perceived ācalibratedā eye.
Iāve noticed, if I set the brightness of the dimmer to ā1ā and I turn the bulb on at the dimmer (LZW31-SN), the bulb comes on to a value much brighter, say 10, and then dims down to 1 as shown below:
However, if I turn on the light from z-wave or the GE accessory switch, the light turns on to the preset value of 1 as shown below:
the dimmer is set up as a 3way using a GE accessory switch with neutral. The rest of the configuration values are pretty much set at default.
All of my dimmers are doing this using a mixture of Philips Warm Glow bulbs (BR30ās and A19ās), GE LED Relax (A19ās) bulbs. Thankfully, we donāt need to set these to 1 too often. Except for movie nights. Even then weāre typically diming them down from 85. So we would almost never see this.
Does this mean you set the value to 1% and then turn the dimmer off and then turn it on? Or you have the default local level set to 1% or what is the exact process here?
@EricM_Inovelli So after setting the minimum value for the light (via the switches parameter settings) in my case 24, I use the Set Level command to set it to 1%. And then as you stated, I turn it off and then back on again.Hopefully, that is clearererer
Edit: the minimum value of 24 is the value necessary to guarantee the LED will turn on again.
Pretty sure most of my dimmers were on 1.35? from memoryā¦ Production version. Updated all so I canāt check. 1,2 Close but not quite. 3 yes!
Basically with neutral enabled on 1.47 all dimming seems to be 15% less than original firmware output. So for min level if I add 15 Iām back in business, but if +15 > 45 Iām sol as that exceeds the params limit.
For example: pre 1.47 for one dimmer min is set at 45 and the lights turned on at ~1% (was already on the edge and wish there was more flexibility) after the update I have to raise my dimmer to ~15% to get the lights to just barely turn on.
Iāve got two dimmers that I canāt update. Multiple others updated fine.
Using the Z-Wave PC Controller software, when I hit the Get button to get the device info on the OTA screen, it never results in the info showing on the screen. The target options donāt show up and so I canāt select a firmware file to flash.
Iāve tried multiple times, and restarting the applications and replugging the AEON stick with no success.
No, weāre still looking into this on our end and working with our engineers to see what they can do. This was hub specific and the switches worked fine with S2 on all the hubs we tested it on. Unfortunately, we did not have a C-7 to test it on to see how it was going to be implemented on their hub. One thing I canāt quite figure out is how the Z-Wave Certification didnāt pick this up on either side, but I guess thatās something weāll take up with them.
