Bug #216

Detection of devices when rejoin with a new NWK address but same IEEE address

Added by Han Alink almost 5 years ago. Updated about 4 years ago.

Status:Closed Start date:08/29/2013
Priority:Normal Due date:
Assignee:Stefano Lenzi % Done:

0%

Category:zigbee.basedriver Spent time: -
Target version:org.aaloa.zb4osgi.zigbee.basedriver-0.8.0
Has a patch:No Has license agreement signed:No

Description

If a device leaves the network and is reset, the device will get a new network address after it is powered up again.
ZB4O does not accept the "new" device on the network:

Adding device 10 on node -17638(00:13:7A:00:00:00:28:02) the network
Node ieee collision, stored is 19881(00:13:7A:00:00:00:28:02) and new one is -17638(00:13:7A:00:00:00:28:02)
Failed to add endpoint 10 to the network map for node -17638(00:13:7A:00:00:00:28:02)


Related issues

related to Improvement #257: Implement different behavior of ZBD for duplciated mac New 08/05/2014

Associated revisions

Revision 885
Added by Giancarlo Riolo almost 5 years ago

refs #216 add new property basedriver mac conflict policy. todo : update basedriver tests

Revision 886
Added by Giancarlo Riolo almost 5 years ago

Commented some tests from ZigBeeNetworkTest. They must reflect new device inspection chain introduced in refs #216.

Revision 887
Added by Giancarlo Riolo almost 5 years ago

ZigBee BaseDriver RetryCountTest updated to reflect changes introduced by refs #216

Revision 888
Added by Giancarlo Riolo almost 5 years ago

updated test to reflect changes in refs #216

History

#1 Updated by Stefano Lenzi almost 5 years ago

  • Category set to zigbee.basedriver
  • Status changed from New to In Progress
  • Assignee set to Giancarlo Riolo
  • Target version set to org.aaloa.zb4osgi.zigbee.basedriver-1.X
Yes, you are right, that is the actual behavior of the ZigBee Base Driver. I think that the best way is to add a configuration property for the basedriver it.cnr.isti.zigbee.driver.discovery.duplciatemac which can assume the following values:
  • ignore : the zigbee base driver continue to behave like now
  • update : the zigbee base driver will update the property of the ZigBeeDevice service
  • register : the zigbee base driver will unregister the ZigBeeDevice with the old service and it will register a new one

#2 Updated by Giancarlo Riolo almost 5 years ago

  • Status changed from In Progress to Resolved

#3 Updated by Giancarlo Riolo over 4 years ago

  • Status changed from Resolved to Closed

#4 Updated by Stefano Lenzi about 4 years ago

  • Subject changed from Detection of devices to Detection of devices when rejoin with a new NWK address but same IEEE address
  • Status changed from Closed to In Progress
  • Target version changed from org.aaloa.zb4osgi.zigbee.basedriver-1.X to org.aaloa.zb4osgi.zigbee.basedriver-0.8.0

Updated wikipage that describe the configuration option Configuration_parameters
The close the ticket for the release

#5 Updated by Stefano Lenzi about 4 years ago

  • Assignee changed from Giancarlo Riolo to Stefano Lenzi

r1051 and r1053 are commits related to this issue

#6 Updated by Stefano Lenzi about 4 years ago

  • Status changed from In Progress to Resolved

It should be fixed, we tested it locally and it works. Please close it if it works for you.

#7 Updated by Han Alink about 4 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF