I saw that there is a new “MT710” device profile available in Petovik. Thank you for making it a priority and getting the new device profile available so quickly!
Unfortunately, when I tried it out it doesn’t quite work right. It sorta works if you disable LBS on the device (though while you do get positions something still isnt right). If LBS in enabled on the device it doesnt work at all.
I’ve been looking over the logs shown in the Flespi “Toolbox” app, and I think the issue is that the data Petovik is receiving from the device isnt being parsed correctly.
- When LBS is enabled this incorrect parsing gives a
000218 [mictrack:78:13] in @lbs: {ext} [5]: not an integer string: '' error, resulting in an instant disconnect and Petovik not receiving any GPS positions
- When LBS is disabled this incorrect parsing gives a
001410 [mictrack:98:7] in @message: {ext} got more split items than expected error. This error doesnt cause a disconnect until the next message is received, potentially allowing Petovik to get GPS positions from the device but forcing a disconnect/reconnect for every new message/position received.
Here are some example logs from Toolbox. Hopefully these are useful in diagnosing the issue,
NOTE: since this is a public thread I have removed the Petovik device ID, IMEI, and IP/port used (replaced with <ID>, <IMEI>, <IP>, <PORT> placeholders). If you need this info let me know and I can email it to you. Also, lines starting with # are comments I added and are not part of the original logs.
------------------------------------------------------------------------------------------------------------------------
# LOGS FROM TOOLBOX WHEN USING MT710 DEVICE PROFILE
------------------------------------------------------------------------------------------------------------------------
# CONNECT LOG EXAMPLE
------------------------------------------------------------------------------------------------------------------------
300: device connected
12/05/2023 21:36:14 (-04:00)
{
"device_id":<ID>,
"event_code":300,
"id":<ID>,
"ident":"<IMEI>",
"origin_id":<ID>,
"origin_type":11,
"source":"<IP>:<PORT>",
"timestamp":1683941774.38468,
"transport":"tcp"
}
------------------------------------------------------------------------------------------------------------------------
# DISCONNECT LOG EXAMPLES
------------------------------------------------------------------------------------------------------------------------
# LBS ENABLED
# INSTANT DISCONNECT ON EVERY CONNECTION, NOT RECIEVING POSITIONS IN PETOVIK
301: device disconnected (received data violates channel's protocol)
12/05/2023 21:36:14 (-04:00)
{
"close_code":4,
"duration":0,
"error_text":"000218 [mictrack:78:13] in @lbs: {ext} [5]: not an integer string: ''\n by [mictrack:114:10] in @message\n by [mictrack:86:5] in @packet",
"event_code":301,
"id":<ID>,
"ident":"<IMEI>",
"msgs":1,
"origin_id":<ID>,
"origin_type":11,
"recv":106,
"send":0,
"source":"<IP>:22042",
"timestamp":1683941774.38499,
"traffic":
{
"conn":3461605394,
"field_boundary":4,
"field_start":4,
"packet_start":37,
"parsed":4,
"timestamp":1683941774.383327
},
"transport":"tcp"
}
------------------------------------------------------------------------------------------------------------------------
# LBS DISABLED
# DISCONNECT AFTER 1ST NEW MESSAGE RECIEVED RECIEVING POSITIONS IN PETOVIK
# TECHNICALLY SORTA-WORKING, BUT STILL DISCONNECTING/RECONNECTING ON EVERY NEW MESSAGE
301: device disconnected (received data violates channel's protocol)
12/05/2023 23:54:41 (-04:00)
{
"close_code":4,
"duration":51,
"error_text":"001410 [mictrack:98:7] in @message: {ext} got more split items than expected\n by [mictrack:86:5] in @packet",
"event_code":301,
"id":<ID>,
"ident":"<IMEI>",
"msgs":2,
"origin_id":<ID>,
"origin_type":11,
"recv":208,
"send":0,
"source":"<IP>:<PORT>",
"timestamp":1683955927.762871,
"traffic":
{
"conn":2415553647,
"field_boundary":34,
"field_start":1,
"packet_start":0,
"parsed":1,
"timestamp":1683955927.762871
},
"transport":"tcp"
}
