Bug #150

Enabling get* commands leads to unwanted commands in tester interface

Added by Han Alink almost 6 years ago. Updated almost 6 years ago.

Status:Closed Start date:10/22/2012
Priority:Low Due date:
Assignee:Stefano Lenzi % Done:

0%

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

Description

Though some "get*" commands now are taken into account, also a number of unwanted "get*" commands pop up in the tester window:
E.g for the OnOff cluster: getActiveSubscriptions, getOnOff, getName ......


Related issues

related to Bug #140: ZigBeeTester doesn't shows command whose name starts with... Closed 10/19/2012

Associated revisions

Revision 565
Added by Stefano Lenzi almost 6 years ago

Trying to show only the Command on the ZigBee Tester ( refs #150 )

Revision 566
Added by Stefano Lenzi almost 6 years ago

Changed again the policy for identifyin command among the methods of a Cluster ( refs #150 )

Revision 570
Added by Stefano Lenzi almost 6 years ago

Added Test Unit for checking the method that are identified as command from the tester
Changed again policy for identifying the command among the methods of a cluster object ( refs #150 )

History

#1 Updated by Stefano Lenzi almost 6 years ago

  • Category set to zigbee.tester
  • Status changed from New to In Progress
  • Assignee set to Stefano Lenzi
  • Priority changed from Normal to Low
  • Target version set to org.aaloa.zb4osgi.zigbee.tester-1.X

We have to change the algorithm for identifying command among the method of the Cluster class

#2 Updated by Stefano Lenzi almost 6 years ago

  • Status changed from In Progress to Feedback

Please give it a try and close the ticket if it works

#3 Updated by Han Alink almost 6 years ago

The unwanted "Get" commands are gone, but also the Identify Query command disappeared!

#4 Updated by Stefano Lenzi almost 6 years ago

I'm afraid that there is no definitive solution for it, because we are using standard Java reflection for identifying the command to be displayed by the Tester, so either we show too many method that are not command or we hide some valuable command.
A solution would be to add a new method ZCLCluster[] getZCLClusters() in the Cluster that will return the "low level" interface where command could be identified by their return type

In the mean while, I have change the policy again, if it satisfies your need please close the ticket

#5 Updated by Stefano Lenzi almost 6 years ago

I hope it is working as expected now, please give it a try and close the ticket in case

#6 Updated by Han Alink almost 6 years ago

  • Status changed from Feedback to Closed

Fixed

Also available in: Atom PDF