Open tcharp38 opened 10 months ago
A l'heure actuelle d'apres les remontées utilisateurs, le FW 3.22 est le + stable (et non pas le 3.A0 = trop de pbs).
Cependant le 3.22 genere parfois un SQN inutilisable. Le comportement est different d'une Zigate v1. Jamais vu ce cas.
Voir SQN=02 On voit l'ordre 02, 03, 0D, 04, 01, 0F, puis à nouveau 02
[2024-01-08 07:50:51] Abeille1, Type=8000/Status, Status=00/Success, SQN=02, PacketType=0100, Sent=01, SQNAPS=0B, NPDU=01, APDU=03 [2024-01-08 07:50:51] Abeille1, Type=8011/APS data ACK, Status=00/Success, Addr=8A58, EP=01, ClustId=0702, SQNAPS=0B [2024-01-08 07:50:51] Abeille1, Type=8002/Data indication, Status=00, ProfId=0104, ClustId=0702, SrcEP=01, DstEP=01, SrcAddrMode=02, SrcAddr=8A58, DstAddrMode=02, DstAddr=0000 [2024-01-08 07:50:51] FCF=18/General/Serv->Cli, SQN=02, cmd=01/Read Attributes Response [2024-01-08 07:50:51] AttrId=0308/Unknown-0702-0308, Status=00, AttrType=41, ValueHex=383132303634363032303932 => 383132303634363032303932 [2024-01-08 07:50:51] Abeille1, Type=8000/Status, Status=00/Success, SQN=03, PacketType=0100, Sent=01, SQNAPS=0C, NPDU=01, APDU=03 [2024-01-08 07:50:51] Abeille1, Type=8012/APS data confirm, Status=00, Addr=8A58, SQNAPS=0C, NPDU=01, APDU=00 [2024-01-08 07:50:51] Abeille1, Type=8011/APS data ACK, Status=00/Success, Addr=8A58, EP=01, ClustId=0B04, SQNAPS=0C [2024-01-08 07:50:51] Abeille1, Type=8002/Data indication, Status=00, ProfId=0104, ClustId=0B04, SrcEP=01, DstEP=01, SrcAddrMode=02, SrcAddr=8A58, DstAddrMode=02, DstAddr=0000 [2024-01-08 07:50:51] FCF=18/General/Serv->Cli, SQN=03, cmd=01/Read Attributes Response [2024-01-08 07:50:51] AttrId=0508/RMS Current, Status=00, AttrType=21, ValueHex=000E => 14 [2024-01-08 07:50:51] Abeille1, Type=8000/Status, Status=00/Success, SQN=0D, PacketType=0530, Sent=01, SQNAPS=0D, NPDU=00, APDU=03 [2024-01-08 07:50:51] Abeille1, Type=8012/APS data confirm, Status=00, Addr=8A58, SQNAPS=0D, NPDU=00, APDU=00 [2024-01-08 07:50:51] Abeille1, Type=8011/APS data ACK, Status=00/Success, Addr=8A58, EP=01, ClustId=0B04, SQNAPS=0D [2024-01-08 07:50:51] Abeille1, Type=8000/Status, Status=00/Success, SQN=04, PacketType=0100, Sent=01, SQNAPS=0E, NPDU=00, APDU=03 [2024-01-08 07:50:51] Abeille1, Type=8012/APS data confirm, Status=00, Addr=8A58, SQNAPS=0E, NPDU=00, APDU=00 [2024-01-08 07:50:51] Abeille1, Type=8002/Data indication, Status=00, ProfId=0104, ClustId=0B04, SrcEP=01, DstEP=01, SrcAddrMode=02, SrcAddr=8A58, DstAddrMode=02, DstAddr=0000 [2024-01-08 07:50:51] FCF=18/General/Serv->Cli, SQN=01, cmd=07/Configure Reporting Response [2024-01-08 07:50:51] Duplicated message for SQN 01 => ignoring [2024-01-08 07:50:52] Abeille1, Type=8011/APS data ACK, Status=00/Success, Addr=8A58, EP=01, ClustId=0B04, SQNAPS=0E [2024-01-08 07:50:52] Abeille1, Type=8000/Status, Status=00/Success, SQN=0F, PacketType=0530, Sent=01, SQNAPS=0F, NPDU=00, APDU=03 [2024-01-08 07:50:52] Abeille1, Type=8012/APS data confirm, Status=00, Addr=8A58, SQNAPS=0F, NPDU=00, APDU=00 [2024-01-08 07:50:52] Abeille1, Type=8011/APS data ACK, Status=00/Success, Addr=8A58, EP=01, ClustId=0B04, SQNAPS=0F [2024-01-08 07:50:52] Abeille1, Type=8002/Data indication, Status=00, ProfId=0104, ClustId=0B04, SrcEP=01, DstEP=01, SrcAddrMode=02, SrcAddr=8A58, DstAddrMode=02, DstAddr=0000 [2024-01-08 07:50:52] FCF=18/General/Serv->Cli, SQN=02, cmd=07/Configure Reporting Response [2024-01-08 07:50:52] Duplicated message for SQN 02 => ignoring
Je suis preneur de n'importe quelle idée ou d'infos sur la génération du SQN.
A l'heure actuelle d'apres les remontées utilisateurs, le FW 3.22 est le + stable (et non pas le 3.A0 = trop de pbs).
Cependant le 3.22 genere parfois un SQN inutilisable. Le comportement est different d'une Zigate v1. Jamais vu ce cas.
Voir SQN=02 On voit l'ordre 02, 03, 0D, 04, 01, 0F, puis à nouveau 02
Je suis preneur de n'importe quelle idée ou d'infos sur la génération du SQN.