Z-wave native binding roadmap (LR and S2)

Add-ons Bindings
, , ,
1

Hello,

I have some questions for the Z-Wave native binding developer(s):

  • Are there plans to support the Long Range feature?
  • Are there plans to support S2 inclusion?
  • If so, is there a timeframe?
  • Or should I move the the Z-Wave JS binding which already supports these features and will have long term support?

The Z-Wave native binding development seems to have been minimal these last years, just some fixes.

A great thanks to the developers for all their hard work.

Louis

2

It remains supported and may get features included. Besides the usual time constraint there have been some additional requirements to get the full set of protocol documentation for newer chips/SDK by the zwave alliance. They are nearly impossible to meet for a project like openHAB.
So significant new features are not likely on the short term.

1 Like
3

I’ve converted 2 systems to Z-Wave JS. The conversion is pretty straightforward. And the availability of features and new devices in Z-Wave JS is quite good. An added benefit is that my door locks work much better now using S2 security.

But the thing I really, really like is that now I can restart openHAB independently from Z-Wave JS. Since I run snapshot releases, I update and restart openHAB frequently, and its nice that I don’t have to incur the long Z-Wave device interview process every time I start openHAB.

Thank you @lsiepel for the integration!!!

4

As an aside, I did get a PR approved to bypass the interview on fully configured nodes in the native Z-wave binding. openhab/org.openhab.binding.zwave: openHAB binding for Z-Wave

As to the OP topic, I can’t speak for the developer but based on the travel requirements of his real job, I don’t see much more than ongoing DB updates. I have contributed some minor enhancements like the above to keep it relevant, but the LR in particular would be a major refactoring with 12-bit IDs, Smart Start and S2 security all required.

OTOH I have tested LR and haven’t found it awesome. I think the LR chip is better, but I just include the device with the classic 8-bit ID, partially for the mesh.

5

Thanks to all for your inputs.

I think I will move to the Z-Wave JS binding for future proofing. I understand that a developer can have changes in his real life and cannot anymore maintain his code.

Also, I agree with mhilbush, it’s nice to be able to restart openHAB and not have the Z-Wave network very slow for a while.