• baja

  • Post #1
  • Edited

This topic will be used to post changes in wiatag protocol implementation
WiaTag

    added validation for battery.level parameter: the valid value is in the range [0, 100]. 255 value is skipped, the range [101, 254] generates data parsing error

    a year later

    WiaTag protocol update is planned for Monday 2020-09-19, 07:00 UTC - parsing will be switched to new parsing engine. This is an internal process, no changes in devices' work are expected.

      namo
      WiaTag protocol is updated to new parsing engine.

          a month later

          • namo

          • Post #5
          • Edited

          New action setting is added for WiaTag device: Start/Stop service, Actions tab:

          a year later

          • kial

          • Post #6

          Next Thursday, 23-Dec-2021, message parameter "position.hdop" in the messages will be renamed to "position.accuracy".
          Currently, we're registering the same value for both parameters, and in a week the old name "position.hdop" will be removed.

          7 days later

          • kial

          • Post #7

          kial Old parameter name removed

              5 months later

              The protocol will be affected by the change in type of parameters gsm.mcc and gsm.mnc to be installed in 2 weeks - May 23rd, 2022: both parameters that now have type "string" will be stored as "number". The possible leading zeroes in MNC will be ignored (e.g. the value "01" will be stored as 1).

              • baja replied to this.

                Wiatag protocol updated: added setting Pair BLE Beacon, Actions tab:

                baja Together with this update a new indexing logic for gsm. prefixed parameters will be installed.
                The first base station info parameters gsm.mcc, gsm.mnc, gsm.lac, gsm.cellid, gsm.signal.dbm, gsm.timing.advance will be stored without indexes, while the next base stations indexes will start from 1.

                  10 days later

                  WiaTag protocol is updated: commands and settings are refactored. The changes are purely internal, no changes in the behavior of WiaTag devices on flespi are expected.

                  6 months later

                  Fixed sending device configuration using the settings command.

                  2 years later

                  Wiatag configurator has appeared on flespi!

                  All widgets that are present in Android and IOS versions of the application are available for configuration.

                  Configurator of device behavior and operation with the ability to configure message sending.

                  Active settings for sending chat messages and stopping the service are also available for use.

                  Important notes:

                  • Toggle Allow to edit which is available in every widget works only for IOS. This option allows you to block the user from customizing the widget in the application. The widget will be visible, including its settings, it will just be dimmed and inactive.
                  • The "Work on schedule" configuration only works in the Android version of the application. Can only be configured by the server. The user can only enable or disable scheduled work.
                  • The active setting of "Start/Stop service" is performed unilaterally. Before the application is turned off on the phone, it does not inform the server about this in any way. Keep this in mind. It is recommended to test on a test device before further use.
                  • The active setting "Message to chat" also works in one direction, without notification of delivery to the server. This is a feature of the protocol. For correct operation of the message sending settings, it is recommended to configure the frequency of sending messages no more than once every 10 seconds.
                  Write a Reply...