From bcc789f3c3893970abe55c3dba4cdff029ca125a Mon Sep 17 00:00:00 2001 From: Ryan Borstelmann Date: Fri, 8 Apr 2016 15:37:01 -0500 Subject: [PATCH] Update z-wave.markdown (#375) --- source/_topics/z-wave.markdown | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/_topics/z-wave.markdown b/source/_topics/z-wave.markdown index 4fff9fea8e2..970303a1c2e 100644 --- a/source/_topics/z-wave.markdown +++ b/source/_topics/z-wave.markdown @@ -31,3 +31,9 @@ Upon first run, the z-wave component will take time to initialize entities and e The alternative to a stick is a hub that supports Z-Wave. Home Assistant supports the following hubs with Z-Wave support: - [Vera](/components/vera/) + + +## {% linkable_title Modifying Zwave Device Settings %} +You may wish to modify the zwave settings ozw*.xml file in your .homeassistant root folder, or certain situations/devices may require it (i.e. Aeon Multisensor 6). To do this, utilize (Open-Zwave Control Panel)[https://github.com/OpenZWave/open-zwave-control-panel]. Alternatively, use (Domoticz)[https://www.domoticz.com/], which incorporates the Open-Zwave Control Panel project into an easy to use Raspberry Pi image. + +The reasoning for using these tools is that your Zwave controller stores the values and data that are used to control the network. The XML file in the .homeassistant folder acts as a settings/values cache for the zwave network, so modifying it directly won't change the network values. The Open-Zwave Control Panel writes values directly to the network, and will provide you with an updated .xml file to overwrite in your .homeassistant folder. This is the most foolproof way to make modifications to your zwave devices.