Yes, I checked it and I found the device sent the LBS and WIFI information, but the server doesn't take their information to save correct position
Please provide the full decoded data record for the sample you posted earlier.
[3G*9705020059*00E3*UD_LTE,100823,135955,V,00.000000,,00.0000000,,0.00,0.0,0.0,0,60,50,0,0,00000000,1,0,420,3,11240,29359410,7,5,,84:d4:7e:ef:7a:c4,-88,,8a:a3:03:0e:e0:e0,-90,,84:d4:7e:ef:7a:c2,-91,,84:d4:7e:ef:7a:c5,-92,,84:d4:7e:ef:73:44,-96,0.0]
[3G*9705020059*0009*LK,0,0,50]
[3G*9705020059*0002*LK]
[3G*9705020059*0009*LK,0,0,52]
[3G*4305000068*0009*LK,0,0,73][3G*4305000068*0009*LK,0,0,73]
I'm talking about actual decoded data in the database. Not the raw data.
Do you want from tc_positions table? or another table
Which other tables do you have it in?
This data stored in tc_positions
| 42286 | watch | 15 | 2023-08-10 12:02:33 | 2023-08-10 12:02:33 | 2023-08-10 10:58:50 | 0x01 | 24.70298 | 46.679784 | 752.7 | 12.7646 | 248 | NULL | {"batteryLevel":36,"steps":0,"distance":0.0,"totalDistance":5729020.48,"motion":true} | 0 | null | null |
| 42287 | watch | 17 | 2023-08-10 12:03:30 | 2023-08-10 12:03:30 | 2023-08-10 05:26:24 | 0x01 | 22.760821 | 113.8436772 | 36.3 | 0.102592 | 0 | NULL | {"batteryLevel":75,"steps":0,"distance":0.0,"totalDistance":1.245511552E7,"motion":true} | 0 | null
Are you sure those are the records corresponding to the sample with LBS data? If that's the case, it means the LBS data is not decoded by Traccar for you device at all.
The above reading when the GPS invalid position,
But when I got the device outdoor the GPS became valid and the server saved the below data:
| 42239 | watch | 15 | 2023-08-10 10:01:07 | 2023-08-10 10:01:06 | 2023-08-10 10:01:06 | 0x01 | 24.70828 | 46.6667668 | 635.1 | 2.61339 | 49.5 | NULL | {"sat":7,"rssi":100,"batteryLevel":39,"steps":0,"distance":5725624.51,"totalDistance":5725624.51,"motion":true} | 0 | {"radioType":"gsm","considerIp":false,"cellTowers":[{"cellId":28542524,"locationAreaCode":11240,"mobileCountryCode":420,"mobileNetworkCode":3,"signalStrength":22},{"cellId":28542504,"locationAreaCode":11240,"mobileCountryCode":420,"mobileNetworkCode":3,"signalStrength":19}],"wifiAccessPoints":[{"macAddress":"30:23:03:9d:c3:bb","signalStrength":-106},{"macAddress":"24:1f:a0:1a:5b:42","signalStrength":-107},{"macAddress":"7c:8b:ca:55:cd:b0","signalStrength":-109},{"macAddress":"36:23:03:9d:c3:bb","signalStrength":-112},{"macAddress":"3a:23:03:9d:c3:bb","signalStrength":-112}]} | null |
|
I guess your device format is not fully supported currently, assuming you're providing the correct information.
Dear Anton,
I tried another device which uses GT06 protocol, and I found this error below in the log file, Kindly could you help me to solve this error?
2023-08-13 09:49:18 INFO: [Tb39e32cf: gt06 > 117.136.33.202] 78780519fa4159f70d0a
2023-08-13 09:49:37 INFO: [Tb39e32cf: gt06 < 117.136.33.202] 787808192308130946267242d380f13b4708318baeefc84908318baeefcd49fc0c459e7d9049e0e0fcab80184be0e0fcfb801d4bcc242efce93154005cc2853304580501cc00000024780d71aa4256000024780a84aa12630000262502cf290350000026250d71cd435e000026250d63fa416c000d0a
2023-08-13 09:49:37 WARN: Geolocation network error -
javax.ws.rs.client.ResponseProcessingException: javax.ws.rs.BadRequestException: HTTP 400 Bad Request
at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:971)
at org.glassfish.jersey.client.JerseyInvocation.access$700(JerseyInvocation.java:82)
at org.glassfish.jersey.client.JerseyInvocation$1.completed(JerseyInvocation.java:863)
at org.glassfish.jersey.client.ClientRuntime.processResponse(ClientRuntime.java:232)
at org.glassfish.jersey.client.ClientRuntime.access$200(ClientRuntime.java:62)
at org.glassfish.jersey.client.ClientRuntime$2.lambda$response$0(ClientRuntime.java:176)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:248)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:244)
at org.glassfish.jersey.internal.Errors.process(Errors.java:292)
at org.glassfish.jersey.internal.Errors.process(Errors.java:274)
at org.glassfish.jersey.internal.Errors.process(Errors.java:244)
at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:288)
at org.glassfish.jersey.client.ClientRuntime$2.response(ClientRuntime.java:176)
at org.glassfish.jersey.client.internal.HttpUrlConnector.apply(HttpUrlConnector.java:283)
at org.glassfish.jersey.client.ClientRuntime.lambda$null$6(ClientRuntime.java:185)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:248)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:244)
at org.glassfish.jersey.internal.Errors.process(Errors.java:292)
at org.glassfish.jersey.internal.Errors.process(Errors.java:274)
at org.glassfish.jersey.internal.Errors.process(Errors.java:244)
at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:288)
at org.glassfish.jersey.client.ClientRuntime.lambda$createRunnableForAsyncProcessing$7(ClientRuntime.java:159)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: javax.ws.rs.BadRequestException: HTTP 400 Bad Request
at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:939)
... 26 more
Dear Anton,
Kindly skip the above message,
I tried another device which uses GT06 protocol, and I found this error below in the log file, Kindly could you help me to solve this error?
2023-08-13 12:36:59 INFO: [Tf0f945fd: gt06 < 117.136.33.202] 787801300d0a
2023-08-13 12:36:59 INFO: [Tf0f945fd: gt06 > 117.136.33.202] 787805307878d5ec0d0a
2023-08-13 12:37:00 INFO: [T84d77b58] connected
2023-08-13 12:37:01 INFO: [T84d77b58] error -
java.net.SocketException: Connection reset
at java.base/sun.nio.ch.SocketChannelImpl.throwConnectionReset(SocketChannelImpl.java:394)
at java.base/sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:426)
at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:256)
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1132)
at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:357)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:151)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:833)
Are you just sending random logs? Why does this need solving? What makes you think it's from GT06 protocol?
I changed the device and the new device uses GT06 protocol
Have you checked the decoded data?