\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\r\n\r\n**App.js**\r\n\r\n```js\r\nimport 'react-native-get-random-values';\r\n```\r\n\r\n### Types\r\nSource code is written in Typescript so types are bundled with the package, you don't need to install any additional package\r\n\r\n### Connect\r\n\r\n#### Symmetric Key\r\n```js\r\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\r\n\r\nconst scopeId = 'scopeID';\r\nconst deviceId = 'deviceID';\r\nconst sasKey = 'masterKey';\r\n\r\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\r\n\r\nasync function main(){\r\n await iotc.connect();\r\n}\r\n\r\nmain();\r\n```\r\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\r\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\r\n\r\n### Operations\r\nAfter successfull connection, IOTC context is available for further commands.\r\n\r\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\r\n\r\n### Send telemetry\r\n\r\nSend telemetry every 3 seconds\r\n```js\r\nsetInterval(async() => {\r\n await iotc.sendTelemetry({\r\n field1: value1,\r\n field2: value2,\r\n field3: value3\r\n }, properties)\r\n```\r\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\r\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\r\n\r\n### Send property update\r\n```js\r\nawait iotc.sendProperty({fieldName:'fieldValue'});\r\n```\r\n### Listen to property updates\r\n\r\n```js\r\niotc.on(IOTC_EVENTS.Properties, callback);\r\n\r\n```\r\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\r\n\r\n```js\r\niotc.on(IOTC_EVENTS.Properties, async (property) => {\r\n console.log('Received '+property.name);\r\n await property.ack('custom message');\r\n});\r\n\r\n```\r\n\r\n### Listen to commands\r\n```js\r\niotc.on(IOTC_EVENTS.Commands, callback);\r\n\r\n```\r\nThe callback is a function accepting a Command object. To reply, just call the reply function.\r\n\r\n```js\r\niotc.on(IOTC_EVENTS.Commands, async (command) => {\r\n console.log('Received '+command.name);\r\n await command.reply(status,'custom message');\r\n});\r\n\r\n```\r\n_status_ is of type *IIoTCCommandResponse*\r\n```js\r\nenum IIoTCCommandResponse {\r\n SUCCESS,\r\n ERROR\r\n}\r\n```\r\n\r\n## One-touch device provisioning and approval\r\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\r\n\r\n### How to set IoTC template ID in your device\r\nTemplate Id can be found in the device explorer page of IoTCentral\r\n\r\n\r\nThen call this method before connect():\r\n\r\n```\r\niotc.setModelId('
\r\n
\r\n
\r\n\r\n**App.js**\r\n\r\n```js\r\nimport 'react-native-get-random-values';\r\n```\r\n\r\n### Types\r\nSource code is written in Typescript so types are bundled with the package, you don't need to install any additional package\r\n\r\n### Connect\r\n\r\n#### Symmetric Key\r\n```js\r\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\r\n\r\nconst scopeId = 'scopeID';\r\nconst deviceId = 'deviceID';\r\nconst sasKey = 'masterKey';\r\n\r\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\r\n\r\nasync function main(){\r\n await iotc.connect();\r\n}\r\n\r\nmain();\r\n```\r\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\r\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\r\n\r\n### Operations\r\nAfter successfull connection, IOTC context is available for further commands.\r\n\r\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\r\n\r\n### Send telemetry\r\n\r\nSend telemetry every 3 seconds\r\n```js\r\nsetInterval(async() => {\r\n await iotc.sendTelemetry({\r\n field1: value1,\r\n field2: value2,\r\n field3: value3\r\n }, properties)\r\n```\r\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\r\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\r\n\r\n### Send property update\r\n```js\r\nawait iotc.sendProperty({fieldName:'fieldValue'});\r\n```\r\n### Listen to property updates\r\n\r\n```js\r\niotc.on(IOTC_EVENTS.Properties, callback);\r\n\r\n```\r\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\r\n\r\n```js\r\niotc.on(IOTC_EVENTS.Properties, async (property) => {\r\n console.log('Received '+property.name);\r\n await property.ack('custom message');\r\n});\r\n\r\n```\r\n\r\n### Listen to commands\r\n```js\r\niotc.on(IOTC_EVENTS.Commands, callback);\r\n\r\n```\r\nThe callback is a function accepting a Command object. To reply, just call the reply function.\r\n\r\n```js\r\niotc.on(IOTC_EVENTS.Commands, async (command) => {\r\n console.log('Received '+command.name);\r\n await command.reply(status,'custom message');\r\n});\r\n\r\n```\r\n_status_ is of type *IIoTCCommandResponse*\r\n```js\r\nenum IIoTCCommandResponse {\r\n SUCCESS,\r\n ERROR\r\n}\r\n```\r\n\r\n## One-touch device provisioning and approval\r\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\r\n\r\n### How to set IoTC template ID in your device\r\nTemplate Id can be found in the device explorer page of IoTCentral\r\n\r\n\r\nThen call this method before connect():\r\n\r\n```\r\niotc.setModelId('
\r\n\r\n
\r\n\r\n**App.js**\r\n\r\n```js\r\nimport 'react-native-get-random-values';\r\n```\r\n\r\n### Types\r\nSource code is written in Typescript so types are bundled with the package, you don't need to install any additional package\r\n\r\n### Connect\r\n\r\n#### Symmetric Key\r\n```js\r\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\r\n\r\nconst scopeId = 'scopeID';\r\nconst deviceId = 'deviceID';\r\nconst sasKey = 'masterKey';\r\n\r\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\r\n\r\nasync function main(){\r\n await iotc.connect();\r\n}\r\n\r\nmain();\r\n```\r\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\r\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\r\n\r\n### Operations\r\nAfter successfull connection, IOTC context is available for further commands.\r\n\r\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\r\n\r\n### Send telemetry\r\n\r\nSend telemetry every 3 seconds\r\n```js\r\nsetInterval(async() => {\r\n await iotc.sendTelemetry({\r\n field1: value1,\r\n field2: value2,\r\n field3: value3\r\n }, properties)\r\n```\r\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\r\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\r\n\r\n### Send property update\r\n```js\r\nawait iotc.sendProperty({fieldName:'fieldValue'});\r\n```\r\n### Listen to property updates\r\n\r\n```js\r\niotc.on(IOTC_EVENTS.Properties, callback);\r\n\r\n```\r\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\r\n\r\n```js\r\niotc.on(IOTC_EVENTS.Properties, async (property) => {\r\n console.log('Received '+property.name);\r\n await property.ack('custom message');\r\n});\r\n\r\n```\r\n\r\n### Listen to commands\r\n```js\r\niotc.on(IOTC_EVENTS.Commands, callback);\r\n\r\n```\r\nThe callback is a function accepting a Command object. To reply, just call the reply function.\r\n\r\n```js\r\niotc.on(IOTC_EVENTS.Commands, async (command) => {\r\n console.log('Received '+command.name);\r\n await command.reply(status,'custom message');\r\n});\r\n\r\n```\r\n_status_ is of type *IIoTCCommandResponse*\r\n```js\r\nenum IIoTCCommandResponse {\r\n SUCCESS,\r\n ERROR\r\n}\r\n```\r\n\r\n## One-touch device provisioning and approval\r\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\r\n\r\n### How to set IoTC template ID in your device\r\nTemplate Id can be found in the device explorer page of IoTCentral\r\n\r\n\r\nThen call this method before connect():\r\n\r\n```\r\niotc.setModelId('
\r\n\r\n
\r\n\r\n**App.js**\r\n\r\n```js\r\nimport 'react-native-get-random-values';\r\n```\r\n\r\n### Types\r\nSource code is written in Typescript so types are bundled with the package, you don't need to install any additional package\r\n\r\n### Connect\r\n\r\n#### Symmetric Key\r\n```js\r\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\r\n\r\nconst scopeId = 'scopeID';\r\nconst deviceId = 'deviceID';\r\nconst sasKey = 'masterKey';\r\n\r\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\r\n\r\nasync function main(){\r\n await iotc.connect();\r\n}\r\n\r\nmain();\r\n```\r\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\r\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\r\n\r\n### Operations\r\nAfter successfull connection, IOTC context is available for further commands.\r\n\r\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\r\n\r\n### Send telemetry\r\n\r\nSend telemetry every 3 seconds\r\n```js\r\nsetInterval(async() => {\r\n await iotc.sendTelemetry({\r\n field1: value1,\r\n field2: value2,\r\n field3: value3\r\n }, properties)\r\n```\r\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\r\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\r\n\r\n### Send property update\r\n```js\r\nawait iotc.sendProperty({fieldName:'fieldValue'});\r\n```\r\n### Listen to property updates\r\n\r\n```js\r\niotc.on(IOTC_EVENTS.Properties, callback);\r\n\r\n```\r\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\r\n\r\n```js\r\niotc.on(IOTC_EVENTS.Properties, async (property) => {\r\n console.log('Received '+property.name);\r\n await property.ack('custom message');\r\n});\r\n\r\n```\r\n\r\n### Listen to commands\r\n```js\r\niotc.on(IOTC_EVENTS.Commands, callback);\r\n\r\n```\r\nThe callback is a function accepting a Command object. To reply, just call the reply function.\r\n\r\n```js\r\niotc.on(IOTC_EVENTS.Commands, async (command) => {\r\n console.log('Received '+command.name);\r\n await command.reply(status,'custom message');\r\n});\r\n\r\n```\r\n_status_ is of type *IIoTCCommandResponse*\r\n```js\r\nenum IIoTCCommandResponse {\r\n SUCCESS,\r\n ERROR\r\n}\r\n```\r\n\r\n## One-touch device provisioning and approval\r\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\r\n\r\n### How to set IoTC template ID in your device\r\nTemplate Id can be found in the device explorer page of IoTCentral\r\n\r\n\r\nThen call this method before connect():\r\n\r\n```\r\niotc.setModelId('
\r\n\r\n
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Types\nSource code is written in Typescript so types are bundled with the package, you don't need to install any additional package\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Types\nSource code is written in Typescript so types are bundled with the package, you don't need to install any additional package\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Types\nSource code is written in Typescript so types are bundled with the package, you don't need to install any additional package\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Types\nSource code is written in Typescript so types are bundled with the package, you don't need to install any additional package\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n
\n\n**App.js**\n\n```js\nimport 'react-native-get-random-values';\n```\n\n### Types\nSource code is written in Typescript so types are bundled with the package, you don't need to install any additional package\n\n### Connect\n\n#### Symmetric Key\n```js\nimport {IoTCClient} from 'react-native-azure-iotcentral-client';\n\nconst scopeId = 'scopeID';\nconst deviceId = 'deviceID';\nconst sasKey = 'masterKey';\n\nconst iotc = new iotCentral.IoTCClient(deviceId, scopeId, IOTC_CONNECT.SYMM_KEY,sasKey);\n\nasync function main(){\n await iotc.connect();\n}\n\nmain();\n```\nIt is possible to use both group keys (_SYMM_KEY_) and device keys (_DEVICE_KEY_).\nWhen specifying a device key as _sasKey_ option the connection type must be _IOTC_CONNECT.DEVICE_KEY_\n\n### Operations\nAfter successfull connection, IOTC context is available for further commands.\n\nAll the callbacks are optional parameters and are triggered when message has reached the ingestion engine.\n\n### Send telemetry\n\nSend telemetry every 3 seconds\n```js\nsetInterval(async() => {\n await iotc.sendTelemetry({\n field1: value1,\n field2: value2,\n field3: value3\n }, properties)\n```\nAn optional *properties* object can be included in the send methods, to specify additional properties for the message (e.g. timestamp, content-type etc... ).\nProperties can be custom or part of the reserved ones (see list [here](https://github.com/Azure/azure-iot-sdk-csharp/blob/master/iothub/device/src/MessageSystemPropertyNames.cs#L36)).\n\n### Send property update\n```js\nawait iotc.sendProperty({fieldName:'fieldValue'});\n```\n### Listen to property updates\n\n```js\niotc.on(IOTC_EVENTS.Properties, callback);\n\n```\nThe callback is a function accepting a Property object. Once the new value is applied, the operation must be acknoledged to reflect it on IoTCentral app.\n\n```js\niotc.on(IOTC_EVENTS.Properties, async (property) => {\n console.log('Received '+property.name);\n await property.ack('custom message');\n});\n\n```\n\n### Listen to commands\n```js\niotc.on(IOTC_EVENTS.Commands, callback);\n\n```\nThe callback is a function accepting a Command object. To reply, just call the reply function.\n\n```js\niotc.on(IOTC_EVENTS.Commands, async (command) => {\n console.log('Received '+command.name);\n await command.reply(status,'custom message');\n});\n\n```\n_status_ is of type *IIoTCCommandResponse*\n```js\nenum IIoTCCommandResponse {\n SUCCESS,\n ERROR\n}\n```\n\n## One-touch device provisioning and approval\nA device can send custom data during provision process: if a device is aware of its IoT Central template Id, then it can be automatically provisioned.\n\n### How to set IoTC template ID in your device\nTemplate Id can be found in the device explorer page of IoTCentral\n\n\nThen call this method before connect():\n\n```\niotc.setModelId('
\n\n