Thanks for the clarification Linvale! Does anybody know if there is a good example/tutorial on exactly how to update the Leviton firmware? Can it be done "over the air" directly in my HE environment? If not, is that a limitation related to Leviton, or are firmware updates for devices basically not a function of HE? If not a current functionality of HE, are there plans for it to be added?
In the HE web GUI, can anyone explain what the Start Level Change (and Direction) and Stop Level Change buttons do? Also, how about the Configure button? As a newbie, I think it would be very helpful to have button-specific labels pop up when you hover mouse over a button that briefly describe what that button does. And maybe add ability to turn help labels on/off for the experts?
Those are how buttons dim (or brighten). You press a button, it sets direction and start. When you release the button, the button sends the stop. We shorthand write this as press/release. Other button actions are press and press/hold.
Pico's are popular button devices here and they support all three button modes.
Take a 5 button Pico, for example. (I'm giving physical button examples here, but virtual devices work the same.)
Button 1 at the top might be used for "on, full brightness" -- it's just a push. Same with button 5 at the bottom: "off" -- another push. That button 2 could be used as push/release to brighten, while button 4 would be the same, but the other direction.
Button 3 is often called "favorite" and could be used to set a specific dim level -- again using Push.
Configure does just that, it moves the configuration from the driver to the device. ZWave devices have many configuration elements, and the driver wants to set them so that driver and device match features.
That Pico also works with push/hold to give 5 more buttons! Yes, that Pico is a 10 button device. Short push = push while long push = push/hold. Push/release and push/hold are the same action to the human finger, the programming being the difference in interpretation.
If, when you join a device, it displays the correct driver, the config is done automatically. But anytime you change the driver, as you experiment perhaps, then clicking Configure will send that driver's "map of features" to the device, overwriting the previous driver, in many cases.
Thanks for the detailed explanation csteele! Written like a true programmer/developer - nice!! So, since I don't have any button devices like the Pico, those Start Level Change and Stop Level Change buttons on the HE web GUI screen are meaningless for me, right? They would not affect the physical buttons/controls on the physical dimmer, right?
you can push them the same as On or Off. They'll do what they're intended to do..
"would not affect the physical buttons/controls on the physical dimmer" <-- not sure what that means, but I'll tell ya what flashed into my head.. those Mickey Mouse hands that come out of the ceiling to physically push a button. 
Perhaps it's better to imagine that the switch you're replacing is swapped to a Relay. The ZWave circuitry controls the relay, the physical buttons tell the ZWave circutry what to do.. exactly the same as the radio commands from a hub. Physical does nothing anymore, except tell something it got touched.
Check out this post regarding updating your Leviton Dimmers. There are numerous revisions with a bunch of fixes and they work much better after updating the firmware.
What I'm asking is if clicking on the Start Level Change or Stop Level Change buttons on the Hubitat web GUI device screen for this dimmer has any effect on the lights attached to this dimmer? e.g. it sounds like you are saying, even without a remote control (e.g. pico), if I click on those 2 buttons on the web GUI something should/will something happen to the dimmer/lights? Do clicking on those 2 buttons equate to pressing the up/down dim bar on the rgt side of physical dimmer? And back on the web GUI, how does the Level setting/value affect these 2 buttons?
I've been a programmer for over 30 years, but I've got to say this isn't intuitive stuff to a newbie in HA 
Yes, I saw that post. I'm hoping there's a step-by-step tutorial somewhere? I'm clueless as to exactly what I'd be doing with the Hubitat's USB stick? If I put it into a Windows computer, do I then boot from the USB stick (and end up in a Linux world)? If I don't boot it, what am I doing to it? Scratching my head
Yes, exactly
Level Setting sets the initial level (dim) from which you would go up or down.
Look at this post. Basically you just need to install the device driver for the Hubitat stick and then the Z-Flash software can use it to flash the FW.
The USB stick is a pair of radios, can't boot from it.
You install the drivers, then run the Purchased software... you can purchase it with their own USB Stick (ZWave only) and that would remove the need to power down the Hub to do the upgrade.
BUT
If you're going to buy another ZWave Stick, buy the Aeon.
It's got an internal battery so it works unplugged and can be used to Exclude and Include devices while you are walking room to room with it.
I guess I really do need a firmware update for this Leviton dimmer, as the web GUI often reports an incorrect value for Current States->Level.
Example 1: I typed in 80 for the Level, then clicked on [Set Level]. The dimmer/lights turned on at 80%. Then I typed 40 in the Level field (did not click on [Set Level]), set the Direction to Down, then clicked on [Start Level Change] - the lights faded to off (should have stopped at 40%, right?). The Current States now list as Level:80 . State: Off
Oh, I thought the USB stick in my Hubitat hub contained the os. I guess that's contained in onboard memory in the hub itself. So the USB stick is both a Z-Wave (and ZigBee) radio, as well as some flash memory?
What does the HomeSeer company/product have to do with flashing Leviton dimmer drivers? They sell some general purpose Windows software that can handle flashing of these radio adapters? Will Hubitat ever have that natively?
Exactly they have software and the actual FW files to flash these devices. Leviton will not give out FW to individuals, only companies.
On most physical dimmer switches, you can push the top to turn on the light, or push the bottom to turn off the light. Once the light is on, if your press and hold the top, the light will get brighter and brighter until you release the switch. Likewise, if you press and hold the bottom, the light will get dimmer and dimmer until you release the switch. (As you can see from the bolded text above, we have three physical events - pushed, held, and released.)
Most Home Automation platforms, allow you to turn 'on', turn 'off', and 'setLevel' a dimmer switch. This is usually enough for automations. For example, someone walks into a room, a motion detector 'sees them', causing a rule to run to turn on the light at a specific dim level. In this situation, there is no reason to use the StartLevelChange or StopLevelChange commands.
However, Hubitat has some amazing support for Lutron Pico remotes which are capable of generating pushed, held, and released events. One of the things that users requested was the ability to emulate the physical switch's dimming behavior (as described above) while using a Pico Remote. @mike.maxwell discovered that both Z-Wave and ZigBee have support in their respective protocols to command the device to 'StartLevelChange" in either an "Up" or "Down" direction. To halt the dimming, you issue a 'StopLevelChange' command.
So, now we have the building blocks necessary to use a Pico remote as a smooth dimmer. Using a Button Controller App, we map the "pushed" events to 'on' and 'off'. We map the "held" events to 'StartLevelChange(up)' and 'StartLevelChange(down)'. And finally, we map the "released" events to 'StopLevelChange'.
Hoepfully this helps explain what these two extra commands are typically used for. Not all physical devices support these commands, your results may vary. I use these commands via a pico remote to control smooth dimming of my Sengled ZigBee bulbs. It works great!
2 Likes
Ahhh, that makes more sense: I thought the Start/Stop Level Change command buttons could be used in the Hubitat web GUI (for the Leviton dimmer device). I guess while they could be "used" within the GUI, they have no real-world application within this GUI's context. BUT they are very applicable when coded/programmed in scenarios like you describe... So maybe nothing is wrong with my Leviton dimmer which is currently set to the not-so-smart Generic Z-Wave Dimmer device type. Maybe if I was really quick at clicking on the [Stop Level Change] button, it might function as expected? Then again, if the Direction is set to Down and the Level is set to say 20%: if I then click on the [Start Level Change] button in GUI, shouldn't the dimmer dim the lights down to 20%, and lights stay on? They are turning off instead...
No, they will continue to dim until they reach 0%, unless a stopLevelChange command is received. Same thin happens on the way up. They will stop at 100%, unless you interrupt the command.
setLevel will change the current dim level to the value you type in before pressing the button. Some dimmers also support a time interval over which the change in level will occur. Not all dimmer do, though.
Ahhh, then I guess my dimmer is behaving correctly. Though the Hubitat web GUI does report the Current State->Level incorrectly after using these 2 commands within the GUI...
Another oddity I've noticed is that after I play around with some of the dimmer's device command buttons in the HE GUI, if I then walk over to dimmer on wall and quickly press the top half of switch, the light will come on and dim level will ramp up to 100% (it should have just turned on at whatever its last Level was set at). And if I momentarily press the smaller dim up (or down) buttons (on rgt side of dimmer), lights will ramp up/down to 100%/0% brightness. They should only ramp up/down one fraction/notch.
I just purchased HomeSeer's Z-Flash utility ($15 special). Keeping fingers crossed that my dimmer will work afterwards
