Bug #127

IdentifyQuery Command

Added by Han Alink over 5 years ago. Updated about 5 years ago.

Status:Closed Start date:10/17/2012
Priority:High Due date:
Assignee:Stefano Lenzi % Done:

100%

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

Description

When an end device is not in identify mode, it will not respond to an IdentifyQuery command. However, the ZB4O software expects an answer, it times out and an exception is thrown:
it.cnr.isti.zigbee.ha.driver.core.ZigBeeHAException: it.cnr.isti.zigbee.zcl.library.api.core.ZigBeeClusterException: it.cnr.isti.zigbee.api.ZigBeeBasedriverException: Timeout expired before recieving an answer

Associated revisions

Revision 619
Added by Stefano Lenzi about 5 years ago

Added a TimeoutException and using it for better output message ( fixes #127 )

History

#1 Updated by Stefano Lenzi over 5 years ago

  • Category changed from zigbee.basedriver to zigbee.zcl.library
  • Status changed from New to In Progress
  • Priority changed from Normal to High
  • Target version set to org.aaloa.zb4osgi.zigbee.zcl.library-1.X
The behavior described by you is correct (see Page 121 of ZigBee Cluster Library document version 075123r02ZB), but I don't know how to fix the issue at the moment.
In fact, I don't have a clear idea on how to distinguish bettween the following case
  1. the IdentifyQuery command get lost on the ZigBeeNetwork and it never reaches the target device
  2. the IdentifyQueryResponse command get lost on the ZigBeeNetwork and it never reaches the device whose sent the IdentifyQuery command
  3. the device receiving the IdentifyQuery command is not identifying itself thus it doesn't generate a IdentifyQueryResponse command

#2 Updated by Stefano Lenzi about 5 years ago

  • Status changed from In Progress to Feedback

Dear Han,
how do you think we should handle the three scenario that I proposed? I believe that the current implementation is the best option available. What do you think?

#3 Updated by Han Alink about 5 years ago

The issue indeed can't be fixed; it's "zigbee behavior".
But isn't it possible to just show "Command timed out" in the result pane (instead of throwing an exeption)?

#4 Updated by Stefano Lenzi about 5 years ago

  • Status changed from Feedback to Closed
  • % Done changed from 0 to 100

Applied in changeset r619.

#5 Updated by Stefano Lenzi about 5 years ago

  • Status changed from Closed to Resolved

Please close if you agree with the solution

#6 Updated by Han Alink about 5 years ago

  • Status changed from Resolved to Closed

Fine; I close the ticket

Also available in: Atom PDF