Skip to Content
🚀 We just launched! Please star us on Github!

Input Controller Device

Device Category: input_controller

Represents a dedicated physical input device such as a multi-button wall controller, push-button panel, or sensor interface without built-in actuators.


Required Channels

These channels are mandatory for the functionality of the input controller:

ChannelDescriptionMultipleDetails
device_informationProvides metadata about the device, including manufacturer details, model information, and operational statuses.NoSee details

Optional Channels

These channels are optional and provide additional features:

ChannelDescriptionMultipleDetails
buttonHardware push-button input reporting press, double press, long press, or raw down/up interactions.YesSee details
binary_inputBinary toggle or contact switch input reporting steady-state on/off or closed/open status.YesSee details
analog_inputAnalog voltage, resistance, or slider input reporting continuous float values.YesSee details
batteryBattery state of charge and power reporting for wireless remotes and battery-powered controllers.NoSee details

Channel Constraints

One or More Required

At least one channel from each of the following groups must be present:

  • button or binary_input or analog_input

Use Case Scenarios

  1. Wall switch and scene controller:

    • Capture physical button clicks, double-presses, long-presses, or binary toggle inputs to trigger automations and scenes throughout the home.
  2. Multi-channel input interface:

    • Expose multiple independent push buttons, toggle switches, or analog potentiometer inputs on dedicated controller devices (e.g. Shelly Plus i4).

Developer Notes

  1. Dedicated input controllers do not require actuator channels (no relay or dimmer).
  2. Button events are emitted as event-type occurrences, bypassing state equality checks.
  3. Configure channel categories truthfully according to the physical wiring and device mode.
Last updated on