Logs?
@Christopher,
Did you solve your issues of VT202 device not sending its location?
I think we have similar problem.
2019-12-05 19:24:04 INFO: [c590c81f: trv < 175.176.21.29] HEX: 545256415031342c3531352c332c31313234312c313931363423
2019-12-05 19:24:04 INFO: [c590c81f: trv > 175.176.21.29] HEX: 545256425031342c302e3030302c302e30303023
2019-12-05 19:24:53 INFO: [391c1299: trv < 175.176.21.20] HEX: 5452564150303033353236323131303935303734343923
2019-12-05 19:24:53 INFO: [391c1299: trv > 175.176.21.20] HEX: 5452564250303023
2019-12-05 19:24:54 INFO: [391c1299: trv < 175.176.21.20] HEX: 545256415031342c3531352c332c31313234312c313931363423
2019-12-05 19:24:54 INFO: [391c1299: trv > 175.176.21.20] HEX: 545256425031342c302e3030302c302e30303023
2019-12-05 19:24:54 INFO: [391c1299: trv < 175.176.21.20] HEX: 5452564350333423
2019-12-05 19:24:54 INFO: [391c1299: trv > 175.176.21.20] HEX: 5452564450333423
2019-12-05 19:28:06 INFO: [391c1299: trv > 175.176.21.20] HEX: 5452564450333523
2019-12-05 19:33:34 INFO: [212311d4: trv < 175.176.21.78] HEX: 5452564150303033353236323131303935303734343923
2019-12-05 19:33:34 INFO: [212311d4: trv > 175.176.21.78] HEX: 5452564250303023
2019-12-05 19:33:35 INFO: [212311d4: trv < 175.176.21.78] HEX: 545256415031342c3531352c332c31313234312c343039393523
2019-12-05 19:33:35 INFO: [212311d4: trv > 175.176.21.78] HEX: 545256425031342c302e3030302c302e30303023
2019-12-05 19:33:35 INFO: [212311d4: trv < 175.176.21.78] HEX: 5452564350333423
2019-12-05 19:33:35 INFO: [212311d4: trv > 175.176.21.78] HEX: 5452564450333423
Yes, got the protocol edited by Anton. But the trv devices have to move quite a distance before they send a new location sometimes.
The first problem is solved. Thank for that.
Tried to build the protocol differently, now i get IndexOutOfBoundsException.
What am I doing wrong?