Unreadable data about nodejs-tk102 HOT 2 CLOSED

I’m no longer updating device support for this package. Even the fakes from the same source have completely different output strings and commands. After wasting more money on 4 different models in order to keep this package current I decided to stay away from closed source trackers. All devices have already died from bad soldering inside anyway.

Your string looks like a heartbeat message where the first number is probably the serial number of the device. It may be listening for commands in order to start sending meaningful data.

The TK102 device I used at first could be watched by only receiving the messages. Setup a TCP server in Node and compare the messages to the current date/time and geolocation of a smartphone. Pretty experimental stuff. Just listen for messages, see what changes when you send different sms commands, and maybe try sending something in return.

I’m sorry I can’t directly help you with your specific model. If I had the device I would start with listening and gradually send back different kinds of commands that are common for other models and see what happens.

from nodejs-tk102.

No problem @fvdm. I eventually got them to work. I messed up with the serial number, works perfectly fine now. Did switch to Traccar at the end since it is a complete opensource suite. Took the Java pain for granted ;-)

from nodejs-tk102.