[ST Edge] Z-Wave Plus 700 series based Sensative Strips Sensors Driver [MANUFACTURER VERSION]

[JDRoberts]

@uberrob

If I look at the strips in the old IDE they are shown as “cloud” executables, not local. This is has been a source of frustration for me for months – I simply cannot get them to install properly.

Information for devices using edge drivers can be inaccurate and incomplete if you try to look at them through the IDE. The IDE has never been updated for the new architecture, so you shouldn’t count on it in that regard. It shows a lot of devices using edge drivers as “cloud“ even though all edge drivers run on the hub.

FAQ: Why does the IDE list “placeholder” for my device? Can I change that?

non-technical answer: the IDE is part of the old groovy based architecture. It will be going away and be replaced with something else. in the meantime, anything which is using the new architecture will be represented in the IDE with “placeholder“ under the device type column. This includes devices using an Edge Driver. Since new edge drivers are being added overtime, it may even be that a device which is the same model number as a device you previously added which used a groovy DTH is now using an Edge driver and so shows up as placeholder. Don’t change it! Once the device is using an integration from the new architecture, you can no longer get to its code details through the IDE, And changing it to a different device type may break the integration altogether. If you need to cha…

To get accurate information about devices using edge drivers, you can use either the CLI, or a community created webpage interface called API Browser +. It’s not as easy to use the first time as the IDE was since you have to grant access, but after that, it’s got a lot of very helpful information.

SmartThings API Browser+ ... Now Available to All

NOTICE!!: SmartThings has now released its own equivalent of this app here, so you may prefer to use that instead. I have a browser-based web app that provides a point-and-click way to explore most of the SmartThings API. For the non-technical, this gives you access to an important SmartThings resource without having to learn tools like Postman, curl, or the CLI. You don’t even need a computer: a tablet or even smartphone can be used. For the more technically inclined, it provides much faster and more convenient access to those commonly-accessed CLI commands. Although I originally thought of it as a portal for the non-technical, I’ve actually found it quite useful to use during my own development activities. This is not intended as a replacement or ‘competitor’ to the CLI, mysmart…