• During traveling in my RV I’m using a Teltonika RUTX50 Router, which gots the ability to send its GPS data in realtime to a website. And here comes Trackserver in: I installed the plugin, an it seems to work. But there are so many options to configure, that I’m confused.

    What do I want?

    I want to offer my followers the opportunity to see the route I have traveled and my current location on the aforementioned website. I currently use [tsmap user=bluefire infobar=y markers=e color=blue][/tsmap] which shows part of the route, but not the entire route.
    Which syntax is the right one and how can I limit the displayed data in terms of dates so that, for example, only the current month, year, a specific date or a defined period of time from … to … is displayed?

    The page I need help with: [log in to see the link]

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author tinuzz

    (@tinuzz)

    Hi,

    If you say ‘part of the route’, do you mean the part that is in the most recent track, and not older parts that are in other tracks? Because that would make sense, that is is the way it is supposed to work.

    Perhaps this will disappoint you, but there are only two ways to select tracks to display on the map:

    1. The latest one. This is what you are doing with ‘user=bluefire’.
    2. One or more arbitrary ones, chosen by their track ID. (‘track=x,y,z’).

    There is no way to select tracks based on timestamps, description or other data. This is on the roadmap for a future version.

    If you want to display your whole track by just using ‘user=bluefire’ (or ‘user=@’ if bluefire is also the user publishing the map), you can merge separate tracks into one.

    Best regards,

    Martijn.

    Thread Starter beatus

    (@beatus)

    Hi Martijn, thanks for your quick response! I found this “[tsmap user=bluefire infobar=y markers=e color=blue continuous=y live=y maxage=30d]” which works fine for me. If I leave out “maxage=30d” then it will show ALL and every points, correct? furthermore, I maybe will use one these “

    [tsmap user=bluefire infobar=y markers=e color=blue continuous=y live=y maxage=30d]

    [tsmap user=bluefire infobar=y markers=e color=blue continuous=y live=y fromrel=-30d]

    [tsmap user=bluefire infobar=y markers=e color=blue from=2024-11-01 to=2024-11-09]

    • This reply was modified 1 week, 6 days ago by beatus.
    Plugin Author tinuzz

    (@tinuzz)

    Hi,

    The ‘maxage’ attribute has a different purpose. It means ‘only show a track if it has been updated in the last X time’. It is meant to be used in a situation where you have a map that follows multiple users, but you only want it to show the users that have been active in the past X time. It then either shows the whole track or it doesn’t. Maxage is not about track points.

    Like I said, there is currently no way to display tracks partially (other than using geofences).

    Your suggestions for track selection criteria are sane and I will surely implement something like this. I just can’t make any promises as to when it will be ready. I am currently slowly working towards the next release (probably 6.0) which will get some new features. I’ll do my best to give this some attention too.

    Edit: forgot to say… using ‘live=y’ on an already live map (user=X) is not useful, you can leave it out.

    Martijn.

    • This reply was modified 1 week, 3 days ago by tinuzz.
    Thread Starter beatus

    (@beatus)

    Hi again. When I was starting with Trackserver Plugin, I was using my iPhone with Sendlocation app for test purposes. Now and finally I configured my Teltonika RUTX50 Router and its GPS feature to send data to Trackserver https://wiki.teltonika-networks.com/view/RUTX50_GPS .

    Under “General – GPS- and Satellite” configuration section all positions are enabled . After turning on GPS, on the Map page of RUTX50 the correct position is shown.

    Unfortunately no position-data are shown in Trackserver-Log. It shows the same entry every hour:

    User: bluefire – Name: OsmAnd – Start: 2024-11-14 07:00:36 – End: 2024-11-14 07:00:36 – Points: 0 – Distance: 0 – Source: Unknown

    I interpret the log entry to mean that RUTX50 is connecting to Trackserver-Plugin, but it seems it is not receiving or accepting any data.
    I have tested the following configurations in the “HTTPS Server Settings” section of the router configuration:

    • Full URL without credentials
    • Full URL with credentials:
      As several server entries (url’s) can be configured, I have tested the two above entries individually and also both together. The result is always the same.

    Question: Do additional details have to be configured in the router configuration or what can I change so that Trackserver is satisfied and showing position data?

    • This reply was modified 1 week, 1 day ago by beatus.
    • This reply was modified 1 week, 1 day ago by beatus.
    • This reply was modified 1 week, 1 day ago by beatus.
    • This reply was modified 1 week, 1 day ago by beatus.
    • This reply was modified 1 week, 1 day ago by beatus.
    Thread Starter beatus

    (@beatus)

    in the error-log of my website I only found errors from Trackserver:

    Deprecated:

    Creation of dynamic property Trackserver::$tbl_tracks is deprecated-

    1. wp-content/plugins/trackserver/class-trackserver.php:74
    2. Trackserver->__construct()
      wp-content/plugins/trackserver/class-trackserver.php:1760

    1Plugin: trackserverVeraltetCreation of dynamic property Trackserver::$tbl_locations is deprecated+

    1. wp-content/plugins/trackserver/class-trackserver.php:75

    1Plugin: trackserverVeraltetCreation of dynamic property Trackserver::$options is deprecated+

    1. wp-content/plugins/trackserver/class-trackserver.php:115

    1Plugin: trackserverVeraltetCreation of dynamic property Trackserver::$mapdata is deprecated+

    1. wp-content/plugins/trackserver/class-trackserver.php:90

    1Plugin: trackserverVeraltetCreation of dynamic property Trackserver::$tracks_list_table is deprecated+

    1. wp-content/plugins/trackserver/class-trackserver.php:91

    1Plugin: trackserverVeraltetCreation of dynamic property Trackserver::$bulk_action_result_msg is deprecated+

    1. wp-content/plugins/trackserver/class-trackserver.php:92

    1Plugin: trackserverVeraltetCreation of dynamic property Trackserver::$url_prefix is deprecated+

    1. wp-content/plugins/trackserver/class-trackserver.php:93

    1Plugin: trackserverVeraltetCreation of dynamic property Trackserver::$have_scripts is deprecated+

    1. wp-content/plugins/trackserver/class-trackserver.php:94

    1Plugin: trackserverVeraltetCreation of dynamic property Trackserver::$need_scripts is deprecated+

    1. wp-content/plugins/trackserver/class-trackserver.php:95

    1Plugin: trackserverVeraltetCreation of dynamic property Trackserver_Admin::$options_page is deprecated+

    1. wp-content/plugins/trackserver/class-trackserver-admin.php:349

    1Plugin: trackserverVeraltetCreation of dynamic property Trackserver_Admin::$options_page_url is deprecated+

    1. wp-content/plugins/trackserver/class-trackserver-admin.php:350

    1Plugin: trackserverVeraltetCreation of dynamic property Trackserver_Profile::$current_user is deprecated+

    1. wp-content/plugins/trackserver/class-trackserver-profile.php:17

    1Plugin: trackserverVeraltetCreation of dynamic property Trackserver_Profile::$app_passwords is deprecated+

    1. wp-content/plugins/trackserver/class-trackserver-profile.php:18

    1Plugin: trackserverVeraltetCreation of dynamic property Trackserver_Profile::$username is deprecated+

    1. wp-content/plugins/trackserver/class-trackserver-profile.php:19

    1Plugin: trackserverVeraltetCreation of dynamic property Trackserver_Profile::$url is deprecated+

    1. wp-content/plugins/trackserver/class-trackserver-profile.php:22

    1Plugin: trackserverVeraltetCreation of dynamic property Trackserver_Profile::$url2 is deprecated+

    1. wp-content/plugins/trackserver/class-trackserver-profile.php:23

    1Plugin: trackserverVeraltetCreation of dynamic property Trackserver_Profile::$password is deprecated+

    1. wp-content/plugins/trackserver/class-trackserver-profile.php:28

    1Plugin: trackserver

    Plugin Author tinuzz

    (@tinuzz)

    Hi @beatus ,

    All these deprecation errors have already been fixed in Git.

    Regarding the problem with the empty tracks… I suspect that your router is sending the GPS data in a format that Trackserver doesn’t understand.

    At first glance, it seems that the manual doesn’t say how it sends the data. What I am talking about here, is the actual query parameters that contain the data. To see what I mean, go to your Trackserver Profile page, and look at the ‘Online tracking web address’ for OsmAnd or the custom URL for GSPLogger or PhoneTrack.

    Trackserver understands only specific URL parameters: ‘lat’, ‘lon’, ‘timestamp’ are the most relevant ones. You should ask Teltonika how this works with your particular device, but what also would be a good idea is to look at the access log of your webserver after making sure that the full request (including query parameters) is logged. That will tell you exactly how your device is sending the data. Please post back here if you have that.

    If the device does not support OsmAnd-style URL placeholders, the only option is to change Trackserver to support your device.

    Martijn.

    Thread Starter beatus

    (@beatus)

    I have no ssh or cli access to my web server, so I would need a plugin update to fix all these deprecation errors. Or is there another option?

    the logs shows this (always the same stuff):

    194.xxx.xxx.xxx – – [15/Nov/2024:10:58:34 +0100] “POST /ts/userid/password?imei=999999999999999&serial_num=9999999999 HTTP/2” 400 12 “-” “-“
    194.xxx.xxx.xxx – – [15/Nov/2024:11:00:32 +0100] “POST /ts?imei=999999999999999&serial_num=9999999999 HTTP/2” 403 14 “-” “-“
    194.xxx.xxx.xxx – – [15/Nov/2024:11:00:34 +0100] “POST /ts/userid/password?imei=999999999999999&serial_num=9999999999 HTTP/2” 400 12 “-” “-“
    194.xxx.xxx.xxx – – [15/Nov/2024:10:59:32 +0100] “POST /ts?imei=999999999999999&serial_num=9999999999 HTTP/2” 403 14 “-” “-“
    194.xxx.xxx.xxx – – [15/Nov/2024:10:59:34 +0100] “POST /ts/userid/password?imei=999999999999999&serial_num=9999999999 HTTP/2” 400 12 “-” “-“
    194.xxx.xxx.xxx – – [15/Nov/2024:11:01:32 +0100] “POST /ts?imei=999999999999999&serial_num=9999999999 HTTP/2” 403 14 “-” “-“
    194.xxx.xxx.xxx – – [15/Nov/2024:11:01:34 +0100] “POST /ts/userid/password?imei=999999999999999&serial_num=9999999999 HTTP/2” 400 12 “-” “-“

    • This reply was modified 1 week ago by beatus.
    Plugin Author tinuzz

    (@tinuzz)

    Hi @beatus ,

    I don’t see any location data in those requests….

    Also strange is the alternation between 400 and 403 HTTP status codes. I assume that in ‘/ts/userid/password’, you replaced your actual user ID and your actual password, and those are not the literal URIs? And you changed your trackserver slug to ‘ts’ ?

    Martijn.

    Plugin Author tinuzz

    (@tinuzz)

    Regarding the errors (or rather: warnings)… you can safely ignore them for now, but if you don’t want to, then update the plugin by downloading a ZIP from Github and uploading it to WP:

    https://github.com/tinuzz/wp-plugin-trackserver/archive/refs/heads/master.zip

    Thread Starter beatus

    (@beatus)

    Your assuming is correct:

    I replaced that in ‘/ts/userid/password’ for security reasons because I don’t want this credentials to post here and yes I changed my trackserver slug to ‘ts’.

    Seems that Teltonika RUTX50 is not sending the needed data. I opened up a topic in Teltonika’s support forum:

    • This reply was modified 1 week ago by beatus.
    • This reply was modified 1 week ago by beatus.
    Plugin Author tinuzz

    (@tinuzz)

    Hmmm.. It only just now occurred to me that these are POST requests, not GET. So the search for GPS data in the URI is futile, the data will of course be in the POST payload.

    Unfortunately, that means, it can be ANYTHING, and there is no reason whatsoever to assume that Trackserver will understand this data and be compatible with it.

    If the protocol isn’t documented anywhere, the only reason to make it work with Trackserver is to reverse engineer it. I.e. write a PHP script dat dumps the POST data to a file, and then hope that the client actually sends the data in the first request….

Viewing 11 replies - 1 through 11 (of 11 total)
  • You must be logged in to reply to this topic.