Galileosky protocol updated: the following parameters are renamed:

  • rs485.fuel.sensor.level.0 - rs485.fuel.sensor.level.15 are renamed into rs485.lls.value.0 - rs485.lls.value.15 correspondingly
  • rs485.fuel.sensor.temperature.0 - rs485.fuel.sensor.temperature.15 are renamed into rs485.lls.temperature.0 - rs485.lls.temperature.15 correspondingly

For backward compatibility, both old and new parameters will be registered until 13-Jun-2022.
13-Jun-2022 we will remove old parameters. Please make sure you code is fully transfered to the new parameters names until the mentioned date.

    24 days later

    namo
    Galileosky protocol is updated: old parameters are removed after renaming.

      4 months later

      Bugfix:
      parameter refrigerator.operate.mode.enum.2 was incorrectly overwritten by value for the parameter refrigerator.engine.mode.enum.2 . Now both parameter have correct values.

      Bugfix schedule.

      String value of indexed parameter (indexes 1,2,3) refrigerator.operate.mode.enum.1,2,3 is now also stored under refrigerator.operate.mode.1,2,3.
      String value of indexed parameter (indexes 1,2,3) refrigerator.engine.mode.enum.1,2,3 is now also stored under refrigerator.engine.mode.1,2,3.

      In one week (November 2, 2022), refrigerator.operate.mode.enum.1,2,3 and refrigerator.engine.mode.enum.1,2,3 will store raw numeric values.

      9 days later

      Galileosky protocol is updated: the following Extended tags are supported:

      • 0x86 - 0x8D Temperature sensor - flespi parameters:
        -- sensor.temperature.id.8 - sensor.temperature.id.15
        -- sensor.temperature.8 - sensor.temperature.15
      • 0x8E GPS satellite information - flespi parameters:
        -- gps.visible.satellites
        -- gps.position.satellites
        -- gps.average.snr
        -- gps.max.snr
      • 0x8F GLONASS satellite information - flespi parameters:
        -- glonass.visible.satellites
        -- glonass.position.satellites
        -- glonass.average.snr
        -- glonass.max.snr
      • 0x90 BEIDOU satellite information - flespi parameters:
        -- beidou.visible.satellites
        -- beidou.position.satellites
        -- beidou.average.snr
        -- beidou.max.snr
      • 0x91 GALILEO satellite information - flespi parameters:
        -- galileo.visible.satellites
        -- galileo.position.satellites
        -- galileo.average.snr
        -- galileo.max.snr
      • 0x92 Active SIM IMSI - flespi parameter gsm.sim.imsi
      • 0x93 Currently used SIM card slot - flespi parameter sim.card.slot
      • 0x94 Active SIM ICCID - flespi parameter gsm.sim.iccid

      baja scheduled bugfix installed

        9 months later

        Galileosky protocol is updated: the following Extended tags are supported:

        • 0xFD - 0xFE iButton code - flespi parameters:
          -- ibutton.code.1 - ibutton.code.2
        a month later

        Attention. Changing the naming of parameters.
        Due to a grammar mistake in the name, the parameter blutooth.sensor.value[index] will be renamed to bluetooth.sensor.value[index]
        The new parameter has already been added to the registration. The old one will be removed on October 1, 2023. If you need more time please contact us via support chat.

          12 days later
          13 days later

          Galileosky protocol has been updated, added tags parsing:

          • 0x78 - 0x7D Input 8 - 13 value - flespi name ain.9 - ain.14
          • 0x49 Transmission channel - flespi name network.type.enum
          • 0x00FC Reason for recording an archive point - flespi name report.reason
          7 days later

          Galileosky protocol has been updated, added 0x21 Milliseconds tag parsing

            2 months later

            Changing parsing parameters!
            The parameter #user.data.value, which is currently registered under tags 0xE2 ... 0xE9, has a signed type, which does not comply with the protocol. The registration of the parameter will be changed on December 14, 2023 at 12:00 UTC+0. The parameter value will be changed to unsigned.
            This information is confirmed by the hardware manufacturer.
            If you need more time to adapt, please let us know via chat.

            After the changes have been applied, you can also return the signed value of these parameters using the PVM plugin:

            {
              "id": 1043089,
              "required": true,
              "enabled": true,
              "validate_message": "",
              "item_type": 11,
              "name": "pvm-plugin-tester",
              "configuration": {
                "code": "// define new optional parameter: event.id\n\nrepeat[8, counter=$i, from=1]:\t// cycle for 8 parameters. tag's range 0xE2-0xE9\n\tformat[\"user.data.value.%d\", $i] ==> $name\t// format name to check index of parameter\n\toptional {$name} ==> binary %uint8 ==> input:\t// check if exists parameter with formated name with current index\n\t\t%int8 ==> #user.data.value.signed[index=$i]\t// register signed value"
              },
              "priority": 0,
              "type_id": 1,
              "timezone": "UTC",
              "metadata": {}
            }

            JSON plugin configuration can be inserted using the corresponding option in the interface as in the screenshot.

              EvgenyShatilo The changes for the user.data.value parameters have been applied.
              Briefly: the value type has changed from singed to unsigned.

                25 days later

                Bugfix: parameters gsm.sim.iccid and gsm.sim.imsi from extended tags 0x94 and 0x92 parsing changed from HEX string to ASCII string.

                  4 months later

                  parameter renaming announcement which will happen in a week (May 22):
                  string parameter tire.sensor.reason.enum will become numeric. Current string value will be stored in tire.sensor.reason

                    14 days later
                    a month later

                    Extended tag 0x0085 - RSSI is fixed to signed value. Previously, it was unsigned, which is an error for the cellular signal strength value.

                      2 months later

                      Fixed registration of extended tag 0xFE parameters.
                      All 4-byte parameters must be signed by default. Previously they were unsigned.

                      Concerns parameters modbus.sensor.value, bluetooth.sensor.value.

                        Write a Reply...