Sort by:
Learn how to install the TeamViewer IoT Agent including provisioning and monitoring setup.
View full article
TeamViewer IoT Cloud UI is a web-based management platform for TeamViewer IoT Service.
View full article
 Learn more about how to use IoT Remote Control from the TeamViewer software.
View full article
Make sure you have the latest TeamViewer IoT Agent!
View full article
Linux based device with ARM5 or ARM7 architecture (like Raspberry Pi). Raspbian is an officially supported operating system.
View full article
Use the setup wizard to connect your sensors and view your data in streaming real-time!
View full article
The TeamViewer IoT C-SDK is a development kit to facilitate integration of sensors to the IoT Agent MQTT API. Get the downloads in this article.
View full article
Please find the MQTT API documentation for TeamViewer IoT under  https://download.teamviewer-iot.com/docs/agentapi/index.html .
View full article
Learn more about Teamviewer's IoT new remote screen feature which allows a user to access the screen attached to a remotely accessed device with the Teamviewer IoT agent installed on it
View full article
Quick step-by-step example on connecting your sensors to TeamViewer IoT!
View full article
TeamViewer IoT is meant to be used on IoT devices such as headless Linux gateways that ha ve  restricted  re sources and are not able to run the TeamViewer full version.
View full article
The monitoring capabilities offer the ability to create monitoring rules, setting up alerts, proactively manage systems to prevent downtime by monitoring different sensors.
View full article
Yes, currently there is a freemium version of TeamViewer IoT available. During the preview phase of TeamViewer IoT can be used as an extended trial at no additional cost.
View full article
The TeamViewer IoT Node.js SDK is a development kit to facilitate integration of sensors to the IoT Agent MQTT API. Get the downloads in this article.
View full article
Stay in tune with the latest features and see what's in store to come!
View full article
Create and manage advanced Rules & Notifications to keep abreast of any and all changes in your IoT network.
View full article
Webhook Samples for Rule Based Alerts & Notification via TeamViewer IoT Cloud.
View full article
As TeamViewer IoT is a web-based service, there is no dedicated download of an .exe file available.
View full article
Please find the Cloud API documentation for TeamViewer IoT under  https://download.teamviewer-iot.com/docs/cloudapi/index.html .
View full article
Securely Connect to TeamViewer IoT from anywhere in your Network!
View full article
To add a device to TeamViewer IoT, you need to log in to the TeamViewer IoT dashboard under  https://teamviewer-iot.com , click on the  Add device  button.
View full article
TeamViewer IoT can be used for a  variety of purpose, for example, m onitoring smart buildings to control room temperature and turn on the heating.
View full article
To use the TeamViewer IoT dashboard, go to  https://teamviewer-iot.com , and log in with your account credentials.
View full article
TeamViewer is not necessarily needed for using TeamViewer IoT.  The TeamViewer full version is however needed to connect to a device via TeamViewer IoT.
View full article
Find out how to quickly integrate your OPC-UA IoT network with TeamViewer IoT!
View full article
Yes, you can use your existing TeamViewer account for TeamViewer IoT. Your TeamViewer account is basically used to identify you for all IoT services.
View full article
Learn more about the TeamViewer IoT Node-Red Plugin and how to use TeamViewer IoT Node to communicate to TeamViewer IoT cloud, create sensors/metrics and push data to TeamViewer IoT.
View full article
Device access is only possible via easy access. This means that access to the devices is only possible via your TeamViewer account.
View full article
You can activate  Two-Factor Authentication  for your account to provide an additional layer of security to your account.
View full article
This article gives a general overview on the TeamViewer IoT solution and the components that come with the  solution   This diagram shows the core components and features of Teamviewer IoT. Sensors and actuators are connected via the MQTT API to the Teamviewer IoT Agent. This Agent can be installed on any edge devices and on the one hand sends the sensor data to the TeamViewer cloud where it can be analyzed in our cloud dashboard and on the other hand allows incoming connections for remote control operations. The connections to the agent are handled by the TeamViewer IoT Global Access Network. The functionality of all components is explained below in detail.   Core Use cases To offer our three main use cases Remote Operations Remote Assistance Remote Alarming there is a base of 2 technical use cases: Monitoring Monitoring is used to make any kind of data processed on the edge device available to the TeamViewer IoT solution. Meaning it can be accessed via the cloud dashboard or the AppControl application on the edge device. The data gathered during monitoring helps the user to better understand his use case and appliance better and provides insights in his operations. Remote Control The Remote Control module inside the TeamViewer IoT agent enables the customer to access the edge device through the TeamViewer client installed on the user's PC. Once connected the user can have full access over the whole device by using our built-in features (see below). This allows the user to react to the data which was gathered in the monitoring process. The components Sensors and actuators Any device which can be connected to edge device and send or receive data can serve as sensors or actuators. They can be bought from 3rd party vendors where normally all devices are supported by TeamViewer if they are connected to the hardware where TeamViewer is installed on Edge gateway The edge gateway can be any computer device which runs a Linux operating system. For detailed platform compatibility check here: Supported platforms by TeamViewer IoT A very prominent device for PoCs is the Raspberry pi, apart from this one TeamViewer uses the devices from Kunbus, Dell and Systec as reference platform.   TeamViewer IoT Agent The TeamViewer IoT agent is the component installed on the edge to enable the use cases provided by TeamViewer IoT. It makes the edge gateway and the peripherals attached to it accessible to the outside by sending the data to the TeamViewer Iot cloud and handling incoming connections. The agent provides three possibilities to remote control the edge device.  AppControl AppControl provides the ability to create a custom user interface for the device or system the TeamViewer IoT agent is installed on. The UI is a HTML page which is stored on the device. The HTML page can be fully customized and can so reflect any use case. All sensors and actuators registered in the TeamViewer IoT agent and can be accessed by this feature. EdgeManagement The edge management is one application provided by TeamViewer which is using AppControl. It provides the possibility to: view the data processed on the device in real time create rules reacting on the data which are processed directly on the edge set up the MQTT API and its clients via a graphical user interface and so enabling a very easy way to integrate sensors and other peripherals Check the knowledge base entry to understand how the edge management application and its feature can be installed and configured here. Remote Terminal The Remote Terminal provides access to the Linux shell on the device and so full access to the operating system. Remote Screen The remote screen feature allows the user to access a screen which is attached to the edge device. for full flexibility there are 3 different grabbing methods Framebuffer grabbing Grabbing of a X11 session Directly accessing a QT application processed on the device The X11 and QT method provide the possibility to view the content of the screen and take control over it. While framebuffer grabbing only provides read-only access. Find out more about the remote screen feature: General setup Instructions to setup grabbing for QT applications System monitoring The system monitoring agent is a special monitoring module which provides data about the internal system conditions of the device like CPU load or used disk space and many others. Check out how the system monitoring can be set up here. Cloud Dashboard The cloud dashboard is the entrance to the TeamViewer IoT solution. It provides the possibility to: manage the devices assigned to the TeamViewer account set up rules to receive an alert if a metric violates a threshold specified in the rule have an overview of all devices and their metrics in operation through dashboard find guidelines on further functionalities like to add additional sensors The TeamViewer IoT dashboard can be reached on this URL: www.teamviewer-iot.com Web API The Web API enables the user to interact with the data stored on the TeamViewer IoT and so enables that the data is downloaded or forwarded to another cloud for further enhanced data processing. TeamViewer can provide example on how to connect to the Thingworx IoT platform and to AWS. User PC To connect to the TeamViewer IoT Agent a PC with a TeamViewer client installed is needed. Currently the connection can only be established from Windows PCs. The cloud dashboard to view the data can be accessed from any browser. The Teamviewer Client can be downloaded here: https://www.teamviewer.com/de/download/windows/ Global Access Network The TeamViewer infrastructure provides a secured and easy to set up point to point connection between PCs and other PCs or devices. For more information about the Global Access Network and its security features click here https://www.teamviewer.com/de/trust-center/sicherheit/  
View full article
TeamViewer IoT uses full encryption. Encryption is based on 2048bit RSA private/public key exchange and 256 Bit AES session encoding.
View full article
All you need is a log! Quickly integrate your IoT network with TeamViewer IoT - no coding required!
View full article
This article applies to all TeamViewer IoT users. who monitor their IoT network. This guide will provide an example of how to integrate with https://ifttt.com/ using TeamViewer IoT Webhooks. On the TeamViewer IoT dashboard, you can configure Webhook alerts to integrate your IoT solution with many third parties.  Webhooks trigger further actions like sending a text message or sending a notification via your messenger like Telegram by using a service like https://ifttt.com/.  After you sign up with Ifttt, click on New Applet to create a new applet:   Set a trigger by clicking on +this Enter Webhooks on the search field and select Webhooks   After confirming, select an Event name for the trigger like alert Then create the trigger and select a service like email   After creating the action, you will see a confirmation, that your Applet is configured, though you now have to configure the webhook and the action (email). So go back to My Applets and switch to the tab Services and configure your Webhooks Then click on Settings to find your Webhook URL like Copy the URL and enter it on your web browser    Remember, our trigger we configured earlier was alert so replace the "{event}" with alert on the URL and you now have the webhook URL, that you enter on the IoT dashboard under Add Rule.   Congratulations! You have successfully configured your trigger! Don´t forget to go ahead and configure your email account at Ifttt and test the connection by entering the webhook URL on your browser and check your inbox if an email has arrived.
View full article
Real Time Rule Engine Processing for your TeamViewer IoT Edge Management Application
View full article
This article will guide the user to enable remote screen grabbing for Qt applications by using the remote screen SDK provided by Teamviewer General TeamViewer currently provides 3 different options to access the content of the screen attached to a device on which the TeamViewer IoT agent installed. In this article the option to directly access Qt applications is described. This is realized through an SDK which TeamViewer provides. This SDK is directly linked into the application and so enables the connection to the Teamviewer IoT agent on the edge device and so to the TeamViewer network.   Building Block Description Qt application The Qt application that in the end provides a user frontend which can be accessed from the outside Customer Qt application The frontend part of the Qt application. This is not provided by TeamViewer, but from the entity that designs the application and device. RemoteScreen SDK Software Development Kit containing an interface and plugin to enable remote control for a customer application (short: SDK/plugin). TeamViewer IoT agent TeamViewer software enable the edge device to create TeamViewer connections for remote control TeamViewer Client The TeamViewer program installed on the user pc. To initiate remote control connections to the device.   Requirements There are some preconditions ,   that you must meet, so that you can use this feature. Please make sure that you fulfill them all: You need a valid license for TeamViewer 14. The TeamViewer IoT agent must be installed on the device There must be a Qt application running on the device and this application must be accessible so the remote screen SDK can be linked to it. This device should either be configured to display the user interface via a Linux frame buffer device or is capable enough to send its image data to the SDK Software dependencies For building the whole package the following libraries and tool need to be available: CMake (3.5 or newer) Compiler tool chain with support for C++14 (like GCC or Clang) Google Protocol Buffers library (3.0 and newer) Google gRPC library (1.20 or newer) zlib (needed by gRPC Qt 5 (5.3 or newer) On debian systems (when writing the documentation debian 10 was the latest) the following development packages can be used for building cmake build-essential or g++ libgrpc++-dev protobuf-compiler-grpc libprotobuf-dev protobuf-compiler qtbase5-dev qtdeclarative5-dev For example :  sudo apt-get -y install cmake Hardware requirements For supported platforms regarding the TeamViewer IoT Agent visit https://www.teamviewer.com/link/?url=150157 At least 30 MB free disk space Systemd software suite Glibc-utils package (version 2.17 higher) Linux 2.6.27 kernel Where to download The TeamViewer Remote Screen SDKcan be downloaded by clicking on the follwoing link: http://download.teamviewer-iot.com/remoteScreenSDK/TVRemoteScreenSDK_1.0.9.zip How to build a Qt application with the Remote Screen SDK To build the remote screen SDK please ensure that all required libraries and dependencies are installed and available. Steps to build:  # create and navigate to a build directory mkdir build cd build # run cmake cmake <path to extracted SDK> # run make make After building the package there should be two binaries:  libTVQtRC.so - integration plugin, used by a Qt application for providing Remote Screen capabilities -qt_simulate - an example application showing the basic usage of the plugin Installation for Development The SDK can also be installed to be used in a development environment: # default installation (as root, if needed) make install The default installation prefix for CMake is /usr/local. So after installation there are two projects installed: TVRemoteScreenSDK The Qt plugin (<prefix>/lib/lbTVQtRC.so) along with the public headers (<prefix>/include/*.h) to use it. TVRemoteScreenSDKCommunication The public C++ API used by the plugin. This API in independent of Qt and can be used together with any other framework. To install the SDK into a custom prefix one can override CMAKE_INSTALL_PREFIX when configuring the SDK before building: # configure to install into custom prefix cmake -DCMAKE_INSTALL_PREFIX=<custom-install-path> <path-to-sources-root> Configuration settings Configuration of the TeamViewer IoT agent The TeamViewer IoT agent needs then to be configured to remote control an "external application". This configuration involves also specifying a so-called "image grab strategy": With that the agent tells the application in what way it expects image updates. To do this: From remote terminal run: sudo teamviewer-iot-agent configure set EnableRemoteScreen 1 sudo teamviewer-iot-agent configure set RemoteScreenChannels \"EAP\" Note: That the value in escaped double quotes can vary from user case. The values could be: Use case Setting External App (SDK) with built-in grabbing [strng] RemoteScreenChannels = \"EAP\" External App (SDK) with notifications about framebuffer changes → FB device /dev/fb42   [strng] RemoteScreenChannels = \"EAP:FBPush:/dev/fb42\" External App (SDK) with frambuffer grabbing → first FB device (/dev/fb0)   [strng] RemoteScreenChannels = \"EAP:FBPull\"    The agent currently supports the following strategies: Application provided (default when setting the remote screen channel to "EAP") The application (or the Qt plugin) is grabbing internally and send resulting images to the TeamViewer agent. Linux frame buffer device continuous (called "FrameBuffer-Pull" or the channel setting "FBPull") This repeatedly copies the contents of a Linux frame buffer device regardless of any actual image changes. Linux frame buffer device with notifications (called "FrameBuffer-Push" or the channel setting "FBPush") This copies the contents of a Linux frame buffer device when the external application notifies the agent to do so. After starting the agent its API for remote screen is now available and can be used by the Qt plugin. Further configuration After installing the IoT Agent it creates a system group called 'tv_api'. Every application that wants to communicate with the agent needs to run under a user that is part of the before mentioned system group: # add current user to group tv_api usermod -a -G tv_api $USER For further information on the TeamViewer IoT agent check here https://community.teamviewer.com/t5/TeamViewer-IoT-Knowledge-Base/TeamViewer-IoT-Remote-Screen/ta-p/58731 Example application In the package for the SDK is an example application included. This example show the basic operations of the SDK and how to integrate the plugin into a Qt Quick based application. It requires Qt 5.3 with the modules Qt Quick 2.3 and Qt Quick Window 2.0 to run. On debian based distributions the following packages are required to run: qml-module-qtquick2 qml-module-qtquick-window2 To start the example application: Open the Build directory using graphical interface Locate the qt_simulate execute the qt_simulate With the example application one can also test and see the basic operations: connectivity to the agent: the circle on the top left corner is green when the IoT agent is available (this does NOT indicate network connectivity) set the control mode: "Set Full Control" (image updates and input), "Set View Only" (image updates, no input), "Disable Remote Control" (no image updates, no input) terminate all incoming TeamViewer sessions: Terminate TV Session" is only enabled if there is at lease one active remote control session. By clicking, it terminates all incoming sessions and the button is disabled afterwards. mouse and keyboard input testing rudimentary animation testing Known Issues Please contact TeamViewer IoT Support ⟨iot-support@teamviewer-iot.com⟩ if you encounter problems when using the remote screen SDK. Inverted Colors On some ARM based devices, the colors may seem inverted or appear wrong on the client’s side. Screen refresh When the RemoteScreenChannels setting is configured with EAP:FBPush, it may happen that the client picture is sometimes not refreshed appropriately during a TeamViewer session. Resizing the window will force an update and will display the actual content of the application in the client window. For more information about the different channel configurations and their use, please visit https://www.teamviewer.com/link/?url=710439 License information The TeamViewer Remote Screen SDK is released under MIT License allowing an easy integration of our source code. To create Qt applications respective Qt licenses are needed Further reading/Realated articles General information on Remote Screen Grabbing How to install the TeamViewer IoT agent Also please check the readme file inside the Remote screen SDK for additional information
View full article
This article describes what the different blinking patterns of the XDK mean and what is the reaction to it if an error occurs. General The Bosch XDK 110 sensor kit is a freely programmable sensor whcih provides 8 different measurements. For the TeamViewer IoT starter kit it is programmed to send all to the TeamViewer IoT agent which then are visible and usable in the TeamViewer IoT solution. The follwing measurements are possible and shown in the TeamViewer IoT cloud: 3-axis accelerometer 3-axis gyroscope 3-axis magnetometer Accoustic noise sensor Air humidity sensor Air pressure sensor Temperature sensor Light sensor Vibration (derived from 3-axis accelerometer) Datasheet + supplier information for the sensor For exact product features operation conditions and the ability to program the sensor please check the supplier's homepage: https://xdk.bosch-connectivity.com/ Datasheet: see attachment of this article FAQ Attaching other sensors to the GPIO pins The XDK sensor is freely programmable and also supports that other devices are attached to it. This requires a new program written for the XDK. The instruction on how to do this can be found in the XDK community. Note: To attach new devices to the starter kit and the TeamViewer IoT solution, TeamViewer in general recommends to attach additional devices directly to the gateway instead of adding them to the sensor. Battery Life The battery lifetime of the XDK sensor is up to 24 hours depending on environmental conditions like temperature. Status LEDs The XDK has 4 LEDs on the top side. Each indicates a different status:   LED   Meaning Green Charging indicator (lights on when the XDK is connected to a power source and the internal battery is charging) Yellow Flashes every time when sensor data is transmitted to the gateway. Orange Blinking while it tries to connect to the gateway Red Blinking while the XDK is connecting to the Teamviewer IoT service Lights on when it is connected Position of the LEDs LED indications Pattern Meaning and action No LED is on The battery is empty, please connect it to a power source with a micro USB cable Green LED is off, but the power source is connected The battery is fully charged Orange LED is constantly blinking Check if the gateway is powered Check if with another device (e.g. smartphone or laptop) the Wifi network "TV_Starter_Kit" is available. If yes restart the XDK, if not move closer to the gateway or restart it. Red LED is lighting, yellow  LED  not flashing  No data is received from this XDK on the dashboards Restart the XDK    
View full article
This article explains how to move the Teamviewer Starter Kit from the preassigned account to another Teamviewer account. Step 1: Find out the IP address of the gateway in the local network Option 1: Ask your network administrator to connect the gateway to the network and provide you with IP address Option 2: You can remotely access the gateway from TeamViewer desktop client application as it is already assigned to the predefined account. Open TeamViewer desktop client application Login with the provided account credentials From the Contacts and Computers tab connect to your gateway Switch to the “Remote Terminal” tab In the Remote SSH window type “ifconfig” command and write down the IP address of the eth0 interface Close TeamViewer remote connection session Step 2: Install SSH client Install SSH client on your desktop computer (e.g Putty). Open SSH connection to the gateway in the local network using the IP address obtained in Step 1. Step 3: Unmanage the gateway Use the bellow Linux command to unmanage the TV Agent from the current account $ sudo teamviewer-iot-agent unmanage Step 4: Create a new TeamViewer IoT account Open your web browser and navigate to https://teamviewer-iot.com. Click “Sign Up” and follow the instructions to create a new TeamViewer IoT account. Remember your E-Mail and Password that has been used for the account creation. Step 5: Provision the gateway to the newly created account. In your SSH session use the below command to provision the gateway to your new account using the E-Mail and Password obtained in Step 4 and follow the instruction. $ sudo teamviewer-iot-agent setup Upon successful provisioning of the gateway, you will have a new device in the TeamViewer desktop client application as well as in your cloud dashboard under the “Devices” tab. Its name will be the hostname of the gateway. Step 6: Configure the TeamViewer IoT Agent to receive measurements from Bosch XDK sensors Disable TeamViewer Monitoring Agent $ sudo teamviewer-iot-agent disable system-health Restore the configurations for the Monitoring Agent $ sudo su $ sudo cat /var/lib/teamviewer-iot-agent/system_monitors_kit.conf > /var/lib/teamviewer-iot-agent/system_monitors.conf Enable TeamViewer Monitoring Agent $ sudo teamviewer-iot-agent enable system-health Step 7 - Configure the digital input and output (DIO) pins To use the DIOs of the Dell gateway with TV Agent first you need to create corresponding Sensors/Metrics. Open your web browser and type the IP address obtained in Step 1 to open the Edge Management application. Navigate to the “API Clients” tab and create a new client.       Enter "Digital Out" as a client name and push the "Create" button then "Manage API Client".         Create "New Sensor" (name "Digital Outputs") with 8 metrics (names "Out 0...7") according to the screenshot below (Value Type: Bool, Display Unit: I/O).             After Pushing the “Create” button you will be provided with the Connector, Sensor and Metric IDs which will be required to edit “teamviewer_gpio.py” file in the next step.             Step 8 Open the “teamviewer_gpio.py” file $ sudo nano teamviewer_gpio.py Replace the “client_id”, “sensor_id” and “Out0_id” to “Out7_id” on the top of the file with corresponding IDs obtained in the previous Step 7. Example: client_id = "5385da5e6c854abc8d65c0c80b5d79e9" sensor_id = "e6218136a1144c8e9d117dc55a24297c" Out0_id = "4ee43a05e70a4a97a20fe13e6baf286e" Out1_id = "58f38038ea0b48519332a190688a325e" Out2_id = "cf1aceeb62f3479fb07d81213dd21269" Out3_id = "05f12c7970704172a374f777bedc83ef" Out4_id = "d67d349dba2347699096bc0989f638c8" Out5_id = "8dac154dfeef4d5aa4ec33b39a675ee4" Out6_id = "cefdd235b1c243a2b6f7d89a6ce639e3" Out7_id = "50835cca2df34f19bb13b8a5e0873ed2"         Step 9: Restart the service for the GPIOs $ sudo service teamviewer_gpio restart Step 10: Check if the DIOs are working To control the DIOs from the dashboard user needs to pin the "Out 0..7" metric from the "Metrics" tab to the dashboard and configure it as a "Control" with "Toggle-Switch" function. Use "true" and "false" for the control values as presented in the below screenshot.  
View full article
This article applies to IoT users who are using the TeamViewer Application running on Windows OS to remotely access the web interface of their IoT Device   Overview TeamViewer uses the browser engine of the Internet Explorer (IE) to render the web content of the Remote AppControl tab in the IoT remote sessions. Starting with version 15.9, TeamViewer will support the Microsoft Edge WebView2 technology for the IoT Devices. Microsoft Edge WebView2 is a Chromium-based web control that can handle web technologies not being supported by IE. Preview Notice Please note that this feature is based on functionality provided by Microsoft, which is still in an evaluation phase. As a result, unexpected behavior and malfunctions may occur. The feature should therefore not be activated for the operation of production or live systems. Please note that with the activation of the feature certain data is transferred to Microsoft. For more information, please refer to the Microsoft privacy policy. The support of the Microsoft Edge WebView2 in TeamViewer is provided in a preview mode. It is intended for early prototyping and testing. The stable version will be provided as soon as the WebView2 Runtime will be released. For more information on the Webview2 release plan please review the Microsoft Edge WebView2 roadmap. Requirements A Windows (7, 8.1, 10) machine, with TeamViewer v15.9 or higher. A Microsoft Edge WebView2 Runtime installed. An IoT Device with a running web application How to Activate the New Browser Engine Before you switch to the new browser engine please make sure that you have the Microsoft Edge WebView2 Runtime installed on your machine. If it is already installed you can skip this step. There is a chance that your machine already has this component as it could come with other applications using WebView2 technology. The WebView2 also comes with Microsoft Edge Insider builds that include the latest fixes by Microsoft. That is why we also recommend installing Microsoft Edge Canary Channel instead of Microsoft Edge WebView2 Runtime. For 32-bit operating systems, you need to install the Microsoft Edge Canary. Open TeamViewer Application and navigate to Extras->Options->Advanced->Show advanced options->IoT options. Enable the checkbox for the Use Microsoft Edge WebView2 for Remote AppControl. On your next connection to the IoT device, Microsoft Edge WebView2 will be used to display the web content. Below is an example of using the old and the new browser engines for the Remote AppControl  tab.
View full article
This article applies to all TeamViewer IoT users that want to install TeamViewer IoT Agent on Raspberry devices. General TeamViewer IoT already had instructions on how to install TeamViewer IoT Agent to Raspberry PI devices that comes with preinstalled OS. But how to do with the devices that has no OS installed on them? With this feature we have made it easier for users to have both OS and Agent installed on Raspberry PI device and automatically register the device to the TeamViewer Account. Compatibility The feature is tested  and is compatible with the following Raspberry PI models: Raspberry Pi Zero W Raspberry Pi 1 Raspberry Pi 2 Raspberry Pi 3 Raspberry Pi 4 Use cases Installing the TeamViewer IoT Agent required an access to CLI GUI, so there was a need to connect a keyboard and monitor to your Raspberry PI device. Now when the Agent is installed automatically by the configuration scripts on device boot, no more need to have/connect an extra equipment. This method can be used for mass deployment of the agent on multiple Raspberry PI devices. Just flash the microSD cards with the required OS and configuration file, insert to the devices and power up. You can have your devices up and running TeamViewer IoT within minutes. How to Setup Login in TeamViewer IoT Management Console from navigation panel click on Inventory and from the ADD dropdown menu on the right select Device. Select the required model of Raspberry PI. Scroll down and select Empty Raspberry PI. Now, will get the Configuration settings. Only the Group field is mandatory in configuration. If you want to automatically configure your network (LAN or WiFi) parameters on your device, then you need to fill Hostname, WiFi Network Name (SSID), WiFi Password and Country. Once you are done with the input of your settings, click Download Configuration. This will download the .zip package which contains scripts and configuration for TeamViewer IoT Agent installation. Once you downloaded the configuration, download the OS that you want to have on your device. It can be one of the followings: Raspbian Buster with desktop and recommended software Raspbian Buster with desktop Raspbian Buster Lite   Note: The links to these images can be found in instructions page for easy reference. After you downloaded the necessary OS, you would need an image writing tool such as Win32 Disk Imager, Rufus, Etcher, ApplePi-Baker, Acronis True Image, etc. Make sure that microSD is properly formatted, and partitions are deleted. Write the OS image to the microSD card from Raspberry PI device. After you have the OS on the microSD card, you will notice the “boot” partition. Extract the downloaded Configuration files from earlier step and copy to boot partition on MicroSD card by replacing all the files on boot partition with downloaded configuration file. Now insert the microSD card back to your Raspberry PI device and power up. Don’t forget to connect the LAN cable if you intend the device to work in LAN network. It will take 3 to 5 minutes for the device to boot and install the TeamViewer IoT Agent on the OS. This will be done by scripts and configuration files you have on microSD card, so no extra step is required. Once the device is up, go to Inventory, or simply refresh the page if you are already on the page and find your device there. Now you can add sensors, metrics, remote connect and use other features of TeamViewer IoT.    
View full article
 This article describes how to connect the Teamviewer IoT Starter Kit to the internet using its internal modem Prerequisites Connect the antennas to the gateway Insert a sim card into the sim card slot Connect the Gateway with LAN cable to the internet and power it up Connect with Teamviewer Client or SSH to the device and login to the remote terminal Enable the WWAN Connectivity Unlock the card The gateway can automatically connect to mobile internet if the SIM card does not require a pin. If the SIM card inserted into the gateway requires a pin, there are 2 ways to unlock it: Insert the SIM card  into a phone and follow the settings to unlock it Follow the steps below to unlock the pin from the gateway: $ sudo nano /etc/systemd/system/pinunlock.service Copy and paste the below text and provide the correct pin instead of **** [Unit] Description=Sim pin unlock After=network.target Requires=snap.modem-manager.modemmanager.service [Service] Type=idle ExecStartPre=/bin/sleep 60 ExecStart=/snap/bin/mmcli -i 0 --pin= **** [Install] WantedBy=multi-user.target Exit the nano editor and execute the service $ sudo systemctl enable pinunlock.service Activate the WWAN modem Check the modem model The gateway is currently equipped with one of 2 gateway options and  depending on the version the commands are different  Command  Description / expected output $ sudo mmcli -L shows the installed modem based on the output from the last section follow instruction either 1 or 2 1. Instructions for [Sierra Wireless, Incorporated] Qualcomm™ Snapdragon™ X7 LTE DW5818 modem  Command  Description / expected output $ sudo nmcli c add type gsm ifname cdc-wdm0 con-name <ConnecctionName> apn <operator_apn> $ sudo reboot create a connection with a meaningful connection name and set the apn from your sim card provider (e.g. web.vodafone.de) reboot the modem   2. Instructions for the [Dell] MBIM modem Unlock the SIM via phone or use below commands  Command  Description / expected output $ sudo mmcli -m 0 $ sudo mmcli - i 0 --pin=<pin_number>  --disable-pin $ sudo nmcli c add con-name <ConnectionName> type gsm ifname cdc-wdm0 apn <apn-name> $ sudo nmcli r wwan $ sudo nmcli c up <Connection-Name> $ sudo reboot modem status display --> check if  card was found unlock card and disable the pin create a connection with a meaningful connection name and set the apn from your card provider (e.g. web.vodafone.de)      
View full article
Learn how to apply complex rules and create Alarms based on them in Cloud UI.
View full article
This article applies to all TeamViewer IoT users. General The Yocto Project enables the creation of custom Linux-based systems for embedded devices. The TeamViewer IoT Agent will run on Yocto Linux devices given minimum requirements and configurations are met. This article is an example how to build Yocto Image with TeamViewer IoT Agent for Raspberry using the layer provided in GitHub. Information about this here   Requirements You need some dependencies to develop projects in the Yocto Project.  Please check here for more information. How to setup Install dependencies based on OS version (use verified OS for building image). Check here Open Terminal on Host Machine and run the commands below:   Clone poky project's zeus branch git clone --branch=zeus git://git.yoctoproject.org/poky.git && cd poky Clone raspberryPi and TeamViewer IoT agent meta-packages git clone --branch=zeus git://git.yoctoproject.org/meta-raspberrypi git clone --branch=zeus https://github.com/teamviewer/meta-teamviewer-iot-agent Configure Environment  source oe-init-build-env Add Layers to bitbake bitbake-layers add-layer ../meta-raspberrypi bitbake-layers add-layer ../meta-teamviewer-iot-agent Change the target Machine on the configuration file and set init manager to systemd echo 'MACHINE = "raspberrypi3"' >> conf/local.conf echo 'DL_DIR = "${TOPDIR}/downloads"' >> conf/local.conf echo 'CONNECTIVITY_CHECK_URIS = "https://www.google.com/"' >> conf/local.conf echo '#Set Systemd to Init Manager' >> conf/local.conf echo 'DISTRO_FEATURES_append = " systemd"' >> conf/local.conf echo 'DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit"' >> conf/local.conf echo 'VIRTUAL-RUNTIME_init_manager = "systemd"' >> conf/local.conf Append ssh and TeamViewer IoT agent layer, 50MB extra space, and set default password for root user echo '#Append TeamViewer IoT agent layer' >> conf/local.conf echo 'IMAGE_INSTALL_append += " teamviewer-iot-agent"' >> conf/local.conf echo 'IMAGE_ROOTFS_EXTRA_SPACE ?= "50000"' >> conf/local.conf echo 'CORE_IMAGE_EXTRA_INSTALL += "openssh"' >> conf/local.conf echo 'INHERIT += "extrausers"' >> conf/local.conf echo 'EXTRA_USERS_PARAMS = "usermod -P raspberry root;"' >> conf/local.conf echo 'VOLATILE_LOG_DIR = "no"' >> conf/local.conf OPTIONAL - For installing Xvfb server in the target device to be able to use X11 features echo '#X11' >> conf/local.conf echo 'DISTRO_FEATURES_append += " X11"' >> conf/local.conf OPTIONAL - For enable edge management with Docker in the target device git clone --branch=zeus git://git.openembedded.org/meta-openembedded ../meta-openembedded git clone --branch=zeus git://git.yoctoproject.org/meta-virtualization ../meta-virtualization sed -i '$d' conf/bblayers.conf echo ' ${TOPDIR}/../meta-openembedded/meta-oe \' >> conf/bblayers.conf echo ' ${TOPDIR}/../meta-openembedded/meta-multimedia \' >> conf/bblayers.conf echo ' ${TOPDIR}/../meta-openembedded/meta-networking \' >> conf/bblayers.conf echo ' ${TOPDIR}/../meta-openembedded/meta-python \' >> conf/bblayers.conf echo ' ${TOPDIR}/../meta-openembedded/meta-filesystems \' >> conf/bblayers.conf echo ' ${TOPDIR}/../meta-virtualization \' >> conf/bblayers.conf echo ' "' >> conf/bblayers.conf bitbake-layers show-layers echo '#Docker layer for supporting Edge services' >> conf/local.conf echo 'DISTRO_FEATURES_append += " virtualization"' >> conf/local.conf echo 'IMAGE_ROOTFS_EXTRA_SPACE = "400000"' >> conf/local.conf Run the command below to start the build bitbake core-image-minimal Notes: You can find target image tmp/deploy/images/raspberrypi3/ here with core-image-minimal-raspberrypi3 prefix. In case of failure or new bash ( terminal ) creation, after all steps executed you need to go to Project's directory and start again from Configure Environment. When using 'ssh' with the built image, the username is 'root' and the password is 'raspberry'.
View full article
This article applies to all TeamViewer IoT users and requires TeamViewer IoT Agent 2.9 or higher and TeamViewer client version 15.5 or higher. General TeamViewer IoT edge devices can be accessed remotely via the internet. Now, with the help of FileTransfer feature that TeamViewer IoT offers, users can upload and download files from their remote computers to the IoT edge devices in the filed and vice versa. How to Set Up Connect with the TeamViewer client to the device and use Remote Terminal Enter this command: sudo teamviewer-iot-agent configure set FileTransferAccessControl 0   Note: Be careful when enabling this feature. You will have access to the file systems of the device with the root permission. It is recommended to disable the File Transfer when sharing the device with other accounts/users. Now, you will see that File Transfer  option is activated when you connect with TeamViewer client.   Click on the File Transfer button;  the transfer window will appear and you can start upload or download files.   How to Disable To disable this feature, from Remote Terminal run: sudo teamviewer-iot-agent configure set FileTransferAccessControl 2
View full article
This article applies to all TeamViewer IoT users and requires TeamViewer IoT Agent 2.8.14 or higher. General The “Easy Setup“ feature for adding sensors is intended to provide an intuitive and easy user experience which will lead through the setup steps in adding the sensors. How to setup Login in TeamViewer IoT Management Console from navigation panel click on Inventory and from the ADD dropdown menu on the right select Add Sensor.   After, click on Easy setup button.   Note: There are thousands of different sensors in the world. Some of them would need special libraries or custom development to get a data from. That’s why we provide a custom solution which will help to setup sensors easily from TeamViewer IoT Management Console Here, select the Device for which you add a sensor (when you used the Device menu, it will come preselected). Make sure the latest version of Agent installed on the device, otherwise a warning will be displayed, and it will not be possible to continue with the setup. After selecting the device, you need to provide a unique Sensor name along with Metric name and ID. Value Type and Value Unit fields are optional.     Note: Sensor name is limited to 50 characters and alphanumeric and special characters can be used. Metric name has a limitation of 30 characters. Metric ID is limited to 32 characters and only Latin letters and numbers can be used (no special characters are allowed). You will get an error message if these rules are not followed. Value Type default selection is “Number”.  Once you are done with configuring one metric, you can add the next one, as well as delete already configured metrics. Up to 10 metrics can be configured per sensor. Now, when the Sensor and Metrics are configured, click on “download the generated template”. The zip downloaded file contains the template examples in Python and Bash. Unzip the file and select your preferred template. The template script prints metric values of a sensor in JSON format and each metric is described as a variable which gets a random value in between 1 and 20. If you don't have a ready script, you might need to search for tutorials on how to read your sensor data, find a library or script that works with your sensor and make sure that your script's output prints the JSON formatted example as presented in the template. Then place the ready script on the edge device and provide the full path information into the configuration page.     Note: The script path and name validations are done with predefined standards and the scripts are checked to have python or shell file extensions. Don't forget to run "sudo chmod +x /<path to script>" on edge device to provide execution permissions to the script. It is advised also to manually execute the script on the device and check if the output matches the required JSON format. This will prevent further confusions. Next, select the frequency by which the data will be sent to the TeamViewer IoT Cloud. It can be defined in seconds or minutes. Press ADD button to send the configuration to the Agent, and once the Agent receives the configuration it will process with the data collection.    
View full article
  General All the gateways of the TeamViewer IoT Starter Kit come with built-in GPS receiver.  If the Starter Kit that you have received does not have the "Location" client  in the "API Clients" list you can simply enable it using this article. Requirements TeamViewer IoT Starter Kit How To Enable GPS receiver From TeamViewer desktop client connect to the Starter Kit then switch to the "Remote Terminal" tab. Another way is to use a remote SSH client to the Dell gateway. For the SSH credentials use "admin" for the user name and password from your Starter Kit account. Install python3-pip package sudo apt-get update sudo apt-get install -y python3-pip Wait for the completion of the installation. At some point, you will receive a message to stop some services. Accept it and continue. Download the Starter Kit configuration package and install it. wget -q https://download.teamviewer-iot.com/teamviewer-iot-kit/v2.0.1/teamviewer_iot_kit-2.0.1-py3-none-any.whl sudo -H pip3 install teamviewer_iot_kit-2.0.1-py3-none-any.whl Configure the location receiver of the gateway. sudo teamviewer-iot-kit -e location_receiver Wait for the configuration process to complete. Configuration On TeamViewer Edge Device Management Switch to the "Remote AppControl" tab and check the "API Clients". You will find the "Location" client which contains data from the location receiver. Make sure that the WiFi antenna is connected to the gateway. The WiFi antenna is also being used for the GPS receiver. Place the gateway next to the window so it will have the sky view. Go to the "Metrics" tab, and pin "Latitude", "Longitude" and "Mode" metrics to the dashboard. Switch to the "Dashboard" tab and configure newly added widgets. You should be receiving data from the location receiver. As soon as "Mode" becomes 2 or 3 you will receive accurate "Altitude" and "Longitude" values. Extra Information: The GPS data is "NMEA 0183" formatted and packed into a JSON object called "NMEA 0183: TPV". In the "Metrics" tab you will find the data in the raw format as well as dedicated metrics for each parameter. The location receiver provides the "NMEA 0183: SKY" object as well which is not presented in the Starter Kit. From that object, two metrics are being calculated and presented separately with the names "In View" and "Used". The below table represents all the available parameters/metrics and their descriptions of the location receiver. Name Always Type Description Time No string Time/date stamp in ISO8601 format, UTC. May have a fractional part of up to .001sec precision. May be absent if the mode is not 2 or 3 NMEA 0183: TPV Yes string NMEA 0183 formatted JSON data of the TPV class Mode Yes numeric NMEA mode: %d, 0=no mode value yet seen, 1=no fix, 2=2D, 3=3D Estimated timestamp error No numeric Estimated timestamp error in seconds. Present if time is present Latitude No numeric Latitude in degrees: +/- signifies  North/South.  Present  when the mode  is 2 or 3 Estimated latitude error No numeric Latitude error estimate in meters. Present if the mode is 2 or 3 and DOPs can be calculated from the satellite view Longitude No numeric Longitude in degrees: +/- signifies East/West. Present when the mode is 2 or 3 Estimated longitude error No numeric Longitude error estimate in meters. Present if the mode is 2D or 3D and DOPs can be calculated from the satellite view Altitude No numeric Altitude in meters. Present if the mode is 3 Estimated vertical error No numeric Estimated vertical error in meters. Present if the mode is 3 and DOPs can be calculated from the satellite view Speed No numeric Speed over ground, meters per second Estimated speed error No numeric Estimated speed error in meters per second. Present for consecutive 2D or 3D fixes. Climb No numeric Climb (positive) or sink (negative) rate, meters per second Estimated vertical error No numeric Estimated climb error in meters per second. Present if consecutive 3D fixes. Track No numeric Course over ground, degrees from true north In View No numeric Number of satellites which are in view of the location receiver Used No numeric Number of satellites to which the location receiver is locked  
View full article
This article applies to all the customers looking for AWS Integration with TeamViewer IoT Solution. General This article helps to establish communication between AWS Greengrass and IoT TV Cloud by publishing and subscribing data from teamviewer-iot-agent to aws greengrass platform and vice-versa. Requirements TeamViewer IoT Agent   installed and provisioned to an account.  TeamViewer IoT Edge Management   installed on the edge device Installing AWS Greengrass  Configure AWS IoT Greengrass on AWS IoT Sign in to the AWS Management Console on your computer and open the AWS IoT console. If this is your first time opening this console, select Get started. In the navigation pane, select   Greengrass  image      On the   Welcome to AWS IoT Greengrass   page, select Create a Group.  An AWS IoT Greengrass   group   contains settings and other information about its components, such as devices, Lambda functions, and connectors. A group defines how its components can interact with each other. Greengrass needs your permission to access other services  dialog box, select Grant permission  to allow the console to create or configure the Greengrass service role for you.  On the   Set up your Greengrass group   page, select Use default creation   to create a group. Enter a name for your group (for example,  MyFirstGroup ), and then select Next . Use the default name, and then select Next. On the Review Group creation page, select Create Group and Core. Download your core's security resources and configuration file. On the confirmation page, under Download and store your Core's security resources, choose Download these resources as a tar.gz. The name of your downloaded  tar.gz  file starts with a 10-digit hash that's also used for the certificate and key file names. After you download the security resources, select Finish. Download the AWS IoT Greengrass Core software installation package. select the CPU architecture and distribution (and operating system, if necessary) that best describe your core device. For example: For Raspberry Pi Model B or B+, download the Armv7l for Raspbian package. For an Amazon EC2 instance, download the x86_64 for Linux package. Start AWS IoT Greengrass on the Edge Device In a   previous step, you downloaded two files to your computer: greengrass- OS-architecture -1.10.0.tar.gz . This compressed file contains the AWS IoT Greengrass Core software that runs on the edge device. hash -setup.tar.gz  (for example,  c6973960cc-setup.tar.gz ). This compressed file contains security certificates that enable secure communications between AWS IoT and the  config.json  file that contains configuration information specific to your AWS IoT Greengrass core and the AWS IoT endpoint. Transfer the two compressed files from your local computer to the edge device. To transfer the compressed files from your computer to edge device, using file transfer feature . Open a terminal on th edge edevice and navigate to the folder that contains the compressed files (for example,  cd /home/pi ). Decompress the AWS IoT Greengrass Core software and the security resources. sudo tar -xzvf greengrass-OS-architecture-1.10.0.tar.gz -C / sudo tar -xzvf hash-setup.tar.gz -C /greengrass Review Server Authentication in the AWS IoT Developer Guide and choose the appropriate root CA certificate. We recommend that you use Amazon Trust Services (ATS) endpoints and ATS root CA certificates. Certificates enable your device to communicate with AWS IoT using the MQTT messaging protocol over TLS. For ATS endpoints (preferred), download the appropriate ATS root CA certificate. The following example downloads  AmazonRootCA1.pem . The  wget -O  parameter is the capital letter O. cd /greengrass/certs/ sudo wget -O root.ca.pem https://www.amazontrust.com/repository/AmazonRootCA1.pem You can run the following command to confirm that the  root.ca.pem  file is not empty: cat root.ca.pem (If the  root.ca.pem  file is empty, check the  wget  URL and try again.) Start AWS IoT Greengrass on your edge device. cd /greengrass/ggc/core/ sudo ./greengrassd start You should see a  Greengrass successfully started  message. Make a note of the PID. You can run the following command to confirm that the AWS IoT Greengrass Core software (Greengrass daemon) is functioning. Replace  PID-number  with your PID: ps aux | grep PID-number Lambda Functions on AWS IoT Greengrass User should copy/paste the code to his lambda function, get the metrics values and use greengrass sdk to push the data to the AWS.  Don't forget to replace the paths, client id and sensor id with your own in the lambda functions described below. aws_iot_tv_pub: This lambda function subscribes data from mqtt-broker from edge device and publishes is to amazon cloud to the topic ‘tv/greengrass’.  Below is the sample code attached for aws_iot_tv_pub: #!/usr/bin/python import paho.mqtt.subscribe as subscribe import paho.mqtt.publish as publish import traceback import json def function_handler(event, context): return # AWS part # Change following parameters aws_host = "a10kx625z9icrs-ats.iot.eu-central-1.amazonaws.com" # Endpoint aws_port = 8883 aws_tls = {'certfile': "/home/pi/Downloads/certs/1b9a6e0dcb.cert.pem", 'keyfile': "/home/pi/Downloads/certs/1b9a6e0dcb.private.key", 'ca_certs': "/home/pi/Downloads/certs/root.ca.pem" } # TV part #Change following parameters tv_iot_api_version = "v1.0" tv_host = "localhost" tv_port = 18884 tv_tls = {'certfile': "/home/pi/Downloads/test_client_greengrass/cert-7a2b7efc1ad1473d87e049517a19628b.pem", 'keyfile': "/home/pi/Downloads/test_client_greengrass/key-7a2b7efc1ad1473d87e049517a19628b.pem", 'ca_certs': "/home/pi/Downloads/test_client_greengrass/TeamViewerAuthority.crt"} client_id = "fd9e67783b7441ffb7cd62dda121567a" sensor_id = "111804" def subscribe_data(): try: mqtt_topic_subscribe_data = "/" + tv_iot_api_version + "/" + client_id + "/sensor/" + sensor_id + "/livedata" print("Suscribing to " + mqtt_topic_subscribe_data) subscribe.callback(on_subscribe, mqtt_topic_subscribe_data, hostname=tv_host, port=tv_port, tls=tv_tls) except Exception as e: traceback.print_exc() print(str(e)) def on_subscribe(client, userdata, message): json_message = json.loads(message.payload.decode('utf8')) msgArr = [] for metric in json_message["metrics"]: messageJ = {} messageJ['metricId'] = metric["metricId"] messageJ['metricValue'] = metric["value"] msgArr.append(messageJ) msgs = [] msgs.append({'topic': "tv/greengrass", 'payload': json.dumps(msgArr)}) print(msgs) publish.multiple(msgs, hostname=aws_host, port=aws_port, tls=aws_tls) subscribe_data() aws_iot_tv_sub: This lambda function subscribes the data from amazon cloud and pushes the data to teamviewer metrics and real-time data can be visualized on edge and teamviewer-cloud dashboard. #!/usr/bin/python import paho.mqtt.subscribe as subscribe import paho.mqtt.publish as publish import traceback import json import ssl def function_handler(event, context): return # AWS part # Change following parameters aws_host = "a10kx625z9icrs-ats.iot.eu-central-1.amazonaws.com" # Endpoint aws_port = 8883 aws_tls = {'certfile': "/home/pi/Downloads/certs/1b9a6e0dcb.cert.pem", 'keyfile': "/home/pi/Downloads/certs/1b9a6e0dcb.private.key", 'ca_certs': "/home/pi/Downloads/certs/root.ca.pem", 'tls_version': ssl.PROTOCOL_TLSv1_2 } # TV part #Change following parameters tv_iot_api_version = "v1.0" tv_host = "localhost" tv_port = 18884 tv_tls = {'certfile': "/home/pi/Downloads/test_client_greengrass/cert-7a2b7efc1ad1473d87e049517a19628b.pem", 'keyfile': "/home/pi/Downloads/test_client_greengrass/key-7a2b7efc1ad1473d87e049517a19628b.pem", 'ca_certs': "/home/pi/Downloads/test_client_greengrass/TeamViewerAuthority.crt"} client_id = "7a2b7efc1ad1473d87e049517a19628b" sensor_id = "71b91c40fb2d4f61bec2fa593172085d" def aws_subscribe(): print("Suscribing to tv/greengrassSub") subscribe.callback(on_subscribe, "tv/greengrassSub", hostname=aws_host, port=aws_port, tls=aws_tls) def on_subscribe(client, userdata, message): try: metric_data = json.loads(message.payload.decode('utf8')) mqtt_topic_push_data = "/" + tv_iot_api_version + "/" + client_id + "/sensor/" + sensor_id + "/metric/pushValues" # metric_data = {"metrics": [{"value": 1, "metricId": "7ad8ad3e2dbe4cdcba0ee3ec0cbd2717"}]} msgs = [] msgs.append({'topic': mqtt_topic_push_data, 'payload': json.dumps(metric_data)}) print(msgs) publish.multiple(msgs, hostname=tv_host, port=tv_port, tls=tv_tls) except Exception as e: traceback.print_exc() print(str(e)) aws_subscribe() Further reading/Realated articles For Troubleshooting purposes click here and here
View full article
This article applies to all TeamViewer IoT users and requires TeamViewer IoT Agent 2.9 or higher. General With this feature is possible to remotely configure IoT Agent by assigning settings from TeamViewer IoT Management Console thus eliminating the need to connect remotely to the device and using Remote Terminal and enables bulk configuration of devices and groups.  This knowledge base article is how to configure (enable/disable) edge-management on the devices. How to Setup Log in TeamViewer IoT Management Console and from navigation panel click on Settings Template Click on Create Template Provide the Template Name and the Configuration Note: Currently, users can configure only Edge-Management on the device. Assignement of a Settings Template To Edge Device Any Settings Templates can be assigned to any number of devices and groups owned by the user. To assign a Settings Template, after you created, click on the right options menu and select Assign From the Menu select devices or groups needed. (searchable drop-down list will show all groups and devices) and click Save Setting Template will be assigned to selected devices or groups, configurations will be updated on the device, and device names will be listed in Settings Template list row.     Note: Depending on the edge device  performance, you need to allow some time for the settings template to assign to the device. Upon assigning to a group, all eligible devices within the group will receive the template assignment as well. Devices with unsupported IoT Agent Version as well as Shared devices will be visible in the list, but you will receive an appropriate warning message.  Unassignement of a Settings Template To unassign a settings template, from the same menu where you assign, remove the device or the group and click Save Editing a Settings Template At any time, you can modify the settings for a template. After each modification, all assigned devices will receive an updated assignment. Once the Settings Template is created, click on the right options Menu and select edit. From Menu make the required changes and click Save. To delete a template, navigate to Settings Template menu, click on the right options Menu on the desired template and select Delete. Changing Device Group to Receive Settings Template Once a Settings Template is assigned to a group, user can assign Group's template to any edge device by adding it to that group. From the left menu, click on Inventory. On the device you want to change, on the option Menu select Properties. Change group of the device to the group where the user has Settings Template assigned Check "Inherit Group Setting Configurations" checkmark and click Save. Note: After proceeding with the above steps all other Settings Templates assigned to that device will be unassigned and Group template will be applied. User can also move a device to a group without assigning Settings Template of the group by leaving the "Inherit" checkmark unchecked, in this case, device settings will be managed independently from the group.  
View full article
This article applies to all TeamViewer IoT users and requires TeamViewer IoT Agent 2.8.14 or higher.   General TeamViewer IoT comes with a pre-configured monitor for monitoring the operating system of your Edge Device. You can use this feature to keep track of the following device operating system metrics: 1 min load 5 min load 15 min load Free Memory Total Memory Free Swap Memory Total Swap Memory Buffers Memory Cached Memory Number of CPU cores User CPU Usage Nice CPU Usage System CPU Usage Idle CPU Usage Io Wait CPU Usage   How to Setup Login in TeamViewer IoT Management Console From navigation panel click on Inventory and from the ADD dropdown menu on the right select Add Sensor. Depending of which data  you want to monitor, select  CPU, Memory or Load. You can activate all the  three sensors on your device. After, you need to Select Device from the dropdown menu. The Sensor Name field will be automatically generated with the selected option. Also, it is possible to input the desired name. Next, select the frequency by which the data will be read. It can be defined in seconds or minutes. After you clicked on ADD, you will be automatically redirected In the Inventory menu. Scroll down and select the Sensor  that you just created and pin to you Dashboard. To disable it, just select the desired Sensor and from the right menu, click on Delete.
View full article
General The journey of the IoT user starts from assigning his edge device to the cloud and the assignment process should be as simple as possible. The assignment of a single device is mostly done for testing purposes or when evaluating the solution. Here the time spent on the device assignment will not have a significant impact. But when dealing with a big project mostly we have a bunch of devices that should be assigned to the account. And here it is required to shorten the time spent on the assignment process up to even without touching the device. TeamViewer IoT cloud offers assignments via token functionality which can be used both for single device assignment and for assigning hundreds or thousands of devices in a secure way. How it works For each IoT account, a unique assignment token is being generated. The assignment token can be used only for the device assignment to the account. During the assignment process, the device connects to TeamViewer IoT cloud and presents its assignment token. The assignment service receives the token and connects the device to the account to which the token belongs. Starting from that moment device continues to work with the assigned account. All this process is organized in a seamless way so the device just provides the assignment token. Using the feature In the TeamViewer IoT dashboard go to the "Assignment token" page from the main menu. There you will find the "Assignment token" generated for your IoT account with detailed instructions on how to use it. Click on revel button to view the assignment token   Open your device terminal and install TeamViewer IoT agent. The article "Install TeamViewer IoT Agent" describes the process of installation. For the single device assignment use the below provided command by replacing <token> with the one obtained from the "Assignment token" page. sudo teamviewer-iot-agent assign -t <token> --accept-license For mass assignment of IoT devices, this command needs to be configured to run once when the device boots.  
View full article
This article applies to all TeamViewer IoT users. General The purpose of collecting the data in the cloud is to analyze it. If you want to do some specific analysis with third-party tools you can download the raw data from the IoT cloud. How to setup First, you need to create or to have a Widget. To create one, login in TeamViewer IoT Management Console from navigation panel  select Dashboard and on the right side click on Add Widget button.   Give a Label for your widget; select the Type of visualization, pick the Metric from your sensor/device and click on “OK” button.                               Note: If you select the Chart visualization option, you can choose up to 3 metrics to appear in the same widget.  Now to Export Data to CSV file, click on the menu button of the Widget and select the Export to CSV. Provide a name for the CSV file and select the date range for which the data needs to be exported. Press the Export button. You can select up to 3 Metrics, for which you need to export the data.                                 You will receive an e-mail with the download link of the file as soon as the export is ready.             Note: CSV file uses comma ( , ) as a list separator. Make sure to have the same setting in your Operating System not to have a display issue in case the file will be imported into third-party analysis tools.
View full article
General With the TeamViewer IoT integration for IBHsoftec Edge Gateways, you instantly and securely remote connect to any of your PLCs – with zero complicated VPN setup, allowing easy access to controllers and their programming. The newly developed gateway IBH Link IoT and pre-installed TeamViewer IoT Agent, the possibility is offered to access almost all PLC systems. No PC required on site Encrypted data ensures high security Comfortable and simple configuration via web interface S7 controllers addressable via S7 TCP/IP or IBH Link S7++ S5-controllers addressable via IBH Link S5++ Support of the SINUMERIK 840D/840D SL Support of Mitsubishi controllers MELSEC IQR, FX5, QnA and L series Support for Rockwell Controllogix and Compactlogix controllers Support for Beckhoff TwinCAT controllers For other PLC models please contact IBHsoftec How to Setup To activate Teamviewer Iot Agent on the device, please follow the steps below. Configuration of the IP Addresses The administration can be made with a recent web browser over the Ethernet port 1 by using the host name http://ibhlink-iot_<serial number> (f.i. http://ibhlink-iot_000161) or over the ports 2-4 by entering the default IP Address 192.168.1.14 On the PC the IBHNet-Iot Driver is required. The Driver is available from here Default login is user admin with password admin. Network: Management Level Network configuration for Port 1 (Management level respectively Supervision Level) Network: Control Level Network configuration for Port 2 - 4 (Control Level respectively Machine Level) TeamViewer Iot Configuratio Login into the TeamViewer Iot Management Console click on your username in the right and from the dropdown menu select Assignment Token Copy the Assignment Token and paste it the TeamViewer IoT menu on the device Install and Configuring of IBH NET IoT driver The required IBH Link IoT Driver is available here and needs to be installed on the pc from where you want to start the connection. After installation, from system tray, click on the IBH Link IoT and select from the menu Agents In the pop-up window, you need to configure the Display Name  and the TeamViewer ID. The Display Name can be freely chosen. The TeamViewer ID to be used for each device can be seen in the web interface of the edge device.     How to connect Now, via the IBH Link IoT Tray  the connection can now be established by selecting IBH Link IoT from menu. After successful connection establishment, the IBH Link IoT appears as WireGuard tunnel in the Network Adapters. From now on, all controls that are connected via the control level of the IBH Link IoT are accessible via TeamViewer.   Note: For the two Edge Gateways IBH Link UA and IBH Link UA Quad Core please contact IBHsoftec for the latest firmware update. This firmware update will have the TeamViewer IoT Agent preinstalled. Once the latest Firmware update is installed, please follow the instructions in the link “Manual TeamViewer IoT” from here
View full article
This article applies to all TeamViewer IoT users and requires TeamViewer IoT Agent 2..11 or higher. Overview OPC Technology stands for “Open Platform Communications” and is an approved communication standard for the process industry. The OPC Unified Architecture (UA) is an interoperability standard and provides a secure and reliable data exchange mechanism. OPC UA is a platform-independent system and ensures information flow between devices from multiple vendors. For real-time data access, the OPC Data Access specification is being used. Architecture TeamViewer IoT provides an OPC UA Connector that connects to the OPC UA Server and collects values from OPC UA Variables. The connector finally communicates with TeamViewer IoT Cloud with the help of IoT Agent. Installation Connect with the TeamViewer Client to the device and use Remote Terminal Run this command: sudo teamviewer-iot-agent install opcua Connector Configuration In most cases, the OPC UA servers are being configured by other companies. And the configuration is specific to the installation and the environment where it is being used. You need to configure the OPC UA Connector according to your server's configuration by providing the URL of the server, security settings, and authentication options. To do this, you need to edit the opcua.conf file. The file is located in /var/lib/teamviewer-iot-agent/scripts/opcua/ directory of the Edge Device. Below are the parameters included in the file: # Server Information EndpointURL="opc.tcp://localhost:46570" # Security Policy # 0 - None # 1 - Basic128Rsa15 # 2 - Basic256 # 3 - Basic256Sha256 # 4 - Aes128Sha256RsaOaep # 5 - Aes256Sha256RsaPss SecurityPolicy=0 # Message Security Mode # 0 - None # 1 - Sign # 2 - Sign & Encrypt MessageSecurityMode=0 # Authentication Settings # 0 - Anonymous # 1 - Username & Password # 2 - Certificate & Private Key AuthenticationType=0 # If "Username & Password" is selected Username="admin" Password="admin" Adding a Sensor via OPC UA Connector Login in TeamViewer IoT Management Console From navigation panel click on Inventory. Select the Edge Device where the Connector is installed and from dropdown menu on the right select Add Sensor Choose the OPC UA from the Connectors section. Provide the Node IDs as they are specified in the server. Associate the OPC UA Nodes with a metric name that will be displayed in Teamviewer IoT Cloud. All the metrics are grouped in a sensor instance. Finally provide the scan rate at which the data will be requested from the server and save your configuration. Monitor the values received from the OPC UA Server by pining the configured metrics to the Dashboard.      
View full article
Top Contributors