allow use commands by simple subscriptions/notifications

CHANGES_NEXT_RELEASE

@@ -1 +1,3 @@
+- Fix update device with useCBflowControl
+- Add: command modes (new field cmdMode): legacy, notification and advancedNotification (#1732)
 - Set Nodejs 20 as minimum version in packages.json (effectively removing Nodev16 and Nodev18 from supported versions)

config.js

@@ -79,7 +79,8 @@ var config = {
     defaultType: 'Thing',
     expressLimit: '1Mb',
     useCBflowControl: false,
-    storeLastMeasure: false
+    storeLastMeasure: false,
+    cmdMode: 'legacy'
 };
 
 module.exports = config;

doc/admin.md

@@ -452,6 +452,17 @@ If this flag is activated, when iotAgent invokes Context Broker will use
 [flowControl option](https://github.com/telefonicaid/fiware-orion/blob/master/doc/manuals/admin/perf_tuning.md#updates-flow-control-mechanism).
 This flag is overwritten by `useCBflowControl` flag in group or device. This flag is disabled by default.
 
+#### `cmdMode`
+
+Set command mode for the IoTAgent instance (it can be overriden by the `cmdMode` at group or device level). Possible values are:
+
+* `legacy` (used as default if this setting is not defined): IoTAgent commands will use Context Broker registers
+mechanims.
+* `notification`:  IoTAgent commands will use subscriptions to be notified for Context Broker commands.
+* `advancedNotification`: IoTAgent commands will use subscriptions to be notified for Context Broker commands (but in a different way as in `notification` mode)
+
+Have a look to [this document](devel/northboundinteractions.md) for more detail on how this modes work.
+
 ### Configuration using environment variables
 
 Some of the configuration parameters can be overriden with environment variables, to ease the use of those parameters
@@ -517,6 +528,7 @@ overrides.
 | IOTA_EXPRESS_LIMIT                   | `expressLimit`                  |
 | IOTA_STORE_LAST_MEASURE              | `storeLastMeasure`              |
 | IOTA_CB_FLOW_CONTROL                 | `useCBflowControl`              |
+| IOTA_CMD_MODE                        | `cmdMode`                       |
 
 Note:
 

doc/api.md

@@ -257,9 +257,9 @@ Additionally for commands (which are attributes of type `command`) the following
     particular IOTAs documentation for allowed values of this field in each case.
 -   **contentType**: `content-type` header used when send command by HTTP transport (ignored in other kinds of
     transports)
--   **headers**: extra customer headers used when send command by HTTP transport (ignored in other kinds of
-    transports)
-Check full detail of these fields in [comand-transformations](https://github.com/telefonicaid/iotagent-json/blob/master/docs/usermanual.md#commands-transformations)
+-   **headers**: extra customer headers used when send command by HTTP transport (ignored in other kinds of transports)
+    Check full detail of these fields in
+    [comand-transformations](https://github.com/telefonicaid/iotagent-json/blob/master/docs/usermanual.md#commands-transformations)
 
 Note that, when information coming from devices, this means measures, are not defined neither in the group, nor in the
 device, the IoT agent will store that information into the destination entity using the same attribute name than the
@@ -1323,6 +1323,8 @@ as `command` in the [config group](#config-group-datamodel) or in the [device pr
 attributes are created using `command` as attribute type. Also, you can define the protocol you want the commands to be
 sent (HTTP/MQTT) with the `transport` parameter at the provisioning process.
 
+**NOTE**: in `advancedNotification` mode the command is not triggered updating an attribute, but creating a command execution entity. However, this mode has not been implemented yet so details are to be clarified.
+
 For a given device provisioned with a `ping` command defined, any update on this attribute "ping" at the NGSI entity in
 the Context Broker will send a command to your device. For instance, to send the `ping` command with value
 `Ping request` you could use the following operation in the Context Broker API:
@@ -1784,6 +1786,7 @@ Config group is represented by a JSON object with the following fields:
 | `endpoint`                     | ✓        | `string`       |            | Endpoint where the group of device is going to receive commands, if any.                                                                                                                                                                                                                                                                                                                                                            |
 | `storeLastMeasure`             | ✓        | `boolean`      |            | Store in device last measure received. See more info [in this section](admin.md#storelastmeasure). False by default                                                                                                                                                                                                                                                                                                                 |
 | `useCBflowControl`             | ✓        | `boolean`      |            | Use Context Broker flow control. See more info [in this section](admin.md#useCBflowControl). False by default                                                                                                                                                                                                                                                                                                                       |
+| `cmdMode`                      | ✓        | `string`       |            | Command mode that will use iotagent with CB: **legacy**, **notification** and **advancedNotification**. **Legacy** is based on registers. **notification** based on simplified schema of subscriptions. **Legacy** by default. More information on how the different modes work can be found in [the northbound interactions documents](devel/northboundinteractions.md).                                                                                                                                                                                                       |
 
 ### Config group operations
 
@@ -2007,6 +2010,7 @@ the API resource fields and the same fields in the database model.
 | `storeLastMeasure`    | ✓        | `boolean` |            | Store in device last measure received. Useful just for debugging purpose. See more info [in this section](admin.md#storelastmeasure). False by default.                                                                                                                                                                                                                                                                    |
 | `lastMeasure`         | ✓        | `object`  |            | last measure stored on device when `storeLastMeasure` is enabled. See more info [in this section](admin.md#storelastmeasure). This field can be cleared using `{}` in a device update request. In that case, `lastMeasure` is removed from device (until a next measure is received and `lastMesuare` gets created again).                                                                                                 |
 | `useCBflowControl`    | ✓        | `boolean` |            | Use Context Broker flow control. See more info [in this section](admin.md#useCBflowControl). False by default.                                                                                                                                                                                                                                                                                                             |
+| `cmdMode`             | ✓        | `string`  |            | Command mode that will use iotagent with CB: **legacy**, **notification** and **advancedNotification**. **Legacy** is based on registers. **notification** based on simplified schema of subscriptions. **Legacy** by default. More information on how the different modes work can be found in [the northbound interactions documents](devel/northboundinteractions.md).                                                                                                                                                                                              |
 
 ### Device operations