Connecting a device
Configuring the device
To connect the equipment to the platform, you need to use
configurator program (for each type of equipment supplied by the equipment developers) or by other methods described in the instruction manual.
equipment developers) or other methods described in the instruction manual of the equipment
To connect the equipment to the platform it is necessary to specify the server address (host) and port:
- address -
dev.rightech.io(IP address89.108.112.87); - port - according to the protocol of the equipment.
Data Transfer Protocols
Transmission and communication protocol is a system of rules that defines the
the format of data exchange between different devices. A protocol specifies
a uniform way of transmitting messages and handling errors during the interaction of the
software. In other words, these are the rules by which IoT devices
IoT devices communicate with each other.
Below is a list of implemented protocols open in the public version of the
platform. If the protocol you need is not in the table, send a request to our
e-mail address info@rightech.io
| Protocol name | Address to connect | Notes |
|---|---|---|
| MQTT/MQTTS | dev.rightech.io:1883/TCP dev.rightech.io:8883/TLS | Example MQTT Specification (MQTT v5.0 and below) |
| MQTT over WebSocket | ws-mqtt.dev.rightech.io:443/WSS | Example MQTT Specification |
| Wialon IPS | dev.rightech.io:20332/TCP | Example Wialon IPS v1.1 and 2.0 |
| Wialon Combine | dev.rightech.io:20333/TCP | Example Wialon Combine |
| Galileosky | dev.rightech.io:20268/TCP | Example Manual |
| Omni E-Scooters | dev.rightech.io:20510/TCP | Manufacturer Website |
| Queclink | dev.rightech.io:20514/TCP | Queclink |
| Teltonika | dev.rightech.io:21451/TCP | [Example](https://rightech.io/en/developers/examples/teltonika Teltonika Wiki |
| AutoFon 8x | dev.rightech.io:20518/TCP | AutoFon |
| AutoFon 7x | dev.rightech.io:20519/TCP | AutoFon |
| AutoFon 5-6 | dev.rightech.io:20520/TCP | AutoFon |
| AutoFon Micro-Beacon | dev.rightech.io:20521/TCP | AutoFon Micro-Beacon |
| OKAI | dev.rightech.io:20516/TCP | OKAI |
| Concox | dev.rightech.io:20515/TCP | Concox |
| Arnavi3 | dev.rightech.io:20512/TCP | Arnavi Guide |
| Navtelecom (Flex) | dev.rightech.io:21400/TCP | Example Navtelecom v6.1 |
| LoRaWAN | dev.rightech.io:1700 | Example LoRaWAN 1.1 (EU868 / RU864) |
| CoAP | dev.rightech.io:5683/UDP | Example RFC7252 |
| LwM2M | dev.rightech.io:5683/UDP | Example OMA LwM2M 1.2 |
| WebSocket | ws://ws.dev.rightech.io wss://ws.dev.rightech.io | Example RFC6455 |
| Available Upon Request | Documentation / Website |
|---|---|
| KNX | knx |
| Modbus TCP/RTU | Modbus |
| Wialon Retranslator | wialon retranslator |
| Starline | starline.ru |
| Omni Lock | smartlockssupplier.com |
| Queclink | queclink.com |
| Gate8000 | skd-gate.ru |
| DiWo | diwo.tech |
| Mta6 | MTA6 |
Limitations
MQTT
- Persistent Session is not supported, whereby the MQTT broker stores messages sent to the client while the client was out of service;
- Message Expiry Interval is not supported, in which the MQTT Broker saves messages sent to the client while the client was out of contact. The MQTT broker deletes a message if it has not been delivered within this time period;
- Extended authorization (SCRAM-SHA-1, GS2-KRB5, etc.) is not supported;
- Password can only be set in UTF-8 format;
- A number of properties added in MQTT v5 are not used.
LwM2M
- Not supported bootstrap server;
- DTLS is not supported.