Connected equipment
Turn on device control and send a command through your local bridge
Control is off by default and works only through a Home Assistant or MQTT bridge you run, only for devices an owner or member turns it on for, and only with the typed controls the device offers.
How to use it
- Open Connected Services and set up your local bridge first. Vendor cloud connections stay read-only: ResiArk does not send commands to a manufacturer cloud.
- Open Device control. Find the device and its listed controls, then choose Turn on control for that device. Opt-in is per device. If a device's controls or topic mapping change, the opt-in is switched off and you must turn it on again.
- Choose a control. Each one has its own type, such as on or off, a number with a range and step, or a fixed choice. Values outside the range are refused. A consequential command asks you to confirm and names the effect.
- Watch the outcome in command history. A command is shown as Requested, Accepted (the bridge or broker took it), Confirmed (the device's own state was seen to match), Rejected, Unknown or Expired. Accepted does not mean the device acted; only Confirmed does.
- Unknown means the command was sent but no matching state was seen. It is not shown as failed or successful, and there is no blind retry. Check the device. An expired command is never sent late.
- Only one command per device can be in flight at a time, and commands are rate limited per person, device and home. Viewers can read history but cannot send commands.
- Check the compatibility list in Connections for exactly which providers, device families and control paths are covered and how each was verified. There is no universal compatibility.
Requires Ark+, household owner or member access and a local Home Assistant or MQTT bridge you run. Control has been tested only against fixtures and an in-process test broker, not a real device. No vendor cloud control is provided.