Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
software:timingunits:tcpimporter [2024/08/09 12:05] henriksoftware:timingunits:tcpimporter [2024/10/02 07:47] (current) – external edit 127.0.0.1
Line 1: Line 1:
 {{indexmenu_n>100}} {{indexmenu_n>100}}
  
-====== Supported timing devices ======+====== Generic TCP importer ======
  
 Using a very simple text-based TCP protocol, you can have your own devices or integration component connect into BBT, and import raw time records this way, just like any natively supported box. Using a very simple text-based TCP protocol, you can have your own devices or integration component connect into BBT, and import raw time records this way, just like any natively supported box.
Line 42: Line 42:
 record.add;ok;id=42 record.add;ok;id=42
  
-Records can be updated using the record.update command. The arguments are the exact same as for record.add, but id is optional.+Records can be updated using the record.update command. The arguments are the exact same as for record.add, but id is required.
 If a record with the provided id does not exist, it might be created. If a record with the provided id does not exist, it might be created.
 +
 +== Device status ==
 +It is possible to send periodic device status information, such as vendor, model, battery information, GPS position, firmware version, read rates and much more. Contact us for details on the supported values.
 +
 +Example command:\\
 +status;device.vendor=My company;device.model=Cool Device Pro;power.battery.available=1;power.battery.pct=53;gps.satellites=7;temp.cpu=42
 +
 +Responses:\\
 +record.status;ok
 +
  
 == Inactivity == == Inactivity ==
Line 54: Line 64:
 Response:\\ Response:\\
 ping;ok ping;ok
 +