Release note

1.2.0

    • V0.17.4nl (2022-11-18)

      • This is a release without lora functionality (no-lora)

    • V0.17.4 (2022-01-20)

      • removed test and staging environments

      • set QoS to 1 for the out messages

    • V0.17.3 (2022-01-13)

      • updated environment def (mqtt hosts)

    • V0.17.2 (2021-07-13)

      • Better control of mqtt out messages (popping from the buffer)

    • V0.17.1 (2021-02-18)

      • Imelda: On incoming mqtt message, only the last 4 digits of the phone number are kept

      • Disabled TLS check for registration check (in the TLS client node)

    • V0.17.0 (2020-09-28)

      • Updated to DECT API v4.x

    • V0.16.0 (2020-09-17)

      • Reorganized worksheets

      • Lora will never delete devices automatically, but there is an option on the Troubleshooting page to remove the devices which are not anymore present in the remote configuration

    • V0.15.3 (2020-08-21)

      • Updated format of lora messages published via mqtt

    • V0.15.2a (2020-08-20)

      • Modbus request timeout is limited to 10s now

      • Fixed incorrect handling of modbus write requests

    • V0.15.1a (2020-07-14)

      • lora messages are sent to a different topic and they have a custom format

    • V0.15.0a (2020-07-01)

      • Implemented Lora protocol

    • V0.14.0 (2020-05-07)

      • Implemented DECT communication

    • V0.13.2 (2020-01-13)

      • Added mqtt status logging to troubleshoot LIFO buffer

      • added wan monitor node to the buffer output enable/disable logic

    • V0.13.0 (2019-12-18)

      • Implemented LIFO buffer, removed Smartbuffer

    • V0.12.0 (2019-11-07)

      • Uses Smartbuffer now

    • V0.11.2 (2019-10-18)

      • increased QoS of the write messages to 2

    • V0.11.1 (2019-10-18)

      • if mqtt will not reconnect for a while, restart the flow

    • V0.11.0 (2019-10-08)

      • Implemented wwan signal strength reporting

    • V0.10.2 (2019-09-26)

      • Optimization for the mqtt queue: Since the mqtt queue unnecessarily stores all the properties of the message in the queue, a new message is now sent to mqtt out containing just the topic and payload

    • V0.10.1 (2019-09-23)

      • Increased mqtt queue to 2000 records

    • V0.10.0 (2019-09-20)

      • Implemented the new registration call

    • V0.9.12 (2019-09-19)

      • adedd logging nodes for mqtt control and sentry

      • improved modbus error handling for reads and writes

    • v0.9.11 (2019-09-19)

      • handles ILLEGAL DATA ADDRESS error

    • V0.9.10 (2019-09-19)

      • changed mqtt Acc port to 8993 (request by Geert)

    • V0.9.9 (2019-09-19)

      • removed erroneous delay after a modbus error

    • V0.9.8 (2019-09-16)

      • small debug improvement added

    • V0.9.7 (2019-09-12)

      • offset and correctionFactor were not processed when writing (were not in the original specs). Implemented as requested by Geert

    • V0.9.6 (2019-09-11)

      • as requested by Geert on 11/09/2019, we’ll look for offset and correctionFactor first at the modbusRegisterConfigs level, then at the modbusvalues level

    • V0.9.5 (2019-09-10)

      • Fixed modbus write (baudrate was wrong)

    • V0.9.4 (2019-09-10)

      • translation field was not working for read operations

    • V0.9.3 (2019-09-06)

      • Back to the increasing registration check delays, from 60 seconds to 1 hour with doubling the delay

    • V0.9.1 (2019-07-25)

      • identical sentry messages are ignored

      • more info sent to sentry

      • added some nodes to help troubleshooting mqtt messages

    • V0.9.0 (2019-07-12)

      • production port is 8993

      • added {version} to the register call

      • the flow version is displayed on the UI page

    • V0.8.5 (2019-07-05)

      • modbus timeout represents the timeout in ds (deciseconds, or tenths of seconds)

    • V0.8.4 (2019-07-05)

      • removed the frequency factor

    • V0.8.3 (2019-07-05)

      • set the default environment to Prod

      • set the environment list

    • V0.8.2 (2019-07-05)

      • fixed LED modes

    • V0.8.1 (2019-06-14)

      • Write errors are handled the same as the read errors (modbuserror + sentry)

      • Write status message contains a hardcoded field type = ‘WRITE’

    • V0.8.0 (2019-06-14)

      • Write operations updates:

        • implemented expiration feature

        • write status will be posted to a different topic

        • uuid will be copied from the request to the status message

        • “result” field is now a string: EXECUTED/ERROR/EXPIRED

    • V0.7.5 (2019-06-14)

      • COIL and DISCRETE values are supported now

    • V0.7.4 (2019-06-14)

      • logs the configuration objects by uuid, for troubleshooting purposes

    • V0.7.3 (2019-06-14)

      • logs the last message sent via mqtt, by uuid, for troubleshooting purposes

    • V0.7.2 (2019-06-14)

      • if the value cannot be decoded, treat is as an error and send it to sentry as well

    • V0.7.1 (2019-06-12)

      • The unhandled modbus errors will not be sent via mqtt

    • V0.7.0 (2019-06-12)

      • implemented LED status

    • V0.6.2 (2019-06-12)

      • fixed EBADQUANT modbus erorr

    • V0.6.2 (2019-06-11)

      • enabled queing feature of mqtt out

    • V0.6.1 (2019-06-11)

      • release nr. and SNR are displayed as node info

      • Modbus errors are sent to sentry

      • Implemented sentry error reporting

      • Implemented GPS data reporting