The first thing is to mention the device in the Suggest a Device topic. 
No guarantees, but at least that gets read.
Smartthings is certified for the âbasic classâ (thatâs Z wave term), and has added some support for some of the additional classes. But it does not support all Zwave classes.
So there are two possible situations for zwave certified devices:
- itâs a device class using zwave command classes that SmartThings already supports, but with some tweakable parameters.
In that case, it might work out of the box, or the device handler might need to be adjusted to allow for setting the parameters.
The fibaro multisensor is a very popular device which Falls into this category. Straight out-of-the-box, it will pair as a motion sensor, but you will not get the reports of temperature or Lux readings even though the device is trying to send them.
So community members have created a custom device handler (formerly called âsmart device typeâ) to handle those additional report. It works very well.
So as long as smart things can handle the command classes that the device is using, itâs just a matter of customizing the device handler, and there are lots of community members Who will be glad to help with that if one doesnât already exist. You just start a new topic in the âconnected thingsâ category with the device name as the topic header and ask for help.
- itâs a device class, or uses zwave commands, that SmartThings does not recognize.
In that case, youâre out of luck. All you can do is ask support when they are going to add it.
This is the current situation with the Aeon labs zwave lightbulb, A brand-new device. No one has it working yet. Smartthings is supposed to be getting one soon for their engineers to look at, and since Aeon devices are very popular they will probably add whatever needs to be added pretty soon. But no guarantees.
Some commands are quite difficult to support, and smartthings neither supports them nor intends to add that at least not for the current generation. A good example of those is scene replication, which is needed for some button remotes. SmartThings just doesnât work with those and thereâs no way to change that.
I couldnât tell from the initial documentation whether the Philio will run into any of these issues or not. Sometimes itâs easy to tell, such as when a device uses scene replication and does not support association. But sometimes itâs quite hard to tell, and that includes some of the devices that rely on notification.
So I canât really tell you now whether it will be possible to develop a custom device handler for the Philio or not. If you buy it from a place with a good return policy it would be worth trying to see what happens. Once you have the device we can see what device class SmartThings assigns the device to and what the logs show the device is sending.