Topflytech protocol will be affected by the refactoring custom command parameters to be installed in 1 week - Sep 4th, 2023

The "name" field will be removed from the custom command, and the full text of the command will need to be entered in one "payload" field.
The ability to send a custom command via SMS will also be removed. Settings will be used to configure the device via SMS.

24 days later

  • omol

  • Post #44

Topflytech protocol has been updated: implemented parsing of Multiplex Segment parameter instead of outdated Analog Inputs 3-4 according to the latest protocol documentation.

    5 days later

    Topflytech protocol has been updated, made some improvements in part of parsing of commands response

      20 days later

      • omol

      • Post #47

      Topflytech BLE parameters (ble.sensors array) have been updated:

      • light.status parameter parsing is fixed according to the updated documentation
      • illuminance parameter is removed as undocumented
        3 months later

        • baja

        • Post #48

        Bugfix for TLW2 series:
        parameter din.1 that was stored from the same Digital I/O Status Bit 14 as engine.ignition.status is now stored based on Bit 8. It might differ from engine.ignition.statuts if user sets ignition detection based on voltage, vibration etc.

          • baja

          • Post #49

          Parsing behavior update

          when device sends the packet 0x81 (that is usually used to respond for commands) but no command from flespi had been sent (e.g. when device responds to SMS in TCP link), then the traffic would be stored as a message with payload.text parameter
          Before that, such packets had been skipped

            4 days later

            Topflytech protocol has been updated, added BLE tags parsing:

            • 0x0E BLE iBeacon
            • 0x0F BLE Eddystone UID
            • 0x11 BLE Eddystone TLM
              14 days later
              a month later

              • namo

              • Post #52

              Topflytech protocol updated: event.enum parameter is added, that corresponds to the Alarm Type byte field.

              Applicable for the Topflytech TLD2-L

                6 days later

                The protocol will be affected by the change in parameter can.dtc to be installed in 2 weeks - Mar 15th, 2024: the parameter can.dtc is currently of string type and will be converted to type array with separate DTC codes.

                Added parameter can.dtc.array as an example of future implementation of can.dtc

                9 days later

                Updated parsing of 0x13 Position message and 0x14 Alarm message reports according to the latest documentation

                  5 days later
                  25 days later

                  Fixed Detect ACC setting for TLW2-12B devices

                    24 days later

                    Fixed parsing of 0x13, 0x14 reports in case of missing coordinates

                      10 days later

                      parameter collision.status renamed to crash.status

                        a month later

                        BLE ELA TAG support has been extended to specification 2.0.
                        Added Alert data parsing, parameters: alert.level and alert.status.

                          Topflytech protocol is updated: Message type 0x27 0x27 0x25 Alarm message is supprted

                            namo
                            Topflytech protocol is updated: fixed parsing of message type 0x27 0x27 0x25 Alarm message