16 days later

Added new counters:

  • ble.uptime - "BLE uptime counter"
  • ble.failures.count - "BLE failures counter"
  • ble.scans.count - "BLE scans counter"
2 months later

iBeacon parsing is supported and ready to use.

    19 days later

    Configuration information update.

    According to the manufacturer's recommendations, devices that use the Edge protocol should initially be directed to the manufacturer's OEM server, and from there redirected to a 3rd party server (flespi). This is necessary so that the device can successfully determine coordinates using the Location Engine developed by the manufacturer, since the device cannot do this on its own. Detailed configuration instructions..

    Also, information about the configuration of this protocol can be found in the usage specification on the protocol page.

      12 days later

      BLE parsing update. Few types of BLE parsing are added:

      • DM Guppy
      • Eddystone
      • ELA T Tag
      • ELA RHT Tag
      • Generic Tag Data

      Also, an unknown type no longer interrupts data parsing.

      a month later
      5 months later

      BLE Tags bug fixes.

      • ELA T Tag & ELA RHT Tag - issue with the tag local_name is fixed.
      • Eddystone Namespace - issue with the extended MAC data is also fixed.
      • other minor improvements.
        a month later
        6 months later

        • baja

        • Post #10
        • Edited

        Channel configuration updated: HTTPS can be enabled, Authorization header can be defined to ensure requests are coming from DM gateway only and protect channel from malicious senders:

        21 days later
        20 days later
        Write a Reply...