Issue adding node


#1

Hi there, I am facing an issue that happens when adding a node to the network, basically the process goes half way through, assigning node id, but eventually silently fails. here is the logs from zip:

Sep 25 14:58:12 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m1539086 DHCP Timeout
Sep 25 14:58:12 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m1539097 Sending DISCOVER
Sep 25 14:58:12 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m1539099 All nodes have an IPv4 address
Sep 25 14:58:12 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m1539393 Name probing done and no duplicates found
Sep 25 14:58:12 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m1539403 state 9 node =30
Sep 25 14:58:12 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m1539406 state 10 node =30
Sep 25 14:58:12 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m1539407 Probe of node 30 is done
Sep 25 14:58:12 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m1539409 Info len 17
Sep 25 14:58:12 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m1539416 Waiting for DHCP
Sep 25 14:58:12 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m1539428 All nodes have been probed
Sep 25 14:58:17 multi-gateway user.notice zipgateway: ^[[0m^[[31;1m1544427 DHCP timeout....^[[0m^[[34;1m1544429 Sending encrypted data
Sep 25 14:58:17 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m1544431 Send to lan
Sep 25 14:58:18 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m1544643 ND for ipv6 address
Sep 25 14:58:18 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m1544645 Sending encrypted data
Sep 25 14:58:18 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m1544647 Send to lan
Sep 25 14:58:18 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m1545284 Sending encrypted data
Sep 25 14:58:18 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m1545288 Send to lan
Sep 25 14:58:18 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m1545304 NetworkManagementCommandHandler
Sep 25 14:58:18 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m1545343 Age is seconds 6
Sep 25 14:58:18 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m1545392 Sending encrypted data
Sep 25 14:58:18 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m1545394 Send to lan
Sep 25 14:58:18 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m1545496 Sending encrypted data
Sep 25 14:58:18 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m1545500 Send to lan
Sep 25 14:58:18 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m1545516 NetworkManagementCommandHandler
Sep 25 14:58:19 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m1545912 Sending encrypted data
Sep 25 14:58:19 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m1545922 Send to lan
Sep 25 14:58:28 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m1555109 DHCP Timeout
Sep 25 14:58:28 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m1555110 Sending DISCOVER
Sep 25 14:58:28 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m1555124 All nodes have an IPv4 address
Sep 25 14:58:30 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m1557126 DHCP Timeout
Sep 25 14:58:30 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m1557127 Sending DISCOVER
Sep 25 14:58:30 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m1557129 All nodes have an IPv4 address
Sep 25 14:58:34 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m1561132 DHCP Timeout
Sep 25 14:58:34 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m1561133 Sending DISCOVER
Sep 25 14:58:34 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m1561135 All nodes have an IPv4 address
Sep 25 14:58:42 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m1569140 DHCP Timeout
Sep 25 14:58:42 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m1569143 Sending DISCOVER
Sep 25 14:58:42 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m1569145 All nodes have an IPv4 address

I am guessing its due to the reason it can not get an ip address from a dhcp server, but does the ZIp actually need a dhcp server? can it run without one, in its own network let say and manage just ipv6 addresses?

thanks in advance for the help


#2

The zipgateway doesn’t need a DHCP server, unless you’re interested in working with IPv4 addresses. It will, regardless of a node having a working IPv6 address, continue to periodically send DHCP DISCOVER frames looking for a DHCP server (more so just after having included a new node). You’ll see them sent out, and then timing out, in the log - these printouts should be interpreted as a warnings, letting you know zipgateway can’t find a DHCP server, and can safely be ignored if you’re working only with IPv6.

It’s not very clear to me from the output log you’ve posted, but it seems that the inclusion process completed and zipgateway was able to probe the new device (I’m assuming the new device was assigned NodeID 30). When you say

do you mean that you’re not getting back a COMMAND_NODE_ADD_STATUS command with an outcome on the operation?

Another likely relevant question: are you trying to include a battery-powered device?


#3

Thanks for the answer Hanskroner.

Okay so that is exactly what is happening, I set the zip gateway to pairing mode, using zware, which will return ZW_ERR_NONE and it is ready to pair, then I press pairing button in an sleeping devices (danfoss thermostat setpoint, certified) then my application will print the following:

 adding node error status: ZW_ERR_NONE
 print_txt: ... SSL_connect would read block
 print_txt: ... curr_tmout = 1
 print_txt: ... dtls_select returns 2
 print_txt: ... SSL_connect returns 1, error = 0
 print_txt: 08:04:06 -- read ready fd:41 IP:
 print_txt: FD 00 AA AA 00 00 00 00 00 00
 print_txt: 00 00 00 00 00 01
 print_txt: 08:04:18 -- read ready fd:41 IP:
 print_txt: FD 00 AA AA 00 00 00 00 00 00
 print_txt: 00 00 00 00 00 01
 print_txt: add_node_nw_cb: status:6 (OK)
 print_txt: new node id:30
 print_txt: listening=0, optional functions=1, sensor=0
 print_txt: Device type: basic=04h, generic=08h, specific=04
 print_txt: unsecure command classes:
 print_txt: 80, 46, 81, 72, 8F, 75, 31, 43, 86, 84,
 print_txt: 08:04:19 -- read ready fd:41 IP:
 print_txt: FD 00 AA AA 00 00 00 00 00 00
 print_txt: 00 00 00 00 00 01
 print_txt: zwnet_get_ip_addr_cb:
 print_txt: Home id:ED3BA014,  node id:30, local=1, ip:
 node event has happened ZWNET_NODE_ADDED
 node added, nodeId: 30
 print_txt: FD 00 BB BB 00 00 00 00 00 00
 print_txt: 00 00 00 00 00 1E
 Add node status: OP_PROTOCOL_DONE
 Add node status: OP_PROTOCOL_INFO
 print_txt: 08:04:19 -- read ready fd:41 IP:
 print_txt: FD 00 AA AA 00 00 00 00 00 00
 print_txt: 00 00 00 00 00 01
 print_txt: 08:04:19 -- read ready fd:41 IP:
 print_txt: FD 00 AA AA 00 00 00 00 00 00
 print_txt: 00 00 00 00 00 01
 print_txt: zwnet_ni_chd_get_cb for node id:30
 print_txt: listening=0, optional functions=1, sensor=0
 print_txt: status=0, age=16384 minutes old
 print_txt: Device type: basic=04h, generic=08h, specific=04
 print_txt: unsecure command classes:
 print_txt: 80, 46, 81, 72, 8F, 75, 31, 43, 86, 84,
 print_txt: 08:04:19 -- read ready fd:41 IP:
 print_txt: FD 00 AA AA 00 00 00 00 00 00
 print_txt: 00 00 00 00 00 01
 print_txt: 08:04:20 -- read ready fd:41 IP:
 print_txt: FD 00 AA AA 00 00 00 00 00 00
 print_txt: 00 00 00 00 00 01
 print_txt: SSL connect failed. Err: -1
 print_txt: SSL connect failed. Err: -1
 print_txt: Send data completed with error:-108, node id:30
 print_txt: SSL connect failed. Err: -1
 print_txt: SSL connect failed. Err: -1
 print_txt: Send data completed with error:-108, node id:30
 print_txt: SSL connect failed. Err: -1
 print_txt: SSL connect failed. Err: -1
 print_txt: Send data completed with error:-108, node id:30
 print_txt: SSL connect failed. Err: -1
 print_txt: SSL connect failed. Err: -1
 print_txt: Send data completed with error:-108, node id:30
 Get node info  completed

while zip gateway prints the following:

Sep 26 08:04:13 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m60568297 Name probing done and no duplicates found
Sep 26 08:04:13 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60568306 EP probe nd=30 ep =0 state=5
Sep 26 08:04:13 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60568308 state 1 node =30
Sep 26 08:04:13 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60568309 state 2 node =30
Sep 26 08:04:13 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m60568315 Sending with scheme 255
Sep 26 08:04:13 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60568401 state 3 node =30
Sep 26 08:04:13 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60568411 state 4 node =30
Sep 26 08:04:13 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60568412 state 7 node =30
Sep 26 08:04:13 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60568413 state 8 node =30
Sep 26 08:04:13 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m60569157 Name probing done and no duplicates found
Sep 26 08:04:13 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60569174 state 9 node =30
Sep 26 08:04:13 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60569175 state 10 node =30
Sep 26 08:04:13 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m60569177 Probe of node 30 is done
Sep 26 08:04:13 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m60569178 Info len 17
Sep 26 08:04:13 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60569191 Waiting for DHCP
Sep 26 08:04:13 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m60569201 All nodes have been probed
Sep 26 08:04:15 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60571024 Send to lan
Sep 26 08:04:17 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m60573215 DHCP Timeout
Sep 26 08:04:17 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60573216 Sending DISCOVER
Sep 26 08:04:17 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m60573218 All nodes have an IPv4 address
Sep 26 08:04:18 multi-gateway user.notice zipgateway: ^[[0m^[[31;1m60574201 DHCP timeout....^[[0m^[[34;1m60574203 Sending encrypted data
Sep 26 08:04:18 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60574205 Send to lan
Sep 26 08:04:19 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60574338 ND for ipv6 address
Sep 26 08:04:19 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60574352 Sending encrypted data
Sep 26 08:04:19 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60574367 Send to lan
Sep 26 08:04:19 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60574951 Sending encrypted data
Sep 26 08:04:19 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60574955 Send to lan
Sep 26 08:04:19 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60574973 NetworkManagementCommandHandler
Sep 26 08:04:19 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60574995 Age is seconds 5
Sep 26 08:04:19 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60575031 Sending encrypted data
Sep 26 08:04:19 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60575041 Send to lan
Sep 26 08:04:19 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60575130 Sending encrypted data
Sep 26 08:04:19 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60575136 Send to lan
Sep 26 08:04:19 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60575152 NetworkManagementCommandHandler
Sep 26 08:04:20 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60575551 Sending encrypted data
Sep 26 08:04:20 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60575553 Send to lan
Sep 26 08:04:20 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60576031 Send to lan
Sep 26 08:04:27 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m60582491 ApplicationControllerUpdate: status=0x84 node=30 NIF len=17
Sep 26 08:04:33 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m60589247 DHCP Timeout
Sep 26 08:04:33 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60589248 Sending DISCOVER
Sep 26 08:04:33 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m60589249 All nodes have an IPv4 address
Sep 26 08:04:35 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m60591250 DHCP Timeout
Sep 26 08:04:35 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60591251 Sending DISCOVER
Sep 26 08:04:35 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m60591253 All nodes have an IPv4 address
Sep 26 08:04:39 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m60595257 DHCP Timeout
Sep 26 08:04:39 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60595258 Sending DISCOVER
Sep 26 08:04:39 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m60595259 All nodes have an IPv4 address
Sep 26 08:04:47 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m60603261 DHCP Timeout
Sep 26 08:04:47 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60603263 Sending DISCOVER
Sep 26 08:04:47 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m60603264 All nodes have an IPv4 address
Sep 26 08:05:03 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m60619277 DHCP Timeout
Sep 26 08:05:03 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60619279 Sending DISCOVER
Sep 26 08:05:04 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m60619291 All nodes have an IPv4 address
Sep 26 08:05:06 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m60621292 DHCP Timeout
Sep 26 08:05:06 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60621293 Sending DISCOVER
Sep 26 08:05:06 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m60621295 All nodes have an IPv4 address
Sep 26 08:05:09 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60624584 Sending encrypted data
Sep 26 08:05:09 multi-gateway user.notice zipgateway: ^[[0mtcpip_ipv6_output: nbr cache entry stale moving to delay
Sep 26 08:05:09 multi-gateway user.notice zipgateway: ^[[34;1m60624590 Send to lan
Sep 26 08:05:10 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m60625297 DHCP Timeout
Sep 26 08:05:10 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60625298 Sending DISCOVER
Sep 26 08:05:10 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m60625302 All nodes have an IPv4 address
Sep 26 08:05:13 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60629024 Send to lan
Sep 26 08:05:14 multi-gateway user.notice zipgateway: ^[[0mtcpip_ipv6_output: nbr cache entry stale moving to delay
Sep 26 08:05:14 multi-gateway user.notice zipgateway: ^[[34;1m60629593 Send to lan
Sep 26 08:05:18 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m60633308 DHCP Timeout
Sep 26 08:05:18 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60633309 Sending DISCOVER
Sep 26 08:05:18 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m60633318 All nodes have an IPv4 address
Sep 26 08:05:19 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60635024 Send to lan
Sep 26 08:05:24 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60640031 Send to lan
Sep 26 08:05:34 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m60649323 DHCP Timeout
Sep 26 08:05:34 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60649324 Sending DISCOVER
Sep 26 08:05:34 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m60649326 All nodes have an IPv4 address
Sep 26 08:05:36 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m60651327 DHCP Timeout
Sep 26 08:05:36 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60651329 Sending DISCOVER
Sep 26 08:05:36 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m60651332 All nodes have an IPv4 address
Sep 26 08:05:40 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m60655336 DHCP Timeout
Sep 26 08:05:40 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60655337 Sending DISCOVER
Sep 26 08:05:40 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m60655339 All nodes have an IPv4 address
Sep 26 08:05:48 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m60663344 DHCP Timeout
Sep 26 08:05:48 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60663345 Sending DISCOVER
Sep 26 08:05:48 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m60663346 All nodes have an IPv4 address
Sep 26 08:05:59 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60674826 Sending encrypted data
Sep 26 08:05:59 multi-gateway user.notice zipgateway: ^[[0mtcpip_ipv6_output: nbr cache entry stale moving to delay
Sep 26 08:05:59 multi-gateway user.notice zipgateway: ^[[34;1m60674833 Send to lan
Sep 26 08:06:03 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60679023 Send to lan
Sep 26 08:06:04 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m60679360 DHCP Timeout
Sep 26 08:06:04 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60679363 Sending DISCOVER
Sep 26 08:06:04 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m60679372 All nodes have an IPv4 address
Sep 26 08:06:04 multi-gateway user.notice zipgateway: ^[[0mtcpip_ipv6_output: nbr cache entry stale moving to delay
Sep 26 08:06:04 multi-gateway user.notice zipgateway: ^[[34;1m60679833 Send to lan
Sep 26 08:06:06 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m60681372 DHCP Timeout
Sep 26 08:06:06 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60681374 Sending DISCOVER
Sep 26 08:06:06 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m60681375 All nodes have an IPv4 address
Sep 26 08:06:08 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60684024 Send to lan
Sep 26 08:06:10 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m60685377 DHCP Timeout
Sep 26 08:06:10 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60685379 Sending DISCOVER
Sep 26 08:06:10 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m60685381 All nodes have an IPv4 address
Sep 26 08:06:13 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60689031 Send to lan
Sep 26 08:06:18 multi-gateway user.notice zipgateway: ^[[0m^[[33;1m60693385 DHCP Timeout
Sep 26 08:06:18 multi-gateway user.notice zipgateway: ^[[0m^[[34;1m60693387 Sending DISCOVER
Sep 26 08:06:18 multi-gateway user.notice zipgateway: ^[[0m^[[32;1m60693388 All nodes have an IPv4 address

the sniffers gets these messages as well:

13	26.09.2017	10:03:53.191	9.6Kbit/s	78	1	2015	001	255	ED 3B A0 14	Broadcast	Transfer Presentation	ED 3B A0 14 01 01 06 0D FF 01 08 01 61
14	26.09.2017	10:03:55.190	9.6Kbit/s	78	1	2000	001	255	ED 3B A0 14	Broadcast	Transfer Presentation	ED 3B A0 14 01 01 07 0D FF 01 08 01 60
15	26.09.2017	10:03:56.709	9.6Kbit/s	64	1	1493	030	255	ED 3B A0 14	Broadcast	Node Info	ED 3B A0 14 1E 01 01 1F FF 01 01 53 9C 00 08 04 80 46 81 72 8F 75 31 43 86 84 EF 46 81 8F B8
16	26.09.2017	10:03:57.000	40Kbit/s	66	1	324	001	030	ED 3B A0 14	Singlecast	Request Node Info	ED 3B A0 14 01 41 07 0C 1E 01 02 CB
17	26.09.2017	10:03:57.006	40Kbit/s	66	1	7	030	001	ED 3B A0 14	Ack		ED 3B A0 14 1E 03 07 0A 01 8C
18	26.09.2017	10:03:57.017	40Kbit/s	68	1	5	030	001	ED 3B A0 14	Singlecast	Node Info	ED 3B A0 14 1E 41 01 1F 01 01 01 53 9C 00 08 04 80 46 81 72 8F 75 31 43 86 84 EF 46 81 8F 06
19	26.09.2017	10:03:57.056	40Kbit/s	82	1	14	001	030	ED 3B A0 14	Ack		ED 3B A0 14 01 03 01 0A 1E 8A
20	26.09.2017	10:03:57.689	40Kbit/s	82	1	662	001	030	ED 3B A0 14	Singlecast	Manufacturer Specific Get	ED 3B A0 14 01 41 08 0C 1E 72 04 B1
21	26.09.2017	10:03:57.712	40Kbit/s	69	1	7	030	001	ED 3B A0 14	Ack		ED 3B A0 14 1E 03 08 0A 01 83
22	26.09.2017	10:03:57.712	40Kbit/s	69	1	5	030	001	ED 3B A0 14	Singlecast	Manufacturer Specific Report	ED 3B A0 14 1E 41 02 12 01 72 05 00 02 01 15 A0 10 02
23	26.09.2017	10:03:57.712	40Kbit/s	82	1	11	001	030	ED 3B A0 14	Ack		ED 3B A0 14 01 03 02 0A 1E 89
24	26.09.2017	10:04:04.571	40Kbit/s	82	1	6854	001	030	ED 3B A0 14	Singlecast	Assign Return Route	ED 3B A0 14 01 41 09 0F 1E 01 0C 01 00 10 D9
25	26.09.2017	10:04:04.571	40Kbit/s	67	1	7	030	001	ED 3B A0 14	Ack		ED 3B A0 14 1E 03 09 0A 01 82
26	26.09.2017	10:04:04.668	40Kbit/s	82	1	95	001	030	ED 3B A0 14	Singlecast	Assign Return Route	ED 3B A0 14 01 41 0A 10 1E 01 0C 01 11 09 10 DD
27	26.09.2017	10:04:04.674	40Kbit/s	67	1	7	030	001	ED 3B A0 14	Ack		ED 3B A0 14 1E 03 0A 0A 01 81
28	26.09.2017	10:04:04.856	40Kbit/s	82	1	181	001	030	ED 3B A0 14	Singlecast	Assign Return Route	ED 3B A0 14 01 41 0B 0F 1E 01 0C 00 20 08 E2
29	26.09.2017	10:04:04.862	40Kbit/s	68	1	7	030	001	ED 3B A0 14	Ack		ED 3B A0 14 1E 03 0B 0A 01 80
30	26.09.2017	10:04:04.890	40Kbit/s	82	1	12	001	030	ED 3B A0 14	Singlecast	Assign Return Route	ED 3B A0 14 01 41 0C 0F 1E 01 0C 00 30 08 F5
31	26.09.2017	10:04:04.890	40Kbit/s	68	1	7	030	001	ED 3B A0 14	Ack		ED 3B A0 14 1E 03 0C 0A 01 87
32	26.09.2017	10:04:11.825	9.6Kbit/s	64	1	6919	030	255	ED 3B A0 14	Broadcast	Node Info	ED 3B A0 14 1E 01 01 1F FF 01 01 53 9C 00 08 04 80 46 81 72 8F 75 31 43 86 84 EF 46 81 8F B8

but at the end although it seems like the device is paired, the device continue to be on unpaired mode (if this particular device is unpaired, by plasseing the paring button it will flash its light fast) so that confirms the node has not been paired. (as expected wi wont receives commands and/or send sensor data)


#4

It seems like the Z-Wave inclusion process completes successfully. The Danfoss device is now actually part of the Z-Wave network, and zipgateway has been able to probe it, gathering its NIF and some information from the Manufacturer Specific Command Class. In short, from a Z-Wave RF perspective the Inclusion process completed successfully.

With that process completed, Z-Ware is now attempting to message the newly included node to gather additional information. It looks like it can’t establish a connection:

Since you’re using IPv6 exclusively, my best guest is that your routing table doesn’t hold a route to the PAN subnet. I would also guess that you can’t control devices from the Z-Ware Web UI. zipgateway uses two different subnets for the IPv6 addresses it assigns. The LAN subnet is for any devices on the LAN that zipgateway assigns and address to - let’s call that fd00:dead::/64. The PAN subnet is for Z-Wave devices that zipgateway is bridging for - let’s call that fd00:beef::/64. My guess is that Z-Ware is on the LAN side, and there are no routes to the PAN side. You could verify this by obtaining the IPv6 address for the node that was included (if you don’t know the device’s address, use the Z/IP ND Command Class - this Command Class should not be encapsulated in a Z/IP Packet and is addressed directly to zipgateway, on its LAN address, so you’ll have no problems sending it) and trying to ping it.

If you’re running all of this on the Raspberry Pi image that Sigma Designs provides you can easily add a routing entry manually, which should solve your issue. Look in your zipgateway.cfg for the following entries (I’m pasting the entries and values from mine, for reference):

ZipPanIp6 = fd00:beef::1
ZipLanIp6 = fd00:dead::3

The subnets for the PAN and LAN subnets are the first two blocks of those addresses. On your Raspberry Pi, you can add a route to the PAN subnet, going through zipgateway like this:

ip -6 route add fd00:beef::/64 via fd00:dead::3

Replace with values from your zipgateway.cfg and you should then be able to communicate with devices that have PAN addresses.


#5

here is my config file, excluding the PSK:

ZipSerialAPIPortName = /dev/ttyAPP4
ZipPanIp6 = fd00:bbbb::1
ZipLanIp6 = fd00:baaa::1
ZipIp4Disable = 1

also the ip route table looks like following:

fd00:aaaa::/64 dev br0  metric 256  expires 7188sec
fd00:baaa::/64 dev tap0  metric 256  expires 7040sec
fd00:bbbb::/64 via fd00:aaaa::1 dev eth0  metric 1024
fe80::/64 dev eth0  metric 256
fe80::/64 dev br0  metric 256
fe80::/64 dev tap0  metric 256
ff00::/8 dev eth0  metric 256
ff00::/8 dev br0  metric 256
ff00::/8 dev tap0  metric 256

which seems to be having the routing from my PAN network to my LAN network. here is the tcpdump log on fail pairing process:

08:59:59.207763 IP6 (flowlabel 0xae452, hlim 64, next-header UDP (17) payload length: 85) fd00:baaa::d008:5ff:fe8a:ea6f.34333 > fd00:baaa::1.41230: [udp sum ok] UDP, length 77
08:59:59.235304 IP6 (hlim 64, next-header UDP (17) payload length: 69) fd00:baaa::1.41230 > fd00:baaa::d008:5ff:fe8a:ea6f.34333: [udp sum ok] UDP, length 61



09:00:03.295256 IP6 (hlim 64, next-header UDP (17) payload length: 76) fe80::21e:32ff:fe12:3.5353 > ff02::fb.5353: [udp sum ok] 0 ANY (Class 0) (QM)? Thermostat [381fc2da1100]._z-wave._udp.local. (68)
09:00:03.547249 IP6 (hlim 64, next-header UDP (17) payload length: 76) fe80::21e:32ff:fe12:3.5353 > ff02::fb.5353: [udp sum ok] 0 ANY (Class 0) (QM)? Thermostat [381fc2da1100]._z-wave._udp.local. (68)
09:00:03.798972 IP6 (hlim 64, next-header UDP (17) payload length: 76) fe80::21e:32ff:fe12:3.5353 > ff02::fb.5353: [udp sum ok] 0 ANY (Class 0) (QM)? Thermostat [381fc2da1100]._z-wave._udp.local. (68)
09:00:04.090473 IP6 (hlim 64, next-header UDP (17) payload length: 50) fe80::21e:32ff:fe12:3.5353 > ff02::fb.5353: [udp sum ok] 0 ANY (QM)? zw381FC2DA11.local. (42)
09:00:04.208349 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 32) fe80::d008:5ff:fe8a:ea6f > fd00:baaa::1: [icmp6 sum ok] ICMP6, neighbor solicitation, length 32, who has fd00:baaa::1
	  source link-address option (1), length 8 (1): d2:08:05:8a:ea:6f
	    0x0000:  d208 058a ea6f
09:00:04.218863 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 32) fd00:baaa::1 > fe80::d008:5ff:fe8a:ea6f: [icmp6 sum ok] ICMP6, neighbor advertisement, length 32, tgt is fd00:baaa::1, Flags [router, solicited, override]
	  destination link-address option (2), length 8 (1): 00:1e:32:12:00:03
	    0x0000:  001e 3212 0003
09:00:04.341652 IP6 (hlim 64, next-header UDP (17) payload length: 50) fe80::21e:32ff:fe12:3.5353 > ff02::fb.5353: [udp sum ok] 0 ANY (QM)? zw381FC2DA11.local. (42)
09:00:04.593074 IP6 (hlim 64, next-header UDP (17) payload length: 50) fe80::21e:32ff:fe12:3.5353 > ff02::fb.5353: [udp sum ok] 0 ANY (QM)? zw381FC2DA11.local. (42)
09:00:04.642240 IP6 (hlim 64, next-header UDP (17) payload length: 101) fd00:baaa::1.41230 > fd00:baaa::d008:5ff:fe8a:ea6f.34333: [udp sum ok] UDP, length 93
09:00:04.663673 IP6 (hlim 64, next-header UDP (17) payload length: 199) fe80::21e:32ff:fe12:3.5353 > ff02::fb.5353: [udp sum ok] 0*- [0q] 3/0/0 _z-wave._udp.local. PTR Thermostat [381fc2da1100]._z-wave._udp.local., Thermostat [381fc2da1100]._z-wave._udp.local. (Cache flush) TXT "info=^H^DM-^@FM-^ArM-^Ou1^@CM-^FM-^DM-oFM-^AM-^Oh" "epid=^@" "mode=^@^A" "productID=^B^@^U^A^PM- " "txtvers=1" "icon=^@^@^@^@", Thermostat [381fc2da1100]._z-wave._udp.local. (Cache flush) SRV zw381FC2DA11.local.:4123 0 0 (191)
09:00:04.755647 IP6 (flowlabel 0xae452, hlim 64, next-header UDP (17) payload length: 69) fd00:baaa::d008:5ff:fe8a:ea6f.34333 > fd00:baaa::1.41230: [udp sum ok] UDP, length 61
09:00:04.800034 IP6 (hlim 64, next-header UDP (17) payload length: 85) fd00:baaa::1.41230 > fd00:baaa::d008:5ff:fe8a:ea6f.34333: [udp sum ok] UDP, length 77
09:00:05.390605 IP6 (flowlabel 0xae452, hlim 64, next-header UDP (17) payload length: 85) fd00:baaa::d008:5ff:fe8a:ea6f.34333 > fd00:baaa::1.41230: [udp sum ok] UDP, length 77
09:00:05.417565 IP6 (hlim 64, next-header UDP (17) payload length: 69) fd00:baaa::1.41230 > fd00:baaa::d008:5ff:fe8a:ea6f.34333: [udp sum ok] UDP, length 61
09:00:05.492027 IP6 (hlim 64, next-header UDP (17) payload length: 101) fd00:baaa::1.41230 > fd00:baaa::d008:5ff:fe8a:ea6f.34333: [udp sum ok] UDP, length 93
09:00:05.642673 IP6 (flowlabel 0xae452, hlim 64, next-header UDP (17) payload length: 85) fd00:baaa::d008:5ff:fe8a:ea6f.34333 > fd00:baaa::1.41230: [udp sum ok] UDP, length 77
09:00:05.656509 IP6 (hlim 64, next-header UDP (17) payload length: 69) fd00:baaa::1.41230 > fd00:baaa::d008:5ff:fe8a:ea6f.34333: [udp sum ok] UDP, length 61
09:00:05.881605 IP6 (hlim 64, next-header UDP (17) payload length: 85) fd00:baaa::1.41230 > fd00:baaa::d008:5ff:fe8a:ea6f.34333: [udp sum ok] UDP, length 77
09:00:08.703642 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 32) fd00:baaa::1 > fd00:baaa::d008:5ff:fe8a:ea6f: [icmp6 sum ok] ICMP6, neighbor solicitation, length 32, who has fd00:baaa::d008:5ff:fe8a:ea6f
	  source link-address option (1), length 8 (1): 00:1e:32:12:00:03
	    0x0000:  001e 3212 0003
09:00:08.704228 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 24) fd00:baaa::d008:5ff:fe8a:ea6f > fd00:baaa::1: [icmp6 sum ok] ICMP6, neighbor advertisement, length 24, tgt is fd00:baaa::d008:5ff:fe8a:ea6f, Flags [solicited]

zware having the ip of “fd00:baaa::d008:5ff:fe8a:ea6f”, there is another strange thing I see here which is tcp dump reports the port of the zware gateway as 34333 which in fact my application reports as 52253:

unsolicit server has set on fd00:baaa::d008:5ff:fe8a:ea6f : 52253

and that is coming from the callback function of zwrep_gw_unsolicit_cb so zip gateway reports it to my after I set it using zwnet_listen_port_get and zwif_gw_unsolicit_set, do you think it has anything to do with that?


#6

just after I poster I noticed I have different routing ZipLanIp6 = fd00:aaaa::1 rather than ZipLanIp6 = fd00:baaa::1 you were right adding the route solved the issue, thanks a lot for all the help :slight_smile:


#7

Your routes seem to be correctly setup and Z-Ware is able to communicate with the device - for a while. The logs you attached earlier show the device has been included successfully (and is being queried for Manufacturer-specfic data, and gets some return routes assigned).

The only other thing I can think of here, is that the battery device is falling asleep in the middle of Z-Ware querying it for information. Z-Ware will not consider the device as “included” until is has managed to extract some basic information from it - regardless of whether the device is included in the Z-Wave network. Try waking the device up manually, and see if the Wake-Up Notification causes Z-Ware to continue interrogating the device.

You’re also likely get better assistance from the Z-Wave Support team (you have a Zniffer, so you probably have a Dev. Kit agreement with Sigma Designs) than you’ll get here on the forums, I would suggest you reach to to them.