Z-Wave Setup help

Configuration Z-Wave
1

I decided to give Z-Wave a try, but am really having no luck. Any pointers?

I’m running Hass 94.3 via Docker on Synology NAS.

I purchased the Aeotec Z-Stick Gen5. That seems to be working fine. NAS picked it up, I updated by Docker run, and added the path (/dev/ttyACM0) to HASS via the UI.

My sensor is a Dome DMMS1 Motion/Light sensor. But trying to pair that has been a bear.

On the Hass/stick side, I click “Add Node Secure” but get no indication that this does anything. Still disco lights on the stick, and I saw a youtube video where hass gave a notice in the lower left (like when you restart), but i don’t get that either.

I did get the following in the log:

2019-06-26 20:36:17.336 Detail, Queuing (Controller) Add Device
2019-06-26 20:36:17.336 Info, Add Device

Then I do the 3 button press on the sensor, but it blinks each button press and never does the 5 blinks it’s supposed to. I had it paired once and saw the Node and Entities (Node 2) but wasn’t getting proper updates on the entities. So finally last night I did the failed node workaround, held the button to reset the device, and then tried again. It’s now connected at Node 3. But now almost 24 hours later the state still says “initializing”.

The entities are there but only one of them has changed value from the initial state, the binary sensor motion detector which was “On” for the first 19 hours but inexplicably changed to “Off” about 4 hours ago. We have walked by it off and on and the device blinks with motion.

The logs do show some messages but almost all show the same old value/new value as initially except for this one change. A short example:

2019-06-27 13:47:09.310 Info, Node003, Received SensorBinary report: Sensor:12 State=On
2019-06-27 13:47:09.310 Detail, Node003, Refreshed Value: old value=true, new value=true, type=bool
2019-06-27 13:47:09.310 Detail, Node003, Changes to this value are not verified
2019-06-27 13:47:09.310 Detail, Node003, Notification: ValueChanged
2019-06-27 14:14:55.631 Detail, Node003,   Received: 0x01, 0x0a, 0x00, 0x04, 0x10, 0x03, 0x04, 0x30, 0x03, 0xff, 0x0c, 0x26
2019-06-27 14:14:55.631 Detail, 
2019-06-27 14:14:55.631 Info, Node003, Received SensorBinary report: Sensor:12 State=On
2019-06-27 14:14:55.631 Detail, Node003, Refreshed Value: old value=true, new value=true, type=bool
2019-06-27 14:14:55.631 Detail, Node003, Changes to this value are not verified
2019-06-27 14:14:55.631 Detail, Node003, Notification: ValueChanged
2019-06-27 15:07:59.724 Detail, Node003,   Received: 0x01, 0x0a, 0x00, 0x04, 0x10, 0x03, 0x04, 0x30, 0x03, 0x00, 0x0c, 0xd9
2019-06-27 15:07:59.724 Detail, 
2019-06-27 15:07:59.724 Info, Node003, Received SensorBinary report: Sensor:12 State=Off
2019-06-27 15:07:59.724 Detail, Node003, Refreshed Value: old value=true, new value=false, type=bool
2019-06-27 15:07:59.724 Detail, Node003, Changes to this value are not verified
2019-06-27 15:07:59.725 Detail, Node003, Notification: ValueChanged

The device is in our hallway about 4 feet from the stick/NAS, so I don’t think distance would be an issue.

Is there something I have done wrong? Or do I just have a bad sensor, or stick, or …?

2

Did you set up a secure network key for your z-wave?

3

I left it blank in the UI, which I thought would generate one at random?

4

I do see this in .storage/core.config_entries (assuming this is where it goes, obfuscated):

            {
                "connection_class": "local_push",
                "data": {
                    "network_key": "...",
                    "usb_path": "/dev/ttyACM0"
                },
                "domain": "zwave",
                "entry_id": "...",
                "options": {},
                "source": "user",
                "title": "Z-Wave",
                "version": 1
            }
5

If you’re getting reports in your log then it’s paired correctly, you may want to check the device’s configuration options.

Initializing state on a battery operated device is fine, don’t worry about that.

6

I think you are right. To be sure, perhaps this link is useful Here

From personal experience, I had devices which I had to exclude and include several times before they were picked up properly. Also you mentioned the notice in the lower left, that isn’t present anymore I believe.

7

The configs should still be the default, which I assumed would do…something. Motion flag from off to on, luminance…something. But only the one on to off and I know I walked by it in the last 4 hours at least once. But I’ll experiment.

Bummer and exclude/include. I would assume resetting to factory and trying would take care of it, but I’ll give it another couple of go’s.

Also the UI is uninspiring, if that’s all it does. It’s unclear that it’s ready to pick up anything, nor do I know if it’s ready right away or needs a few minutes. Needs feedback of some sort.

8

There’s a motion reset time as one of the configs. Check that setting.

9

Think I got it. Thanks, all.

The options.xml did have a network key that was disabled, so I set it to the same key from core.config_entries, and rebooted. Then I set all the options, even if I set them to the same thing. I made sensitivity and reset times higher, and some of them I had to set a couple of times before it seemed to “take”. But it seems alive now.

Finicky and not super user friendly, but at least it’s working now. Thanks again!

10

From what I hear the battery operated device are a little weird and touchy, but one they’re working you’re golden. I only have 1 battery powered zwave device and to get it to pair when I bought it I had to add, then remove, then add it once again before it’d work.

My mains powered devices just work.

11

Thanks for the insight. I had hoped to use these where it was hard to get power, like doors and certain motion areas, but I may have to rethink that. As is, once I moved the device to where I wanted to use it, it quit reporting, so I think the range issues were also part of my problem. Powered when possible it is…