How to configure MyURemote for Home Control

MyURemote Home Control lets you control lights, scenes, curtains/screens, and other smart-home functions from within the same interface you use for AV control. Home Control is configured in the Configuration Panel and can be used on PC, tablet or phone. The interface is responsive and adapts automatically to different screen sizes.

1. Where do I configure Home Control?

Home Control is configured inside the MyURemote Configuration Panel. You can add one or more Home Control pages depending on your setup (for example: one page for “Home”, one for “Garden”, one for “Office”).

→ Open Configuration Panel

2. The core Home Control concept

Home Control pages are built from two building blocks:

  1. Groups (also called “Zones”): logical sections like “Living”, “Kitchen”, “Office”, “Garden”.
  2. Elements: the actual controls inside a group (buttons, dimmers, scenes, curtains, etc.).

Each element connects to a Home integration (a controller), such as Home Assistant, KNX/BAOS, Philips Hue, or other supported systems. The controller determines how MyURemote talks to your smart-home environment.

Important: Home Control is separate from AV Zones

AV Zones (rooms) are used for audio/video master device logic (amplifier, display, inputs). Home Control Groups are used to organize smart-home controls. They can match your AV Zones, but they don’t have to.

3. Step 1 — Prepare your Home integration

Before adding Home Control elements, make sure the smart-home system you want to control is available in MyURemote. Depending on the integration, this can be discovered automatically or configured manually.

Recommended: Home Assistant

Home Assistant is a popular hub that can unify many brands and protocols (lights, sensors, scenes, climate, etc.). If you use Home Assistant, start here:

→ Home Assistant UI integration guide

Other systems and brands

MyURemote also supports brand/system-specific integrations. These can require different setup steps (IP address, pairing, tokens, gateways, etc.). You can find all available integrations here:

→ Integrations overview (brands & systems)

Controllers and “Extenders”

In MyURemote, smart-home integrations are typically represented as a controller (often called an “Extender” in the configuration). This is simply the connection endpoint to your smart-home system (IP-based, paired bridge, gateway, etc.).

Examples:

  • Home Assistant controller (token-based API)
  • KNX/BAOS IP gateway
  • Philips Hue bridge (paired)

4. Step 2 — Create a Home Control page

In the Configuration Panel, Home Control pages are created from the Tabs / Zones list. The first tab is usually an Audio/Video zone. From the second tab onwards, you can add either an Audio/Video tab or a Home Control page.

Add a Home Control page

  1. Open Zones (the tab list).
  2. Click the + button.
  3. Select Home Control page.
  4. Give the page a label and select an icon if available.
  5. Save.

After saving, MyURemote will open the Home Control editor where you can create groups and elements.

5. Step 3 — Create Groups (Home Control sections)

Groups organize your controls into logical sections. Typical group labels are: Living, Kitchen, Office, Bedroom, Garden.

Add a group

  1. Open the Home Control page.
  2. On the left side, click the + next to Groups.
  3. Enter a Group label.
  4. Set the Order (sort number) to control the group order.
  5. Save.

Group order

Group order is a simple numeric sorting value (example: 10, 20, 30). This makes it easy to insert new groups later without renumbering everything.

6. Step 4 — Add Elements (the actual controls)

Elements are the buttons and sliders you use for smart-home control. Each element is linked to:

  • a controller (the integration / extender)
  • a connection (how the controller talks to the system, when applicable)
  • a parameter (what to control: entity, datapoint, channel, scene id, etc.)
  • an optional max value for slider/dimmer style elements

Element types (typical)

  • Switch / Dimmer: a slider-type element (lights, dimmable outputs)
  • Curtain / Screen: slider-type element for blinds/screens
  • Small button: compact on/off or action button
  • Scene / Large button: one-tap scene or grouped action

Add an element

  1. Select a Group on the left.
  2. Click the + next to Elements.
  3. Enter a clear Label (example: “Spots”, “Screen”, “All Off”).
  4. Set Order (example: 10, 20, 30).
  5. Select the Type (button, dimmer, scene, curtain).
  6. Select the Controller (integration/extender).
  7. Select the Connection if required (e.g. IP, network, port, channel).
  8. Enter the Domotics parameter (the target datapoint/entity/channel).
  9. Set Max value for slider elements (often 255 or 100, depending on system).
  10. Save.

What is the “Domotics parameter”?

The parameter tells MyURemote what the element controls. The exact meaning depends on the integration:

  • Home Assistant: often an entity id (example: light.living_spots) or a specific service/action target.
  • KNX/BAOS: can be a datapoint number or channel reference.
  • Hue: can be lamp/group identifiers depending on configuration.

Always refer to the integration-specific documentation for the correct format. See: Integrations overview.

Max value (sliders/dimmers)

Many systems represent dimming levels in a numeric range (for example 0–255). MyURemote uses Max value to convert the UI percentage to the correct absolute value.

  • Typical values: 255 (common), 100 (percentage-based), or 1 (binary).

7. Testing and troubleshooting

Verify your controller connection

  • Make sure the integration/controller is reachable (IP correct, device online, pairing/token valid).
  • If an integration needs pairing (e.g. Hue), complete the pairing step first.

Common issues

  • Nothing happens when pressing a button: check controller selection + parameter format.
  • Slider moves but device does not change: verify max value and integration range.
  • Wrong element updates: make sure each element has a unique parameter where required.
  • Home Assistant specific: validate entity id and permissions in the token scope.

Tip: start small

Create one group and add 1–2 elements first (for example one light and one scene). Once that works, expand your configuration.

Related documentation