Hi everyone,
After upgrading to Traccar 6.10, we noticed that the "motionstate" column in the "tc_devices" table no longer reflects the real-time motion status of devices.
We usually rely on this column to filter and show devices that are currently moving (or stopped), but it seems the value isn’t updating correctly according to the latest device motion status.
Before we dive deeper into debugging, I just wanted to check if:
There were any changes in how motionstate is updated in version 6.10?
Is it now tied to a different logic or event (like motion attribute, or server-side computation)?
Or is there a recommended new method to identify moving devices at database level?
Would really appreciate if anyone could confirm how this field behaves in the latest version, or point me to any related documentation or release note.
Thanks in advance!
I think it is still correct field to use.
Hi Anton ,
Thanks for confirming.
I think there was a tiny glitch somewhere that "tc_device" table "motionstate" did not update , we did a reboot and things looks fine now.
Hi everyone,
After upgrading to Traccar 6.10, we noticed that the "motionstate" column in the "tc_devices" table no longer reflects the real-time motion status of devices.
We usually rely on this column to filter and show devices that are currently moving (or stopped), but it seems the value isn’t updating correctly according to the latest device motion status.
Before we dive deeper into debugging, I just wanted to check if:
There were any changes in how motionstate is updated in version 6.10?
Is it now tied to a different logic or event (like motion attribute, or server-side computation)?
Or is there a recommended new method to identify moving devices at database level?
Would really appreciate if anyone could confirm how this field behaves in the latest version, or point me to any related documentation or release note.
Thanks in advance!