Releases: telefonicaid/iotagent-json
3.11.0
NOTE: this version deprecated IOTA_MONGO_* env vars. Use IOTA_MONO_URI instead (this is actually due to the upgrade in iotagent-node-lib to 4.11.0, but it has to be also taken into account in the IOTA JSON using the library)
Changes (since 3.10.0)
- Fix: receive and store cmd notification when command mode is notification
- Upgrade iotagent-node-lib dependency from 4.10.0 to 4.11.0
3.10.0
This release removes support from Nodev16 and Nodev18. Note that Nodev16 and Nodev18 were deprecated in September 2023 and April 2025 respectively, according to the node release schedule. You are highly encouraged to use Nodev20 or newer.
Changes (since 3.9.0):
- Set Nodejs 20 as minimum version in packages.json (effectively removing Nodev16 and Nodev18 from supported versions)
- Upgrade NodeJS version from 16-bullseye-slim to 24-bullseye-slim in Dockerfile
- Upgrade iotagent-node-lib dependency from 4.9.0 to 4.10.0
3.9.0
This is the last version of the library supporting Nodev16 and Nodev18. Note that Nodev16 and Nodev18 were deprecated in September 2023 and April 2025 respectively, according to the node release schedule. You are highly encouraged to use Nodev20 or newer.
Changes (since 3.8.0):
- Fix: init express trust proxy to proper fill from field of domain logger
- Fix: fill from log field with real IP
- Fix: store as lastMeasure just orignal measure when is provided (iota-node-lib#1669)
- Upgrade NodeJS version from 16-slim to 16-bullseye-slim in Dockerfile
- Upgrade iotagent-node-lib dependency from 4.8.0 to 4.9.0
3.8.0
Changes (since 3.7.0)
- Add: allow receive command notifications from CB (iotagent-node-lib#1455)
- Add: config.mqtt.subscribeBatchSize option (IOTA_MQTT_SUBSCRIBE_BATCH_SIZE) to batch topic subscriptions into multiple SUBSCRIBE packets (#875)
- Add: allow define custom headers with jexl expressions in http commands (#873)
- Fix: bad json measures are reported as 500 Error instead of 400 (#863)
- Fix: Subscription fails on AWS IoT Core broker (#875)
- Upgrade mqtt from 4.3.7 to 5.13.0
- Upgrade iotagent-node-lib dependency from 4.6.0 to 4.7.0
3.7.0
Changes (since 3.6.0):
- Add: allow MQTT single array measures (#856)
- Add: X-Processing-Time response header with processing time (in milliseconds) expended by current HTTP measure (iotagent-node-lib#1650)
- Add: print also IOTA_CONFIG_RETRIEVAL, IOTA_DEFAULT_KEY, IOTA_DEFAULT_TRANSPORT env var values at iotagent startup
- Fix: allow single array MQTT measures of 1 element handed like array, not single value (#856)
- Fix: allow send multiple measures in MQTT to CB in a batch (POST /v2/op/update) and sorted by TimeInstant when possible, instead of using multiples single request (#825, iotagent-node-lib#1612) (reopened)
- Fix: check endpoint expression when execute http command
- Fix: use config.defaultTransport (from config.js or IOTA_DEFAULT_TRANSPORT env var) instead of magic 'HTTP' at provision device
- Upgrade express from 4.20.0 to 4.21.2
- Upgrade iotagent-node-lib dependency from 4.6.0 to 4.7.0
3.6.0
3.5.0
Changes (since 3.4.0)
- Fix: update device using previous device apikey to avoid error when apikey is updated (#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 (#825, iotagent-node-lib#1612)
- Fix: default express limit to 1Mb instead default 100Kb and allow change it throught a conf env var 'IOTA_EXPRESS_LIMIT' (#827)
- Upgrade iotagent-node-lib dependency from 4.4.0 to 4.5.0