4.5.0

Changes (since 4.4.0)

• Fix: do not propage TimeInstant when explicitAttrs is empty array (#1606)
• Fix: update device using previous device apikey to avoid error when apikey is updated (iotagent-json#833)
• Fix: allow send multiple measures to CB in a batch (POST /v2/op/update) and sorted by TimeInstant when possible, instead of using multiples single request (iotagent-json#825, #1612)
• Fix: default express limit to 1Mb instead default 100Kb and allow change it throught a conf env var 'IOTA_EXPRESS_LIMIT' (iotagent-json#827)
• Fix: accept 201 status code from context broker with NGSI-LD interface when first measure is sent and device is created in it (#1617)

4.4.0

Changes (since 4.3.0):

• Add: allow devices with the same device_id in the same service and subservice but different apikey (#1589)
• Add: process JEXL expressions in metadata attributes (#1598)
• Fix: TimeInstant mapped from attribute overrides default behaviours (#1557)
• Fix: reduce information showed handling errors to just config flags (#1594)
• Upgrade pymongo dep from 4.3.3 to 4.6.3
• Upgrade express dep from 4.18.1 to 4.19.2

4.3.0

Changes (since 4.2.0):

• Add: POST /iot/op/delete operation to delete multiple devices at once (#1578)
• Add: log and return device/group information when EntityGenericError, TypeNotFound, DeviceNotFound, BadTimestamp, BadGeocoordinates, CommandNotFound, GroupNotFound, MissingAttributes, DuplicateDeviceId and DuplicateGroup errors (iotagent-json#815)
• Fix: store device subscriptions updates (#1086)
• Fix: badtimestamp error should not progress to ContextBroker
• Hardening: simplify implementation so typeInformation contains global config values (#1515)

4.2.0

Changes (since 4.1.0):

• Add: progress non expected id and type in measures under measure_ prefix

4.1.0

Changes (since 4.0.0):

• Add: include apikey in queries to memory registry for groups
• Add: transport and endpoint to Group model (#1542)
• Fix: store commands from Group at Device level at provision device time
• Fix: log device id when BadTimestamp error (*)

(*) Also in hotfix version 4.0.1

4.0.1

Hotfix for version 4.0.0

Changes (since 4.0.0):

• Fix: log device id when BadTimestamp error

4.0.0

Changes (since 3.4.0):

• Large refactor of IOTA Lib code to make it simpler
• Add: payloadType to device and groups model to support NGSI-v2 and NGSI-LD formats in southbound measures (iotagent-json#778)
• Fix: use but not store timestamp and explicitAttrs from group with autoprovisioned devices (#1504, partially)
• Fix: MongoDB connection authentication (user and password were not actually used) (#1510)
• Fix: add static attributes when use explicitAttrs (#1506)
• Fix: ensure service and subservice in context of error handlers using req headers
• Fix: remove attribute of measures with name id or type to avoid collisions (#1485)
• Fix: ensure entity id and type are string (#1476)
• Fix: update ctxt allow nested expressions (#1493)
• Fix: change log level contextAvailable expression exception (from WARN to INFO)
• Fix: null values arithmetics in JEXL expressions (#1440)
• Fix: remove mongo DeprecationWarning: current Server Discovery and Monitoring engine is deprecated by setting useUnifiedTopology = true
• Fix: mongodb.authSource / IOTA_MONGO_AUTH_SOURCE was not correctly supported (#1526)
• Upgrade mongodb dev dep from 4.17.0 to 4.17.1
• Remove: single configuration mode (along with IOTA_SINGLE_MODE env var) (#1469)
• Remove: extractVariables from jexl plugin (no needed anymore since the removal of bidireational plugin)
• Remove: time compression support
• Remove: autocast (including env var IOTA_AUTOCAST) (#1498)

3.4.4

Hotfix version for release 3.4.0.

Changes (since 3.4.3):

• Fix: remove attribute of measures with name id or type to avoid collisions (#1485)

3.4.3

Hotfix version for release 3.4.0.

This version is an improvement of the 3.4.2 hotfix.

3.4.2

Hotfix version for release 3.4.0.

This version is an improvement of the 3.4.1 hotfix.