With watch protocol, I know the first warning is because there is no GPS reported, but the second error is weird one (NullPointerException (DeviceManager:427 < *:416 < FuelDropEventHandler:50 < BaseEventHandler:29 < ...)
), with this error cannot get the location of the device, and the whole bellow log is appearing every 5 minutes.
2022-01-19 09:10:24 INFO: [1a475c34] connected
2022-01-19 09:10:24 INFO: [1a475c34: watch < 171.73.212.92] HEX: 5b33472a383830393033323636392a303030392a4c4b2c302c302c37365d
2022-01-19 09:10:24 INFO: [1a475c34: watch > 171.73.212.92] HEX: 5b33472a383830393033323636392a303030322a4c4b5d
2022-01-19 09:10:24 WARN: Failed to store position - Data truncation: Incorrect datetime value: '1970-01-01 00:00:00' for column 'fixtime' at row 1 - MysqlDataTruncation (... < QueryBuilder:446 < DataManager:429 < DefaultDataHandler:40 < ...)
2022-01-19 09:10:24 WARN: [1a475c34] error - NullPointerException (DeviceManager:427 < *:416 < FuelDropEventHandler:50 < BaseEventHandler:29 < ...)
2022-01-19 09:10:24 INFO: [1a475c34] disconnected
Any possible reason for it?
Maybe attributes field is null?
Yeah the field is null, I will try to add something to it and will share the result.
I am confirming that adding an attribute to the device solved the issue.
Thanks @Anton for your help!
With watch protocol, I know the first warning is because there is no GPS reported, but the second error is weird one (
NullPointerException (DeviceManager:427 < *:416 < FuelDropEventHandler:50 < BaseEventHandler:29 < ...)
), with this error cannot get the location of the device, and the whole bellow log is appearing every 5 minutes.Any possible reason for it?