How to configure MyURemote for KNX control (via BAOS)

MyURemote can control KNX installations through a BAOS IP gateway (for example a Weinzierl BAOS module). This integration is part of the Home Control system.

You configure your KNX setup by creating Home Control pages with Groups (zones) and Elements (buttons, sliders, curtains, scenes). Each element sends and reads BAOS datapoint values so the UI stays in sync with the KNX bus.

For other integrations (Home Assistant, Hue, etc.), see: /website/docs/integrations/ — and for the Home Assistant UI specifically: Home Assistant UI.

1. What do I need?

  • A working KNX installation (lights, dimmers, shutters, scenes, etc.).
  • A BAOS IP gateway reachable on your LAN (IP address + port).
  • MyURemote with access to the Configuration Panel.
  • MyURemote configured with a Home Control tab.

Important: BAOS works with datapoints

In MyURemote, each Home Control Element points to a BAOS datapoint using the Domotics parameter field (usually a number). MyURemote sends write commands and continuously reads status to keep the UI in sync with the KNX bus.

2. Step 1 — Add a BAOS controller (Extender)

BAOS is handled as a controller (Extender) in MyURemote. Once added, it becomes selectable in Home Control Elements.

Add the BAOS extender

  1. Open the Configuration Panel.
  2. Go to Controllers / Extenders (depending on your UI naming).
  3. Click + to add a new extender.
  4. Select the extender type that uses the BAOS module.
  5. Enter the IP address and port of your BAOS gateway.
  6. Save.

After saving, the BAOS extender will appear in the dropdown list when creating or editing Home Control Elements.

3. Step 2 — Create a Home Control page (Tab)

Home Control configuration is stored in the database and edited in the Ionic Settings UI. A Home Control page contains:

  • Groups (zones): e.g. Living Room, Kitchen, Terrace
  • Elements: buttons and sliders inside a group

Home Control page structure

  1. Create a new tab and choose Home Control (typically from the 2nd tab onwards).
  2. Add one or more Groups.
  3. Add Elements inside each group.

4. Step 3 — Add Elements (what each field means)

Each element defines what MyURemote sends to KNX via BAOS. The most important fields are:

Element fields

  • Label: the visible name in the Home Control UI (e.g. “Spots”, “Screen”, “Daylight”).
  • Order: sorting number within the group (10, 20, 30… makes reordering easier).
  • Type:
    • 0 — Slider (dimmer-style): value range 0..Max
    • 1 — Slider (screen/curtain-style): value range 0..Max
    • 2 — Small toggle button (0/1)
    • 3 — Large button (scenes or group actions, 0/1)
  • Extender: select your BAOS extender (the controller that will handle the command).
  • Domotics parameter: the BAOS datapoint identifier used by MyURemote. In BAOS/KNX setups this is typically a number.
  • Max value: slider elements (type 0/1) are displayed as a percentage (0–100%), but BAOS receives a raw value. Example: 255 for dimming, or 1 for binary up/down.

Typical examples

  • Dimmer: Type 0, Parameter = datapoint, Max = 255
  • On/Off light: Type 3, Parameter = datapoint, Max can stay 255 (button uses 0/1)
  • Screen up/down: Type 1, Parameter = datapoint, Max = 1
  • Scene trigger: Type 3, Parameter = scene datapoint, button toggles 0/1

5. How BAOS communication works in MyURemote (high-level)

The BAOS extender in MyURemote builds BAOS frames and sends them through the MyURemote gateway layer. It supports:

  • Write: set a datapoint value (when you press a button or move a slider)
  • Read: poll datapoint values to keep the UI updated (status feedback)

Status polling: the “+80 mapping”

The BAOS module uses a legacy scan strategy: it reads status datapoints in blocks and maps them back. Internally it reads datapoints in the range 81..160 and maps them back by doing (datapoint – 80). This keeps Home Control fast and avoids reading each datapoint one-by-one.

Values are handled as bytes (0..255). Sliders show percentages, but BAOS receives the raw byte value.

6. Troubleshooting

Nothing happens when I press a button

  • Verify the BAOS extender IP/port is correct and reachable from the MyURemote host.
  • Confirm the Element’s Extender is set to the BAOS controller.
  • Confirm the Domotics parameter matches the intended datapoint.

Slider moves but value in KNX is wrong

  • Check Max value (255 is typical; some objects are binary and should use 1).
  • Remember: UI shows percentage; BAOS receives a raw byte.

UI does not update (no feedback)

  • Status polling reads datapoints via the BAOS read strategy (scan blocks). If your installation uses a different mapping, adjust datapoints accordingly.
  • Make sure the gateway returns datapoint value responses (the BAOS module expects a datapoint-value response type).

Related documentation