Device types
What each device type is, which properties it needs to actually work, and what the customer gets on the panel. Property names are the keys you type when you bind a group address, a register or a Z-Wave value.
1.How a device gets its type
Read this first — almost every 'the card looks wrong' question is answered here.
A device's appearance is not chosen by hand. The platform works down an ordered list of rules and takes the first one that matches, looking at the device type you picked, the device-type name, and in some cases the properties you bound.
- Order matters. Dimmer is tested before plain light, and air conditioner before fan coil before thermostat. A device whose name matches two rules gets the earlier one.
- Properties can decide it. A device with a
positionproperty and nobrightnessis treated as a blind even if nothing in its name says so. Any colour property makes a light dimmable, because a colour already contains a brightness. - The same rules drive Apple Home and Google Home. If the panel shows a dimmer, Apple Home gets a dimmable bulb. You never configure the bridges separately — fix the device once and all three agree.
- Property names are normalised. Case, spaces, underscores and dashes are ignored, and common synonyms are folded together —
dimming_value,dim_valueandbrightness_levelall mean brightness.
2.Light (on/off)
A lamp or circuit that is either on or off. The simplest device there is.
| Property | What it does | Values |
|---|---|---|
on_offrequired | Switches the circuit. Also the state the panel reads back. | Boolean — 1 on, 0 off |
How to configure it
- Create the device in Devices, choose the room, pick the light device type.
- Bind one property named
on_off(orswitch) to the switching object of the actuator channel. - If the actuator has a separate status object, bind it as the status address of the same property so the panel shows the real state rather than what it last sent.
What the customer sees
A card with a power button. Tapping the card toggles it directly — no need to open anything.
3.Dimmer
A light with a level. Tested before the plain light, so any device that can dim becomes a dimmer.
| Property | What it does | Values |
|---|---|---|
brightnessrequired | Absolute level. This is what makes the device a dimmer. | 0–100 % |
on_off | Power. Optional — without it, level 0 means off. | Boolean |
relative, increase, decrease, step or up_down are deliberately ignored — they step the light but cannot be set to a value, so a slider bound to one would do nothing.What the customer sees
A power button and a 0–100 % slider. Switching on a light that was at 0 brings it back at 60 % rather than leaving the customer looking at a lamp that is technically on and visibly off.
4.RGB and RGBW lights
Not a separate device type: any light with a writable colour property becomes a colour light and gets the colour wheel instead of the plain slider.
| Property | What it does | Values |
|---|---|---|
rgbcolor | Colour of an RGB fixture. | Hex #RRGGBB |
rgbwcolor | Colour of an RGBW fixture — the last byte is the white lamp. | Hex #RRGGBBWW |
color_temperature | Tunable white. Offered only when the fixture has no colour wheel. | 2000–6500 K |
- Name it for what the fixture is. If you bind an RGBW fixture as
rgbcolor, the white channel is lost. When both exist, RGBW wins. - Colour-only fixtures (a WLED strip with no separate switching object) are switched by colour: off writes all zeros, on restores the last colour the customer had. That memory survives a reload and is shared with Apple Home and Google Home, so a light switched off from a phone and on from the panel returns to the same colour.
- Tunable white and a colour wheel are mutually exclusive on one fixture, because "warm white" would otherwise mean two different things on the same lamp.
5.Blinds and shutters
Roller shutters, venetian blinds, curtains and awnings.
| Property | What it does | Values |
|---|---|---|
positionrequired | Where the blind sits, and where it is sent. | 0–100 % — 0 closed, 100 open |
move_up_down | The drive object behind the Open and Close buttons. | Boolean — down/close is 1 |
stop | Stops travel. If you do not bind it, the stop command is sent on the position object instead. | Boolean |
angle | Slat tilt on a venetian blind. | 0–180° in the panel, written to the bus as 0–100 % |
What the customer sees
Open, Stop and Close buttons, a position slider, and — if you bound an angle — a tilt slider underneath.
6.Thermostat
Room temperature control with a setpoint. Matched after air conditioner and fan coil, so a device whose name mentions HVAC or fan coil is claimed by those first.
| Property | What it does | Values |
|---|---|---|
setpoint_temprequired | Target temperature the customer sets. | °C, slider defaults to 5–35 |
temperature | Measured room temperature. Without it, the panel shows the setpoint as the reading. | °C, read-only |
mode | Heating or cooling. | 1-bit: 1 heat, 0 cool — or your own coded list |
on_off | Power, if the unit has one. | Boolean |
What the customer sees
The target temperature with − and + in half-degree steps, the measured temperature underneath, and a mode button when a mode object is bound. Thermostats can also carry a weekly schedule.
7.Fan coil
A fan coil unit with a setpoint and a fan speed.
| Property | What it does | Values |
|---|---|---|
setpoint_temprequired | Target temperature. | °C |
temperature | Measured room temperature. | °C, read-only |
fan_speed | Fan level. Accepts a percentage or a named level. | 0–100 %, or off / low / medium / high / auto |
mode | Heat or cool. | Device-specific |
on_off | Power. | Boolean |
8.Air conditioner / multi-mode HVAC
Split units, VRF, Airzone and anything else that speaks in coded modes rather than a simple heat/cool bit.
| Property | What it does | Values |
|---|---|---|
setpoint_temprequired | Target temperature. | °C |
temperature | Measured room temperature. | °C, read-only |
mode | The unit's own mode code. | Whatever the unit uses — 2 = cool, 3 = heat, … |
fan_speed | The unit's own fan code. | Whatever the unit uses |
on_off | Power. | Boolean |
Configuring the mode and fan lists
This is what separates an air conditioner from a fan coil. In the device editor you give the unit its own list of modes and fan speeds — each entry is the raw value the unit expects, a label the customer reads, and an icon. As soon as a device has a mode list, it is treated as a multi-mode HVAC unit whatever protocol it speaks.
- Open the device and find the HVAC modes section.
- Add one entry per mode the unit actually supports: value
2, label Cool, snowflake icon, and so on. - Do the same for fan speeds if the unit has coded ones.
- Save. The panel now shows a mode dropdown with exactly those entries.
9.Heating actuator (valve)
A radiator or underfloor valve driven by a percentage.
| Property | What it does | Values |
|---|---|---|
heat_levelrequired | How far the valve opens. | 0–100 % |
on_off | Power, where the channel has one. | Boolean |
temperature | Measured temperature, if the channel reports one. | °C, read-only |
- The customer gets a power button and three presets — Eco 30 %, Comfort 60 %, Boost 100 %.
- Boost always writes 100 %, whatever value the button appears to carry.
- A device of this type with no
heat_levelbound is exported to Apple Home as a thermostat rather than a valve — bind the level, or pick the thermostat type deliberately.
10.Relay / switch actuator
A generic switched output: a pump, a socket circuit, a gate release, an extractor fan.
| Property | What it does | Values |
|---|---|---|
on_offrequired | Switches the output. | Boolean |
Identical in behaviour to a light, with neutral wording and iconography. Tapping the card toggles it. Apple Home and Google Home both show it as a switch.
11.Sprinkler
Irrigation valve.
| Property | What it does | Values |
|---|---|---|
on_offrequired | Opens the valve. | Boolean |
Behaves like a relay on the panel, but Apple Home shows it as an irrigation valve and Google Home as a sprinkler, so voice commands about watering reach the right device.
12.Lock
An electric strike or motor lock driven by one output.
| Property | What it does | Values |
|---|---|---|
on_offrequired | Drives the lock output. | Boolean |
- Unlocking asks for a second confirming tap within three seconds — a pocket cannot open a door.
- Apple Home and Google Home see a switch, not a native lock tile, so neither will ask for a phone passcode. Treat the panel passcode as the real protection.
13.Alarm / security
A burglar-alarm panel: arming, sensors, siren and notifications. The device holds the wiring; the behaviour lives in an Alarm block on the Flows page.
| Property | What it does | Values |
|---|---|---|
arm_disarm | Away arming bit. | Boolean |
stay_disarm | Stay (home) arming bit. | Boolean |
alarm_sensor_1…n | Interior motion sensors. Add as many as the panel has. | Boolean |
window_contact_1…n | Door and window contacts. | Boolean |
siren_output | Drives the siren. | Boolean |
notify | Notification output. | Boolean |
panic | Panic button. | Boolean |
How arming really works
- Arm away sets
arm_disarmand clearsstay_disarm. - Arm stay sets
stay_disarmand clearsarm_disarm. - Disarm clears both.
- Both bits always move together, so the panel can never end up in a state where it is armed two ways at once.
14.Sensors
All read-only. Even if a sensor's object happens to be writable, the platform will never offer it as a control.
| Property | What it does | Values |
|---|---|---|
temperature | Temperature sensor. | °C |
humidity | Humidity. May sit on the same device as a temperature. | 0–100 % |
contact | Door or window contact. | Boolean — shown as Open / Closed |
motion | Motion detector. | Boolean — Detected / Clear |
presence | Presence detector. | Boolean — Present / Absent |
illuminance | Brightness sensor. | 0–100 000 lux |
co2 | Air quality. | 0–5000 ppm |
- A combined temperature-and-humidity sensor is one device with both properties — do not split it into two.
- Use
presenceoroccupancyfor presence detectors; those are the names the Apple Home and Google Home bridges look for. - A sensor that has never reported reads as unknown rather than as "no motion", so a dead sensor does not look like a quiet room.
15.Energy meter
Power and consumption metering.
| Property | What it does | Values |
|---|---|---|
power | Instantaneous power. | W |
energy | Cumulative consumption. | Reported in Wh, shown in kWh |
voltage | Line voltage. | V |
current | Line current. | A |
The card shows all four values in a grid with a count of how many are live, so a half-configured meter is obvious at a glance.
16.Weather station
Outdoor conditions, usually a KNX weather unit on the roof.
| Property | What it does | Values |
|---|---|---|
temperature | Outside temperature. | °C |
humidity | Outside humidity. | 0–100 % |
wind_speed | Wind speed. | km/h |
illuminance | Outside brightness. | lux |
17.Scene controller
A device whose whole job is to fire a stored scene.
The card is a single Activate button that confirms with a tick when the scene has run. This is a device that triggers a scene; it is not the same thing as the scenes you build on the Scenes page, which appear on the panel by themselves and are what most installations use.
18.Intercom
A door station with video and two-way audio.
The intercom has no properties to bind — it is not a bus device. Tapping its card opens the live preview and call controls, and a call from the door station rings through on the panels. It is configured in the intercom settings, not as a set of group addresses, and it is deliberately not exported to Apple Home or Google Home.
19.Camera, logic and infrastructure
Three types that exist so the equipment appears in the system, with limited interaction.
- Camera — appears with its name and icon. There is no live stream in the device card and no Apple/Google export; a camera needs a public relay, which this platform deliberately does not run.
- Logic — shows Enable, Disable and Run buttons. These write properties named exactly
enable,disableandrun; if you do not create those properties, the buttons do nothing. For real automation use the Flows page instead. - Infrastructure — IP interfaces, gateways, button panels. Displays link state, protocol and type only. Nothing to configure, nothing to control.
20.Reference tables
The things worth checking when a value looks wrong.
Default ranges when nothing else is configured
- Temperature and setpoints: 5–35 °C on sliders; readings accept −270 to 100 °C.
- Anything that is a position, angle, brightness, dimming or level: 0–100 %.
- Humidity and battery: 0–100 %. Illuminance: 0–100 000 lux. CO₂: 0–5000 ppm.
- Colour temperature: 2000–6500 K. Scene numbers: 0–63. Anything else: a 0–255 byte.
Properties that are always read-only
temperature, humidity, co2, voc, pressure, air quality, wind speed, illuminance, rain, motion, presence, contact, window, door, water leak, smoke, alarm sensor, power, energy, voltage, current and battery. Giving one of these a control address will not make it writable — that is deliberate, so a measurement can never be "set" by mistake.
Commands a device can receive
on, off, toggle, brightness, position, open, close, stop, angle, power, heat level, boost, setpoint, fan speed, mode, scene — plus the alarm's arm away, arm stay, disarm and panic. Anything else is written straight to the property of that name, which is how the logic device type and custom HTTP or MQTT devices work.