Filter Acc Status, Computed Attributes?
failure to recognize the acc byte in the positioning packet
What do you mean by this?
In the location packets, a closed message appears even though the ignition is on, or it may think that the result is so due to a protocol error. I can send you the protocol document if you would like to review it. If we can make the protocol fully compatible, we want to use more than 200 devices
If you're not aware, most GT06 devices don't send ignition status with the location message. So it's not a compatibility problem. It's a cheap device problem.
I contacted the manufacturer, they said it doesn't send acc information but traccar may be misinterpreting the protocol. It works flawlessly in its own system, in Traccar, the ignition status constantly changes on/off while the vehicle is moving, and the tampering alarm is also triggered while it is parked. If you would like to take a look at the protocol document, I can send it to you.
If you would like to look at the document, I would be grateful and I am curious about your comments.
If you want us to investigate it, we do have professional services option available.
Can we achieve this with computed attributes?
We want to filter the acc status in the positioning packet.
We only want to use the acc status from the heartbeat package
Note: When Acon/off changes, the device will instantly upload a heartbeat packet to the platform.
Therefore, failure to recognize the acc byte in the positioning packet will not cause a delay in the acc change.
Gt06 variant protochol