What will happen to the z-wave component when I upgrade?

Configuration Z-Wave
1

Hi all,

I’m on .38 which is working well, but I want to upgrade to get access to the nice things in the latest release. However, I’m wondering what will happen when I upgrade?

  1. Can I run OZWCP and HASS z-wave side by side, simply stop z-wave in HASS and start OZWCP?

  2. Also, I seem to remember it was necessary to compile your own support for the z-wave component back when I started (around .34), should I comment out the z-wave config path to make sure HASS uses the z-wave support now provided natively in HASS? Currently my config path for the zwave component in configuration.yaml is: /usr/local/lib/python3.5/dist-packages/libopenzwave-0.3.1-py3.5-linux-x86_64.egg/config/

Or do I simply upgrade and everything should work out?

Thanks in advance, just don’t want to mess up a working system! :blush:

2

The latest version uses pip to install python-openzwave automagicly for you. So unless you had to compile a custom version to get devices working, you should be fine to upgrade.

Also note that device names will be changed as well, so you’ll need to modify any automations for your Zwave devices.

3

^ and to answer 1. yes.

4

How is the change to how zwave devices are named going to impact him?

5

If he has automations setup he’ll have to modify them to the new naming system.

6

Thanks guys! Yes, I read about the naming convention being changed which will be a one-time effort so I’m ok with it. Thanks again for the quick response, I feel confident to upgrade now!

7

Yea, That’s what I think every time I upgrade too. LOL

1 Like