Vera has made it very difficult, but not impossible to support Z-Wave devices not on the officially supported list.
First, make sure that the device that you are interested in is built for the flavor of Z-Wave in your country. Then try to pair the device as a generic Z-Wave device and see how much functionality you get.
If not enough, then comes the hard part. You need to create a custom plug-in for your device. Make sure that you have a full specification of all of the command classes, device options and specific behavior of your device. This is not part of the owner’s manual, or otherwise available on-line, the Z-Wave alliance maintains a pretty good database of this information on their website.
Then you need to write a device driver in Lua. This is non trivial. There is one “SendData” call which allows sending arbitrary Z-Wave data to a device. However, not only does this require a deep knowledge of the Z-Wave serial host protocol, but also, heavy use of “SendData” can trigger a long-standing “Failed to get lock” race confusion in the Vera firmware which has not been fixed even after it was reported several years ago.! Furthermore, there is no good buit-in method to receive arbitrary data from a Z-Wave device.
That’s why, when I wrote my Scene controller plugin for Evolve LCD1, Cooper RFWC5, Nexia One-Touch, and HomeSeer switches and dimmers, I ended up writing a special Lua extension in C, compiled to MIPS machine code which I call the Z-Wave Interceptor, or Zwint. Zwint gets in between the LuaUPnP engine’s Z-Wave support library and the Z-Wave controller. It monitors all Z-Wave serial protocol traffic from both sides, parses each packet, and uses a set of filters based on regular expressions to intercept selected packets and deliver them to the plugin as HTTP messages.
The debug version of my Scene controller plugin has many examples on how to use Zwint in various ways and I encourage anyone who wants to use it to go ahead and take it.
Unfortunately, Vera will soon be obsoleting all of the old custom plugins with their new Ezlo API and the currently published API does not (yet) include adequate support for custom Z-Wave devices.
SmartThings has a nice Z-Wave library which makes creating custom plugins for that platform relatively easy, but I’m fundamentally opposed to their approach that puts all functional logic for your home device automation in a cloud server.
I also looked at HomeSeer and their controllers have no good support for custom Z-Wave plugins either.