Seitenvergleich

Loxone do not supply a Z-Wave extension but sometimes it may be desirable to integrate with such devices.

...

1. Loxone Air Extension + 10 x Loxone Door & Window Contact Air costs around 800€
2. Raspberry Pi kit (inc. case, SD card, PSU) + Z-wave.Me UZB + 10 x Coolcam Neo DS01Z window sensors costs around 230€

For the record, the Coolcam Neo DS01Z have similar specifications to the Loxone Door & Window Contact Air, and some may say the Coolcam product is more aesthetically pleasing. There are, or course, many other Z-Wave options for those with different needs or tastes. And of course, a Raspberry Pi in your installation can do much more than just act as a bridge for this one purpose. In fact, the author was already using one so in this instance it's 'cost' was 'free'.

Materials

You will need:

1. At least one Z-Wave sensor or actuator (example uses Coolcam Neo DS01Z window sensors).
2. A Z-Wave USB stick (the author chose a z-wave.me UZB).
3. PC or SBC (eg. Raspberry Pi) to act as a Z-Wave Bridge.

...

1. Gather your materials (hardware).
2. Plug the Z-Wave USB key into the Raspberry Pi and after installing your distribution of choice, check it has correctly loaded the driver. Ie. check for presence of /dev/ttyACM0 or similar.
3. Install the ioBroker package, Z-Wave adapter and Loxone adapter. It is beyond the scope of this How-To to discuss this, please follow the relevant installation instructions. Be sure to configure the Z-Wave adapter with the correct USB device (/dev/ttyACM0 or similar).
4. The Z-Wave and Loxone adapters perform auto-discovery and should create objects for both the Z-Wave devices and the Loxone Virtual Inputs that were configured above. Using the 'Objects' list in the ioBroker admin interface verify this.
5. If this is the first time pairing Z-Wave devices then use the Z-Wave adapter's settings screen to add (pair) your nodes. NB: If nodes are already paired then it may take some time for them to 'wake up' and become fully registered with the adapter (this is dependant on the wake-up time configured for each node). At this point it would also be useful to go through the Z-Wave objects and assign them useful names so they are easier to identify in the next steps.
6. The final step is to connect the Z-Wave and sensors so they update Loxone Virtual input objects, for inputs. For this the ioBroker Javascript adapter is required. This may sound more daunting than it really is - this adapter allows scripts to be created using a drag-and-drop 'blocky' interface similar to the Loxone Config software, or, for more advanced users, code can be written in pure Javascript.
   1. Install the ioBroker Javascript adapter.
   2. Create a new ioBroker script then drag and simply & drop the relevant blocks to have any change in specific Z-Wave objects reflected in the Loxone Virtual Input objects. It is assumed that those wanting to code directly in Javascript will know how to do this. For the the less technical, this connection is achieved using the 'bind' System block:
      Image Added
   3. In the example door sensor, 2 'bind' blocks are required for each one - one for the actual door state, and one to show the battery level in the Loxone interface. For each block, insert the Object ID of the Z-Wave input in the left hand box, and the Object ID of the Loxone Virtual Input to be updated in the right hand one. After creating such blocks for several door sensors, the script appears as below:
      Image Added
   4. Save the script and make sure the Javascript adapter is running, and this newly created script is running too (there should be a 'pause' symbol next to it's name in the list of scripts, indicating, if it can be paused, that it should be running).

And that is is. You should now have the status of Z-Wave sensors communicated to Loxone Virtual Inputs. It should be possible to view the objects changing in real time in both the ioBroker Objects list (in the web admin interface) and Loxone web interface.

...

1. Gather your materials (hardware).
2. Plug the Z-Wave USB key into the Raspberry Pi and after installing your distribution of choice, check it has correctly loaded the driver. Ie. check for presence of /dev/ttyACM0 or similar.
3. Install the Home Assistant Z-Wave software. It is beyond the scope of this How-To to discuss this, but note:
   1. Some might suggest that novice users will fair best if installing the Hass.io distribution.
   2. If using a Docker container note that there is (or at least was as of mid-May 2018) no latest tag for homeassistant/raspberrypi3-homeassistant and therefore one has to pull a specific version (the author used 0.69.0b3).
4. Manually edit the Home Assistant configuration file to specify the device your Z-Wave USB key is on. Eg. add this:
   

   # Z-Wave
   zwave:
    usb_path: /dev/ttyACM0

5. Restart Home Assistant and ensure Z-Wave management appears in the 'Configuration' menu:
   

6. Proceed to add nodes to your Z-Wave network. In the case of the Coolcam Neo DS01Z window sensors this was as easy as hitting 'Add Node' in Home Assistant and triple tapping the button on the window sensor device. Note:
   1. In the case of the Coolcam Neo DS01Z window sensors this not only created the binary sensor (open/close) input we require but also some alarm and other entities that were superfluous to requirements. Each time these can be removed by selecting the entity and checking 'Exclude this entity from Home Assistant'. The author found this sometimes didn't take immediate effect or required a restart of Home Assistant. YMMV.
7. Repeat the step above for each device required. Name each device as required.
8. If everything goes as planned when returning to the Home Assistant overview you will see your Z-Wave device(s) listed with the correct status (note in this example the superfluous entities have already been removed). Go ahead and test the sensors by open/closing them, etc.

...