Settings

Devices can have settings that can be changed by the user. These are presented to the user as Advanced settings. The device settings are defined in the /drivers/<driver_id>/driver.settings.compose.json file.
/drivers/<driver_id>/driver.settings.compose.json
1
[
2
  {
3
    "id": "username",
4
    "type": "text",
5
    "label": { "en": "Username" },
6
    "value": "John Doe",
7
    "hint": { "en": "The name of the user." }
8
  },
9
  {
10
    "id": "password",
11
    "type": "password",
12
    "label": { "en": "Password" },
13
    "value": "Secret",
14
    "hint": { "en": "The password of the user." }
15
  }
16
]
Copied!
Defining settings
Every setting has a type property that determines what values it can have and how it is presented to the user. The value property of each setting is the initial value of the setting, this property is required for all settings. The following setting types are supported:
Text
This is a single line text input whose value is a string. You can optionally validate the value using a regex pattern by adding a pattern property. For example adding "pattern": "[a-zA-Z]" to the setting definition will make sure the user can only input letters.
1
{
2
  "id": "username",
3
  "type": "text",
4
  "label": { "en": "Username" },
5
  "value": "John Doe",
6
  "hint": { "en": "The name of the user." }
7
}
Copied!
Password
Settings with the type password behave the same as text but the input is visually hidden.
1
{
2
  "id": "password",
3
  "type": "password",
4
  "label": { "en": "Password" },
5
  "value": "Secret",
6
  "hint": { "en": "The password of the user." }
7
}
Copied!
Text area
textarea type settings behave the same as text but allow multi-line input.
1
{
2
  "id": "description",
3
  "type": "textarea",
4
  "label": { "en": "Description" },
5
  "value": "Initial description",
6
  "hint": { "en": "A custom device description." }
7
}
Copied!
Number
The number type settings can only contain numbers, this means that the value must also be a number. Number settings also support min max and step properties. You can also optionally provide the unit of the setting by setting the units property.
1
{
2
  "id": "duration",
3
  "type": "number",
4
  "label": { "en": "Duration" },
5
  "value": 3,
6
  "min": 0,
7
  "max": 5,
8
  "units": { "en": "minutes" }
9
}
Copied!
Checkbox
checkbox settings can be true or false.
1
{
2
  "id": "allow_override",
3
  "type": "checkbox",
4
  "value": true,
5
  "label": { "en": "Allow override" }
6
}
Copied!
Dropdown
Settings with the type dropdown allow the user to pick a value from a predefined set of choices. The values of the checkbox must be strings.
1
{
2
  "id": "mode",
3
  "type": "dropdown",
4
  "value": "heating",
5
  "label": { "en": "Default mode" },
6
  "values": [
7
    {
8
      "id": "heating",
9
      "label": { "en": "Heating" }
10
    },
11
    {
12
      "id": "cooling",
13
      "label": { "en": "Cooling" }
14
    }
15
  ]
16
}
Copied!
Group
You can add a type group to your settings to group multiple settings together with a label.
1
{
2
  "type": "group",
3
  "label": { "en": "Login details" },
4
  "children": [
5
    {
6
      "id": "username",
7
      "type": "text",
8
      "label": { "en": "Username" },
9
      "value": "John Doe",
10
      "hint": { "en": "The name of the user." }
11
    },
12
    {
13
      "id": "password",
14
      "type": "password",
15
      "label": { "en": "Password" },
16
      "value": "Secret",
17
      "hint": { "en": "The password of the user." }
18
    }
19
  ]
20
}
Copied!
Label
You can add additional explanation or headings to the device settings page by adding a setting with the type label. This acts as a read-only text field and can only be updated by your app.
1
{
2
  "id": "label",
3
  "type": "label",
4
  "label": { "en": "IP address" },
5
  "value": "192.168.0.10",
6
  "hint": { "en": "The IP address of the device." }
7
}
Copied!
Using settings
Once you have defined what settings your device has you can read the settings in from your Device class. You can retrieve the current values of all settings as follows:
/drivers/<driver_id>/device.js
1
const Homey = require('homey');
2
​
3
class Device extends Homey.Device {
4
  async onInit() {
5
    const settings = this.getSettings();
6
    console.log(settings.username);
7
  }
8
}
9
​
10
module.exports = Device;
Copied!
When settings are changed by a user, Device#onSettings() will be called. You can overwrite the method in your device.js to react to changes to the settings. It is also possible to throw an error from this method if the settings are invalid. The thrown error will be shown to the user and they be asked to change their settings in order to store them.
/drivers/<driver_id>/device.js
1
const Homey = require('homey');
2
​
3
class Device extends Homey.Device {
4
  async onSettings({ oldSettings, newSettings, changedKeys }) {
5
    // run when the user has changed the device's settings in Homey.
6
    // changedKeysArr contains an array of keys that have been changed
7
    // if the settings must not be saved for whatever reason:
8
    // throw new Error('Your error message');
9
  }
10
}
11
​
12
module.exports = Device;
Copied!
It is also possible to update the settings from your Device by calling Device#setSetting().
/drivers/<driver_id>/device.js
1
const Homey = require('homey');
2
​
3
class Device extends Homey.Device {
4
  async onInit() {
5
    await this.setSettings({
6
      // only provide keys for the settings you want to change
7
      username: "Jane Doe",
8
    });
9
  }
10
}
11
​
12
module.exports = Device;
Copied!
When changing device settings programmatically using Device#setSettings(), the Device#onSettings() function is not fired.

Energy

Best practices

Last modified 21d ago

Copy link

Contents