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 position property and no brightness is 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_value and brightness_level all mean brightness.
If a device renders as the wrong type, look at its device-type name first. Renaming a type like "Fan Coil Controller" to something containing "dimmer" or "shutter" will silently change how every device of that type behaves.

2.Light (on/off)

A lamp or circuit that is either on or off. The simplest device there is.

PropertyWhat it doesValues
on_offrequiredSwitches the circuit. Also the state the panel reads back.Boolean — 1 on, 0 off

How to configure it

  1. Create the device in Devices, choose the room, pick the light device type.
  2. Bind one property named on_off (or switch) to the switching object of the actuator channel.
  3. 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.

On/off telegrams are sent more than once by design (twice, 60 ms apart) because a busy bus occasionally drops one. A lamp reacting twice is invisible; a lamp not reacting is a call-out.

3.Dimmer

A light with a level. Tested before the plain light, so any device that can dim becomes a dimmer.

PropertyWhat it doesValues
brightnessrequiredAbsolute level. This is what makes the device a dimmer.0–100 %
on_offPower. Optional — without it, level 0 means off.Boolean
Bind the absolute dimming object, not relative dimming. Objects whose names contain 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.

PropertyWhat it doesValues
rgbcolorColour of an RGB fixture.Hex #RRGGBB
rgbwcolorColour of an RGBW fixture — the last byte is the white lamp.Hex #RRGGBBWW
color_temperatureTunable 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.

PropertyWhat it doesValues
positionrequiredWhere the blind sits, and where it is sent.0–100 % — 0 closed, 100 open
move_up_downThe drive object behind the Open and Close buttons.Boolean — down/close is 1
stopStops travel. If you do not bind it, the stop command is sent on the position object instead.Boolean
angleSlat tilt on a venetian blind.0–180° in the panel, written to the bus as 0–100 %
Position is counted from closed: 0 % is fully shut, 100 % is fully open. Most KNX actuators count the opposite way — if a blind drives to the mirror image of what you asked for, open the device in the HomeKit page and set reverse on its position property. One flag fixes the panel, Apple Home and Google Home together.

What the customer sees

Open, Stop and Close buttons, a position slider, and — if you bound an angle — a tilt slider underneath.

Commission the travel time in the actuator itself before binding. The platform asks for a position and trusts the actuator to reach it; if the actuator's travel time is wrong, every position in the house is wrong and no amount of configuration here will fix it.

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.

PropertyWhat it doesValues
setpoint_temprequiredTarget temperature the customer sets.°C, slider defaults to 5–35
temperatureMeasured room temperature. Without it, the panel shows the setpoint as the reading.°C, read-only
modeHeating or cooling.1-bit: 1 heat, 0 cool — or your own coded list
on_offPower, 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.

PropertyWhat it doesValues
setpoint_temprequiredTarget temperature.°C
temperatureMeasured room temperature.°C, read-only
fan_speedFan level. Accepts a percentage or a named level.0–100 %, or off / low / medium / high / auto
modeHeat or cool.Device-specific
on_offPower.Boolean
Named fan levels map onto the single percentage object the unit really has: low is 33 %, medium 66 %, high 100 %. Both off and auto write 0 %, because a percentage object has no way to say "decide for yourself" — if the unit has a real auto mode, give it a coded fan list instead (next section).

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.

PropertyWhat it doesValues
setpoint_temprequiredTarget temperature.°C
temperatureMeasured room temperature.°C, read-only
modeThe unit's own mode code.Whatever the unit uses — 2 = cool, 3 = heat, …
fan_speedThe unit's own fan code.Whatever the unit uses
on_offPower.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.

  1. Open the device and find the HVAC modes section.
  2. Add one entry per mode the unit actually supports: value 2, label Cool, snowflake icon, and so on.
  3. Do the same for fan speeds if the unit has coded ones.
  4. Save. The panel now shows a mode dropdown with exactly those entries.
Only list modes the unit really has. The labels are also what Apple Home and Google Home are told the unit can do — advertising dry and fan-only on a two-pipe unit that cannot enter them produces a device that fails every voice command for those modes.

9.Heating actuator (valve)

A radiator or underfloor valve driven by a percentage.

PropertyWhat it doesValues
heat_levelrequiredHow far the valve opens.0–100 %
on_offPower, where the channel has one.Boolean
temperatureMeasured 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_level bound 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.

PropertyWhat it doesValues
on_offrequiredSwitches 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.

PropertyWhat it doesValues
on_offrequiredOpens 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.

PropertyWhat it doesValues
on_offrequiredDrives 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.
For anything the customer would mind being opened by a guest, turn on the per-device passcode in the panel's security settings.

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.

PropertyWhat it doesValues
arm_disarmAway arming bit.Boolean
stay_disarmStay (home) arming bit.Boolean
alarm_sensor_1…nInterior motion sensors. Add as many as the panel has.Boolean
window_contact_1…nDoor and window contacts.Boolean
siren_outputDrives the siren.Boolean
notifyNotification output.Boolean
panicPanic button.Boolean

How arming really works

  • Arm away sets arm_disarm and clears stay_disarm.
  • Arm stay sets stay_disarm and clears arm_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.
Many KNX alarm panels report status as a byte where 128 means clear and 129 means active rather than a plain 0/1. The platform understands this, so do not "fix" it with an inversion — bind the object as it is.
Entry and exit delays, stay-mode bypass and siren logic are configured on the Alarm block in Flows, not here — see the worked example.

14.Sensors

All read-only. Even if a sensor's object happens to be writable, the platform will never offer it as a control.

PropertyWhat it doesValues
temperatureTemperature sensor.°C
humidityHumidity. May sit on the same device as a temperature.0–100 %
contactDoor or window contact.Boolean — shown as Open / Closed
motionMotion detector.Boolean — Detected / Clear
presencePresence detector.Boolean — Present / Absent
illuminanceBrightness sensor.0–100 000 lux
co2Air quality.0–5000 ppm
  • A combined temperature-and-humidity sensor is one device with both properties — do not split it into two.
  • Use presence or occupancy for 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.

PropertyWhat it doesValues
powerInstantaneous power.W
energyCumulative consumption.Reported in Wh, shown in kWh
voltageLine voltage.V
currentLine current.A
The energy register is expected in watt-hours and divided by 1000 for display. A meter that already reports kWh will read a thousand times too low — scale it in the meter, or bind the Wh register.

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.

PropertyWhat it doesValues
temperatureOutside temperature.°C
humidityOutside humidity.0–100 %
wind_speedWind speed.km/h
illuminanceOutside brightness.lux
Wind speed is the input worth wiring first: one flow that drives every blind to safety above a threshold protects more value than every comfort automation in the house combined.

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.

Scenes you create in Scenes can also be exposed to Apple Home and Google Home, where they become one-tap buttons and voice phrases.

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, disable and run; 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.

Wi-Fi devices that speak HTTP or MQTT (Tasmota, ESPHome and similar) do not use any of the bus paths above — you give them URL or topic templates in the device editor and the platform fills in the values.
Next: connect the protocol these devices live on, or see them working together.