Bug #231

Detection of devices

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

Status:In Progress Start date:12/13/2013
Priority:Normal Due date:
Assignee:Giancarlo Riolo % Done:


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


ZB4O registers an endpoint (default 2) on the dongle with all the clusters it finds on devices in the network.
When ZB4O is stopped completely and then restarted (no power down, flush is FALSE), the endpoint still exists at the dongle and a "non existing device" is detected/displayed in the tester interface. A new endpoint is created (3), which also will be displayed when this cycle is repeated etc etc ...
See attachement ( the OnOffSwitch is the newly created device by ZB4O).
Note: Sandbox giancarlo.riolo revision 900, but also valid for the latest trunk release.

tester.jpg (63.3 kB) Han Alink, 12/13/2013 12:27 pm

Related issues

related to Bug #232: Endpoint registration on the dongle In Progress 12/17/2013
blocked by Improvement #233: Add some kind of persistance to ZigBee Base Driver New 12/18/2013


#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-0.7.0

Yes it is a known behavior, it is an issue related to no persistance stored at ZigBee Base Driver level which should be provided and it also need for some Use Case.

Giancarlo and me are considering the best option for provide this persistance level so that this issue and other things is going to be fixed!

#2 Updated by Stefano Lenzi over 4 years ago

  • Target version changed from org.aaloa.zb4osgi.zigbee.basedriver-0.7.0 to org.aaloa.zb4osgi.zigbee.basedriver-1.X

Moved for next release

Also available in: Atom PDF