# Razpberry problems with routing to different z-wave products

**URL:** <https://community.openhab.org/t/razpberry-problems-with-routing-to-different-z-wave-products/45678>\
**Category:** Bindings\
**Tags:** openhab2, zwave1\
**Created:** [May 30, 2018, 9:24am UTC](https://community.openhab.org/t/razpberry-problems-with-routing-to-different-z-wave-products/45678 "2018-05-30T09:24:15Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Dim](https://community.openhab.org/user_avatar/community.openhab.org/dim/32/4568_2.png) [@Dim](https://community.openhab.org/u/Dim)\
**Post date:** [May 30, 2018, 10:12am UTC](https://community.openhab.org/t/razpberry-problems-with-routing-to-different-z-wave-products/45678/4 "2018-05-30T10:12:38Z")

</div>

> [@OH2 Z-Wave refactoring and testing... and SECURITY](https://community.openhab.org/t/oh2-z-wave-refactoring-and-testing-and-security/21653):
>
> The latest version of the development binding dated 8th Sep 2018 is [here](http://www.cd-jackson.com/downloads/openhab2/org.openhab.binding.zwave-2.4.0-SNAPSHOT.jar). Toward the end of last year I spent some time doing some initial refactoring of the ZWave binding in OH2. This focussed on rewriting the way transactions work as this is an enabler for other areas of the code. At the same time I also restructured the different layers of the binding to make things cleaner, and done some changes to support a system of autocoding the command classes directly from the Z-Wave standard which s…

---

_[View the full topic](https://community.openhab.org/t/razpberry-problems-with-routing-to-different-z-wave-products/45678)._
