Switch "capability-status" not updating when pressing actual switch (Linear WT00Z-1)

I have some development experience, so I thought I might try my hand at creating an Edge driver for a Linear WT00Z-1 that I’ve been using as a scene setter for years. I have the new driver installed.

Though I’m dumb as a box of hammers, I do like puzzles: can anyone point me in the right direction? What’s likely wrong in my source file?

  • With logcat, I can see the up and down “events” (with different payloads for on and off).
  • When I control the switch (on/off) from the app, the switch “capability-status” updates on/off. However when I tap the physical switch, “capability-status” does not update.
  • FWIW, (re)installing the driver also causes the status to update to current state.

I’ve already tried to remove/add the switch device, power-cycled the switch, etc.

Here are the events emitted when the switch is physically pushed:

ON (pushed up)

2023-01-15T01:38:45.563187175+00:00 TRACE Linear Z-Wave Switch  Received event with handler unnamed
2023-01-15T01:38:45.567984359+00:00 INFO Linear Z-Wave Switch  <ZwaveDevice: ... [14] (Linear WT00Z-1 Switch)> received Z-Wave command: {args={value=255}, cmd_class="BASIC", cmd_id="SET", dst_channels={}, encap="NONE", payload="\xFF", src_channel=0, version=1}
2023-01-15T01:38:45.663126764+00:00 DEBUG Linear Z-Wave Switch  Linear WT00Z-1 Switch device thread event handled

OFF (pushed down)

2023-01-15T01:39:20.348425881+00:00 TRACE Linear Z-Wave Switch  Received event with handler unnamed
2023-01-15T01:39:20.352485090+00:00 INFO Linear Z-Wave Switch  <ZwaveDevice: ... [14] (Linear WT00Z-1 Switch)> received Z-Wave command: {args={value=0}, cmd_class="BASIC", cmd_id="SET", dst_channels={}, encap="NONE", payload="\x00", src_channel=0, version=1}
2023-01-15T01:39:20.357853673+00:00 DEBUG Linear Z-Wave Switch  Linear WT00Z-1 Switch device thread event handled

Thanks for any help…

Is this the first generation of that device? Zwave Classic, not zwave plus?

If so, it doesn’t use central scenes. It uses zwave direct association.

Do you have a link to the DTH that it used to use? That would be the best way to check how it was being handled. :thinking:

1 Like

Perfect! I’ve been messing with a “central_scene_notification_handler” for the last 2 hours, and I think you’ve hit the nail on the head.

Thank you!

2 Likes

If that’s the issue, it may be as simple as adding the hub to association group 2 for that device, but again, I would check the original DTH. :thinking:

1 Like

I’m trying to get buttons to respond on this device. Were you able to get it working?

I did get them basically working. It’s been a year but my recollection is that I had to install the SmartThings CLI on my computer to install a hacky custom driver.

TBH I never really took the time to understand fully how the new drivers work: I just changed/added things in a driver development template until the switches did what I wanted. And I never overcame the status update delay (though there had always been a delay of several seconds even before the ST architecture change and elimination of Groovy DTHs).