Linear NGDZ00-4 Garage Door

Configuration Z-Wave
976 
homeassistant@hass:~/.homeassistant$ head OZW_Log.txt 
2019-06-23 16:11:05.961 Always, OpenZwave Version 1.4.3428 Starting Up
2019-06-23 16:11:22.372 Info, Setting Up Provided Network Key for Secure Communications
2019-06-23 16:11:22.376 Info, mgr,     Added driver for controller /dev/ttyUSB-ZStick-5G
2019-06-23 16:11:22.376 Info,   Opening controller /dev/ttyUSB-ZStick-5G
2019-06-23 16:11:22.376 Info, Trying to open serial port /dev/ttyUSB-ZStick-5G (attempt 1)
2019-06-23 16:11:22.387 Info, Serial port /dev/ttyUSB-ZStick-5G opened (attempt 1)
2019-06-23 16:11:22.387 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-06-23 16:11:22.387 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-06-23 16:11:22.387 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-06-23 16:11:22.387 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
977

Alright, show the output of the following:

sudo -H -u homeassistant /bin/bash
source /srv/homeassistant/venv/bin/activate
pip freeze | grep home

Note you may need to change the source command to where your venv is located.
Should get something like this:

home-assistant-frontend==20190604.0
homeassistant==0.94.4
homeassistant-pyozw==0.1.4
978 
(homeassistant) homeassistant@hass:~/.homeassistant$ pip freeze | grep home
home-assistant-frontend==20190604.0
homeassistant==0.94.3
homeassistant-pyozw==0.1.4
homekit==0.14.0
979

Does it show up in your zwave menu in configuration at all?

980

Yes. I see the garage door controller (it is correctly identified) and I have 5 sensors, and a binary sensor, just no cover.

981

Strange, and you still have

cover:
  platform: zwave

in your configuration.yaml?

982

I didnā€™t have that before when it was working, but Iā€™ve added that during the troubleshooting process and since removed it.

I just added that back to my configuration.yaml and restarted HA. Still no cover. :frowning:

983

Have you updated your python venv to 3.7?

984

Not that I know of.

985

Something tells me your openzwavelib didnā€™t update for some reason. Mine reports the following:

2019-06-22 16:44:28.926 Always, OpenZwave Version 1.4.3440 Starting Up

I had to recompile it when I upgraded to Python 3.7.3 in my venv.

1 Like
986

Interesting. I noticed your homeassistant version was 0.94.4. Maybe upgrading to 0.94.4 would also upgrade openzwavelib?

987

Nah the ozw didnā€™t get updated in 94.4

988

Would upgrading ozw be as easy as running the following command from within the venv?

pip3 install --upgrade python-openzwave
989

Might work, but add a --no-cache-dir flag too.

990

Says everything is already up to date:

(homeassistant) homeassistant@hass:/home/hassadmin$ pip3 install --upgrade python-openzwave --no-cache-dir
Requirement already up-to-date: python-openzwave in /srv/homeassistant/lib/python3.6/site-packages (0.4.19)
Requirement already satisfied, skipping upgrade: pyserial in /srv/homeassistant/lib/python3.6/site-packages (from python-openzwave) (3.4)
Requirement already satisfied, skipping upgrade: six in /srv/homeassistant/lib/python3.6/site-packages (from python-openzwave) (1.12.0)
Requirement already satisfied, skipping upgrade: PyDispatcher>=2.0.5 in /srv/homeassistant/lib/python3.6/site-packages (from python-openzwave) (2.0.5)
991

Also --force-reinstall

992

Still showing 1.4.3428 :frowning:

2019-06-23 17:31:26.117 Always, OpenZwave Version 1.4.3428 Starting Up

So I did notice I seem to have two different ozw installs. One at /srv/homeassistant/lib/python3.6/site-packages/python_openzwave/ozw_config, and another one level deeper at /srv/homeassistant/lib/python3.6/site-packages/python_openzwave/ozw_config/config. The second one seems to be an older version as its missing a few aeotec devices. Maybe this is causing some problems? Iā€™m specifying to use the first location in my configuration.yaml under the config_path: option.

993

Hello Community,

Hope someone can help. Iā€™m running Has.io 0.93.2 with OZW 1.4.3440 and I have 3 NGDZ00-4 controllers. I was able to setup of the first one after healing/refreshing the node several times. I secure added the 2nd controller and it appears in the zwave configuration, but it only discovers the binary sensor and not the other entities. Iā€™ve tried removing, re-adding (always secure), but the other entities donā€™t show up. I have cover: in my configuration.yaml (althought I didnā€™t need it for the first node). I changed the batteries in the tilt sensor.

Does anyone have any ideas? Iā€™m pulling my hair out!

TIA

994

Check the dev tools for additional cover entities.

image

Hard to see itā€™s the <> button

995

Hey firstof9,

Thanks for the suggestion. Turns out to be distance. Iā€™m posting my solution in the hope it helps others down the road.

I have 3 NGDZ00-4s. I paired the controller closest to the house first. It paired, but was fussy about adding all the associated entities. I eventually got it fully registered and could use the lovelace UI to open and close the door. Yay!

When I tried door #2, no such luck. It added the radio without problem, but wouldnā€™t pickup the other entities. I tried every combination of refresh node, heal node, pushing the button and even replaced the battery on the tilt sensor. No love.

Even though these devices are wired, they have a short range. Iā€™m about 12 meters from door #2. Since they need to paired in secure mode (and you canā€™t use the button), I decided to move my Ubuntu server into the garage with some crazy long cat5e and power extension cables, and presto! Once detected, I updated the Names and IDs and ā€œsaved configā€. Reboot to be safe and did the same with door #3.

Tldr;

You need to be within 10 meters of the device to pair successfully with a Gen5 Aeotec Zwave stick. Use ā€œadd node secureā€ to include the device.