Track Any Device
Sign in

TAD101 universal protocol

Present your idea

TAD101 is an open, self-hosted protocol designed to be extended. If you have a device, sensor, or use case that isn't covered yet, we want to hear from you — and help you ship it.

What you can build

Hardware devices

  • Custom GPS tracker (ESP32 + Neo-8M)
  • Smart helmet with SOS button
  • School bag tracker for children
  • Livestock / pet collar tracker
  • Vehicle OBD-II adapter feeding TAD101
  • Environmental sensor node (temperature, humidity, air quality)
  • Industrial asset tracker
  • Personal safety wearable

Software integrations

  • Flutter / React Native tracking app
  • Web dashboard widget (embed the TAD101 map anywhere)
  • Home Assistant integration
  • MQTT ↔ TAD101 bridge
  • Custom alert rules & automations
  • Delivery / fleet management overlay
  • Geofencing notification service

How to submit your idea

Option A — New device type

  1. Fill in the proposal template below.
  2. Open a GitHub issue with label tad101-device-proposal.
  3. We'll create your DeviceType and a documentation page like this one.

Option B — New sensor

  1. Describe the sensor: name, unit, data type, how it's produced.
  2. We'll add it to the Sensor Registry and update the TAD101 payload spec.

Option C — New protocol bridge

If you have a device on a different protocol (GT06, MQTT, CoAP) and want it to feed into TAD101, propose a bridge driver implementing DeviceDriverInterface.

Device type proposal template

Name:           [Your device name]
Slug:           [lowercase_underscore]
Category:       [wearable | vehicle | industrial | personal | other]
Connection:     [WiFi | BLE+Gateway | LTE | LoRa | Other]
Sensors:        [list every sensor it produces]
Special Events: [any events beyond standard update/sos/heartbeat]
GSM Commands:   [if any SMS commands, list format]
Open Source:    [yes/no — will you share the firmware/code?]
Hardware Cost:  [approximate BOM cost USD]
Description:    [what problem does this solve? who uses it?]

Distribution model

Once your device type is accepted:

  • It gets a permanent documentation page in this system.
  • It appears in the Filament device type catalogue.
  • Customers can select it when adding a device.
  • You can distribute pre-configured hardware.
  • Your onboarding guide is built into the platform UI.