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:
| Channel | Description | Multiple | Details |
|---|---|---|---|
device_information | Provides metadata about the device, including manufacturer details, model information, and operational statuses. | No | See details |
Optional Channels
These channels are optional and provide additional features:
| Channel | Description | Multiple | Details |
|---|---|---|---|
button | Hardware push-button input reporting press, double press, long press, or raw down/up interactions. | Yes | See details |
binary_input | Binary toggle or contact switch input reporting steady-state on/off or closed/open status. | Yes | See details |
analog_input | Analog voltage, resistance, or slider input reporting continuous float values. | Yes | See details |
battery | Battery state of charge and power reporting for wireless remotes and battery-powered controllers. | No | See details |
Channel Constraints
One or More Required
At least one channel from each of the following groups must be present:
buttonorbinary_inputoranalog_input
Use Case Scenarios
-
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.
-
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
- Dedicated input controllers do not require actuator channels (no relay or dimmer).
- Button events are emitted as event-type occurrences, bypassing state equality checks.
- Configure channel categories truthfully according to the physical wiring and device mode.
Last updated on