ym88659208ym87991671
Transmitting status change commands (commands) | Documentation for developers

Transmitting status change commands (commands)

Last updated on May 17, 2023

Direction: cloud → controller.

Sber Smart Home requests from the agent app installed on the controller changes in the state of devices.

Use case example:

  1. The user changes the lamp state, e.g. by turning it off, in the Salute app, on SberPortal, SberBox or on another device with installed Salute assistants.
  2. The Smart Home sends a lamp state change request to the agent app installed on the controller.
  3. The agent delivers the request to the controller, and the controller switches the lamp off.

Message format

Topic:

sberdevices/v1/<username>/down/commands
ParameterTypeMandatory?Description
usernamestring✔︎Login for connection to the Sber MQTT server (see "Having your controller authorized" for integrators and DIY enthusiasts)

Message body:

FieldTypeMandatory?Description
devicesdict<string object>✔︎Devices whose state needs to be changed. For each device, the device ID in the vendor's system and the new state of its functions are transmitted
IDstring✔︎Device ID in the vendor's system
stateslist<object>✔︎List of new states (see Device state (state))
{
"devices": {
"id": {
"states": [
{
"key": string,
"value": {
"type": string,
"type_value": object
}
},
{
// ...
}
]
}
}
}

Message example

Sber Smart Home requests from the agent app installed on the controller changes in the socket state.

Topic:

sberdevices/v1/1234567/down/commands

Message body:

{
"devices": {
"ABCD_003": {
"states": [
{
"key": "online",
"value": {
"type": "BOOL",
"bool_value": true
}
},
{
"key": "on_off",
"value": {
"type": "BOOL",
"bool_value": true
}
}
]
}
}
}
Sber process cookies only to personalize services according to Cookies Usage Policy. You can prevent the processing of cookies in your browser settings.