Following up to my reply on the driver firmware topic where the first attempt at an update failed. I'm wondering if I have a faulty switch
I did a ZWave repair and rebooted the hub as suggested and also pulled the air gap on the switch, then tried again.
Things still didn't work (get version had no response either using the driver or the Z-Wave PC tool). I finally excluded the switch and factory reset and then was able to update with no problems during the update.
Except the switch isn't reporting reporting button press events or on/off state. I did a second factory reset and it then started reported the first couple of presses and then stopped again. It is reporting power though, and I get some data when I and responding to on/off commands from the hub. Also, the association groups look weird. My highest ID is 0x59, the switch I'm flashing. This is what I see in the state data:
I may have resolved it. Using the association tool again, this time I told it to reset the association variables. Even though I was changing group 2, it also fixed group 1 to be  and now I'm getting events.
I can't say I've seen random associations get set. Any idea how they may have got there? If you add or remove associations through the command boxes on the device page (and not through the Z-Wave association tool) then you need to hit the configure button or hit "Save Preferences" to send them. That is probably why the desired groups changed but not the actual.
@ericm The random associations were there after I updated the firmware. I had some issues initially getting it to update and had to exclude/factory reset/include before I could update it. Once it succeeded, the associations were there. I didn't notice initially, but I wasn't getting events from the device and eventually saw that.
I tried to set the associations both from the driver (I did click config) and from your association tool. It wasn't until I checked the box to reset the association variables that the change took.
I did update a second switch without problems though, so maybe the failed update left it in a weird state? I didn't think that was supposed to happen though.