A structure containing general information about the service discovery.
Public Attribute Documentation#
status#
EmberAfServiceDiscoveryStatus EmberAfServiceDiscoveryResult::status
The status indicates both the type of request (broadcast or unicast) and whether a response has been received.
634 of file /Users/vihuszar/Git/EmbeddedSoftware/super/protocol/zigbee/app/framework/include/af-types.hzdoRequestClusterId#
uint16_t EmberAfServiceDiscoveryResult::zdoRequestClusterId
This indicates what ZDO request cluster was associated with the request. It is helpful for a callback that may be used for multiple ZDO request types to determine the type of data returned. This will be based on the ZDO cluster values defined in ember-types.h.
642 of file /Users/vihuszar/Git/EmbeddedSoftware/super/protocol/zigbee/app/framework/include/af-types.hmatchAddress#
EmberNodeId EmberAfServiceDiscoveryResult::matchAddress
This is the address of the device that matched the request, which may be different than the device that actually is responding. This occurs when parents respond on behalf of their children.
649 of file /Users/vihuszar/Git/EmbeddedSoftware/super/protocol/zigbee/app/framework/include/af-types.hresponseData#
const void* EmberAfServiceDiscoveryResult::responseData
Only if the status code indicates a response will this data be non-NULL. When there is data, the type is according to the ZDO cluster ID sent out. For NETWORK_ADDRESS_REQUEST or IEEE_ADDRESS_REQUEST, the long ID will be contained in the responseData, so it will be a value of type ::EmberEUI64. The short ID will be in the matchAddress parameter field. For the MATCH_DESCRIPTORS_REQUEST the responseData will point to an EmberAfEndpointList structure.
660 of file /Users/vihuszar/Git/EmbeddedSoftware/super/protocol/zigbee/app/framework/include/af-types.h