Skip to content
Image of Teltonika router
Template

Teltonika router

by LoxonautNo rating yet77 downloads

Content languageEnglish

Description

This integration enables seamless communication between Loxone and Teltonika LTE routers, allowing Loxone systems to send SMS messages, read router data via REST API, and retrieve operational values using Modbus TCP. Using this integration, the Teltonika router becomes an active part of the automation system, not just a network device. Loxone can trigger SMS notifications for alarms, system states, or user-defined events such as security alerts, power failures, or system errors. At the same time, important router information can be retrieved and processed directly within Loxone. In addition to REST API communication, the integration also contains Modbus TCP. Via Modbus TCP, the following values are integrated and available in Loxone:

- RSSI (signal strength) - Device temperature - Amount of transmitted and received data

This allows continuous monitoring of LTE signal quality, device health, and data usage directly from the Loxone system. The integration communicates with the Teltonika router using the official Teltonika Networks REST API and Modbus TCP, ensuring compatibility with supported router models and firmware versions. Secure authentication and reliable communication are handled according to Teltonika’s official documentation.

The integration is based on the official Teltonika API: https://developers.teltonika-networks.com/reference/rutx09/7.19.5/v1.11.1/messages#post-messages-actions-send

Inputs and outputs · 32

NameTypeCommandUnit
API 32VirtualInHttptoken":"\s31\1<v.1>
API 2VirtualInHttptoken":"\s1\1<v.1>
API 3VirtualInHttptoken":"\s2\1<v.1>
API 4VirtualInHttptoken":"\s3\1<v.1>
API 5VirtualInHttptoken":"\s4\1<v.1>
API 6VirtualInHttptoken":"\s5\1<v.1>
API 7VirtualInHttptoken":"\s6\1<v.1>
API 8VirtualInHttptoken":"\s7\1<v.1>
API 9VirtualInHttptoken":"\s8\1<v.1>
API 10VirtualInHttptoken":"\s9\1<v.1>
API 11VirtualInHttptoken":"\s10\1<v.1>
API 12VirtualInHttptoken":"\s11\1<v.1>
API 13VirtualInHttptoken":"\s12\1<v.1>
API 14VirtualInHttptoken":"\s13\1<v.1>
API 15VirtualInHttptoken":"\s14\1<v.1>
API 16VirtualInHttptoken":"\s15\1<v.1>
API 17VirtualInHttptoken":"\s16\1<v.1>
API 18VirtualInHttptoken":"\s17\1<v.1>
API 19VirtualInHttptoken":"\s18\1<v.1>
API 20VirtualInHttptoken":"\s19\1<v.1>
API 21VirtualInHttptoken":"\s20\1<v.1>
API 22VirtualInHttptoken":"\s21\1<v.1>
API 23VirtualInHttptoken":"\s22\1<v.1>
API 24VirtualInHttptoken":"\s23\1<v.1>
API 25VirtualInHttptoken":"\s24\1<v.1>
API 26VirtualInHttptoken":"\s25\1<v.1>
API 27VirtualInHttptoken":"\s26\1<v.1>
API 28VirtualInHttptoken":"\s27\1<v.1>
API 29VirtualInHttptoken":"\s28\1<v.1>
API 30VirtualInHttptoken":"\s29\1<v.1>
API 31VirtualInHttptoken":"\s30\1<v.1>
API 1VirtualInHttptoken":"\1<v.1>

FAQ

No questions have been answered yet.

Ratings and comments

No ratings or comments yet.

Questions and answers

  1. Cannot save Regenerate token HTTP response into file in Miniserver

    Open

    When I request token (manually or with pulse generator) and with this template is HTTP response saved into /user/common/APIKeyTeltonica.xml, when I check https://Miniserver IP/dev/fsget/user/common/APIKeyTeltonica.xml , I get error 404 Not Found, so no response is saved. When I use same settings with local API tester (Insomnia), its working properly. Modbus is working, too. Miniserver 17.1.6.30

    No replies

Report this entry

Report abuse

You have to be logged in to report an entry. Log in