Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

APS data confirm fail ; what are status codes & pending ? #47

Closed
nouknouk opened this issue Jul 11, 2018 · 7 comments

Comments

@nouknouk
Copy link

commented Jul 11, 2018

I recently faced 'APS data confirm fail' responses ; context was just after having sent two "attribute request" in a row.

Unescaped & parsed data is:

  • length = 00 0e
  • status = e9
  • endpointSource = 01
  • endpoint = 03
  • addressmode = 02
  • address = 6e 25
  • seq number = 01
  • ??? = 04 00 00 00 03 9c 4b

Here are my questions:

  1. what's the meaning of the status "e9" ; is there a place where we can get the full list of statuses ?

  2. why do I get 7 more bytes of data after the seq number field ?

Thanks in advance.

@ISO-B

This comment has been minimized.

Copy link
Collaborator

commented Mar 4, 2019

Do you still get these?

@pipiche38

This comment has been minimized.

Copy link

commented Mar 4, 2019

@ISO-B , For me there is a decoding issue from @nouknouk .
As from the doc, the address is always coded by the zigate as an IEEE despite the fact that the mode is specifying 0x02 (short address)

See #161

ISO-B added a commit to ISO-B/ZiGate-firmware that referenced this issue Mar 6, 2019

Changed 8702 to respect address mode. fairecasoimeme#161 fairecasoime…
…me#47

Previously destination address parameter was always formated to uint64
even if it was short address or group. Now it respects address mode
same way as other event responses.

fairecasoimeme added a commit that referenced this issue Mar 7, 2019

@ISO-B

This comment has been minimized.

Copy link
Collaborator

commented Mar 7, 2019

I tried to find what status e9 means, but couldn't find anything. This might be manufacturer specific status code. Response format should now be correct so no more u64 address when address mode is not 0x03.

@fairecasoimeme

This comment has been minimized.

Copy link
Owner

commented Mar 7, 2019

It seems that 0xe9 status is MAC_ENUM_NO_ACK --> No ack received when expected

We can find all of status / error code here :
https://www.nxp.com/docs/en/user-guide/JN-UG-3113.pdf
page 437

@ISO-B

This comment has been minimized.

Copy link
Collaborator

commented Mar 8, 2019

8702 now respects address mode so decoding should work correctly.

@ISO-B ISO-B closed this Mar 8, 2019

@sifus

This comment has been minimized.

Copy link

commented Mar 28, 2019

hello i have this error log

[2019-03-28 21:57:44][ERROR][zigate](ZiGate-Decode data) : RESPONSE 0x8702 - APS Data Confirm Fail : status:240, source_endpoint:1, dst_endpoint:1, dst_address_mode:2, dst_address:1dd9, sequence:72, lqi:0
[2019-03-28 22:07:13][ERROR][zigate](ZiGate-Decode data) : RESPONSE 0x8702 - APS Data Confirm Fail : status:240, source_endpoint:1, dst_endpoint:1, dst_address_mode:2, dst_address:2229, sequence:73, lqi:0
[2019-03-28 22:31:38][ERROR][zigate](ZiGate-Decode data) : RESPONSE 0x8702 - APS Data Confirm Fail : status:240, source_endpoint:1, dst_endpoint:1, dst_address_mode:2, dst_address:a79a, sequence:74, lqi:0
[2019-03-28 22:33:50][ERROR][zigate](ZiGate-Decode data) : RESPONSE 0x8702 - APS Data Confirm Fail : status:240, source_endpoint:1, dst_endpoint:1, dst_address_mode:2, dst_address:43d7, sequence:75, lqi:0
[2019-03-28 22:58:02][ERROR][zigate](ZiGate-Decode data) : RESPONSE 0x8702 - APS Data Confirm Fail : status:240, source_endpoint:1, dst_endpoint:1, dst_address_mode:2, dst_address:1dd9, sequence:76, lqi:0
[2019-03-28 23:07:32][ERROR][zigate](ZiGate-Decode data) : RESPONSE 0x8702 - APS Data Confirm Fail : status:240, source_endpoint:1, dst_endpoint:1, dst_address_mode:2, dst_address:2229, sequence:77, lqi:0
[2019-03-28 23:31:51][ERROR][zigate](ZiGate-Decode data) : RESPONSE 0x8702 - APS Data Confirm Fail : status:240, source_endpoint:1, dst_endpoint:1, dst_address_mode:2, dst_address:a79a, sequence:78, lqi:0
[2019-03-28 23:34:11][ERROR][zigate](ZiGate-Decode data) : RESPONSE 0x8702 - APS Data Confirm Fail : status:240, source_endpoint:1, dst_endpoint:1, dst_address_mode:2, dst_address:43d7, sequence:79, lqi:0
[2019-03-28 23:58:17][ERROR][zigate](ZiGate-Decode data) : RESPONSE 0x8702 - APS Data Confirm Fail : status:240, source_endpoint:1, dst_endpoint:1, dst_address_mode:2, dst_address:1dd9, sequence:80, lqi:0
[2019-03-29 00:07:54][ERROR][zigate](ZiGate-Decode data) : RESPONSE 0x8702 - APS Data Confirm Fail : status:240, source_endpoint:1, dst_endpoint:1, dst_address_mode:2, dst_address:2229, sequence:81, lqi:0
[2019-03-29 00:24:51][ERROR][zigate](ZiGate-Decode data) : RESPONSE 0x8702 - APS Data Confirm Fail : status:240, source_endpoint:1, dst_endpoint:1, dst_address_mode:2, dst_address:43d7, sequence:82, lqi:0
[2019-03-29 00:32:02][ERROR][zigate](ZiGate-Decode data) : RESPONSE 0x8702 - APS Data Confirm Fail : status:240, source_endpoint:1, dst_endpoint:1, dst_address_mode:2, dst_address:a79a, sequence:83, lqi:0
@ISO-B

This comment has been minimized.

Copy link
Collaborator

commented Mar 29, 2019

Status code 240 is 0xF0. Chapter 10.2.4 Mac codes in JN-UG-3113 v1.5 states:

0xF0 Pending transaction has expired and data discarded

This means that node you are trying to send commands didn't receive command within time limit

@fairecasoimeme fairecasoimeme referenced this issue Jul 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.