Forward URL storing accuracy values between curly brackets instead of the value sent by the device
I suspect you are using outdated version of Traccar.
Version 3.17, I'm scared about having the last version running with my current implementation, are the changes too big between such versions?
You can check blog and/or GitHub for information about changes.
It's working but I'm receiving a maldormed URI exception, because of a empty space in the name of the device, how can I make it string url encoded in that case from the config file? or is it a way to avoid the malformed URL comming from the database? the name has empty spaces.
2018-08-28 05:39:55 WARN: [5bf6895a] error - java.net.URISyntaxException: Illegal character in query at index 158: http://mydomain.com/position?uniqueId=151717120&deviceId=151717120&valid=true&fixTime=1535427528000&deviceTime=1535427528000&protocol=osmand&name=IVECO TRUCK&latitude=7.0611547&longitude=-73.1070554&altitude=0.0&speed=0.0&course=0.0&accuracy=23.090999603271484&address=12-528+Cl.+200%2C+Floridablanca%2C+Santander%2C+CO&gprmc=$GPRMC,033848.000,A,0703.6693,N,07306.4233,W,0.00,0.00,280818,,*14&attributes=%7B%22batteryLevel%22%3A62.0%2C%22distance%22%3A2.6%2C%22totalDistance%22%3A8873818.24%2C%22motion%22%3Afalse%7D - UriBuilderException (... < WebDataHandler:135 < BaseDataHandler:27 < ... < *:29 < ... < *:29 < ...)
2018-08-28 05:39:55 INFO: [5bf6895a] disconnected
You need to wait for next release. It has a fix for it. Or build from source.
Thank you very much, I just removed that field and everything worked out of the box. thanks
I have enabled forward URL and it's working nice, but in the endpoint the data for accuracy it's been stored as "{accuracy}", the HEX output in the logs is showing there is accuracy data comming from the device, so this is the url I'm using:
I did the test with POSTMAN and if I send accuracy the data it's correctly stored, somehow the accuracy is not been replaced in the forward URL, this is the HEX output: