MyURemote ↔ Home Assistant

Contents

1. Concept

MyURemote acts as a local gateway. The Home Assistant extender communicates with Home Assistant using raw HTTP requests over TCP (default ip:8123).

• The Domotics page uses polling to read states.
• Macros send a single command string.
• The extender translates that string into Home Assistant service calls.

Design goal: MyURemote stays generic and predictable, while Home Assistant remains the source of truth for logic and state.

2. Why MyURemote + Home Assistant

Home Assistant offers a huge ecosystem and powerful automation logic. MyURemote focuses on fast, AV-first control: a consistent remote UI, zones/inputs, and one-button macros. Together, they provide the best of both worlds.

3. Requirements

• Home Assistant reachable on the local network.
• A MyURemote device/extender of type homeassistant.
• Home Assistant entities created using the naming rules below.

Tip: use a fixed IP (DHCP reservation) for Home Assistant to avoid changing addresses.

4. Home Assistant Long-Lived Access Token

1. Open the Home Assistant UI.
2. Click your profile (top right).
3. Go to Security.
4. Create a Long-Lived Access Token.
5. Copy the token.
6. Paste it into the MyURemote pairing dialog and save.

The token is stored as a MyURemote device parameter (HAToken).

5. Naming Convention (very important)

MyURemote sends a single command string. The extender maps that string to the correct entity ID and service call. Keep naming consistent (prefer lowercase, no spaces).

5.1 Lights

MyURemote commands:
light_{room}_{n}_on
light_{room}_{n}_off
light_{room}_{n}_{level}pct

Home Assistant entity:
light.light_{room}_{n}

Examples:
light_living_1_on    → light.light_living_1
light_living_1_off   → light.light_living_1
light_living_1_50pct → light.light_living_1

5.2 Screens / Curtains

MyURemote commands:
screen_{room}_{n}_open
screen_{room}_{n}_close

Home Assistant entity:
cover.screen_{room}_{n}

5.3 Scenes

MyURemote commands:
SCENE_FILM
SCENE_AllOff
SCENE_LEAVE
SCENE_97

Home Assistant entities:
scene.film
scene.alloff
scene.leave
scene.scene97

6. Domotics Page (UI & Feedback)

On the MyURemote Domotics page you configure:

• Domotics Object (the HA entity ID)
• maxValue (defines how feedback is interpreted)

maxValue rules

• 1 → binary (on/off, open/close)
• 255 → dimmer (brightness)
• 100 → cover position

The extender polls Home Assistant using GET /api/states/{entity} and converts the response to a MyURemote value.

7. Macros & executeCommand()

A macro in MyURemote sends only a single command string. The Home Assistant extender interprets this string and executes the correct Home Assistant service.

// Examples of executed HA services

light.turn_on
light.turn_off
cover.open_cover
cover.close_cover
scene.turn_on

This design keeps MyURemote generic, while Home Assistant handles all automation logic.

8. Common patterns (practical)

8.1 “Movie” button (AV + lights + scene)

• Switch AV to the right input (receiver/TV control).
• Trigger a Home Assistant scene (lights, blinds, etc.).

Tip: keep AV switching in MyURemote (fast remote UX) and keep home-automation logic in HA scenes (easy to maintain).

8.2 Dimmer presets

Use commands like light_living_1_30pct for quick presets. Set maxValue=255 for dimmers.

8.3 Covers as binary buttons

For open/close only: set maxValue=1 and map to the correct cover.* entity.

9. Troubleshooting

400 Bad Request

• Usually caused by double URL encoding.
• Ensure raw HTTP is encoded only once.

No feedback in UI

• Check polling is active.
• Verify entity IDs in Home Assistant Developer Tools.
• Verify maxValue.

Token issues (401/403)

• Ensure the token is correct and not revoked.
• Re-save the token if Home Assistant user permissions change.
• Prefer using IP instead of hostname if DNS is unreliable.

10. Known pitfalls

• Wrong entity domain (light. vs switch. vs cover.).
• Mixed casing/spaces in naming → breaks predictable mapping.
• Reusing command names for different entities → ambiguity.
• Network segmentation (VLANs/firewalls) blocking access to :8123.

11. FAQ

Do I need Home Assistant Cloud?

No. This integration is designed for local network access.

Should I use scenes or individual commands?

Prefer HA scenes for complex home-automation logic, and keep MyURemote macros focused on orchestration (AV + triggering HA).

Can I use both Domotics and macros?

Yes. Domotics is best for UI feedback and interactive control. Macros are best for “one button” workflows.

12. Changelog

• v2 – Added contents, positioning section, common patterns, known pitfalls, expanded troubleshooting.
• v1 – Initial integration guide.