H02 protocol Device online but No State or position

Hi there,

I'm trying a new device, it's called LK930 and it's using h02 protocol at port 5013.

The device appears online, but the State window is completely empty.

The log shows:

*HQ,4930014770,V1,114224,V,0000.0000,N,00000.0000,E,000.00,000,280218,FFFFFBFF,214,07,0,0,6#

I entered the following entries to my config:

<entry key='geolocation.enable'>true</entry> 
<entry key='geolocation.type'>mozilla</entry> 
<entry key='geolocation.key'>test</entry> 
<entry key='geolocation.processInvalidPositions'>true</entry>

But stills show Online, but no info about the device and no position reported.

Any suggestions?

Thanks in advance.

It also sometimes reports

*HQ,4930014770,V5,115521,V,0000.0000,N,00000.0000,E,000.00,000,3,FC:B4:E6:E4:6F:69,-52,E0:41:36:BB:CF:E1,-90,78:94:B4:88:67:71,-75,214,7,0,4,3803,20541,30,3803,20282,16,3803,20233,15,3803,20253,15,280218,FFFFFBFF,6#

Its supposed to be a GPS, GLONASS, LBS, WIFI, AGPS tracker.

Have you checked server logs?

Let me give you a quick update,

The fact is that when I started moving with the device, it started to report location properly, since I entered on a building with it, and now its stucked in the middle of nowhere, not zero coordinates, it reports -49.500 Lat and -153.058 Long, but on the server logs reports the correct coordenates.

This is what the log say

2018-03-01 22:37:49 DEBUG: [E5228953: 5013 < 176.83.99.251] HEX: 2a48512c343933303031343737302c23
2018-03-01 22:38:08 DEBUG: [E5228953: 5013 < 176.83.99.251] HEX: 2a48512c343933303031343737302c56312c3231333830372c412c323832362e383837302c4e2c30313631382e313137382c572c3030302e30302c3030302c3031303331382c46464646464246462c3231342c30372c302c302c3623
2018-03-01 22:38:08  WARN: Geocoding failed - Empty address - GeocoderException (JsonGeocoder:69 < *:34 < *:96 < ...)
2018-03-01 22:38:08  INFO: [E5228953] id: 4930014770, time: 2018-03-01 22:38:07, lat: 28.44812, lon: -16.30196, speed: 0.0, course: 0.0
2018-03-01 22:38:08  WARN: Empty address

It also reports an SOS alarm, and the date is 2029-12-31 at time 00.00.00

Your problem is that device reporting time in future. This issue has been discussed countless number of times on the forum. Please use search.