Open msp1974 opened 1 month ago
Think this is caused by an invalid message from the integration but how do we handle this better? How do we better deal with a message that gets no ACK from the alarm?
Also, maybe invalid ACKs from integration. It sends 0d 02 fd 0a which most of the time should be 0d 02 43 ba 0a.
Invalid message - this gets no ACK. Also not sure 39 is valid command as get no response when sending valid message with a 39.
2024-08-07 09:48:16,930 INFO HASS->Alarm 3 - 9769 VIS-BBA 0d b0 01 17 07 01 ff 08 ff 01 39 01 43 a8 0a
Valid message
2024-08-07 10:04:59,798 INFO Message Builder Received - b0 17 39
2024-08-07 10:04:59,798 INFO Message Builder Returned: 0d b0 01 17 07 01 ff 08 ff 01 39 00 43 a9 0a
2024-08-07 10:04:59,799 INFO REC << HASS 4 - 0000 VIS-BBA 0d b0 01 17 07 01 ff 08 ff 01 39 00 43 a9 0a
2024-08-07 10:04:59,799 INFO HASS->Alarm 3 - 0614 VIS-BBA 0d b0 01 17 07 01 ff 08 ff 01 39 00 43 a9 0a
2024-08-07 10:04:59,799 INFO Waiting ACK: From Alarm 3 for HASS 4 for msg id 614
2024-08-07 10:04:59,838 INFO ------------------------------------------------------------
2024-08-07 10:04:59,838 INFO REC << Alarm 3 - 0614 VIS-ACK 0d 02 43 ba 0a
2024-08-07 10:04:59,838 INFO Received awaited ACK for HASS 4 from Alarm 3 for msg id 614
2024-08-07 10:04:59,839 INFO Alarm->HASS 4 - 0614 VIS-ACK 0d 02 43 ba 0a
2024-08-07 10:05:00,355 INFO ------------------------------------------------------------
Sometime the message tracker sends a message form the message builder with the wrong message id, resulting in the message being ignored by the panel and an ACK timeout.