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

0x8702 - Dest Address not always contains a IEEE ! But AddrMode = 0x02 #161

pipiche38 opened this issue Feb 23, 2019 · 1 comment


Copy link

commented Feb 23, 2019

When receiving APS Failure, it looks like the DestMode is not correct.

In fact what ever the APS failure is related to a Group or a End Device, we always get 0x02 as the DestMode ! While Destination Address is a 64uint.

Then I'm receiving time to time either a Group ID or a Short Address uint16 . Like the example here after

Here 5af8 is a End Device:
Feb 23 21:55:41 rasp domoticz[771]: (Zigate-DEV) Decode8702 - SQN: db AddrMode: 02 DestAddr: 5af8000000000000 SrcEP: 01 DestEP: 01 Status: f0 - Pending transaction has expired and data discarded
Feb 23 21:55:51 rasp domoticz[771]: (Zigate-DEV) Decode8702 - SQN: dd AddrMode: 02 DestAddr: 5af8000000000000 SrcEP: 01 DestEP: 01 Status: f0

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…

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 ISO-B added this to the v3.1a milestone Mar 7, 2019

@pipiche38 pipiche38 closed this Mar 21, 2019


This comment has been minimized.

Copy link

commented Jun 21, 2019


@fairecasoimeme fairecasoimeme referenced this issue Jul 12, 2019


V3.1a #209

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.