FW 3.22 hybrid mode: No 8002 for 'Get Group Membership Response'

[tcharp38]

Hello
Is that behavior expected in HYBRID mode ?
If yes, it is different than v1 behavior.

On v2 FW 3.22

NO 8002 !!
[2023-03-23 18:02:17] Abeille1, Type=8062/Get group membership response (unused).

On v1 FW 3.23

[2023-03-26 12:46:25] Abeille1, Type=8002/Data indication, Status=00, ProfId=0104, ClustId=0004, SrcEP=01, DstEP=01, SrcAddrMode=02, SrcAddr=0000, DstAddrMode=02, DstAddr=0000
[2023-03-26 12:46:25] FCF=19/Cluster-specific/Serv->Cli, SQN=01, cmd=02/Get group membership response
[2023-03-26 12:46:25] Get group membership response: Capacity=05, GroupCount=00
[2023-03-26 12:46:25] Groups: NONE
[2023-03-26 12:46:25] Abeille1, Type=8062/Get group membership response (unused).

[fairecasoimeme]

Hello,
I'm going to see ASAP

[fairecasoimeme]

I'm just testing in hybrid mode with ZiGate v2 FW 3.A0 and I get 0x8002 message and 0x8062 message:

15:52:48.367 -> 01 02 10 62 02 10 02 16 E2 02 12 77 F3 02 11 02 11 02 10 03 
15:52:48.598 <- 01 80 00 00 09 8C 00 05 00 62 01 62 00 01 00 03
15:52:48.852 <- 01 80 12 00 0A 33 00 01 01 02 77 F3 62 00 00 4F 03
15:52:49.067 <- 01 80 11 00 08 7A 00 77 F3 01 00 04 62 00 03
15:52:49.277 <- 01 80 02 00 13 88 00 01 04 00 04 01 01 02 77 F3 02 00 00 19 05 02 04 00 86 03
15:52:49.677 <- 01 80 62 00 09 ED 05 01 00 04 04 00 77 F3 86 03

I used ZWGUI tool to generate Get Group command

[tcharp38]

Might be ok on 3.A0 and not on 3.22.

[fairecasoimeme]

I re did the test with v3.22 and all were OK

16:58:28.523 -> 01 02 10 62 02 10 02 16 74 02 12 13 02 11 02 11 02 11 02 10 03 
16:58:28.733 <- 01 80 00 00 09 F4 00 01 00 62 01 1E 00 01 00 03
16:58:28.973 <- 01 80 12 00 0A 96 00 01 01 02 13 01 1E 00 00 00 03
16:58:29.153 <- 01 80 11 00 08 90 00 13 01 01 00 04 1E 00 03
16:58:29.313 <- 01 80 02 00 13 00 00 01 04 00 04 01 01 02 13 01 02 00 00 19 01 02 04 00 9C 03
16:58:29.673 <- 01 80 62 00 09 65 01 01 00 04 04 00 13 01 9C 03

[fairecasoimeme]

the issue happen all the time ?

[tcharp38]

Ok with 3.22 ? Argh...

This is the first time I see this behaviour.
The user reversed the FW back to 3.22 from 3.A0 to get a stable system back. No more infos at this time :(