gl200 protocol devices table positionId set as NULL

SwayDev5 months ago

I upgraded from v5.8 to v6.2 roughly 2 weeks back. (No modifications)

I have a little over 100 devices operating on the gl200 protocol.

All of the devices work and able to see location updates.

However, randomly a fully function device starts behaving strange, the devices table positionId value gets set as NULL(Screenshot of DB and UI attached)

Random few devices, not all of them.

Did not notice any error that stands out in the log either.

Any advise on where or what should I look out for, to troubleshoot this situation?

tra-gl.png

SwayDev5 months ago

Additional information: Found this in the log.

2024-06-23 01:16:02  INFO: [Td1f11109: gl200 < 147.8.7.6] 2b524553503a4754494e462c3432333033362c3836363838343034363130343133392c2c34312c38393130333030303030303036343832303034322c32322c39392c302c2c2c332e38322c302c302c312c302c302c32303234303632323138333135392c35372c2c2c2c2c32303234303632333031313534382c3030354324
2024-06-23 01:16:02  INFO: Event id: 866884046104139, time: 2024-06-23 01:16:02, type: deviceOnline, notifications: 0
2024-06-23 01:16:02  WARN: Failed to store position - Data truncation: Incorrect datetime value: '2168-08-06 23:01:15' for column 'devicetime' at row 1 - MysqlDataTruncation (... < QueryBuilder:469 < DatabaseStorage:95 < DatabaseHandler:44 < ...)
  • Note: Not same device in the earlier screenshot, but same model with same problem.
Anton Tananaev5 months ago

Looks like the timestamp is invalid for some reason.

SwayDev5 months ago

When I decode the data, I get the following information where the time-stamp seems to be correct based on UTC.

+RESP:GTINF,423036,866884046104139,,41,89103000000064820042,22,99,0,,,3.82,0,0,1,0,0,20240622183159,57,,,,,20240623011548,005C$

Any change between v5.8 to v6.2 that could be causing this would you know?

Asking that, because between May 2023 and June 2024 this worked on v5.8 without this problem.

Also since it works most of the day and randomly shows up, this may be specific to this specific packet GTINF shared above?

Anton Tananaev5 months ago

Most likely there were some protocol changes.

SwayDev5 months ago

Would you be able to spare some time on this please? I am unable to figure out the cause.

Also would this be considered a bug since the positionid is getting set as null? Even with a error positionid should never get set back to null right? It should always have the last known location

Anton Tananaev5 months ago

Do you have the protocol documentation?

SwayDev5 months ago
Anton Tananaev5 months ago

Yeah, it doesn't seem to be supported currently. Feel free to create a ticket on GitHub.

SwayDev5 months ago

Created a GitHub issue. #5355

Thank you