A few questions from the beginner (units, distances, states, iButton)

Hi,
At the outset, I would like to apologize for a large number of questions - I have a Traccar server recently and I am trying to understand some things.

1. Speed ​​unit - the speed unit in the interface is kn. I would like them to be km / h. For this, I set the speed unit to km / h in the server settings and saved it. Unfortunately, the units have not been updated - they are still kn, and when I access the server's attributes after refreshing the page, I cannot see the previously saved attributes.
2. Distance - I don't know what's going on here, but completely random distances appear. I am 20 km from one of the devices and the indicated distance is 0.05 km.
3. Total distance - I entered the mileage of the car in the attributes of the device, because I thought that the distance traveled with the locator is added to this value. Yesterday I entered the mileage of the car, and today, after driving 50 km, I checked whether the 50 km traveled was added to the mileage value - unfortunately not. What am I doing wrong?
4. Status and location of individual devices - is it possible to add other data here? I have Teltonika FMB120 locators and I would like to have visible states of all 3 inputs (and preferably also outputs). I can only see the "Di1" state on the preview, unfortunately I do not see the state of the other inputs.
5. Problem with the iButton Dallas reader - I added an e-mail notification when a driver is authorized. Unfortunately, from what I noticed, reading is often delayed and e-mail notifications often do not come. Is it possible to do something about it, to check it more often? SMS messages from the GPS module about the change of the dallas key status come immediately, only from the traccar service it often works with a very long delay.

I apologize in advance if any of my questions are basic. I searched the forum for answers to my questions, but unfortunately I did not find it.
I will be grateful for the hints.

1. Not sure how you searched, but simply Googling "traccar speed units" gives me correct result immediately.
2. Distance is distance from previous location, not from you.
3. Sounds like you are doing correct thing. You should probably check what your device reported in between.
4. This sounds like a device issue. Probably need to contact Teltonika support.
5. We don't have a notification for authorized driver, so it's interesting that you are receiving something.

Thank you for your quick reply.

1. I did exactly as here: https://www.traccar.org/forums/topic/change-speed-unit-in-traccar-server-online/#post-25073 Unfortunately, after saving the attributes and refreshing the page, the saved ones disappeared attributes.
2. Ohh, I get it. I thought it was a distance from the device I am checking from. :)
3. Ok, then I'll try to reconfigure both the device and the traccar.
4. Thank you, then I'll check it out.
5. I meant the driver change notification, so also about putting the dallas key to the socket. When I put the dallas key to the reader, it takes a while for the information about the read key to appear in the status and location tab. Is it possible to shorten the time the traccar reads this? Teltonika sends this information immediately.
   I will be grateful for your response.

1. Either you didn't save it correctly or there was some issue with saving. Check browser console.

2. Let's start with clearing your assumption that there's some delay. Traccar pushes the data immediately. There are no delays, unless something is not working correctly, like WebSocket connection is failing because of your network restrictions for example. As for the event, it's a change of driver, so it requires to have different driver id in a previous location report. If your device doesn't report driver id in every message, you won't get an event, which is probably what's happening in your case.

1. Okay, I'll check it out later and come back with the answer.

2. Thank you for the explanation! Now I can see that the delay I mentioned is due to the status of the device - information about logging in the driver is sent only when the device status is online (green color). If the device has been offline for several minutes (red color), information about driver changes is not sent. When the device has been offline for several minutes and the driver is authorized, the notification will not be sent.
   By the way, I wanted to ask if it is possible to make a notification when the dallas key is applied and taken? My point is to get information when the key is announced on site and taken (such key deposit).

You can use attribute copying to keep old driver id. Then driver change should work.

I don't know what you mean. Can you tell me more about it?

You can probably search. It has been discussed before. Basically attributes copying ensures that you have driver id in every message by copying it from previous message if missing.

Thank you, I will look for more information on this topic and let you know.

I did some reading on the forum and found that adding the following code to the traccar.xml file should help.

<entry key='processing.copyAttributes.enable'>true</entry>
<entry key='processing.copyAttributes'>driverUniqueId</entry>

Unfortunately, I have the impression that it does not work in my case as I expected. I want the same ibutton identifier to be read a several times in a row. Besides, is there anything I can do to get the traccar notifications about the dallas key application immediately, whether the device is online or offline?
I want the traccar to receive information about the applied ibutton key immediately and that the same ibutton key can be read several times in a row.

I want it to work like this because there will be an ibutton in the glove compartment of the company car along with the car key. I want to control the presence of the key in the socket, so that I will know if the car keys are in place (the ibutton key is in the socket = the car keys are in place; the ibutton key is not in the socket = the car keys are not in place).

Unfortunately that's not supported. One workaround you can try is to create an alarm using computed attributes.