Skip to main content

First real tracker

The goal is to see one real GPS point in Phimi, not to finish the platform.

Already confirmed​

  • 1NCE SIM active, 4G session online on Sunrise.
  • APN sensor.net accepted by the tracker.
  • Two-way SMS works.
  • Current server: a.igps123.com:8888.
  • Not yet: a GPS fix in the last diagnostic, or any connection to Phimi.

Steps​

  1. Allowlist the tracker. Add its 12-digit terminal id to device-allowlist in the phimi-ingest Secret and restart the ingest pod. The id is in the 0x0100 header; iGPS123 or the IMEI suffix usually reveals it.
  2. Expose the endpoint. Forward public TCP 8888 on the router to 192.168.100.97:30888. From outside the LAN (for example a phone hotspot): nc -vz 85.195.196.223 8888, then phimi-simulator --addr 85.195.196.223:8888 --terminal <an allowlisted test id>.
  3. Get a fix first. Charge the V53 and test it outdoors until it reports a GPS position on iGPS123.
  4. Check the redirect syntax. Send IP# by SMS and note the reply, including the undocumented fourth field (IP,a.igps123.com,8888,0#).
  5. Redirect one tracker only. SMS IP,85.195.196.223,8888# (or a DNS name once one exists). Keep IP,a.igps123.com,8888# ready to send back.
  6. Watch it arrive. 
    kubectl -n phimi logs deploy/phimi-ingest -f
    kubectl -n phimi exec deploy/phimi-ingest -- wget -qO- 127.0.0.1:9090/internal/sessions
    Expect registration, authenticated, then location and heartbeat lines. The status page in the dashboard lists the connected tracker.
  7. Settle the open questions. Compare the logged recorded_at with the actual time to confirm PHIMI_DEVICE_UTC_OFFSET_MINUTES; plug and unplug the charger to read the charging byte; note the heartbeat interval.
  8. Prove reconnection and rollback. Toggle flight mode and check the tracker comes back; then send it to iGPS123 and back once before migrating the other three.

If nothing arrives​

  • phimi_ingest_connections_total stays at 0: port forward or public IP problem.
  • phimi_ingest_unknown_devices_total increases: the terminal id is not allowlisted; the log shows its last four digits.
  • phimi_ingest_auth_failures_total increases: the tracker reuses iGPS123's auth code. Phimi answers with a failure, which should make it register again; if it does not, the tracker may need a restart (RESET# per the SMS command sheet).
  • phimi_ingest_frames_rejected_total increases: capture the raw bytes for a new fixture.