The connectivity environment is where device partners configure their device or where a user can configure its data stream to other systems. From one connectivity environment devices and data stream can data streams can be assigned to multiple monitoring environments. This section explains all aspects related to the connectivity environment.
In short: In the connectivity environment you can configure secure access for your devices through HTTPS webhooks or client certificates. You can define event handlers in TypeScript that parse incoming payloads into measurement reports, return instructions to devices (including FOTA) and monitor device health. But you can also monitor activity of your devices and generate device tokens to share with the end customer so they can securely claim the devices in their end-user environment
To get an overview of your environment you can view all activity, devices and commands. It is possible to filter these lists.
This shows an overview of all the device types that are available in your environment. For each device you can edit the event handler.
The event handler is where you can define how each incoming payload is parsed and which quantities are created.
There are two ways to create device authentications. One is through webhooks for example with a gateway or other data source. The other way is through X.509 certificates. For more information see the separate client certificate documentation.
All the quantities used by the different devices are listed in this overview. It is possible to apply pre-defined issue triggers which will be automatically added to a monitoring environment when a device is claimed.
All the reports from the different devices are listed in this overview. For each report a report parser can parse the payload coming in to create the desired report.
All the command types from the different devices are listed in this overview. For each command a command parser can parse the payload coming in to create the desired report. For each command it is possible. Per command it can be determined whether the end user in the monitoring environment can activate the command. For example in many cases a firmware over the air update is often only executed from the connectivity environment.
In the settings overview of the IoT developer environment users can be added and the name of the environment can be changed.