C-7 Zigbee behavior on 2.3.5.105

[C-7] now causes some Zigbee devices to change the short Network IDs :

This is an excerpt from a log when re-pairing a previously joined device , paired directly to the C-7 hub

child:[Loratap, 488D, type:EMBER_SLEEPY_END_DEVICE]

...........
dev:38042023-03-11 16:50:38.617debugLoratap received device announcement, Device network ID: 488D
dev:38042023-03-11 16:50:38.614debugLoratap catchall descMap: [raw:catchall: 0000 0013 00 00 0040 00 488D 00 00 0000 00 00 158D484275C6EAFE38C1A480, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:488D, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[15, 8D, 48, 42, 75, C6, EA, FE, 38, C1, A4, 80]]

^^^^^15 seconds later ^^^^

dev:38042023-03-11 16:50:23.538debugLoratap received device announcement, Device network ID: 8103
dev:38042023-03-11 16:50:23.534debugLoratap catchall descMap: [raw:catchall: 0000 0013 00 00 0040 00 8103 00 00 0000 00 00 0E03814275C6EAFE38C1A480, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:8103, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[0E, 03, 81, 42, 75, C6, EA, FE, 38, C1, A4, 80]]
.........

2 Likes