A capability is a programmatic representation of a device's state.

A simple example of capabilities is onoff. This is a boolean capability that tells Homey whether the device is turned on (when true) or off (when false). Homey ships with many capabilities (called system capabilities). These can be found in the Device Capability Reference.

Using capabilities

In your App Manifest, for every driver an array capabilities is required. This is an array with the keys of all capabilities. This array can be overwritten during pairing.

Your Device (device.js) instance needs to keep the device synchronised with Homey. Capabilities need to be synchronized both ways. This means that if a device's state changes, for example if the user turns on the lights, your app needs to tell Homey. It is also possible for Homey to request your app to change the state of the device, for example when a Flow is triggered to turn off the lights.

Your Device class should listen for changes to the device's and then update the capability value within Homey by calling Device#setCapabilityValue(). You should also register a method with Device#registerCapabilityListener() that to update the state of the physical device.

const Homey = require('homey');
const DeviceApi = require('device-api');
class Device extends Homey.Device {
async onInit() {
this.registerCapabilityListener("onoff", async (value) => {
await DeviceApi.setMyDeviceState({ on: value });
DeviceApi.on('state-changed', (isOn) => {
this.setCapabilityValue('onoff', isOn);
module.exports = Device;

Capability options

Some capabilities make use of capability options, which can be set to improve the user experience. Capability-specific options can be found in the Device Capability Reference.

Capability options can be set using the capabilitiesOptions object in the driver's entry in the App Manifest.

"name": { "en": "My Driver" },
"images": {
"small": "/drivers/my_driver/assets/images/small.png",
"large": "/drivers/my_driver/assets/images/large.png"
"class": "light",
"capabilities": ["onoff", "dim"],
"capabilitiesOptions": {
"dim": { "preventInsights": true }

Options that apply to all capabilities are:




Overwrite the capability title { "en": "My Custom Title" }


Prevent Insights from being automatically generated


Prevent a Flow Tag from being automatically generated

Custom capabilities

In some cases these might not suit your device. Your app can provide additional capabilities (called custom capabilities).

Define custom capabilities in your App Manifest, in an object capabilities.

"type": "boolean",
"title": { "en": "My Boolean capability" },
"getable": true,
"setable": true,
"uiComponent": "toggle",
"uiQuickAction": true,
"icon": "/assets/my_boolean_capability.svg"
"type": "number",
"title": { "en": "My Numeric capability" },
"uiComponent": "slider",
"getable": true,
"setable": false,
"units": { "en": "Cb" },
"min": 0,
"max": 30,
"step": 0.5
"name": { "en": "My Driver" },
"images": {
"small": "/drivers/my_driver/assets/images/small.png",
"large": "/drivers/my_driver/assets/images/large.png"
"class": "other",
"capabilities": ["onoff", "my_boolean_capability", "my_numeric_capability"]

The following options can be set for all custom capabilities:




A capability can be of type boolean, number, string or enum.


A translation object with the capability's title.


Default: true, a boolean whether the capability's value can be requested by a front-end. When getable is false, your Device doesn't need to call Device#setCapabilityValue.


Default: true, a boolean whether the capability's value can be set by a front-end. When setable is false, your Device doesn't need to register a capability listener.


A translation object of the capability's units, when applicable.


A preferred component to display in the UI. To hide a capability in the UI, set uiComponent to null.


A path to an .svg Icon.


Default: false, whether this capability should create an Insights log.

When the capability type is boolean the following additional properties can be set:




Set this to true when you want the user to quick-toggle the capability's value from the UI.


A translation object which describes the title when shown in a Timeline.


A translation object which describes the title when shown in a Timeline.

When the capability type is number the following additional properties can be set:




A minimum for the capability value.


A maximum for the capability value.


A step size of the capability value.


The number of decimals to show in the UI.

When the capability type is enum the following additional properties can be set:




An array of possible values for this capability. A value consists of an id, which will be the capability value, and a title, which is a translation object. The three values should have the ID's up, idle, and down.{ "id": "option1", "title": { "en": "First option" }}

Device Indicators and Custom Capabilities

The Homey web app and mobile app can display indicators next to the device icons. This gives users the ability to view a specific capability, such as a temperature value or battery status, at a glance. Custom boolean and number capabilities can also be shown as indicators as device indicators.

Boolean Capabilities

Boolean capabilities, also called Alarms in Homey, are displayed in two different ways if they start with the prefix alarm_. By default all capabilities with this prefix are grouped, and a warning icon is shown if the value of any of the boolean capabilities is true. Alternatively users can choose to show the indicator value of a single specific Alarm capability. The alarm_battery capabilities will show an "empty battery" icon instead of an exclamation mark.

Number Capabilities

Number capabilities, are displayed as a numeric value together with the unit of the capability. Users are able to select capabilities that start with either the prefix measure_ or meter_. The measure_battery capability will always be displayed with a custom battery icon instead of a number.

An example with capabilities: 'meter_power', 'measure_battery' and 'alarm_motion'.

UI Components

All system capabilities have their own UI component. Custom capabilities can also use these UI components. Homey will automatically try to find the right component, but you can override this by specifying the uiComponent property in your custom capability.


"uiComponent": "toggle"

The toggle component displays one boolean capability. Depending on the capability, the look might change.


"uiComponent": "slider"

The slider component displays one number capability. Depending on the capability, the look might change.


"uiComponent": "sensor"

The sensor component displays multiple number, enum, string or boolean capabilities.

Booleans that are true and begin with alarm_ will flash red.


"uiComponent": "thermostat"

The thermostat component displays a target_temperature capability, and an optional measure_temperature.

If you use sub-capabilities for target_temperature and measure_temperature, make sure the dot suffix of the capabilities are the same so that they will be displayed together, for instance: and


"uiComponent": "media"

The media component accepts the speaker_playing, speaker_next, speaker_prev, speaker_shuffle and speaker_repeat capabilities.

Additionally, it shows the album art as set using Device#setAlbumArt().


"uiComponent": "color"

The color component accepts the light_hue, light_saturation, light_temperature and light_mode capabilities.


"uiComponent": "battery"

The battery component accepts either a measure_battery or alarm_battery capability.


"uiComponent": "picker"

The picker component accepts one enum capability and shows a list of possible values.


"uiComponent": "ternary"

The ternary component accepts one enum capability with three values, meant for motorized components.

No UI component

"uiComponent": null

To hide the UI component, specify null as value.

Maintenance Actions

This feature depends on Homey v3.1.0 and Homey Smartphone App v3.0.1.

Button capabilities can be flagged as maintenance action. This will show a button in 'Device settings > Maintenance actions' and hide the uiComponent in the device view. When this button is pressed the registered capability listener will be triggered. This allows you to initiate actions from the device's settings.

Example use cases:

  • Starting the calibration process on a device

  • Resetting accumulated power measurements

Creating a maintenance action

A maintenance action capability must be a capability that extends the system capability button. In order to mark it as a maintenance action add the maintenanceAction: true property to the capabilitiesOptions object of the driver manifest. Additionally, provide a title property, and optionally a desc property.

"name": { "en": "P1 Meter" },
"capabilities": [
"capabilitiesOptions": {
"button.calibrate": {
"maintenanceAction": true,
"title": { "en": "Start calibration" },
"desc": { "en": "Start the sensor calibration process." }
"button.reset_meter": {
"maintenanceAction": true,
"title": { "en": "Reset power meter" },
"desc": { "en": "Reset the accumulated power usage (kWh), this can not be restored." }

Listening for maintenance action events

Register the capability listeners in device.js to listen for maintenance action events.

const Homey = require('homey');
class Device extends Homey.Device {
async onInit() {
this.registerCapabilityListener('button.reset_meter', async () => {
// Maintenance action button was pressed
this.registerCapabilityListener('button.calibrate', async () => {
// Maintenance action button was pressed, return a promise
throw new Error('Something went wrong');
module.exports = Device;

Using the same capability more than once

In certain cases it might occur that a device should use a capability more than once. You can use a sub-capability for this purpose.

An example would be a device with an outside and inside temperature sensor. Simply append a dot followed by an identifier after the capability string during in your driver, e.g. measure_temperature.inside & measure_temperature.outside.

Flow Cards will not be automatically generated for sub-capabilities, you should create these cards yourself.