tobadia / petgps Goto Github PK

Hey! can you help me with few questions about this device?:

1. With this cheap modules do you have to interact with the button? Or they start powered "on"?
2. Do they support 3G?
3. that 1-2 MB daily data you said was using what rate? Does the device automatically saves data when there is no movement?

Thanks!

Bought myself too a CAT gps Tracker, its indeed also based on 365GPS (topin)
http://www.topin.hk/web/

is there also an integration possible for Home Assistant?

thnx in advance

Hey, nice Project! These little Trackers are awesome in size and function. The only thing I hate is the hardcoded stuff like the default server for fallback. Anybody who ever tried reverse engeneering these little pcbs? extracting firmware, flashing firmware, modify the firmware, remove the hard coded Server IP, add or modify commands?
Ive searched the whole internet, but seems like nobody ever did this step.

First of all, thank you very much for your project, it is quite interesting how you decrypted the data sent to the server.

Of course, I have a problem regarding the googlemaps API.
I am running this script on a raspberry, even though I had some misconceptions regarding phyton to run the script and in addition to getting an API from google, I was finally able to start the server.

The problem is that the script, at the moment of giving the coordinates, indicates an error that does not appear:

Decoding location-based data using Google Maps Geolocation API ...
Google Maps Geolocation API queried with: {'wifi': [{'macAddress':' e4: ab: 89: 59: 68: 30 ',' signalStrength ': -28}, {' macAddress': 'e4: ab: 89: 59: 68: 00 ',' signalStrength ': -28}, {' macAddress ':' c6: d4: a1: 90: 23: ef ',' signalStrength ': -38}, {' macAddress ':' b0: b2: 8f: 42: ba: 3b ',' signalStrength ': -54}, {' macAddress ':' b0: b2: 8f: 42: b1: 2b ',' signalStrength ': -54}, {' macAddress ':' b2: 68: e6: 62: 95: 4f ',' signalStrength ': -57}, {' macAddress ': '60: 08: 10: 0f: 1b: d4', 'signalStrength': -60 }, {'macAddress': 'c0: 25: e9: 64: 2e: 2c', 'signalStrength': -73}], 'gsm-cells': [{'locationAreaCode': 29721, 'cellId': 9038, 'signalStrength': -90}, {'locationAreaCode': 29721, 'cellId': 8456, 'signalStrength': -100}, {'locationAreaCode': 29721, 'cellId': 21511, 'signalStrength': -100}, {'locationAreaCode': 29721, 'cellId': 8454, 'signalStrength': -100}], 'gsm-carrier': {'n_gsm_cells': 4,' MCC ': 730,' MNC ': 2},' gps ': {}}
[191.125.49.87] ERROR: socket was closed due to the following exception:

This thread is now closed

Do you ahve any idea how to solve that? or is it is okay?

Hi, do you have some examples of device communication data? If yes, could you please share them?

Hi
Thanks for sharing with the community your work.
I have cloned your repo, and I have created a key for maps API.

But when I receive an incoming connection I receive this error:

127.0.0.1:41748 has connected.
[ 127.0.0.1 ] IN Hex : 474554202f20485454502f312e310d0a486f73743a206c6f63616c686f73743a393939390d0a557365722d4167656e743a204d6f7a696c6c612f352e3020285831313b205562756e74753b204c696e757820693638363b2072763a32342e3029204765636b6f2f32303130303130312046697265666f782f32342e300d0a4163636570743a206170706c69636174696f6e2f786d6c2c6170706c69636174696f6e2f7868746d6c2b786d6c2c746578742f68746d6c3b713d302e392c746578742f706c61696e3b713d302e382c696d6167652f706e672c2a2f2a3b713d302e350d0a4163636570742d456e636f64696e673a206964656e746974790d0a582d466f727761726465642d466f723a2038322e38342e31312e3137370d0a582d466f727761726465642d486f73743a207265706f72742e70726f67726573736966792e69740d0a582d466f727761726465642d5365727665723a207265706f72742e70726f67726573736966792e69740d0a436f6e6e656374696f6e3a204b6565702d416c6976650d0a0d0a (length in bytes = 394 )
[ 127.0.0.1 ] ERROR: socket was closed due to the following exception:
'20'
This thread is now closed.

What is 20 exception?

EDIT:
I have printed the stack trace:

Traceback (most recent call last):
  File "/home/progressify/Documenti/dev/petGPS/gps_tcp_server.py", line 93, in handle_client
    keepAlive = read_incoming_packet(client, packet)
  File "/home/progressify/Documenti/dev/petGPS/gps_tcp_server.py", line 131, in read_incoming_packet
    protocol_name = protocol_dict['protocol'][packet_list[1]]
KeyError: '20'

Hello,

I'm just starting using this python script and facing a strange issue for me, which maybe is normal I don't know.

Before switching to the script, GPS365 report a wifi position on 04 August which is good :

then switched to my computer, and it report a position from 27 July which was a good position this day but outdated :

pi@ragnar:~ $ tail logs/location_log.txt -f
2021/08/04 17:41:00 10.0.0.2 359339075435809 LBS-GSM-WIFI 2021/07/28 21:34:51 1 +48.4064013 +2.7940479 116.1
2021/08/04 17:43:01 10.0.0.2 359339075435809 LBS-GSM-WIFI 2021/07/28 21:34:51 1 +48.407402100000006 +2.7956312 1175
2021/08/04 17:45:01 10.0.0.2 359339075435809 LBS-GSM-WIFI 2021/07/28 21:34:51 1 +48.407402100000006 +2.7956312 1175
2021/08/04 17:47:07 10.0.0.2 359339075435809 LBS-GSM-WIFI 2021/07/28 21:34:51 1 +48.407402100000006 +2.7956312 1175
2021/08/04 17:49:02 10.0.0.2 359339075435809 LBS-GSM-WIFI 2021/07/28 21:34:51 1 +48.407402100000006 +2.7956312 1175
2021/08/04 17:51:03 10.0.0.2 359339075435809 LBS-GSM-WIFI 2021/07/28 21:34:51 1 +48.407402100000006 +2.7956312 1175
2021/08/04 17:53:04 10.0.0.2 359339075435809 LBS-GSM-WIFI 2021/07/28 21:34:51 1 +48.407402100000006 +2.7956312 1175
2021/08/04 17:55:04 10.0.0.2 359339075435809 LBS-GSM-WIFI 2021/07/28 21:34:51 1 +48.407402100000006 +2.7956312 1175
2021/08/04 17:57:14 10.0.0.2 359339075435809 LBS-GSM-WIFI 2021/07/28 21:34:51 1 +48.407402100000006 +2.7956312 1175
2021/08/04 17:58:35 10.0.0.2 359339075435809 LBS-GSM-WIFI 2021/07/28 21:34:51 1 +48.407402100000006 +2.7956312 1175
2021/08/04 18:00:36 10.0.0.2 359339075435809 LBS-GSM-WIFI 2021/07/28 21:34:51 1 +48.407402100000006 +2.7956312 1175
2021/08/04 18:02:36 10.0.0.2 359339075435809 LBS-GSM-WIFI 2021/07/28 21:34:51 1 +48.407402100000006 +2.7956312 1175
2021/08/04 18:04:42 10.0.0.2 359339075435809 LBS-GSM-WIFI 2021/07/28 21:34:51 1 +48.407402100000006 +2.7956312 1175

here is an example of received frames :

[ 10.0.0.2 ] IN Hex : 78780713374c0819390d0a (length in bytes = 11 )
The current packet is for protocol: status which has method:
[ 10.0.0.2 ] STATUS : Battery = 55 ; Sw v. = 76 ; Status upload interval = 8 ; Signal strength = 25
[ 10.0.0.2 ] IN Hex : 78780517210728193451caeac75f117c4fcaeac75f117e4fcaeac75f117d5118d6c7902df45b1ad6c7902df45c0200d01455fc1d985a55fc1d9664000d0a (length in bytes = 62 )
The current packet is for protocol: wifi_offline_positioning which has method: datetime_position_response
[ 10.0.0.2 ] POSITION/WIFI : BSSID = ca:ea:c7:5f:11:7c ; RSSI = -79
[ 10.0.0.2 ] POSITION/WIFI : BSSID = ca:ea:c7:5f:11:7e ; RSSI = -79
[ 10.0.0.2 ] POSITION/WIFI : BSSID = ca:ea:c7:5f:11:7d ; RSSI = -81
[ 10.0.0.2 ] POSITION/WIFI : BSSID = 18:d6:c7:90:2d:f4 ; RSSI = -91
[ 10.0.0.2 ] POSITION/WIFI : BSSID = 1a:d6:c7:90:2d:f4 ; RSSI = -92
[ 10.0.0.2 ] POSITION/LBS : LAC = 22012 ; CellID = 7576 ; MCISS = -90
[ 10.0.0.2 ] POSITION/LBS : LAC = 22012 ; CellID = 7574 ; MCISS = -100
[ 10.0.0.2 ] OUT Hex : 787807172107282134510D0A (length in bytes = 12 )
Decoding location-based data using Google Maps Geolocation API...
Google Maps Geolocation API queried with: {'wifi': [{'macAddress': 'ca:ea:c7:5f:11:7c', 'signalStrength': -79}, {'macAddress': 'ca:ea:c7:5f:11:7e', 'signalStrength': -79}, {'macAddress': 'ca:ea:c7:5f:11:7d', 'signalStrength': -81}, {'macAddress': '18:d6:c7:90:2d:f4', 'signalStrength': -91}, {'macAddress': '1a:d6:c7:90:2d:f4', 'signalStrength': -92}], 'gsm-cells': [{'locationAreaCode': 22012, 'cellId': 7576, 'signalStrength': -90}, {'locationAreaCode': 22012, 'cellId': 7574, 'signalStrength': -100}], 'gsm-carrier': {'n_gsm_cells': 2, 'MCC': 208, 'MNC': 20}, 'gps': {}}
Google Maps Geolocation API returned: {'location': {'lat': 48.407402100000006, 'lng': 2.7956312}, 'accuracy': 1175}
[ 10.0.0.2 ] OUT Hex : 787815172b34382e3430373430322C2b322e3739353633310D0A (length in bytes = 26 )

so I don't know why this is an old one ? note there is no gps location for now.

board is ZX303, pet is a Beagle Dog but we don't care :)

thanks.

Hi

Congratulation for your work. Could you to do a manual or documentation to implement yor develop. I purchase the ZX303 model but I'm not can implement your PETGPS work.

Thanks

Hi. I see that you read a packet without any loops with one recv. But afaik it can returns partial data.

I could be wrong, didn’t jump deep into the code.

Hey,
I'd really like to fork this, but I would love if you could add license to your repository, so it is clear what your conditions for reusing this code are.

Congratulations on your work, I am trying to configure a topin zx620 gps, and petGPS works perfectly, but this device allows you to send audio to the server and I can't get the server to receive it, do you know anything about this? Thanks