I might be way off base here but I don't think we're treating EmberGpAddress correctly unless there's some kind of fancy deserialization routine that consumes application ID. For reference, the current definition looks like this:
class EmberGpAddress(EzspStruct):
# A GP address structure.
# The GPD's EUI64.
gpdIeeeAddress: named.EmberEUI64
# The GPD's source ID.
sourceId: basic.uint32_t
# The GPD Application ID.
applicationId: basic.uint8_t
# The GPD endpoint.
endpoint: basic.uint8_t
But the spec looks like there's a generic uint64_t that could contain either an IEEE address or a short 32-bit GDP ID, but not both:
Please let me know if I'm off base here, it's totally possible I'm wicked wrong.
I might be way off base here but I don't think we're treating EmberGpAddress correctly unless there's some kind of fancy deserialization routine that consumes application ID. For reference, the current definition looks like this:
But the spec looks like there's a generic uint64_t that could contain either an IEEE address or a short 32-bit GDP ID, but not both:
Please let me know if I'm off base here, it's totally possible I'm wicked wrong.