Unsupported Devices / Driver development

[syepes]

Hello,

Currently investigating the hub platforms out there and I have just found Z-Way.

I am currently using SmartThings and Hubitat and I was wondering if with Z-Way we have the possibility to add and develop our own user drivers for unsupported devices?

Could you please point me out to some of the docs or resources.

[PoltoS]

There is no need to make drivers for devices in Z-Way. Here the concept is different: Z-Way supports the Z-Wave protocol and it's Command Classes and handles all features it supports. Support of new Command Classes requires developer to implement them first in low lever parser.

Some devices might need some tweaking - in most cases to fix their misbehavior or bugs. This is done via postfix. But this is rare.

[syepes]

Thanks for the precision, as I am coming form SmartThings and Hubitat were they support a well defined list of CC but we still have to create / develop the drivers for handle the actual functionality of each device.

In Z-Way were is this specific device logic setup?

[rafale77]

as PoltoS is saying the concept is different.
SmartThing/Hubitat don't actually support any CC per say, They just are receiving and sending through these CC requiring drivers to support these CC. Z-Way is different in the fact that the supported command classes are actually being functionally handled (That's what we call supported). It is a different philosophy. That being said, I too would like to have more ability to customize and adapt to how each of these command classes are handled.
For example I have sensors reporting through multiple command classes and though they are all supported by z-way at the CC level, they are not all reported at the smarthome/vDev level. I have several sensors reporting the wrong command class to the vDev. Instead of reporting the sensor which trips, they report the CC for tamper for example or a completely different notification altogether.

[syepes]

Very interesting indeed, so in the case we want to handle / modify the default behavior of a CC. Is this still possible?
Is this done from the JS engine or C code directly?

[PoltoS]

CCs are handled inside the C code (libzway).

You can still manipulate some of their data (commansClasses[X].data) and alter the JS code that binds CCs to vDev (Smart home virtual devices)

[rafale77]

How and where could I do this? I would like to change which CC are being reported to the vDev for some of my devices. I even have devices as I PM'd you which have perfectly supported CC and fully interviewed which report to no vDev at all. This has been a point of frustration.

[PoltoS]

Here it is: https://github.com/Z-Wave-Me/home-autom ... x.js#L5903

[rafale77]

Thank you, this is very helpful. I will modify the config xml file accordingly and see where I will go from there.