processing.copyAttributes not working for GPS103

Hi Anton,
I have enabled copyAttributes for ignition,battery,power . Device sending ignition details once but seems copyAttributes not working. Ignition is not available in next data.
I want ignition data in each row.

I am using Traccar 3.14 Version.

Below is the sample data.

|        6 | {"distance":33.6,"totalDistance":9375477.53,"motion":true}                                     | 2018-02-19 03:38:09 |
|        6 | {"distance":16.6,"totalDistance":9375443.93,"motion":true}                                     | 2018-02-19 03:37:39 |
|        6 | {"distance":2.25,"totalDistance":9375427.33,"motion":true}                                     | 2018-02-19 03:37:09 |
|        6 | {"distance":30.32,"totalDistance":9375425.08,"motion":true}                                    | 2018-02-19 03:37:08 |
|        6 | {"distance":8.49,"totalDistance":9375394.76,"motion":false}                                    | 2018-02-19 03:36:39 |
|        6 | {"distance":9.15,"totalDistance":9375386.27,"motion":true}                                     | 2018-02-19 03:36:09 |
|        6 | {"distance":11.75,"totalDistance":9375377.12,"motion":false}                                   | 2018-02-19 03:35:39 |
|        6 | {"distance":0.0,"totalDistance":9375365.37,"motion":false}                                     | 2018-02-19 03:35:09 |
|        6 | {"distance":9.7,"totalDistance":9375365.37,"motion":false}                                     | 2018-02-19 03:34:39 |
|        6 | {"distance":13.98,"totalDistance":9375355.67,"motion":false}                                   | 2018-02-19 03:34:09 |
|        6 | {"distance":0.0,"totalDistance":9375341.69,"motion":false}                                     | 2018-02-19 03:33:39 |
|        6 | {"distance":0.0,"totalDistance":9375341.69,"motion":false}                                     | 2018-02-19 03:33:09 |
|        6 | {"distance":6.39,"totalDistance":9375341.69,"motion":false}                                    | 2018-02-19 03:32:38 |
|        6 | {"alarm":"powerOn","ignition":true,"distance":2.39,"totalDistance":9375335.3,"motion":true}    | 2018-02-19 03:32:11 |
|        6 | {"alarm":"powerOff","ignition":false,"distance":3.52,"totalDistance":9375332.91,"motion":true} | 2018-02-19 03:32:08 |
|        6 | {"alarm":"powerOff","ignition":false,"distance":2.04,"totalDistance":9375329.39,"motion":true} | 2018-02-19 03:31:59 |

Is that the fix time in the second column? If yes, you would need to check server time as well.

Also, please provide your config fragment related to the attribute copying.

Yes, 30 second is fix time for data interval.

Below is the details of copy attributes.

<entry key='processing.copyAttributes'>power,ignition,battery</entry>

Do you have processing.copyAttributes.enable?

Yes,

<entry key='processing.computedAttributes.enable'>true</entry>
<entry key='processing.copyAttributes'>power,ignition,battery</entry>

I would recommend you to read my previous comment more carefully. And then keep looking at your config until you see the difference.

Oh sorry Anton, Now problem has been resolved.
Again Thanks for kind response.