I'm beginning to think support really doesn't understand the issue, this is somewhat typical at this level of support...
Only an engineer would understand this in all probability, and even he/she might not understand the implications until an explanation is provided...
yeah, except the switch exhibits the very same behavior, and presumably doesn't have this parameter setting...
Jasco support is still stuck thinking that the issue we're on about is the device providing a multilevel report at the end of it's dimming tranistion, this is not the issue.
The issue is that the central scene class for pushed is held up for 1 to 2 seconds, central scene has nothing whatsoever to do with the dimmers level or transition times...
Agreed. I don't think that they quite understand the issue - as you say, not atypical at 1st line support when it comes to technical problems.
Since I am now only using the switch for ON/OFF This would be exactly what I need. I changed the value to 1 as suggested using the Z-wave parameter tool per instructions. However, no change. I must have done something wrong. Any ideas?
Did you do a parameter read to verify it changed?
Other than that, no advice. I use my user driver, and switch mode it one of the configurable parameters in it - so that's how I did it.
I stand corrected. I see the same thing on my 46203s.
It is about 1s delay on mine, but definitely a noticeable delay for the on/off central scene report receipt. As you mentioned, the other central scene reports seem to be quicker, as is the multilevel report.
Sorry for the misinformation earlier. I would swear that I tested exactly this and did not see the delay. But I am clearly remembering incorrectly, as it is there.
I did verify that the parameter changed but there was no change to the action. Close as I could get with a stopwatch in a real word configuration delay is 2.5 to 3 sec. You said you used your user driver. which Driver is this?
2.5-3 seconds from what to what? To turn on the light? To receive the report back? Other?
I ask because changing it to switch mode won't make it report on/off status back to the hub any faster.
You can find my driver in here, search for enbrighten dimmer.
My test setup is a zigbee on/off switch controlling a basic led lamp. The measurement, obviously somewhat crude, is what the user actually sees. Press the button, start the stopwatch, stop the stopwatch when the light is on. If I set up the switch for hold or double press the time from press to light on is really too short to measure with this method. It appears to be immediate or at least sub second.
Ok, so the delay is on the on/off event to the hub. Nothing you can do to speed that up in this device. Sorry.
Seems like that report is just slow in this device and firmware.
Sorry to keep this going but I had another somewhat useless conversation with enbrighten support today. I think they finally understood the issue. They also said the delay is normal and changing parameter 16 to 1 should eliminate the delay. I explained that I changed it to 1 and confirmed the change but there was no change in behavior of the device. Their only possible solution was that the software I used to change the parameter did not actually change it or that the hardware (switch) was defective. They offered to look at the switch if I would send it to them. Since I have 3 switches that are doing exactly the thing I doubt it is hardware. They also said firmware 5.4 is the latest and greatest and I could not revert to an earlier version. Your thoughts please!
I think I am finished with GE enbrighten!! Can someone recommend a paddle switch that will support pushed, Held, and double tap, on top and bottom. Is Inovelli red a choice?
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
