I am having problems with Digital Matter devices updating on the Traccar platform. There are 2 separate issues going on.
The first is with TCP. There are 2 different devices that are having the issues. They will report fine for days, weeks, or months. Then they will get the error below and can't recover until I switch the connector to HTTP then back to TCP.
Yabby
2019-09-06 12:39:11 INFO: [b2f40c45] connected
2019-09-06 12:39:11 INFO: [b2f40c45: dmt < 104.45.185.0] HEX: 0255003100c5ba0200333532373533303933333139333634003839303131373032323732303438393232313730004d02020400000000
2019-09-06 12:39:11 INFO: [b2f40c45: dmt > 104.45.185.0] HEX: 02550108006f2c900c00000000
2019-09-06 12:39:12 INFO: [b2f40c45: dmt < 104.45.185.0] HEX: 025504ab013d00c21a00004829900c0300154929900cbd163617b08a94c7fa003c07032c131a0302080300000000000300060f019b14037e0e0463000558140607213d00c31a0000
ca29900c030015ca29900ca3033817bbb895c71401be0603b310190302080300000000000300060f019b14036d0e0463000558140607213d00c41a0000472a900c030015472a900c8d453817423e96c7fa000200040013270302080300000000000300060f019b1
403840e0463000546140606213d00c51a0000c52a900c030015c52a900c184c3817c35296c724010400050016180302080300000000000300060f019b1403750e0463000547140606213d00c61a0000462b900c030015462b900cbd8a361703b495c710018c0708
5a10210302080300000000000300060f019b1403630e0463000546140606213d00c71a0000c52b900c030015c52b900cf6d63517455a94c7e9004c05035a10240302080300000000000300060f019b14036e0e0463000545140606213d00c81a00004b2c900c030
0154b2c900c766d3517ddf093c7320107000d00102e0302080300000000000300060f019b1403750e046300054314060521
2019-09-06 12:39:12 WARN: [b2f40c45] error - readerIndex(431) + length(2) exceeds writerIndex(432): PooledSlicedByteBuf(ridx: 431, widx: 432, cap: 432/432, unwrapped: PooledHeapByteBuf(ridx: 432, widx: 432,
cap: 1024)) - IndexOutOfBoundsException (... < DmtProtocolDecoder:208 < *:282 < ExtendedObjectDecoder:51 < ... < WrapperContext:102 < ...)
2019-09-06 12:39:12 INFO: [b2f40c45] disconnected
Oyster 2
2019-09-07 17:39:59 INFO: [2f712c3a] connected
2019-09-07 17:39:59 INFO: [2f712c3a: dmt < 52.151.234.162] HEX: 02550031001eb90200333532373533303933373136323437003839343435303031303531393134393033343400004d02020400000000
2019-09-07 17:39:59 INFO: [2f712c3a: dmt > 52.151.234.162] HEX: 02550108006fc4910c00000000
2019-09-07 17:40:01 INFO: [2f712c3a: dmt < 52.151.234.162] HEX: 0255043d003d00b46c0000a2bd910c030015a2bd910cabee8c172b8006c26006310d024a1c0e0302080300000000000300060f01c21003ad0704170005c20f06041f
2019-09-07 17:40:01 WARN: [2f712c3a] error - readerIndex(65) + length(2) exceeds writerIndex(66): PooledSlicedByteBuf(ridx: 65, widx: 66, cap: 66/66, unwrapped: PooledHeapByteBuf(ridx: 66, widx: 66, cap: 10
24)) - IndexOutOfBoundsException (... < DmtProtocolDecoder:205 < *:282 < ExtendedObjectDecoder:51 < ... < WrapperContext:102 < ...)
2019-09-07 17:40:01 INFO: [2f712c3a] disconnected
The second issue is with HTTP. It will not update the map with the locations. It sends acknowledgement, but never updates the database.
2019-09-07 21:53:29 INFO: [0fb47eda] connected
2019-09-07 21:53:29 INFO: [0fb47eda: dmthttp < 104.45.185.0] HEX: 504f5354202f536176655265636f72647320485454502f312e310d0a436f6e74656e742d547970653a206170706c69636174696f6e2f6a736f6e3b20636861727365743d7574
662d380d0a4163636570743a20746578742f68746d6c2c746578742f786d6c2c746578742f6a736f6e2c6170706c69636174696f6e2f7868746d6c2b786d6c2c6170706c69636174696f6e2f786d6c3b713d302e392c2a2f2a3b713d302e380d0a486f73743a203
130342e3233372e3133302e38313a353133390d0a436f6e74656e742d4c656e6774683a20313830380d0a436f6e6e656374696f6e3a20436c6f73650d0a0d0a7b225365724e6f223a3137383436322c22494d4549223a2233353237353330393337313632343722
2c224943434944223a2238393434353030313035313931343930333434222c2250726f644964223a37372c224657223a2237372e322e322e34222c225265636f726473223a5b7b225365714e6f223a32383338362c22526561736f6e223a332c224461746555544
3223a22323031392d30392d30372031383a31323a3531222c224669656c6473223a5b7b22477073555443223a22323031392d30392d30372031383a31323a3531222c224c6174223a33392e323933363932352c224c6f6e67223a2d3130322e373438343133372c
22416c74223a313336362c22537064223a333334382c22537064416363223a312c2248656164223a34352c2250444f50223a32302c22506f73416363223a32352c2247707353746174223a332c224654797065223a307d2c7b2244496e223a332c22444f7574223
a302c2244657653746174223a332c224654797065223a327d2c7b22416e616c6f67756544617461223a7b2231223a343239302c2233223a323330302c2234223a31342c2235223a343036312c2236223a373838357d2c224654797065223a367d5d7d2c7b225365
714e6f223a32383339362c22526561736f6e223a332c2244617465555443223a22323031392d30392d30372031383a31343a3535222c224669656c6473223a5b7b22477073555443223a22323031392d30392d30372031383a31343a3535222c224c6174223a333
92e323933333236312c224c6f6e67223a2d3130322e373030313536362c22416c74223a313337322c22537064223a333336302c22537064416363223a322c2248656164223a34352c2250444f50223a32332c22506f73416363223a33312c224770735374617422
3a332c224654797065223a307d2c7b2244496e223a332c22444f7574223a302c2244657653746174223a332c224654797065223a327d2c7b22416e616c6f67756544617461223a7b2231223a343239302c2233223a323239392c2234223a31342c2235223a34303
9372c2236223a373838357d2c224654797065223a367d
2019-09-07 21:53:29 INFO: [0fb47eda: dmthttp < 104.45.185.0] HEX: 5d7d2c7b225365714e6f223a32383430362c22526561736f6e223a332c2244617465555443223a22323031392d30392d30372031383a31363a3539222c224669656c6473223a
5b7b22477073555443223a22323031392d30392d30372031383a31363a3539222c224c6174223a33392e323933313632312c224c6f6e67223a2d3130322e363531393038342c22416c74223a313333342c22537064223a333332362c22537064416363223a322c2
248656164223a34342c2250444f50223a31392c22506f73416363223a33392c2247707353746174223a332c224654797065223a307d2c7b2244496e223a332c22444f7574223a302c2244657653746174223a332c224654797065223a327d2c7b22416e616c6f67
756544617461223a7b2231223a343239302c2233223a323239312c2234223a31342c2235223a343130332c2236223a373838357d2c224654797065223a367d5d7d2c7b225365714e6f223a32383431372c22526561736f6e223a332c2244617465555443223a223
23031392d30392d30372031383a31393a3033222c224669656c6473223a5b7b22477073555443223a22323031392d30392d30372031383a31393a3033222c224c6174223a33392e3239343330322c224c6f6e67223a2d3130322e363033363832342c22416c7422
3a313335332c22537064223a333335352c22537064416363223a322c2248656164223a34342c2250444f50223a31392c22506f73416363223a33352c2247707353746174223a332c224654797065223a307d2c7b2244496e223a332c22444f7574223a302c22446
57653746174223a332c224654797065223a327d2c7b22416e616c6f67756544617461223a7b2231223a343239302c2233223a323236342c2234223a31342c2235223a343130372c2236223a373838357d2c224654797065223a367d5d7d2c7b225365714e6f223a
32383432372c22526561736f6e223a332c2244617465555443223a22323031392d30392d30372031383a32313a3037222c224669656c6473223a5b7b22477073555443223a22323031392d30392d30372031383a32313a3037222c224c6174223a33392e3239343
43030312c224c6f6e67223a2d3130322e35353534332c22416c74223a313333302c22537064223a333337342c22537064416363223a332c2248656164223a34342c2250444f50223a31392c22506f73416363223a34302c2247707353746174223a332c22465479
7065223a307d2c7b2244496e223a332c22444f7574223a302c2244657653746174223a332c224654797065223a327d2c7b22416e616c6f67756544617461223a7b2231223a343239302c2233223a323234362c2234223a31342c2235223a343130392c2236223a3
73838357d2c224654797065223a367d5d7d5d7d
2019-09-07 21:53:29 INFO: [0fb47eda: dmthttp > 104.45.185.0] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2019-09-07 21:53:29 INFO: [0fb47eda] disconnected
Could be some protocol implementation issue or could just be some changes in the protocol.
What do I need to request from DM? This is affecting a lot of my devices.
You would need to get latest protocol documentation.
We are having EXACTLY the same issue:
We use DigitalMatter Hardware. We have been running successfully for many months Traccar with dmthttp protocol. Exactly as Norm states above our tc_positions table STOPPED updating. Take a look we have the same in the LOG
We are using the same hardware. We have checked with Digital Matter and they claim the 'protocol' has not changed... Did Norm find a solution.. ... or any further ideas regarding this ?
Issue is solved. PostGIS appears to be incompatible with Traccar....................
We merged Traccar tables from a working (for many months) PostgreSQL to a new Database
that had installed the PostGIS extension.. It was after this that we experienced our 'bad behavior' (note: reported in prior forum entry)
We found this is the culprit.
We DO need PostGIS for other aspects of our application and will keep the Traccar Database Separate and join
our two database with a db_link.
I am having problems with Digital Matter devices updating on the Traccar platform. There are 2 separate issues going on.
The first is with TCP. There are 2 different devices that are having the issues. They will report fine for days, weeks, or months. Then they will get the error below and can't recover until I switch the connector to HTTP then back to TCP.
Yabby
Oyster 2
The second issue is with HTTP. It will not update the map with the locations. It sends acknowledgement, but never updates the database.