Megastek MT65Plus

Hello,

I have this gps tracker and traccar doesn't notice that the device is online.
In logs you can see the HEX and it looks good but no change in the status.

Is it possible to modify the detection that MT65Plus would work fine?

Thanks and kind regards,
Tobias

Please share logs.

2024-08-02 14:08:27  INFO: [Te706853f: megastek < 80.187.126.221] 30323236244d47563030322c3836303533373036353034343533392c2c532c3032303832342c3132303831392c562c353333392e31313532392c4e2c30313031312e31353537352c452c30302c30302c30302c39392e392c332e3235352c2c35322e312c2c3236322c30312c464646452c323737413630322c31312c3030302c303030302c303030302c302c2c2c2c2c30303230302c3037382c54696d65722c3530653633363938643164353a38307c3034623466653931336138353a38317c6463313563383938343830343a38347c3434303533666461636436653a38372c2c302c2c3b21

here are some more and with an error too:

2024-08-02 14:06:53  INFO: [Tc017e5da: megastek < 80.187.126.221] 3034313824434d563030312c3836303533373036353034343533393b523030312c4f4b2c3030303030303b523030322c4f4b2c696e7465726e65742e74656c656b6f6d2c636f6e67737461722c63733b523030332c4f4b2c636f6269622e73656c66686f73742e627a2c353032343b523030342c4f4b2c3b523030352c4f4b2c323b523030362c4f4b2c3230303b523030372c4f4b2c32303b523030382c4f4b2c303b523030392c4f4b2c313b523031302c4f4b2c30303439313737373132373530312c3030312c2c3030302c2c3030303b523031362c4f4b2c313b523031382c4f4b2c2c30302e30303030303030302c3030302e30303030303030302c302e302c2c30302e30303030303030302c3030302e30303030303030302c302e302c2c30302e30303030303030302c3030302e30303030303030302c302e302c2c30302e30303030303030302c3030302e30303030303030302c302e302c2c30302e30303030303030302c3030302e30303030303030302c302e303b523032302c4f4b2c3132303b523033382c4f4b2c30303a30302c30303a30303b523035332c4f4b2c32303b21
2024-08-02 14:06:53  INFO: [Tc017e5da] error - Range [21, 2) out of bounds for length 422 - StringIndexOutOfBoundsException (... < MegastekProtocolDecoder:147 < *:449 < ExtendedObjectDecoder:75 < ... < WrapperContext:102 < ...)
2024-08-02 14:06:53  INFO: [Tc017e5da] disconnected
2024-08-02 14:07:47  INFO: [Te706853f] connected
2024-08-02 14:07:49  INFO: [Te706853f: megastek < 80.187.126.221] 30323236244d47563030322c3836303533373036353034343533392c2c532c3032303832342c3132303731392c562c353333392e31313532392c4e2c30313031312e31353537352c452c30302c30302c30302c39392e392c332e3235352c2c35322e312c2c3236322c30312c464646452c323737413630322c31342c3030302c303030302c303030302c302c2c2c2c2c30313030302c3037382c54696d65722c6463313563383938343830343a36357c3530653633363938643164353a37307c3434303533666461636436653a37337c6530353136333134663261373a38382c2c302c2c3b21
2024-08-02 14:07:54  INFO: [Te706853f: megastek < 80.187.126.221] 30323331244d47563030322c3836303533373036353034343533392c2c522c3032303832342c3132303734392c562c353333392e31313532392c4e2c30313031312e31353537352c452c30302c30302c30302c39392e392c332e3235352c2c35322e312c2c3236322c30312c464646452c323737413630322c31342c3030302c303030302c303030302c302c2c2c2c2c30313230302c3037382c4c637261646c654f66662c3530653633363938643164353a38307c3034623466653931336138353a38317c6463313563383938343830343a38347c3434303533666461636436653a38372c2c302c2c3b21
2024-08-02 14:08:23  INFO: [Te706853f: megastek < 80.187.126.221] 30323238244d47563030322c3836303533373036353034343533392c2c522c3032303832342c3132303830362c562c353333392e31313532392c4e2c30313031312e31353537352c452c30302c30302c30302c39392e392c332e3235352c2c35322e312c2c3236322c30312c464646452c323737413630322c31312c3030302c303030302c303030302c302c2c2c2c2c30303230302c3037382c42656c744f66662c3530653633363938643164353a38307c3034623466653931336138353a38317c6463313563383938343830343a38347c3434303533666461636436653a38372c2c302c2c3b21

Looks like it's not supported currently. If you have the protocol documentation, you can submit a ticket on GitHub.

Thanks, I did it but not knowing if I put it in the correct category

@Anton thanks for the fix but how can I install it on my own Raspberry PI server?

You can wait for the next release or compile from source.