It looks like your dimmer slider sends continuous commands as someone slides? This may be an issue depending on the design of the lighting system's driver (and the design of the lighting system for that matter). For example, you could cause massive delays on a z-wave network if you send 50 commands in succession to increase brightness in steps. Perhaps there could be a global variable to toggle the slides behavior? However, if someone can click anywhere on the slide control, what you have will work, and I just won't grab and slide.
How this type of issue is handled for thermostats in the z-wave VRc0P module is a timer is set when a new temp value is received. Then, if another value is received within a second, the timer restarts. This causes a delay of 1 second, but was the easiest way to handle things as the Automation Browser used a push button (not a push and hold button) that uses a script to subtract or add to the temperature setpoint: sys://Schema/Modules/Plugins/ControlsLibrary/ThermostatControls/CurrentSetPointControls/Decrease/OnClick
This is in contrast to the automation browsers implementation for dimmers as a brightness state change does not occur until the user stops raising brightness by releasing the push and hold type button; this meant that the VRC0P module did not require the same addtimer work around and so dimming is fast and accurate.
Also, the slides behavior may cause havoc for IR volume control as most IR controllers have a cache of IR commands. Imagine sliding to 80% from 50% and having to wait for 30 IR commands, each with a built in delay, to be sent. Typical IR command delays (minimum delay until the device will accept a new IR command) range from 50ms to 200ms; so the issue would depend on the device.
How this type of issue is handled for thermostats in the z-wave VRc0P module is a timer is set when a new temp value is received. Then, if another value is received within a second, the timer restarts. This causes a delay of 1 second, but was the easiest way to handle things as the Automation Browser used a push button (not a push and hold button) that uses a script to subtract or add to the temperature setpoint: sys://Schema/Modules/Plugins/ControlsLibrary/ThermostatControls/CurrentSetPointControls/Decrease/OnClick
This is in contrast to the automation browsers implementation for dimmers as a brightness state change does not occur until the user stops raising brightness by releasing the push and hold type button; this meant that the VRC0P module did not require the same addtimer work around and so dimming is fast and accurate.
Also, the slides behavior may cause havoc for IR volume control as most IR controllers have a cache of IR commands. Imagine sliding to 80% from 50% and having to wait for 30 IR commands, each with a built in delay, to be sent. Typical IR command delays (minimum delay until the device will accept a new IR command) range from 50ms to 200ms; so the issue would depend on the device.
