flespi telematics hub supports digital-matter protocol. The list of supported devices Digital Matter Bolt Digital Matter Dart Digital Matter Dart2 Digital Matter Eagle LCV Digital Matter Falcon Digital Matter G52 Solar Digital Matter G60 Digital Matter G62 Cellular Digital Matter G100 Digital Matter G120 light Digital Matter G150 Global Digital Matter Oyster Cellular (v1) Digital Matter Oyster2 Cellular Digital Matter Oyster3 Global Digital Matter Yabby GPS Digital Matter Yabby WiFi Cellular Digital Matter Flexi1 Digital Matter Remora Digital Matter Remora2 Digital Matter Remora3 Digital Matter Sting Digital Matter Barra GPS Digital Matter Arrow Global BLE

Digital matter update: Added new device models: Digital Matter Remora3 New protocol features are supported: WiFi Location Scan Detailed Cell Tower Scan Bluetooth Tag Types: DM Guppy Tag Data Apple iBeacon Eddystone ELA T Tag

BLE parsing update: ELA RHT Tag has been added.

Digital Matter protocol has been updated: fixed parsing Detailed Cell Tower Scan field with multiple towers data.

Digital Matter protocol has been updated: fixed parsing Commit Request message with non-zero Location Request value.

Digital Matter protocol has been updated: added response for Version Messages packet.

Digital Matter protocol has been updated: fixed FID = 21: Profiling Counters parsing

Added support for Driver / Operator ID data: Digital Matter RFID tag reader iButton (1-wire) tag 4 digit PIN 5 digit PIN

FID's added: FID = 26 : TRIP Distance, Trip Duration FID = 27 : Device Odometer, Run Hours

iBeacon parsing is fixed. According to the communication protocol major and minor should be parsed in little-endian bytes format. Before the fix it was in big-endian. Example: before: "64CF11B4-0000-2222-1111-4E3A00E56A8B: 0FA0 : 00C0 " after: "64CF11B4-0000-2222-1111-4E3A00E56A8B: A00F : C000 "

Analogue data parsing has been fixed. Added registration of parameters that can be configured in the configurator starting from index 7. Parameter naming corresponds to #ain.7, 8, 9 and etc.

[Changelog] digital-matter protocol

YuryAheichyk

Added debug.level, debug.module.id, debug.info parameters instead of error.level and error.type.description

Parameters error.level, error.type.description will be deleted in two weeks 16 Sep 2024

YuryAheichyk

YuryAheichyk updates installed

EvgenyShatilo

Added parsing of BLE 'Eddystone TLM Frame''.

baja

Added parsing for FID = 36: Multi Cell Tower Scan. Parameters parsed:
gsm.cell.type
gsm.network.type
gsm.cellid
gsm.lac
gsm.mcc
gsm.mnc
gsm.timing.advance
network.signal.rsrp
network.signal.rspq
gsm.earfcn
gsm.cellid.physical
gsm.timing.difference

baja

New device type added - Manta Fusion
REJECTED: device may work only through digital-matter-edge protocol

EvgenyShatilo

Added registration of the battery.health.status parameter from the FID=2 structure. The parameter has an index of 1 bit (starting with 0). If true - everything is fine with the battery, false - replacement is required.

YuryAheichyk

Fixed rssi and state values registration from BLE tags

YuryAheichyk

Added 15, 151, 152 counters values registration to resets.brownout.count, resets.count, reboot.count parameters

namo

Digital-matter protocol is updated: fixed parsing field length for data records

baja

New device type added: Digital Matter Arrow Global BLE

namo

Digital-matter protocol is updated: parsing of Wifi and BLE MAC addresses is refactored.

namo

Digital-matter protocol announcement:
MAC address in ble.beacons array is now stored in mac parameter. Obsolete parameter mac.address will be removed in two weeks, 2025-11-24. Make sure to update your applications accordingly.

namo

Digital-matter protocol has been updated: removed mac.address field from ble.beacons array (see namo)

baja

Device behavior analysis shows that parameter position.valid can not be applied to Digita-matter devices. They only show position type is 2d fix, 3d fix (currently stored as position.fix.type), and old fix (due to loss of signal) now stored in boolean parameter position.outdated=true

parameter position.valid removed from the protocol implementation

also added parameter gsm.network.type.enum storing the raw value used in gsm.network.type. It is useful when the parameter gsm.network.type mapping can not be resolved based on the existing documentation