GT06 protocol stopped informing the address

Hello!

GT06 protocol stopped informing the address
I have already looked at all the topics in the forum, but no solution worked for me.

In the Log files the following error appears

WARN: Failed to store position - Incorrect string value: '\xC4\x83os, ...' for column 'address' at row 1 - SQLException (... < QueryBuilder:480 < DataManager:458 < DefaultDataHandler:40 < ...)

DATABASEURL:

<entry key='database.url'>jdbc:mysql://localhost:3306/traccar?serverTimezone=UTC&useSSL=false&allowMultiQueries=true&autoReconnect=true&useUnicode=yes&characterEncoding=UTF-8&sessionVariables=sql_mode=''</entry>

I changed the grouping of the database address table to utf8_general_ci
As I saw in the previous topics

OBS: I tried the alterations of the topic below, but as it was 5 years ago, I believe it is not for today
https://www.traccar.org/forums/topic/mysql-error-change/

Sorry about my English

The link you provided is still relevant.

Sorry, I still couldn't find the error.

The wrapper.conf file comes with UTF8 by default.
My DATABASEURL as informed above, is in the correct format informed in the topic I quoted.

Is with useUnicode = yes
characterEncoding = UTF-8, e & amp as you asked for in that topic

The address field of the tc_positions table is in UTF8MB4_General_ci format

Well, the error is coming directly from the database driver, so the issue is either with database configuration or database connection URL.

Thank you.
You have informed where you are, it is up to me to find the solution.

Finding it, I'll post it to everyone and answer the solution here

Hello! Did you find the solution? I'm having the same problem and I can't find the equipment that is generating this.

In my case it generates an error that disorganizes the index of the tc_positions table.

WARN: Update device status error - HikariPool - 1 Connection is not available, request time out after...
WARN: Failed to store position - HikariPool - 1 Connection is not available, request time out after 3000...

I have already increased the database timeout (Mysql), configured it by optimizing resources, openfile limits, etc ... but the error persists after a few hours.

This occurs whenever GT06 are configured.

If I disable the GT06 port the error does not occur.

I don't think this error has anything to do with GT06, so I would recommend sticking to the original thread. Please don't duplicate your comments.

I still haven't managed to fix it. I've tried all the forum solutions. I've been trying with 3 more programmers for 8 months

Log:

2020-10-22 01:29:24  INFO: [71856dc5: gt06 < 200.233.216.86] HEX: 7878058a0015aa330d0a78780a130506040002001a4b550d0a79790020940a035592910025454007243202008696548955320200000869654200168e540d0a79790008940004e60017c38b0d0a79790008940004e600183b7c0d0a79790008940004e600192af50d0a

When I go to decode it appears: Binary Hex can't be converted to Text

Looks like there are several messages inside:

7878058a0015aa330d0a
78780a130506040002001a4b550d0a
79790020940a035592910025454007243202008696548955320200000869654200168e540d0a
79790008940004e60017c38b0d0a
79790008940004e600183b7c0d0a
79790008940004e600192af50d0a

None of them include any location data, afaik.

What are you expecting to see?

All of my more than 5,000 GT06 protocol trackers send latitude and longitude normally. I sent this LOG just because it was the only one I couldn't decode. But it is sending normally!

We have about 30 thousand vehicles with 120 systems, with more than 100 models of trackers, only the GT06 protocol that represents 5,000 vehicles that rarely appear the address, but it is not a problem of the tracker, because when consulting the history is displayed normally.

I will have to pay your support to get more information. I will contact you by email

Did you try to decode these messages individually? It does not work. The same thing appears

Hello ... I decided to isolate a piece of equipment and remove it from the platform.

The traccar protocol is ok, the problem was in the equipment sending data in the wrong format.

I just didn't understand why it blocked the platform.

But anyway, problem with the equipment.

Thanks Anton for the service.

Central de Ratsreamento
Como você resolveu?

Olhei o log, vi o momento que o erro aconteceu, movi esses equipamentos (que estavam proximo do erro) para outra plataforma, e fui analisando o log para retirar o equipamento que causava o problema.

Era um accurate!