Leaf Spy Protocol (HTTP pass + Lat/Long)
Leaf Spy on HTTP 5193: pass is the bind key, Lat and Long plot, reply status 0, RPM/63 is speed.
On Traxelio
What Leafspy trackers do once they are on Traxelio
Point this protocol at Traxelio
Point Leafspy at Traxelio
-
1
Capture a Leaf Spy fingerprint
Confirm an HTTP query or body with pass, Lat, and Long.
-
2
Point Leaf Spy at 5193
Configure only Leaf Spy to HTTP 5193. Leaf Spy on 5193 is not Moovbox on 5212 or Path Away on 5099.
-
3
Wait for status 0
A known pass gets HTTP 200 and status 0. An unknown pass gets HTTP 400.
-
4
Prove one Leaf Spy fix
Send one request with Lat and Long not both 0 on 5193 and verify a map point.
Still offline after GPS lock
Leafspy still not landing
- Leaf Spy aimed at the wrong port
Leaf Spy on 5193 is not Moovbox XML on 5212 or Path Away on 5099.
- HTTP 400 instead of status 0
The pass field is unknown. Bind that value before debugging GPS.
- Status 0, pin did not move
Lat and Long were both 0, so the last location was reused. Send a non-zero pair.
FAQ
Leafspy leftover questions
Does Leaf Spy send Concox 0x7878 frames?
No. Leaf Spy is an HTTP query or body with pass, Lat, and Long. Concox families use 0x7878 binary login.
Which field is the Leaf Spy bind key?
pass. Lat and Long hold the coordinates. Extra keys such as RPM, Elv, SOC, user, ChrgMode, and Odo ride along.
Why does a Leaf Spy request succeed without a map move?
A known pass is enough for status 0. If Lat and Long are both 0, Traxelio reuses the last stored location.
How is Leaf Spy speed derived?
RPM is stored as engine RPM. Speed is that same RPM divided by 63 and treated as km/h.
Can a Leaf Spy unit run SMS setup or a controlled-action flow?
This dialect is positions only. Leaf Spy Pro is the listed device. There is no SMS family on this row.