What you will need
Make sure that you have prepared the following points:
This application provides a GUI wizard for you to create secure clients and define sensors and metrics, as defined by the TeamViewer IoT MQTT API. You will need to then push your sensor data as specified in the MQTT API Push Metric Values section to visualize it in real-time.
Using the wizard, you can create new Clients or authorize existing ones.
Create new clients
You can create new clients either automatically or by using an existing Certificate Signing Request (CSR). To create clients using a CSR, you must upload the CSR & the associated private key.
Once a secure client has been created, you can download its credentials for use on edge devices (to easily integrate sensors on edge devices to your TeamViewer IoT Agent).
For more information see Remote Clients.
Once a secure client has been created, you can use the wizard to define the sensors and metrics you want to connect. The wizard will provide you with the details and a template to push the sensor’s data as described in MQTT API Push Metric Values.
Authorize existing clients
Any existing client will automatically appear on your clients page of the IoT Management Console. However, you must upload its Certificate credentials using the clients page, to view it in real-time.
View data in real-time
Using the Metrics page of the IoT Management Console, you can view a list of all your sensor metrics and quickly view each in real-time by clicking on the metric name.
📌Note: All client/sensor/metric metadata shown in the application is the same as displayed in the TeamViewer IoT Cloud Dashboard.
Manage certificates
All client certificates, created by the application or uploaded by the user, are stored under:
/var/lib/docker/volumes/teamviewer-iot-edge-device-management-cert/_data
Public Key: cert-clientId.pem
Private Key: key-clientId.pem
The certificate file names contain the client Id
, in case the certificates are needed on edge devices.
⚠CAUTION: Do not rename, delete, or modify files under the cert/ directory. Doing so will cause data corruption.
For more information see Remote Clients.