This article applies to TeamViewer IoT users who monitor their IoT networks.
The solution presented in this article requires TeamViewer IoT Agent v 1.1.102 (or higher). To identify the version of your agent, run: sudo teamviewer-iot-agent info (an error, or no result, indicates an older version of the agent is installed).
This article describes how to use the TeamViewer IoT Edge Device Management Application, which provides Real-Time Visualization on your IoT device, in addition to, a setup Wizard to provision your sensor network.
Note: This article guides the installation of the application to be under the following directory:
If you choose to install the application under a different directory, apply the same change to the paths identified in this article.
The application requires the following to be installed on the device:
sudo teamviewer-iot-agent info
sudo node -v
sudo mkdir -p /usr/local/teamviewer-iot-agent/monitoring/ sudo tar -xzvf teamviewer-iot-edge-device-management-1.3.0.tar.gz -C /usr/local/teamviewer-iot-agent/monitoring/
Install the application using the following commands:
cd /usr/local/teamviewer-iot-agent/monitoring/teamviewer-iot-edge-device-management/ sudo npm install
To start the application on default port 80, use the following command:
To stop the application, use the following command:
If you have issues running the application or if the default TeamViewer IoT Agent settings have been changed, verify and update the application configurations as necessary:
If the configurations differ, update the application configuration parameters to match the TeamViewer IoT agent and restart the application.
sudo teamviewer-iot-agent configure show | grep WebControlPort
sudo teamviewer-iot-agent configure set WebControlPort XXXX sudo teamviewer-iot-agent restart
In case you need further troubleshooting, the application persists logs under:
After the installation is complete, you can use TeamViewer Client for Windows to remotely create secure applications, register sensors and metrics, and view real-time streaming data.
Note: Currently, Remote Access to TeamViewer IoT devices is only supported by TeamViewer Client for Windows.
To get started, log into your TeamViewer IoT Cloud Dashboard and Click on the Control button on the Devices page. This will open the TeamViewer Client and start a secure connection to your IoT device.
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.
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 remote devices (to easily integrate sensors on remote devices to your TeamViewer IoT Agent). Reference Remote Clients for details.
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 use to push the sensors data as described in MQTT API Push Metric Values.
Any existing Client will automatically appear on your Clients lists. However, you must upload its Certificate credentials using the Clients page, to view it in real-time.
Using the Metrics page, 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 Clients/Sensor/Metric metadata shown in the application is the same as displayed in the TeamViewer IoT Cloud Dashboard.
All Client certificates, created by the application or uploaded by the user, are stored under:
The certificate file names contain the Client Id, as shown in the template below, in case the certificates are needed on remote devices Reference Remote Clients for details.
Public Key: cert-clientId.pem Private Key: key-clientId.pem