9 days later

Digital matter update:

Added new device models:

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
a month later

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.

2 months later

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

    7 days later

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

      7 days later

      Added support for Driver / Operator ID data:

      • Digital Matter RFID tag reader
      • iButton (1-wire) tag
      • 4 digit PIN
      • 5 digit PIN
        18 days later

        FID's added:

        • FID = 26: TRIP Distance, Trip Duration
        • FID = 27: Device Odometer, Run Hours
          11 days later

          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"

            13 days later

            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.

              11 days later

              Added registration of RSSI parameter for BLE tags data.

                7 days later

                digital-matter protocol has been updated, Bluetooth Tag Type: Generic Tag Data added

                  9 days later

                  Changes with the device types.
                  In accordance with the manufacturer's recommendations The device type "Digital Matter Oyster Edge" is no longer available for creation with the protocol Digital-Matter. You can read more about the configuration of this type of device here.

                    9 days later

                    Fixed the multiplier for the #vehicle.odometer parameter. Initially the distance was calculated incorrectly. The device in its raw form transmits the distance in units with an accuracy of 10 m, and the parameter should display the distance in kilometers. Corrected.

                      5 days later

                      Added the ability to send commands.
                      Custom async messages - the command has 2 fields:
                      Async Message Type - has a size of 2 bytes and a HEX input pattern.
                      Async Message Body - Unlimited data size, HEX input pattern. This field is optional, because there are commands that do not require a body.
                      Note: The byte order of the input data must be Little-endian.

                      Request configuration from OEM - this is action setting without additional fields. The aim of this command is to tell the device to obtain the current default configuration from the manufacturer's server. If everything goes well, it will reconnect to the flespi server and continue sending data.

                        2 months later

                        Parsing update: added parsing parameter counter.

                        Internal Battery Voltage, V ==> #battery.voltage
                        Internal Battery, % ==> #battery.level
                        Est. Battery Capacity Used, Ah ==> #battery.capacity.used
                        Maximum Temperature, C° ==> #device.temperature.max
                        Initial Internal Battery Voltage, V ==> #battery.voltage.initial
                        Average Successful GPS Fix Time, 1s per fix ==> #gnss.average.fix.duration
                        Average Failed GPS Fix Time, 1s per failed fix ==> #gnss.average.failed.fix.duration
                        Average GPS Freshen Time, 1s per freshen attempt ==> #gnss.average.refresh.time
                        Average Wakeups Per Trip, 1 wakeup per trip ==> #trip.average.wakeup.number
                        Successful Uploads, 1 upload ==> #counter.uploads
                        Successful Upload Time, 1s ==> #counter.uploads.time
                        Failed Uploads, 1 upload ==> #counter.uploads.failed
                        Failed Upload Time, 1s ==> #counter.uploads.failed.time
                        Successful GPS Fixes, 1 fix ==> #gnss.position.fixes
                        Successful GPS Fix Time, 1s ==> #gnss.position.fixes.time
                        Failed GPS Fixes, 1 fix ==> #gnss.position.fixes.failed
                        Failed GPS Fix Time, 1s ==> #gnss.position.fixes.failed.time
                        GPS Freshen Attempts, 1 attempt ==> #gnss.refresh.attempts
                        GPS Freshen Time, 1s ==> #gnss.refresh.duration
                        Accelerometer Wakeups, 1 wakeup ==> #accelerometer.wakeup.number
                        Trips, 1 trip ==> #trip.id
                        GPS Fixes Due to ‘Upload on Jostle’, 1 fix ==> #jostle.position.fixes
                        Uploads Due to ‘Upload on Jostle’, 1 upload ==> #jostle.position.fixes.uploads
                        Uptime, 1s ==> #device.uptime
                        Tx Count, 1 tx ==> #counter.tx.power
                        Rx Count, 1 rx ==> #counter.rx.range
                        Successful Wi-Fi Scans, 1 ==> #wifi.successful.scans
                        Failed Wi-Fi Scans, 1 ==> #wifi.failed.scans
                        BLE events. Uptime ==> #ble.uptime
                        BLE events. Failures ==> #ble.failures.count
                        BLE events. Scans ==> #ble.scans.count
                        6 days later

                        Parsing changes: added registration of the position.timestamp parameter. This is the timestamp for generating the coordinates. The parameter corresponds to the logic and capabilities of the protocol.

                          18 days later

                          Parsing changes: added the "Socket Closure Request" package when the device itself finalizes the current session. The package refers to the general data structure and does not affect the device model in any way.

                            a month later

                            Parsing changes & protocol update:

                            • Support for the new model "Hawk" is added.
                            • Changes have been made to the parsing of the structure "Analogue data. FID=6".
                              • Fixed the calculation of the #external.battery.voltage parameter - it was previously calculated incorrectly.
                              • Renamed the parameter #gsm.signal.dbm to #gsm.signal.quality. This is because dbm should show the signal strength in decibels, which it actually did not. This parameter showed and shows a value that is a signal quality measure from 0 to 31, with 99 being an invalid value.