Position invalid after Session/IP Change

I have a h02 China device, i have a seen an "issue" till the last days and im really wondering about it.
Today at exactly 10am, the IP address from the tracker was changed:
XX.XXX.XXX.236 to XX.XXX.XXX.126, i also got a new (?!) session for this connection:

2022-04-20 10:00:01  INFO: [d90445bb] id: 7201XXXX3, time: 2022-04-20 09:59:50, lat: 49.XX881, lon: 9.XX139, course: 0.0
2022-04-20 10:02:57  INFO: [9c3ed13b] connected
2022-04-20 10:02:57  INFO: [9c3ed13b: h02 < XX.XXX.XXX.126] HEX: XXX -> decoded: 
*HQ,720XXXX23,V1,080246,V,49XX.XX86,N,009XX.8834,E,000.00,000,200422,FFFFF9FF,262,03,0,0,6#
2022-04-20 10:02:57  INFO: [9c3ed13b: h02 > XX.XXX.XXX.126] HEX: XXX -> decoded: *HQ,72XXXX23,V4,V1,20220420080257#

Till this session chnage all ingoing new positions are marked as invalid in the reports.

I noticed this the last days more times, so i think it should be a problem if the IP was changed?! Maybe its a known issue? Solving this needs a restart on the device (which is not comfortable if i have to do it once a day)

The question from my side would be, what are the parameters that a transmitted position is a valid or a invalid once.

This sounds like a device issue to me. Not sure why it's in the server forum. You can see that the device is reporting "V", which means invalid GPS location.

Or is it only a option like v=lbs, a=GPS? Or something else? I opened it in the server topic because I thought it could be a server issue.

Just had a look into the h02 protocol, yes v stands for invalid....

Shity device, why does it sent out almost known "invalid" positions... ;-)

Anton, is there any possibility to send a restart command automaticly after N times of unvalid positions? Maybe by adding something like a cron job which checks all devices?

Sure, you can have a script for that or you can change the code.

I use it on windows and I stuck on the jar files. With "board equipment" it's not possible? Or via the API?