Regrettably the Zwave standard does not work the way you appear to imagine.
The standard applies only at the “basic” level (that a Zwave term), which means that a certified Zwave controller, like the SmartThings hub, will be able to send a basic command to any certified Zwave device. Essentially just an on/off.
Any features above that may or may not be supported. You have to look at the actual command sets to see what’s going on.
There are many Zwave certified devices which do not work well with SmartThings, because they require advanced features which SmartThings does not support.
It is important to understand this, particularly when you are participating in conversations about devices with which you have no personal experience, since otherwise you may be leading other community members to spend money on things that in fact will not work.
In the case of this particular device, it is not a simple on/off switch. You can see that from the conformance statement to which the original poster linked.
Not Just a Generic Switch
This is a multiple channel device, with three different switches. It also has multiple sensors.
As you get more familiar with the forums, you will discover that SmartThings does not handle multiple endpoint devices particularly gracefully. These almost always require a custom device type, and even then it can be tricky to get all the information reported correctly.
Beyond that this particular switch cannot be used as a “button controller” in the SmartThings’ terminology since it does not control association. That means at best it can be used as a multiple endpoint device, sort of like the Aeon power strip. But getting status back from it may be challenging.
Consequently, this particular device is going to take considerable work before it could be usable in a SmartThings’ set up and even then, I’m not sure you’re going to get all the manufacturer-intended features.
(Note also that the command sets in the conformance statement include “manufacturer proprietary” which may mean there’s no way to fully access its features. Zwave does allow for manufacturer proprietary features within its standard.)
I’m sure there are knowledgeable community members who would be happy to help try and develop a custom device type for the device, but at this point it’s not easy to say whether that would be successful or not. It’s certainly not going to be as simple as using the generic Z wave dimmer device type that applies to a single switch device.
BTW, I made the same conceptual error when I first bought SmartThings. I assumed it would work out of the box with any certified Zwave device that worked with Vera. But because ST is a multiprotocol platform, it did not implement controller-based scene management. That’s not basic level functionality, so it didn’t have to, but it means many multibutton devices require custom device types.
Submitted with respect.