I apologise if this has been covered elsewhere but I haven't been able to find an answer.
Using Aeotec Nano Dimmers with halogen downlights. Using the default 'Aeotec Nano Dimmer' driver.
Works great for all functions.... But.... There is a delay of about 1 before the lights turn on after triggering. They respond immediately when turning off.
From what I can gather it is because they do some sort of load test before turning on. I found a thread for Smartthings where you were able to change a setting to prevent this after the initial testing once you're comfortable the load is within range.
However, I cannot seem to find anyway to do this with Hubitat.
If this was a z-wave parameter, you should be able to do it using Basic Z-wave tool. Download the driver from that URL, temporarily change the driver for the Nano dimmer to the Basic Z-wave tool driver, change the parameters you need, and then change it back to the original driver.
Thanks for the info. I tried this but it doesn't seem to actually change the parameters when I click 'Set Parameters'.
From some more reading I did find that setting both 'Minimum Brightness' and 'Maximum Brightness' in the standard driver to the same values. E.g. '90%'. This does then trigger instant on and off. However, doing this prevents dimming capabilities.
Hey thanks for your advice. I had previously tried setting 249, which didn't work. But hadn't tried unlocking 252. Just tried this then, but still no change unfortunately...
Set parameter 252 to 0 then 249 to 0. Then switched back to Aeotec driver and tested.
I did noticed that in the list of variables, where it shows the parameters, like minimum brightness is 131, maximum brightness is 132 etc. There is no 249.
@GrumpyTeddy. I haven't changed mine - i haven't noticed any slowness.
The State Variables don't show all the parameters.
When you have the nano dimmer set to use the Basic Z-Wave driver you can use the Get Parameter Report button, just put 249 in the parameterNumber box and click the Get Parameter Report button. The report will show up in the Logs.
Thanks @Wounded. I had a look at the logs and the parameters are definitely adjusting. But unfortunately changing parameter 249 doesn't resolve the issue. I have found that reducing the distance between minimum and maximum brightness helps though.
I.e. setting minimum brightness to 30% and maximum to 70% seems to greatly reduce the turn on lag.
Appreciate everyone's help.
@GrumpyTeddy, perhaps it has something to do with the halogen lights. Maybe they need a minimum voltage before they turn on?
Parameter 125 is the dimming rate in seconds. I have always assumed it was the dimming speed from max to 0 but maybe it is also for going from min to max. Try changing it to 0 and see if there is a difference.
I wish they would expose all these settings properly in the device handler to save us having to poke about with the zwave tool and fiddling with parameters.
I suspected the same. I've tried setting 125 to 0 but it doesn't change. 1 seems to be the minimum.
I'm about to start building a new house that will have LEDs throughout so will see what happens then. Thanks for all the tips!
Mine are the opposite - the four LEDs it’s driving turn on almost immediately, but fade down over about a second when turning off. I have the minimum dim value set to 40% otherwise a couple of the lights go off completely lower than that (might need the bypass hardware?). My dim speed is set to 2 or 3 seconds.
Have you tried changing the dim mode from trailing to leading? It will probably mess them up completely the other way, but it’s worth a try.
