To poll or not to poll (GE, Aeon, Ecolink devices)

Configuration Z-Wave
1

EDIT: See my last post (#13) for updated information. I made some false information and have done more research.

I ran into a rather frustrating issue about a week ago and did a little testing and gained some insight while fixing my problem. Here’s my setup:

2 - GE 45605 Duplex Receptacle
1 - GE 12721 Duplex Receptacle
2 - GE 12729 Dimmer Switch (1 with 3-way add-on switch, 1 without)
2 - GE 12727 In-Wall Smart Switch
2 - GE 12720 Outdoor Smart Switch
1 - GE 45603 Plugin Appliance Module
1 - Kwikset 910 Deadbolt
1 - Ecolink PIR Motion Detector
2 - Aeotec ZW096 Smart Switch 6

First thing I noticed early on was my dimmer switches would briefly update the brightness in HA, but never go full “on” or “off” when I used the physical switch. If I used HA, they would work every time. Then I started noticing some of the receptacles weren’t updating their state from physical interaction or from within HA. To fix this, I automatically assumed I needed to set “polling_intensity: 1” and "refresh_value: True"on every device and set “polling_interval: 30000” to get these to work. Well turns out, no. That actually made things worse. Not only did I not fully read the docs, but I was overwhelming my Z Wave network. This caused my devices to seemingly at random respond to HA very slow and if I switched multiple devices there would be long pauses and delays.

What I learned: NO, GE Z Wave devices DO NOT NEED TO BE POLLED!* They are perfectly capable of sending their instant status updates. The exception (*) is the dimmer switches still don’t update quite right, but I’m in the process of testing the refresh_value: True setting. Also, it’s possible the add-on switch does not cause the master switch (when connected to a switch and not a dimmer in a 3-way configuration) to re-transmit the status, but I can’t confirm that. Also, my deadbolt and motion detector are battery powered and they do not need to be polled. Lastly, the smart switch 6’s also do not need polling, not even for the energy reporting since they have a “Hail” reporting feature. I’m having some trouble with them right now, but that’s a separate issue.

My take-aways: Don’t just assume the device needs polling. Test it first then try 1 setting at a time. The more devices you setup polling for, the slower the Z Wave network will run. The shorter the polling interval, the slower the Z Wave network will run. Also as soon as you setup polling on a device, this overrides the default reporting and the network/HA will only update states when the device gets polled. Watch the OZW log and HA log with verbose debugging for each and you’ll see the difference and effect polling has.

2 Likes
2

I might be suffering from this. My z-wave network isn’t quite fast enough; my deadblolt batteries die too fast. Right now I have polling_intensity set to 2, refresh_value set to true, and delay set to 5. This is for ALL lights. Two bulbs are go-control but the rest are GE Z-wave switches.

Would you recommend I take all of these options out and see what devices give me trouble. Then adjust the values as as needed for only those lights?

I’m not even sure where I got those numbers from - some forum post a long time ago when there were far less z-wave devices in my home.

3

yes. You can remove all these options, however they will still stick even through a reboot. The Z Wave polling configuration actually changes the XML in zwcfg_xxxxxx.xml. I eventually removed a few nodes, but if you invert or reset your options and restart HA then remove the options and restart HA again. it will “reset” the polling options. set polling_interval: 0 and refresh_value: False. Another option is to reset your Z Wave network completely by removing each node then doing a factory reset on the Z Wave hub.

No matter what you do, start with one device of each type and test it for local control and how it responds in HA frontend, and also test it for remote control in HA and how it responds. My battery powered devices have decent battery life. The motion detector is new and still says 100% after 2 months, but I’ve replaced the deadbolt batteries 3 or 4 times in about 2 years and after resetting some of the Z Wave options the battery level is pretty stable still with constant use.

4

Here’s an update: I recently tried working with the Aeotec smart switches. I want them to report the power and energy readings. According to other posts in the forums here it’s recommended to enable “Hail” reporting which is parameter 80. DO NOT DO THIS! This absolutely floods the Z Wave network and prevents other devices from reporting their status changes from physical interaction with the device. If using HA, the status is reflected properly, but physical interaction fails to update HA with the correct status. I haven’t set parameter 80 to “Basic” reporting yet and used the reporting intervals but that will be my next test.

EDIT: the GE add-on switches do not tell the master switch to update its status. This is regardless of being connected to a dimmer or a switch. Any 3-way configuration with an add-on switch probably needs polling as that’s the best it can do unless you always use the master switch.

1 Like
5

I’ve had to reset my z-wave network once or twice in the last year or so. What an nightmare. I have 17 zwave lights made up of GE Dimmers, GE Switches, and 4 go-control bulbs. Around 9 or 10 motion sensors and as many door sensors. At least 4 or 5 of the same smart switches you have. I didn’t care for Hue at first because Zwave seemed to be a superior technology but I have 100x more trouble with zwave than any other component installed in HA. I loathe renaming or setting up a new device. When I need another switch I’m getting TP Link wi-fi instead.

I don’t recall setting parameter 80 on any of those smart switches but if I watch the log (and I rarely understand it) my switches are talking way more than they should be. Report Group 1 is set to 120. Report groups 2 and 3 are set to 600. Setting report group one to 120 allowed me to monitor the output of washer , dryer, television, and desktop monitors accurately.

I’ve seen all sorts of posts about how the usb stick should be central in the house. I never noticed a problem with mine tucked in the corner of basement but yesterday I read about how I am probably creating a traffic jam on the 1 or 2 devices closest to the usb stick. I don’t run pi but a VM on an Dell server tower, so it’s not very portable. I’m supposing this could be another big problem - just cause it’s all working most of the time doesn’t mean it’s working well most of the time.

Really appreciate you posting your findings here. Not sure I have the energy to tear down the whole place this weekend and will probably need to wait for wife to have a girl’s weekend away! :slight_smile:

6

I counted, I have 54 z-wave devices on my system.

Here is a pastebin link to 10 minutes of my OZW log file. https://pastebin.com/zTrREQg7

I checked and do not appear to be using Hail mode on notification status. Mine is set to Nothing (Default)

7

yep I’m in a similar situation as you (Docker container running on Synology tucked away in a corner of the basement). My wife is also one very patient woman. Best thing I could do is put the USB stick on a 12 foot shielded USB extension cable and attach it to the sub floor in the basement ceiling joists. I also have a GE switch, GE Appliance module, and Door lock within 5 feet of the stick (with 1 floor separation).

I put my smart switches back to “Nothing (Default)” and the network seems to be working better. I’ve played around with reporting groups, but I think parameter 80 needs to be set to “Basic” for those to work. Otherwise, I don’t get any current/energy reporting.

1 Like
8

If the device does not support instant status, you will get better UI performance doing the polling. At least that has been my experience. I have a number of GE 12724 Dimmers (12730 Fan) and polling is required if you want the UI to update timely. My GE 14294 Dimmers do not need it.

9

Can confirm. Since I disabled all the options on z-wave last night my bathroom dimmers don’t respond well in the UI. And now that I think about it, this is what set me down the path of using the options. I still have all options off and will try to observe how things work over the next few days.

10

The usb extension is a good idea. Is 12’ a limitation of how z-wave will work or is it just the longest cable you have? If the later I’ll buy the longest shielded usb cable I can find!

EDIT: I found a 16’ one on amazon. But thinking on it, I’m not even sure where I will put the other end. Server is so far back. And while I can run ethernet most spots in the house I don’t have anywhere to put this beast.

11

The spec for USB 2.0 limits non-powered extension cables to 5 meters (16 feet). If you have powered hubs, it’s different. Also the longer the cable, if it doesn’t have adequate shielding, the more interference it is susceptible to and can cause communication problems. I had a 12’ shielded (about the thickness of standard coax RG-6 cable) laying around, so that’s what I went with.

12

Yep, read the exception note I had posted right after the part you quoted from my original post… dimmers act differently. I’m playing around with the refresh_value: True setting, but they may still need polling to display properly. Also in another post I confirmed the add-on switches in a 3-way configuration do not force the master switch to update its state regardless if the master is a switch or dimmer.

13

Ok so I want to clarify some things. I was wrong. I made some incorrect conclusions based on some testing I did and the results I saw, but I failed to dig further and confirm what was actually happening.

GE devices DO NOT do instant status updates. They appear to do instant status by using a workaround in the Z Wave protocol. As can be found in many other posts about Z Wave devices online, instant status is a patent (though the name is not patented, just the method) previously held by Lutron (US Patent #5,905,442). This patent is said to have expired, though I cannot confirm, but others have. GE decided not to license this patent from Lutron in their Z Wave and possibly others. The GE/Jasco 45XXX/12XXX series devices use a feature of the Z Wave protocol to get around this and make it look like it can do instant status updates. The new GE/Jasco 14XXX series devices still do not have instant status updates, but they support OTA firmware updates, so this may come in a future update.

What GE does to get around the instant status updates is send a hail command to the network. This is a broadcast message the controller responds to. From what I have read and understand, the controller is the only device that responds to these broadcast messages. So the device sending a hail must have the controller (node 1) as it’s primary or first neighbor. If the device has a routing slave between it and the controller, the routing slave will not re-broadcast or route broadcast messages. When the controller receives a hail command or broadcast message, it tells the controller to query the node that sent the message. The device responds to the query and tells the controller its new status.

What I was experiencing was some devices no longer had node 1 (the controller) as its primary neighbor. Those nodes were the ones not updating their status on physical interaction. I had to do multiple network heals and in OZWCP force an update of the return routes for specific nodes.

So to re-cap, GE/Jasco (and others that didn’t license the Lutron patent) can use hail commands on physical state change to provide pseudo instant status updates. However, if you have any devices that are far enough away from the main controller, you will want to setup polling for these devices.

To support my further research, here’s the two articles I read.

Comment from discussion GE instant status.

How to Fix GE Z-Wave Switches Not Updating in the Home Assistant UI

Also here is a snippet of my OZW log that shows physically interacting with a switch. This shows the hail command, the query from the controller, followed by the response from the device with its new status.

switch on:

2017-12-03 20:59:36.682 Detail, Node007,   Received: 0x01, 0x11, 0x00, 0x49, 0x84, 0x07, 0x0b, 0x04, 0x10, 0x01, 0x25, 0x27, 0x75, 0x73, 0x70, 0x86, 0x72, 0x77, 0xcd
2017-12-03 20:59:36.682 Detail, 
2017-12-03 20:59:36.682 Info, Node007, UPDATE_STATE_NODE_INFO_RECEIVED from node 7
2017-12-03 20:59:36.682 Detail, Node007, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Dynamic live=1
2017-12-03 20:59:36.682 Detail, Node007, QueryStage_Dynamic
2017-12-03 20:59:36.683 Detail, Node007, Queuing (Send) SwitchBinaryCmd_Get (Node=7): 0x01, 0x09, 0x00, 0x13, 0x07, 0x02, 0x25, 0x02, 0x25, 0x3b, 0xd9
2017-12-03 20:59:36.683 Detail, Node007, Queuing (Query) Query Stage Complete (Dynamic)
2017-12-03 20:59:36.683 Detail, 
2017-12-03 20:59:36.683 Info, Node007, Sending (Send) message (Callback ID=0x3b, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=7): 0x01, 0x09, 0x00, 0x13, 0x07, 0x02, 0x25, 0x02, 0x25, 0x3b, 0xd9
2017-12-03 20:59:36.690 Detail, Node007,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-12-03 20:59:36.690 Detail, Node007,   ZW_SEND_DATA delivered to Z-Wave stack
2017-12-03 20:59:36.707 Detail, Node007,   Received: 0x01, 0x07, 0x00, 0x13, 0x3b, 0x00, 0x00, 0x02, 0xd2
2017-12-03 20:59:36.707 Detail, Node007,   ZW_SEND_DATA Request with callback ID 0x3b received (expected 0x3b)
2017-12-03 20:59:36.707 Info, Node007, Request RTT 24 Average Request RTT 25
2017-12-03 20:59:36.707 Detail,   Expected callbackId was received
2017-12-03 20:59:36.717 Detail, Node007,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x07, 0x03, 0x25, 0x03, 0xff, 0x2f
2017-12-03 20:59:36.717 Detail, 
2017-12-03 20:59:36.717 Info, Node007, Response RTT 34 Average Response RTT 35
2017-12-03 20:59:36.717 Info, Node007, Received SwitchBinary report from node 7: level=On
2017-12-03 20:59:36.717 Detail, Node007, Refreshed Value: old value=false, new value=true, type=bool
2017-12-03 20:59:36.718 Detail, Node007, Changes to this value are not verified
2017-12-03 20:59:36.718 Detail, Node007,   Expected reply and command class was received
2017-12-03 20:59:36.718 Detail, Node007,   Message transaction complete
2017-12-03 20:59:36.718 Detail, 
2017-12-03 20:59:36.718 Detail, Node007, Removing current message
2017-12-03 20:59:36.718 Detail, Node007, Notification: ValueChanged
2017-12-03 20:59:36.718 Info, Notification: Value Changed Home 0xdd0757f3 Node 7 Genre user Class SWITCH BINARY Instance 1 Index 0 Type bool
2017-12-03 20:59:36.718 Detail, Node007, Query Stage Complete (Dynamic)
2017-12-03 20:59:36.718 Detail, Node007, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Configuration live=1
2017-12-03 20:59:36.718 Detail, Node007, QueryStage_Configuration
2017-12-03 20:59:36.718 Detail, Node007, QueryStage_Complete
2017-12-03 20:59:36.718 Warning, CheckCompletedNodeQueries m_allNodesQueried=0 m_awakeNodesQueried=1
2017-12-03 20:59:36.718 Warning, CheckCompletedNodeQueries all=0, deadFound=0 sleepingOnly=1
2017-12-03 20:59:36.718 Detail, Node007, Notification: NodeQueriesComplete
2017-12-03 20:59:36.718 Info, Notification: Node 7 Queries Complete

switch off:

2017-12-03 20:59:55.720 Detail, Node007,   Received: 0x01, 0x11, 0x00, 0x49, 0x84, 0x07, 0x0b, 0x04, 0x10, 0x01, 0x25, 0x27, 0x75, 0x73, 0x70, 0x86, 0x72, 0x77, 0xcd
2017-12-03 20:59:55.720 Detail, 
2017-12-03 20:59:55.720 Info, Node007, UPDATE_STATE_NODE_INFO_RECEIVED from node 7
2017-12-03 20:59:55.720 Detail, Node007, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Dynamic live=1
2017-12-03 20:59:55.720 Detail, Node007, QueryStage_Dynamic
2017-12-03 20:59:55.720 Detail, Node007, Queuing (Send) SwitchBinaryCmd_Get (Node=7): 0x01, 0x09, 0x00, 0x13, 0x07, 0x02, 0x25, 0x02, 0x25, 0x3c, 0xde
2017-12-03 20:59:55.720 Detail, Node007, Queuing (Query) Query Stage Complete (Dynamic)
2017-12-03 20:59:55.721 Detail, 
2017-12-03 20:59:55.721 Info, Node007, Sending (Send) message (Callback ID=0x3c, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=7): 0x01, 0x09, 0x00, 0x13, 0x07, 0x02, 0x25, 0x02, 0x25, 0x3c, 0xde
2017-12-03 20:59:55.728 Detail, Node007,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-12-03 20:59:55.728 Detail, Node007,   ZW_SEND_DATA delivered to Z-Wave stack
2017-12-03 20:59:55.745 Detail, Node007,   Received: 0x01, 0x07, 0x00, 0x13, 0x3c, 0x00, 0x00, 0x03, 0xd4
2017-12-03 20:59:55.745 Detail, Node007,   ZW_SEND_DATA Request with callback ID 0x3c received (expected 0x3c)
2017-12-03 20:59:55.745 Info, Node007, Request RTT 24 Average Request RTT 24
2017-12-03 20:59:55.745 Detail,   Expected callbackId was received
2017-12-03 20:59:55.756 Detail, Node007,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x07, 0x03, 0x25, 0x03, 0x00, 0xd0
2017-12-03 20:59:55.756 Detail, 
2017-12-03 20:59:55.756 Info, Node007, Response RTT 35 Average Response RTT 35
2017-12-03 20:59:55.756 Info, Node007, Received SwitchBinary report from node 7: level=Off
2017-12-03 20:59:55.756 Detail, Node007, Refreshed Value: old value=true, new value=false, type=bool
2017-12-03 20:59:55.756 Detail, Node007, Changes to this value are not verified
2017-12-03 20:59:55.756 Detail, Node007,   Expected reply and command class was received
2017-12-03 20:59:55.756 Detail, Node007,   Message transaction complete
2017-12-03 20:59:55.756 Detail, 
2017-12-03 20:59:55.756 Detail, Node007, Removing current message
2017-12-03 20:59:55.756 Detail, Node007, Notification: ValueChanged
2017-12-03 20:59:55.756 Info, Notification: Value Changed Home 0xdd0757f3 Node 7 Genre user Class SWITCH BINARY Instance 1 Index 0 Type bool
2017-12-03 20:59:55.756 Detail, Node007, Query Stage Complete (Dynamic)
2017-12-03 20:59:55.756 Detail, Node007, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Configuration live=1
2017-12-03 20:59:55.756 Detail, Node007, QueryStage_Configuration
2017-12-03 20:59:55.756 Detail, Node007, QueryStage_Complete
2017-12-03 20:59:55.756 Warning, CheckCompletedNodeQueries m_allNodesQueried=0 m_awakeNodesQueried=1
2017-12-03 20:59:55.757 Warning, CheckCompletedNodeQueries all=0, deadFound=0 sleepingOnly=1
2017-12-03 20:59:55.757 Detail, Node007, Notification: NodeQueriesComplete
2017-12-03 20:59:55.757 Info, Notification: Node 7 Queries Complete

I apologize if I led anyone astray in my posts. I apologize for the incomplete research and incorrect conclusions I made.

EDIT: For comparison, here is a snippet of the OZW log showing toggling the switch from a z wave command or HA frontend.

switch on:

2017-12-04 00:05:25.991 Info, Node006, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True
2017-12-04 00:05:25.991 Info, Node006, SwitchBinary::Set - Setting node 6 to On
2017-12-04 00:05:25.992 Detail, Node006, Queuing (Send) SwitchBinaryCmd_Set (Node=6): 0x01, 0x0a, 0x00, 0x13, 0x06, 0x03, 0x25, 0x01, 0xff, 0x25, 0x57, 0x4a
2017-12-04 00:05:25.992 Detail, Node006, Queuing (Send) SwitchBinaryCmd_Get (Node=6): 0x01, 0x09, 0x00, 0x13, 0x06, 0x02, 0x25, 0x02, 0x25, 0x58, 0xbb
2017-12-04 00:05:25.992 Detail, 
2017-12-04 00:05:25.992 Info, Node006, Sending (Send) message (Callback ID=0x57, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=6): 0x01, 0x0a, 0x00, 0x13, 0x06, 0x03, 0x25, 0x01, 0xff, 0x25, 0x57, 0x4a
2017-12-04 00:05:25.999 Detail, Node006,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-12-04 00:05:25.999 Detail, Node006,   ZW_SEND_DATA delivered to Z-Wave stack
2017-12-04 00:05:26.053 Detail, Node006,   Received: 0x01, 0x07, 0x00, 0x13, 0x57, 0x00, 0x00, 0x06, 0xba
2017-12-04 00:05:26.053 Detail, Node006,   ZW_SEND_DATA Request with callback ID 0x57 received (expected 0x57)
2017-12-04 00:05:26.054 Info, Node006, Request RTT 62 Average Request RTT 69
2017-12-04 00:05:26.054 Detail,   Expected callbackId was received
2017-12-04 00:05:26.054 Detail,   Expected reply was received
2017-12-04 00:05:26.054 Detail,   Message transaction complete
2017-12-04 00:05:26.054 Detail, 
2017-12-04 00:05:26.054 Detail, Node006, Removing current message
2017-12-04 00:05:26.054 Detail, 
2017-12-04 00:05:26.054 Info, Node006, Sending (Send) message (Callback ID=0x58, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=6): 0x01, 0x09, 0x00, 0x13, 0x06, 0x02, 0x25, 0x02, 0x25, 0x58, 0xbb
2017-12-04 00:05:26.062 Detail, Node006,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-12-04 00:05:26.062 Detail, Node006,   ZW_SEND_DATA delivered to Z-Wave stack
2017-12-04 00:05:26.119 Detail, Node006,   Received: 0x01, 0x07, 0x00, 0x13, 0x58, 0x00, 0x00, 0x06, 0xb5
2017-12-04 00:05:26.119 Detail, Node006,   ZW_SEND_DATA Request with callback ID 0x58 received (expected 0x58)
2017-12-04 00:05:26.119 Info, Node006, Request RTT 64 Average Request RTT 66
2017-12-04 00:05:26.119 Detail,   Expected callbackId was received
2017-12-04 00:05:26.175 Detail, Node006,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x06, 0x03, 0x25, 0x03, 0xff, 0x2e
2017-12-04 00:05:26.175 Detail, 
2017-12-04 00:05:26.175 Info, Node006, Response RTT 121 Average Response RTT 127
2017-12-04 00:05:26.175 Info, Node006, Received SwitchBinary report from node 6: level=On
2017-12-04 00:05:26.175 Detail, Node006, Refreshed Value: old value=false, new value=true, type=bool
2017-12-04 00:05:26.175 Detail, Node006, Changes to this value are not verified
2017-12-04 00:05:26.175 Detail, Node006,   Expected reply and command class was received
2017-12-04 00:05:26.175 Detail, Node006,   Message transaction complete
2017-12-04 00:05:26.176 Detail, 
2017-12-04 00:05:26.176 Detail, Node006, Removing current message
2017-12-04 00:05:26.176 Detail, Node006, Notification: ValueChanged
2017-12-04 00:05:26.176 Info, Notification: Value Changed Home 0xdd0757f3 Node 6 Genre user Class SWITCH BINARY Instance 1 Index 0 Type bool

switch off:

2017-12-04 00:06:09.841 Info, Node006, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - False
2017-12-04 00:06:09.842 Info, Node006, SwitchBinary::Set - Setting node 6 to Off
2017-12-04 00:06:09.842 Detail, Node006, Queuing (Send) SwitchBinaryCmd_Set (Node=6): 0x01, 0x0a, 0x00, 0x13, 0x06, 0x03, 0x25, 0x01, 0x00, 0x25, 0x59, 0xbb
2017-12-04 00:06:09.842 Detail, Node006, Queuing (Send) SwitchBinaryCmd_Get (Node=6): 0x01, 0x09, 0x00, 0x13, 0x06, 0x02, 0x25, 0x02, 0x25, 0x5a, 0xb9
2017-12-04 00:06:09.842 Detail, 
2017-12-04 00:06:09.842 Info, Node006, Sending (Send) message (Callback ID=0x59, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=6): 0x01, 0x0a, 0x00, 0x13, 0x06, 0x03, 0x25, 0x01, 0x00, 0x25, 0x59, 0xbb
2017-12-04 00:06:10.349 Warning, WARNING: 500ms passed without reading the rest of the frame...aborting frame read
2017-12-04 00:06:10.350 Warning, WARNING: Out of frame flow! (0x13).  Sending NAK.
2017-12-04 00:06:10.350 Detail, Node006,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-12-04 00:06:10.350 Detail, Node006,   ZW_SEND_DATA delivered to Z-Wave stack
2017-12-04 00:06:10.351 Detail, Node006,   Received: 0x01, 0x07, 0x00, 0x13, 0x59, 0x00, 0x00, 0x06, 0xb4
2017-12-04 00:06:10.351 Detail, Node006,   ZW_SEND_DATA Request with callback ID 0x59 received (expected 0x59)
2017-12-04 00:06:10.351 Info, Node006, Request RTT 510 Average Request RTT 288
2017-12-04 00:06:10.351 Detail,   Expected callbackId was received
2017-12-04 00:06:10.352 Detail,   Expected reply was received
2017-12-04 00:06:10.352 Detail,   Message transaction complete
2017-12-04 00:06:10.352 Detail, 
2017-12-04 00:06:10.352 Detail, Node006, Removing current message
2017-12-04 00:06:10.352 Detail, 
2017-12-04 00:06:10.352 Info, Node006, Sending (Send) message (Callback ID=0x5a, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=6): 0x01, 0x09, 0x00, 0x13, 0x06, 0x02, 0x25, 0x02, 0x25, 0x5a, 0xb9
2017-12-04 00:06:10.359 Detail, Node006,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2017-12-04 00:06:10.359 Detail, Node006,   ZW_SEND_DATA delivered to Z-Wave stack
2017-12-04 00:06:10.415 Detail, Node006,   Received: 0x01, 0x07, 0x00, 0x13, 0x5a, 0x00, 0x00, 0x06, 0xb7
2017-12-04 00:06:10.415 Detail, Node006,   ZW_SEND_DATA Request with callback ID 0x5a received (expected 0x5a)
2017-12-04 00:06:10.415 Info, Node006, Request RTT 62 Average Request RTT 175
2017-12-04 00:06:10.415 Detail,   Expected callbackId was received
2017-12-04 00:06:10.472 Detail, Node006,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x06, 0x03, 0x25, 0x03, 0x00, 0xd1
2017-12-04 00:06:10.472 Detail, 
2017-12-04 00:06:10.509 Info, Node006, Response RTT 157 Average Response RTT 142
2017-12-04 00:06:10.509 Info, Node006, Received SwitchBinary report from node 6: level=Off
2017-12-04 00:06:10.509 Detail, Node006, Refreshed Value: old value=true, new value=false, type=bool
2017-12-04 00:06:10.509 Detail, Node006, Changes to this value are not verified
2017-12-04 00:06:10.510 Detail, Node006,   Expected reply and command class was received
2017-12-04 00:06:10.510 Detail, Node006,   Message transaction complete
2017-12-04 00:06:10.510 Detail, 
2017-12-04 00:06:10.510 Detail, Node006, Removing current message
2017-12-04 00:06:10.510 Detail, Node006, Notification: ValueChanged
2017-12-04 00:06:10.510 Info, Notification: Value Changed Home 0xdd0757f3 Node 6 Genre user Class SWITCH BINARY Instance 1 Index 0 Type bool
7 Likes
14

Thanks a bunch - this is good info. I know that many switches and dimmers from the past few years do this.

It seems the latest switches/dimmers (typically Zwave plus) do now do status updates.

15

Is it possible to assign the neighbors manually?

16

Nope, it is discovered by the zwave protocol.

17

The closest I got to manually assigning neighbors was in the OZWCP you can assign return routes. I don’t think it sticks though as once I shut down the docker for OZWCP and started up HA again, I have one switch that doesn’t have node 1 as its primary neighbor. It’s probably my third most used switch out of 11 and the 6th closest node to the controller. But for that switch, the signal has to pass through 2 walls, a floor with HVAC, electrical, and plumbing in it and a stove (if following line of sight), so it makes sense why it found a better path for communication.

18

What’s interesting is some of my closest nodes are not registering the controller as first neighbor.

Do you know of a tool that will help visualize the mesh/neighbors? Would be cool to see an SVG output or something similar.

19

I’ve never gotten the topology option in OZWCP to work, but yes someone did make a network visualizer for HA. I’ve seen it floating around the forums. Might check the share your projects section.

20

I think you’re right. With the release of the 500 series z wave chips (Z Wave+) most new devices are doing instant status updates.