Traccar 4.1 does not recognize ignition status

Hello Anton, I updated my traccar to version 4.1 and realized that 3 protocols are not displaying ignition status, they are:
KHD (port 5058) https://static.wixstatic.com/media/3e9b00_5845ce1bb40141188932fd594fbe4566~mv2.png/v1/fill/w_524,h_804,al_c,q_85/KHD_fw.webp
EASYTRACK (port 5056) https://static.wixstatic.com/media/3e9b00_442ee69c89db41f58d4909d75199e77d~mv2.png/v1/fill/w_512,h_790,al_c,q_85/EASYTRACK_fw.webp
GL200 (port 5004) https://static.wixstatic.com/media/3e9b00_2a907f42b31e4d1cad75fec47f695ab7~mv2.png/v1/fill/w_512,h_642,al_c,q_80/GL200_fw.webp
could you verify?
In version 3.16 it worked fine.

Thanks in advance for your attention.

You would have to provide HEX samples for messages with ignition that worked before.

KHD - 29298000280c838a42181109145945810172288363409600240040fa00979d7fff130000b4000000000000b80d

EASYTRACK - 2a45542c3335383135353130303034383230302c48422c412c3132306230632c3062303530652c38303537383763662c38313437393764352c303335352c356435632c34306330303030302c31612c3130302c303030302c31613761642c3933230d0a

GL200 - 2b524553503a47544652492c3246303730322c3836333833303033313731383837332c2c31343233312c35302c312c312c31372e372c32342c3138322e382c2d33362e3739323138392c2d392e3935353334352c32303138313131313032353935372c303732342c303030322c413834412c303732322c30302c363438362e342c2c2c2c3130302c3232303130302c2c2c2c32303138313131313033303031322c3637463724

I installed version 4.2 on a test server.
protocol GL200 ran the ignition state. https://static.wixstatic.com/media/3e9b00_80943f786506402e8ef501b941e530c8~mv2.png/v1/fill/w_359,h_715,al_c,q_80/GL200-4_2_fw.webp

KHD protocol did not operate the ignition state. https://static.wixstatic.com/media/3e9b00_2e55f48991aa44a3a7b65434fb3ad1a4~mv2.png/v1/fill/w_398,h_684,al_c,q_80/KHD-4_2_fw.webp

I have not had easytrack testing yet, I'm out of stock.

OK, so only KHD is not working, right?

I just checked KHD protocol and ignition was never supported for it. Not even in 3.16. I'm waiting for some kind of explanation from you.

a developer sent the protocol with ignition status to you, Michaell Oliveira