setbox support for eelink TK419

TomD

Hi, I am trying to confugure my eelink TK419 tracker via setbox (sorry I messed up topic title, I meant to write setbox not flexbox but can't edit it). I had to choose an older device (TK319) to see options. The protocol is the same for TK319, TK418, TK419, etc. as they all use 2.0 protocol, so can you enable options for TK419? Also, the majority of settings in the native app are missing from flexbox. Would it be possible to add these? I have attached screen prints from the native app. Only cut engine (relay) is currently available in setbox, but it looks a little different. Here is the documentation for 2.0 (I'm sure you have it already but posting it here for reference):

https://www.eelinktracker.com/Images/default/EELINK%20Device%20Protocol%20V2.0.3%20(A4).pdf

"Operation" menu in native app

Alarm menu (all can be enabled or disabled, with screen prints for additional options below)

Options for "motion alarm"

Options for "speed alarm"

Options for "shift alarm"

Input for "administrator number"

Input for "terminal number"

Options for "working mode"

Options for "cut engine off"

namo

Hello TomD ,
I've added settings for Eelink TK419 and some alarms settings for Eelink devices. Changelog is here. Could you please test the settings and give your feedback to me?
I'll try to add more settings for Eelink devices, but this will take some time.

namo

Hey TomD ,
I've added a series of settings for Eelink TK419: alarms settings and geofences and managers settings. You may follow eelink changelog thread on the forum to be notified about the changes in Eelink protocol implementation in flespi.
Thank you for your assistance with testing the settings with a real tracker.

TomD

Also, is there a simple way to send custom commands to the tracker via internet using setbox? I have a data only SIM in the tracker so it's not very easy to send custom commands via SMS (I have to swap out the SIM with one that has SMS, send the command, then swap back to the data only SIM). I tried to follow the docs to figure it out how to send a command via REST but it looks very complicated with tokens, etc. Would be nice if one could just do it via setbox?

shal

TomD I think the best way to contact us with a request to integrate more settings to the protocol is via HelpBox. In that mode we will have access to a device to test these settings.

Regarding the second question, if I got you correctly, you may use curl sample to deliver command to the device using REST API call. Please check this guide about commands and settings, should be easy to understand and follow.

TomD

namo Thanks, I just tested and it looks like it is not correctly reading the alarm settings (it shows nothing set when you try to read or refresh) but when you send a new setting it works (verified by pulling up the native app to read the settings). Also, I'm having some issues with the alarms settings page as it gets stuck on reading and the page eventually crashes with script error.

TomD

Also, now my device keeps getting disconnected due to perpetual error.

301: device disconnected (received data violates channel's protocol)

error_text :

"0000b8 [eelink:747:32] in settings/@speed_alarm/parse: {ext} [9]: not an integer string: '0.00'\n by [eelink:329:4] in @instruction_package\n by [eelink:135:7] in @packet"

TomD

Also, not sure if related to shift fence getting stuck "reading" as well but I noticed this typo (bolded) in name:

317: the command to request or change the setting has been sent
.
.
.
name :

"shirt_fence"

dexif

Hello. Thanks for your report. We will check it.

TomD

Another bug, if you update the backend server uri via setbox you need to leave out the quotes and the tcp:// prefix. For example if you add quotes "tcp://server.com:port" (which is how it shows up pre-populated followed by ip in parentheses) it would set the server to:
tcp://"tcp://server.com:port"(ip)
and if you remove the quotes and ip but leave the tcp:// prefix it would set the server to
tcp://tcp://server.com:port

There may be issues with setting other uri such as AGPS server uri via setbox but I did not want to test and risk bricking my tracker.

namo

Hello TomD,
Thank you very much for testing and reporting the issues!
It would be much easier to fix the issues if I could take a look at raw traffic between the device and the channel. Could you please contact us via flespi support chat from your account?
You may export the traffic from Traffic Viewer and attach it to your message in the support chat. I will take a look into it on Monday.