New device type support has been added: Syrus Lynx.
DCT-Syrus protocol is updated, fixed GTERI, GTFRI reports for Syrus Lynx device.
DCT-Syrus protocol is updated, fixed Custom command for Syrus Lynx device.
Device Syrus Lynx has been migrated to the btg-iot protocol
Device Syrus Lynx has been returned to the dct-syrus protocol
DCT-Syrus protocol is updated, fixed Device Status field parsing for GTFRI, GTERI reports from Syrus Lynx device.
DCT-Syrus protocol is updated, fixed GTBAA report parsing, added parsing of GTUPD report from Syrus Lynx device
parameter renaming announcement which will happen in a week (May 22): parameter total.idle.seconds will be renamed to total.idle.time
New parameter position.valid added for Lynx devices. Derived from GNSS Accuracy field: true when GNSS fix is successful (HDOP 1-50), false when no fix (HDOP 0).
true
false
Added new devices:
Syrus 4G LITE extended EV tag support. REV reports with unknown or truncated extended tags no longer fail to store. New parameters parsed from Syrus 4 REV reports:
GPS speed from the SPD tag now populates position.speed. Fixed: the SV tag (satellites in view) now populates position.satellites instead of overwriting position.speed.
Fixed packet framing for Syrus devices that omit the trailing CR/LF. Devices configured with CR_FLAG=F terminate reports with a bare < and were silently storing no messages. Reports from these devices across all classic Syrus device types (Syrus, Syrus 2G SL, Syrus 3G+, Syrus 4G LITE) now parse and store correctly.
CR_FLAG=F
<
dct-syrus: Syrus 4 IX tag is now parsed — devices report engine.ignition.status, din, dout, external.powersource.status, backup.battery.status, device.tamper.status, and the new dout.short.circuit.status parameter.
New parameter for Syrus 4 (syrus_4g_lite) devices: the AD tag is now parsed as ain.9 (device ADC voltage).
AD
GTJDS cellular jamming is now reported via gsm.jamming.alarm.status (on/off state). gnss.jamming.status continues to be emitted during a transition period and will be removed after 2026-07-12. gsm.jamming.event now fires only when jamming is entered (no longer on the quit report). The new gsm.jamming.warning.status parameter reports jamming warning states where a device sends them.
