MQTT integration protocol | Documentation for developers
Skip to main content

MQTT integration protocol

Last updated on November 25, 2022

Connection under the MQTT protocol is suitable for devices that have no own cloud. You can use a ready-made client or implement the protocol support by yourself.

The MQTT server address of Sber is displayed in SmartMarket Studio in the integration project on the tab

(see "Having your controller authorized in Sber cloud" section for MQTT integrators and DIY enthusiasts).

For the data exchange, topics listed in the below table are used. Addresses of topics use the username parameter – a login which allows for connection to Sber’s MQTT server. The login can also be viewed in the integration project in SmartMarket Studio.

For the topic message format, see MQTT topics.

sberdevices/v1/__configReadingGlobal configuration transmission
sberdevices/v1/username/down/commandsReadingTransmitting status change commands. After applying changes, it is necessary to send the current state of devices
sberdevices/v1/username/down/status_requestReadingDevice status request. It is necessary to send the current status of the transmitted devices
sberdevices/v1/username/down/config_requestReadingDevices configuration request. It is necessary to send the current configuration of the devices
sberdevices/v1/username/up/statusWritingDevices status transmission
sberdevices/v1/username/up/configWritingDevices configuration transmission

If you are developing your own agent app for controller, use information API to implement the GUI. API provides information about devices supported by Sber Smart Home, their functions and models. This will help you to automatically draw the app’s GUI.