You’re right, the local handler for Z-Wave switches isn’t populating the physical/digital field. We actually intended to deprecate and remove that functionality before this release, but that fell through the cracks. I apologize for the communication failure.
The reason we’re not continuing to support the physical/digital field is that it only works on a subset of switch devices, and even then it’s basically just a hack for most of those. For example, on most switches it doesn’t work through repeaters. We’ve also had issues with false positives.
For now, you’ll have to use a custom DTH to continue to get that functionality. I’m hopeful we can replace it with a capability like Button that more precisely represents the device’s behavior, but I don’t know what kind of priority that will have.
Fair enough, thank you for the informative answer. Although changes like these can tend to be annoying, being able to roll your own custom DTH and SmartApps are a testament to the flexibility and extensibility of the SmartThings platform. Keep up the good work ST!
Can you please point me to where I can find the prior version of these DTHs (that continue to report the physical/digital field, prior to yesterdays rollout) ?
Do the latest versions in the SmartThingsPublic github repo accurately report the physical / digital field? They seem to be (in glancing at the code), but I just want to be sure:
@duncan, do I read correctly that local support for Z-Wave switches is being removed? That meaning Smart Lights automations switching security lighting using Z-Wave switches will fail to execute in the absence of internet connectivity to the ST cloud?
With my Iris motion sensors, I had to click ‘Check now’ in the device portion of the IDE (where it shows the firmware level) before it eventually showed that a firmware update was available. I notice that of the 5 Iris motion sensors I have, one does continue to report its original 67% battery level that it had before the update; the other four went to 100%. Odd.
I created a new DTH for my switches by just using one of the Z-Wave Switch templates (From Template, then selected the 2nd Z-Wave Switch) … and now I have the interactions back in the logs, after I updated my GE switches to use the newly created DTH. Of course, now execution location is now in the cloud.
Nope, not at all. The code supporting these switches (and other locally running devices) is different, but we only plan to expand the set of devices that are supported locally over time – expect to see several more devices supported locally with subsequent hub releases (including 19.x).
Has anyone had problems with a z-wave repair since the backend update?
When I try to run it, after 1 second it shows as finished (twice) and nothing else
I’ve tried running it both through the ios app and the ide
