{"id":50,"date":"2026-02-05T07:50:24","date_gmt":"2026-02-05T07:50:24","guid":{"rendered":"https:\/\/www.myuremote.com\/website\/?page_id=50"},"modified":"2026-02-05T07:54:37","modified_gmt":"2026-02-05T07:54:37","slug":"home-assistant-ui","status":"publish","type":"page","link":"https:\/\/www.myuremote.com\/website\/docs\/integrations\/home-assistant-ui\/","title":{"rendered":"Home Assistant UI"},"content":{"rendered":"\n
\n\n
\n

\n MyURemote \u2194 Home Assistant\n <\/h1>\n

\n Official guide to control Home Assistant<\/strong> from MyURemote<\/strong>,\n both via the Domotics page<\/strong> (UI & feedback) and via Macro commands<\/strong>.\n <\/p>\n <\/header>\n\n \n

\n

Contents<\/h2>\n
\n \n 1.<\/strong> Concept\n <\/a>\n \n 2.<\/strong> Why MyURemote + Home Assistant\n <\/a>\n \n 3.<\/strong> Requirements\n <\/a>\n \n 4.<\/strong> Long-Lived Access Token\n <\/a>\n \n 5.<\/strong> Naming Convention\n <\/a>\n \n 6.<\/strong> Domotics Page (UI & Feedback)\n <\/a>\n \n 7.<\/strong> Macros & executeCommand()\n <\/a>\n \n 8.<\/strong> Common patterns\n <\/a>\n \n 9.<\/strong> Troubleshooting\n <\/a>\n \n 10.<\/strong> Known pitfalls\n <\/a>\n \n 11.<\/strong> FAQ\n <\/a>\n \n 12.<\/strong> Changelog\n <\/a>\n <\/div>\n <\/section>\n\n
\n\n \n
\n

1. Concept<\/h2>\n

\n MyURemote acts as a local gateway. The Home Assistant extender communicates with Home Assistant using\n raw HTTP requests over TCP (default ip:8123<\/code>).\n <\/p>\n

    \n
  • The Domotics page<\/strong> uses polling to read states.<\/li>\n
  • Macros<\/strong> send a single command string.<\/li>\n
  • The extender translates that string into Home Assistant service calls.<\/li>\n <\/ul>\n

    \n Design goal:<\/strong> MyURemote stays generic and predictable, while Home Assistant remains the source of truth for logic and state.\n <\/p>\n <\/section>\n\n \n

    \n

    2. Why MyURemote + Home Assistant<\/h2>\n

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

    \n
    \n MyURemote does best<\/strong>\n
      \n
    • Remote UI & AV navigation<\/li>\n
    • Macros across protocols<\/li>\n
    • Zones & inputs (AV-first model)<\/li>\n <\/ul>\n <\/div>\n
      \n Home Assistant does best<\/strong>\n
        \n
      • Entities & state model<\/li>\n
      • Automations & scenes<\/li>\n
      • Integration ecosystem<\/li>\n <\/ul>\n <\/div>\n <\/div>\n <\/section>\n\n \n
        \n

        3. Requirements<\/h2>\n
          \n
        • Home Assistant reachable on the local network.<\/li>\n
        • A MyURemote device\/extender of type homeassistant<\/code>.<\/li>\n
        • Home Assistant entities created using the naming rules below.<\/li>\n <\/ul>\n

          \n Tip: use a fixed IP (DHCP reservation) for Home Assistant to avoid changing addresses.\n <\/p>\n <\/section>\n\n \n

          \n

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

            \n The token is stored as a MyURemote device parameter (HAToken<\/code>).\n <\/p>\n <\/section>\n\n \n

            \n

            5. Naming Convention (very important)<\/h2>\n

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

            5.1 Lights<\/h3>\n 
            MyURemote commands:\nlight_{room}_{n}_on\nlight_{room}_{n}_off\nlight_{room}_{n}_{level}pct\n\nHome Assistant entity:\nlight.light_{room}_{n}<\/code><\/pre>\n\n    
            Examples:\nlight_living_1_on    \u2192 light.light_living_1\nlight_living_1_off   \u2192 light.light_living_1\nlight_living_1_50pct \u2192 light.light_living_1<\/code><\/pre>\n\n    
            5.2 Screens \/ Curtains<\/h3>\n    
            MyURemote commands:\nscreen_{room}_{n}_open\nscreen_{room}_{n}_close\n\nHome Assistant entity:\ncover.screen_{room}_{n}<\/code><\/pre>\n\n    
            5.3 Scenes<\/h3>\n    
            MyURemote commands:\nSCENE_FILM\nSCENE_AllOff\nSCENE_LEAVE\nSCENE_97\n\nHome Assistant entities:\nscene.film\nscene.alloff\nscene.leave\nscene.scene97<\/code><\/pre>\n  <\/section>\n\n  \n  
            \n    
            6. Domotics Page (UI & Feedback)<\/h2>\n    
            \n      On the MyURemote Domotics page you configure:\n    <\/p>\n    
              \n      
            • Domotics Object<\/strong> (the HA entity ID)<\/li>\n      
            • maxValue<\/strong> (defines how feedback is interpreted)<\/li>\n    <\/ul>\n\n    
              maxValue rules<\/h3>\n    
                \n      
              • 1<\/code> \u2192 binary (on\/off, open\/close)<\/li>\n      
              • 255<\/code> \u2192 dimmer (brightness)<\/li>\n      
              • 100<\/code> \u2192 cover position<\/li>\n    <\/ul>\n\n    
                \n      The extender polls Home Assistant using GET \/api\/states\/{entity}<\/code> and converts the response to a MyURemote value.\n    <\/p>\n  <\/section>\n\n  \n  
                \n    
                7. Macros & executeCommand()<\/h2>\n    
                \n      A macro in MyURemote sends only a single command string. The Home Assistant extender interprets this string and executes\n      the correct Home Assistant service.\n    <\/p>\n    
                \/\/ Examples of executed HA services\n\nlight.turn_on\nlight.turn_off\ncover.open_cover\ncover.close_cover\nscene.turn_on<\/code><\/pre>\n    
                \n      This design keeps MyURemote generic, while Home Assistant handles all automation logic.\n    <\/p>\n  <\/section>\n\n  \n  
                \n    
                8. Common patterns (practical)<\/h2>\n\n    
                8.1 \u201cMovie\u201d button (AV + lights + scene)<\/h3>\n    
                  \n      
                • Switch AV to the right input (receiver\/TV control).<\/li>\n      
                • Trigger a Home Assistant scene (lights, blinds, etc.).<\/li>\n    <\/ul>\n    
                  \n      Tip: keep AV switching in MyURemote (fast remote UX) and keep home-automation logic in HA scenes (easy to maintain).\n    <\/p>\n\n    
                  8.2 Dimmer presets<\/h3>\n    
                  \n      Use commands like light_living_1_30pct<\/code> for quick presets. Set maxValue=255<\/code> for dimmers.\n    <\/p>\n\n    
                  8.3 Covers as binary buttons<\/h3>\n    
                  \n      For open\/close only: set maxValue=1<\/code> and map to the correct cover.*<\/code> entity.\n    <\/p>\n  <\/section>\n\n  \n  
                  \n    
                  9. Troubleshooting<\/h2>\n\n    
                  400 Bad Request<\/h3>\n    
                    \n      
                  • Usually caused by double URL encoding.<\/li>\n      
                  • Ensure raw HTTP is encoded only once.<\/li>\n    <\/ul>\n\n    
                    No feedback in UI<\/h3>\n    
                      \n      
                    • Check polling is active.<\/li>\n      
                    • Verify entity IDs in Home Assistant Developer Tools.<\/li>\n      
                    • Verify maxValue<\/code>.<\/li>\n    <\/ul>\n\n    
                      Token issues (401\/403)<\/h3>\n    
                        \n      
                      • Ensure the token is correct and not revoked.<\/li>\n      
                      • Re-save the token if Home Assistant user permissions change.<\/li>\n      
                      • Prefer using IP instead of hostname if DNS is unreliable.<\/li>\n    <\/ul>\n  <\/section>\n\n  \n  
                        \n    
                        10. Known pitfalls<\/h2>\n    
                          \n      
                        • Wrong entity domain (light.<\/code> vs switch.<\/code> vs cover.<\/code>).<\/li>\n      
                        • Mixed casing\/spaces in naming \u2192 breaks predictable mapping.<\/li>\n      
                        • Reusing command names for different entities \u2192 ambiguity.<\/li>\n      
                        • Network segmentation (VLANs\/firewalls) blocking access to :8123<\/code>.<\/li>\n    <\/ul>\n  <\/section>\n\n  \n  
                          \n    
                          11. FAQ<\/h2>\n\n    
                          Do I need Home Assistant Cloud?<\/h3>\n    
                          No. This integration is designed for local network access.<\/p>\n\n    
                          Should I use scenes or individual commands?<\/h3>\n    
                          \n      Prefer HA scenes for complex home-automation logic, and keep MyURemote macros focused on orchestration (AV + triggering HA).\n    <\/p>\n\n    
                          Can I use both Domotics and macros?<\/h3>\n    
                          \n      Yes. Domotics is best for UI feedback and interactive control. Macros are best for \u201cone button\u201d workflows.\n    <\/p>\n  <\/section>\n\n  \n  
                          \n    
                          12. Changelog<\/h2>\n    
                            \n      
                          • v2<\/strong> \u2013 Added contents, positioning section, common patterns, known pitfalls, expanded troubleshooting.<\/li>\n      
                          • v1<\/strong> \u2013 Initial integration guide.<\/li>\n    <\/ul>\n  <\/section>\n\n<\/section>\n\n","protected":false},"excerpt":{"rendered":"
                            MyURemote \u2194 Home Assistant Official guide to control Home Assistant from MyURemote, both via the Domotics page (UI & feedback) and via Macro commands. Contents 1. Concept 2. Why MyURemote + Home Assistant 3. Requirements 4. Long-Lived Access Token 5. Naming Convention 6. Domotics Page (UI & Feedback) 7. Macros & executeCommand() 8. Common patterns […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":28,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-50","page","type-page","status-publish","hentry"],"blocksy_meta":{"has_hero_section":"disabled","styles_descriptor":{"styles":{"desktop":"","tablet":"","mobile":""},"google_fonts":[],"version":6}},"_links":{"self":[{"href":"https:\/\/www.myuremote.com\/website\/wp-json\/wp\/v2\/pages\/50","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.myuremote.com\/website\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.myuremote.com\/website\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.myuremote.com\/website\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.myuremote.com\/website\/wp-json\/wp\/v2\/comments?post=50"}],"version-history":[{"count":2,"href":"https:\/\/www.myuremote.com\/website\/wp-json\/wp\/v2\/pages\/50\/revisions"}],"predecessor-version":[{"id":52,"href":"https:\/\/www.myuremote.com\/website\/wp-json\/wp\/v2\/pages\/50\/revisions\/52"}],"up":[{"embeddable":true,"href":"https:\/\/www.myuremote.com\/website\/wp-json\/wp\/v2\/pages\/28"}],"wp:attachment":[{"href":"https:\/\/www.myuremote.com\/website\/wp-json\/wp\/v2\/media?parent=50"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}