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

Closed
pipiche38 opened this issue Feb 23, 2019 · 1 comment
Closed
Milestone

Comments

@pipiche38
Copy link

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
…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.
@ISO-B ISO-B added this to the v3.1a milestone Mar 7, 2019
@pipiche38
Copy link
Author

Confirmed

@fairecasoimeme fairecasoimeme mentioned this issue Jul 12, 2019
Alx2000y added a commit to Alx2000y/JN-ZigbeeNodeControlBridge-firmware that referenced this issue Nov 1, 2022
Alx2000y added a commit to Alx2000y/JN-ZigbeeNodeControlBridge-firmware that referenced this issue Nov 10, 2022
Исправлены OTA обновления для 1000000 (буфера не хватало при сильно пустых (много нулей) блоках прошивки)
Заодно починился бэкап/восстановление на той же лимонной скорости и без дебага.

apply from zigate:
fix bindgroup command + change version
Added fields for 0x8030, 0x8031. Both responses now include source endpoint, addressmode and short address. fairecasoimeme/ZiGate#161
Alx2000y added a commit to Alx2000y/JN-ZigbeeNodeControlBridge-firmware that referenced this issue Nov 10, 2022
…устых (много нулей) блоках прошивки)

Заодно починился бэкап/восстановление на той же лимонной скорости, даже не в дебаг версии.

Fix UART tx and rx queue size то MAX_PACKET_SIZE

Случайно перенесено из зигаты:
fix bindgroup command + change version
Added fields for 0x8030, 0x8031. Both responses now include source endpoint, addressmode and short address. fairecasoimeme/ZiGate#161
Alx2000y added a commit to openlumi/JN-ZigbeeNodeControlBridge-firmware that referenced this issue Nov 10, 2022
…устых (много нулей) блоках прошивки)

Заодно починился бэкап/восстановление на той же лимонной скорости, даже не в дебаг версии.

Fix UART tx and rx queue size то MAX_PACKET_SIZE

Случайно перенесено из зигаты:
fix bindgroup command + change version
Added fields for 0x8030, 0x8031. Both responses now include source endpoint, addressmode and short address. fairecasoimeme/ZiGate#161
Alx2000y added a commit to openlumi/JN-ZigbeeNodeControlBridge-firmware that referenced this issue Nov 10, 2022
…устых (много нулей) блоках прошивки)

Заодно починился бэкап/восстановление на той же лимонной скорости, даже не в дебаг версии.

Fix UART tx and rx queue size то MAX_PACKET_SIZE

Случайно перенесено из зигаты:
fix bindgroup command + change version
Added fields for 0x8030, 0x8031. Both responses now include source endpoint, addressmode and short address. fairecasoimeme/ZiGate#161

Proposed by @VOVAiS
Tested by @VOVAiS
Confirmed by @VOVAiS
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants