Skip to main content

Control other Devices

A local event on one Device can be configured to execute a Command on an Operation of another Device in the same Project.

Configure the target​

Use a selector such as:

Room → Device → Operation → Command

Read the available Commands from the authoritative Project Device metadata; do not guess or hard-code another Device's Command values.

Runtime control topic​

Publish the configured cross-device command through:

projectCode/ControlOthers

The selected Device, Operation, and Command come from the saved configuration.

Permission is separate from configuration​

Choosing another Device/Operation in Dedicated Setting HTML does not automatically grant execution permission. Sensitive cross-device capabilities require server-side authorization and may require approval by the Project owner/Master.

The same principle applies to:

  • ListenToDevice / RequestDeviceLastValue;
  • ControlOthers;
  • server-side scenario access/management.

Firmware and HTML must not bypass a server authorization decision.

For executing a predefined server scenario instead of directly controlling an Operation, see Server-side scenarios.