{"id":126,"date":"2026-02-07T07:29:52","date_gmt":"2026-02-07T07:29:52","guid":{"rendered":"https:\/\/www.myuremote.com\/website\/?page_id=126"},"modified":"2026-03-26T09:28:09","modified_gmt":"2026-03-26T09:28:09","slug":"baos-knx-home-control","status":"publish","type":"page","link":"https:\/\/www.myuremote.com\/website\/docs\/integrations\/baos-knx-home-control\/","title":{"rendered":"Baos knx Home Control"},"content":{"rendered":"\n\n\n<div class=\"myu-doc\">\n\n  <h1>BAOS KNX Integration with MyURemote<\/h1>\n  <div style=\"margin: 20px 0 30px 0; text-align: center;\">\n  <img decoding=\"async\" \n    src=\"https:\/\/www.myuremote.com\/website\/wp-content\/uploads\/2026\/03\/0x0ss-2-scaled.png\" \n    alt=\"MyURemote KNX BAOS Home Control interface\"\n    style=\"max-width: 100%; height: auto; border-radius: 10px; box-shadow: 0 4px 20px rgba(0,0,0,0.2);\"\n  >\n<\/div>\n\n<p style=\"text-align: center; font-size: 16px; color: #666; margin-top: -10px;\">\n  Example of KNX control through BAOS in the MyURemote Home Control interface\n<\/p>\n\n  <p>\n    This page explains in detail how MyURemote works with a KNX installation through a\n    BAOS gateway, how datapoints should be structured in ETS, how commands and feedback\n    are mapped, and what the practical difference is between 1-bit and 1-byte datapoints.\n  <\/p>\n\n  <p>\n    This documentation is intended for installers, advanced users and developers who want\n    to configure KNX control correctly for use inside MyURemote.\n  <\/p>\n\n  <hr>\n\n  <h2>Overview<\/h2>\n\n  <p>\n    MyURemote can control KNX functions through a BAOS IP gateway. In this setup, the\n    BAOS gateway is treated by MyURemote as an IP-based controller. MyURemote does not\n    communicate directly with ETS or with KNX group addresses in the traditional way.\n    Instead, it sends and reads BAOS datapoint values through the gateway.\n  <\/p>\n\n  <p>\n    In practical terms, this means:\n  <\/p>\n\n  <ul>\n    <li>ETS is used to define the BAOS datapoints.<\/li>\n    <li>The BAOS gateway exposes these datapoints over IP.<\/li>\n    <li>MyURemote sends commands to these datapoints.<\/li>\n    <li>MyURemote reads feedback datapoints to keep the user interface in sync.<\/li>\n  <\/ul>\n\n  <p>\n    The current MyURemote implementation is based on a fixed datapoint mapping model:\n  <\/p>\n\n  <ul>\n    <li><strong>Datapoints 1 to 80<\/strong> are used as the main operational datapoints.<\/li>\n    <li><strong>Datapoints 81 to 160<\/strong> are used as status or feedback datapoints.<\/li>\n    <li>Feedback datapoints are mapped back to the main datapoints using a fixed <strong>+80 \/ -80<\/strong> offset.<\/li>\n  <\/ul>\n\n  <p>\n    Example:\n  <\/p>\n\n  <ul>\n    <li>Main datapoint <strong>1<\/strong> has feedback datapoint <strong>81<\/strong>.<\/li>\n    <li>Main datapoint <strong>10<\/strong> has feedback datapoint <strong>90<\/strong>.<\/li>\n    <li>Main datapoint <strong>44<\/strong> has feedback datapoint <strong>124<\/strong>.<\/li>\n  <\/ul>\n\n  <hr>\n\n  <h2>General architecture<\/h2>\n\n  <p>\n    The full chain looks like this:\n  <\/p>\n\n  <p>\n    <strong>MyURemote App \/ Configuration Panel \u2192 MyURemote BAOS module \u2192 IP connection \u2192 BAOS gateway \u2192 KNX datapoints<\/strong>\n  <\/p>\n\n  <p>\n    The configuration happens in two different places:\n  <\/p>\n\n  <ol>\n    <li>\n      <strong>ETS \/ BAOS configuration<\/strong><br>\n      Here the datapoints are created and assigned a type and a meaning.\n    <\/li>\n    <li>\n      <strong>MyURemote configuration panel<\/strong><br>\n      Here the BAOS gateway is added as an IP controller, commands are generated, and\n      Home Control elements are linked to specific datapoint numbers.\n    <\/li>\n  <\/ol>\n\n  <hr>\n\n  <h2>How MyURemote sees a BAOS gateway<\/h2>\n\n  <p>\n    Inside MyURemote, a BAOS gateway is configured as an <strong>IP device<\/strong>.\n    The gateway needs at least:\n  <\/p>\n\n  <ul>\n    <li>an IP address<\/li>\n    <li>a port number<\/li>\n    <li>the BAOS JavaScript module<\/li>\n  <\/ul>\n\n  <p>\n    Once configured, MyURemote can:\n  <\/p>\n\n  <ul>\n    <li>send write commands to a datapoint<\/li>\n    <li>read status blocks from the gateway<\/li>\n    <li>update the Home Control user interface with returned values<\/li>\n  <\/ul>\n\n  <p>\n    In the configuration panel, commands are stored in a very compact format such as:\n  <\/p>\n\n  <ul>\n    <li><code>1-0<\/code><\/li>\n    <li><code>1-1<\/code><\/li>\n    <li><code>41-0<\/code><\/li>\n    <li><code>41-128<\/code><\/li>\n    <li><code>41-255<\/code><\/li>\n  <\/ul>\n\n  <p>\n    The meaning is simple:\n  <\/p>\n\n  <ul>\n    <li>the first number is the <strong>datapoint number<\/strong><\/li>\n    <li>the second number is the <strong>value to write<\/strong><\/li>\n  <\/ul>\n\n  <p>\n    So:\n  <\/p>\n\n  <ul>\n    <li><code>1-0<\/code> means: write value 0 to datapoint 1<\/li>\n    <li><code>1-1<\/code> means: write value 1 to datapoint 1<\/li>\n    <li><code>41-128<\/code> means: write value 128 to datapoint 41<\/li>\n  <\/ul>\n\n  <hr>\n\n  <h2>Important datapoint model used by MyURemote<\/h2>\n\n  <p>\n    The current MyURemote BAOS implementation is built around a fixed datapoint layout.\n    This is important, because the software expects feedback datapoints to exist in a\n    second range with an offset of 80.\n  <\/p>\n\n  <h3>Main operational datapoints<\/h3>\n\n  <p>\n    Datapoints <strong>1 to 80<\/strong> are treated as the main datapoints used by\n    buttons, sliders and other Home Control elements.\n  <\/p>\n\n  <p>\n    These are the datapoints MyURemote sends commands to.\n  <\/p>\n\n  <h3>Feedback datapoints<\/h3>\n\n  <p>\n    Datapoints <strong>81 to 160<\/strong> are treated as the feedback datapoints.\n  <\/p>\n\n  <p>\n    These are the datapoints MyURemote reads back from the BAOS gateway to know the\n    current state of lights, dimmers, screens and other functions.\n  <\/p>\n\n  <h3>Fixed mapping rule<\/h3>\n\n  <p>\n    The feedback datapoint for a main datapoint is calculated as:\n  <\/p>\n\n  <p>\n    <strong>feedback datapoint = main datapoint + 80<\/strong>\n  <\/p>\n\n  <p>\n    And when MyURemote receives feedback, it maps the datapoint back as:\n  <\/p>\n\n  <p>\n    <strong>main datapoint = feedback datapoint &#8211; 80<\/strong>\n  <\/p>\n\n  <p>\n    Examples:\n  <\/p>\n\n  <ul>\n    <li>Datapoint 1 \u2194 feedback 81<\/li>\n    <li>Datapoint 2 \u2194 feedback 82<\/li>\n    <li>Datapoint 19 \u2194 feedback 99<\/li>\n    <li>Datapoint 41 \u2194 feedback 121<\/li>\n    <li>Datapoint 44 \u2194 feedback 124<\/li>\n    <li>Datapoint 50 \u2194 feedback 130<\/li>\n  <\/ul>\n\n  <p>\n    This means that, for correct use with MyURemote, ETS should be programmed with this\n    offset logic in mind.\n  <\/p>\n\n  <hr>\n\n  <h2>Recommended ETS structure<\/h2>\n\n  <p>\n    Based on the current MyURemote BAOS implementation, the recommended structure is:\n  <\/p>\n\n  <ul>\n    <li><strong>1 to 40<\/strong>: binary command datapoints<\/li>\n    <li><strong>41 to 80<\/strong>: byte-based command datapoints<\/li>\n    <li><strong>81 to 120<\/strong>: binary feedback datapoints for 1 to 40<\/li>\n    <li><strong>121 to 160<\/strong>: byte-based feedback datapoints for 41 to 80<\/li>\n  <\/ul>\n\n  <p>\n    This structure is not just a documentation preference. It matches the way the current\n    BAOS logic in MyURemote scans and maps datapoints.\n  <\/p>\n\n  <p>\n    In other words:\n  <\/p>\n\n  <ul>\n    <li>main command datapoints stay in the first range<\/li>\n    <li>feedback for those datapoints must exist exactly 80 positions higher<\/li>\n  <\/ul>\n\n  <h3>Why this layout is practical<\/h3>\n\n  <ul>\n    <li>It keeps command datapoints and feedback datapoints clearly separated.<\/li>\n    <li>It makes debugging much easier.<\/li>\n    <li>It fits directly with the current MyURemote polling and response parser logic.<\/li>\n    <li>It avoids confusion between operational values and status values.<\/li>\n  <\/ul>\n\n  <hr>\n\n  <h2>Difference between 1-bit and 1-byte datapoints<\/h2>\n\n  <p>\n    A very important part of the setup is the distinction between <strong>1-bit<\/strong>\n    and <strong>1-byte<\/strong> datapoints.\n  <\/p>\n\n  <h3>1-bit datapoints<\/h3>\n\n  <p>\n    1-bit datapoints are used for simple binary actions. They only have two possible values:\n  <\/p>\n\n  <ul>\n    <li><strong>0<\/strong><\/li>\n    <li><strong>1<\/strong><\/li>\n  <\/ul>\n\n  <p>\n    Typical examples:\n  <\/p>\n\n  <ul>\n    <li>light off \/ on<\/li>\n    <li>relay off \/ on<\/li>\n    <li>screen up \/ down<\/li>\n    <li>button action<\/li>\n    <li>toggle state<\/li>\n  <\/ul>\n\n  <p>\n    In ETS these are typically configured as a binary datapoint type such as:\n  <\/p>\n\n  <ul>\n    <li><strong>DPT 01<\/strong> \u2013 Binary \u2013 1 Bit<\/li>\n  <\/ul>\n\n  <p>\n    In MyURemote these appear as commands like:\n  <\/p>\n\n  <ul>\n    <li><code>1-0<\/code><\/li>\n    <li><code>1-1<\/code><\/li>\n    <li><code>2-0<\/code><\/li>\n    <li><code>2-1<\/code><\/li>\n  <\/ul>\n\n  <p>\n    These are ideal for:\n  <\/p>\n\n  <ul>\n    <li>buttons<\/li>\n    <li>switches<\/li>\n    <li>small toggle controls<\/li>\n  <\/ul>\n\n  <h3>1-byte datapoints<\/h3>\n\n  <p>\n    1-byte datapoints are used when a function needs a value range rather than a simple\n    off\/on state.\n  <\/p>\n\n  <p>\n    A 1-byte value can contain values from:\n  <\/p>\n\n  <ul>\n    <li><strong>0 to 255<\/strong><\/li>\n  <\/ul>\n\n  <p>\n    Typical examples:\n  <\/p>\n\n  <ul>\n    <li>dimmer level<\/li>\n    <li>light intensity<\/li>\n    <li>percentage control<\/li>\n    <li>position values<\/li>\n    <li>analog setpoints<\/li>\n  <\/ul>\n\n  <p>\n    In ETS these are often configured as:\n  <\/p>\n\n  <ul>\n    <li><strong>DPT 05<\/strong> \u2013 1 Byte<\/li>\n  <\/ul>\n\n  <p>\n    In MyURemote, these can result in a large list of possible commands, for example:\n  <\/p>\n\n  <ul>\n    <li><code>41-0<\/code><\/li>\n    <li><code>41-1<\/code><\/li>\n    <li><code>41-2<\/code><\/li>\n    <li>&#8230;<\/li>\n    <li><code>41-255<\/code><\/li>\n  <\/ul>\n\n  <p>\n    In the Home Control interface these are typically used as sliders, where MyURemote\n    displays a percentage while internally sending a value between 0 and the configured\n    maximum.\n  <\/p>\n\n  <hr>\n\n  <h2>How Home Control uses BAOS datapoints<\/h2>\n  <h3>Example in Home Control configuration<\/h3>\n\n<p>\n  Below is an example of how Home Control elements are linked to BAOS datapoints\n  in the MyURemote configuration panel.\n<\/p>\n\n<div style=\"margin: 20px 0; text-align: center;\">\n  <img decoding=\"async\" \n    src=\"https:\/\/www.myuremote.com\/website\/wp-content\/uploads\/2026\/03\/mur-baos-2.png\" \n    alt=\"MyURemote Home Control BAOS configuration\"\n    style=\"max-width: 100%; height: auto; border: 1px solid #ddd; border-radius: 6px;\"\n  >\n<\/div>\n\n<p>\n  Each element is linked to a specific datapoint using the <strong>Param<\/strong> field.\n  For example, <strong>Param: 44<\/strong> means that the element controls datapoint 44\n  in the BAOS gateway.\n<\/p>\n\n  <p>\n    In the Home Control page, each UI element is linked to:\n  <\/p>\n\n  <ul>\n    <li>a label<\/li>\n    <li>a type<\/li>\n    <li>an extender<\/li>\n    <li>a module<\/li>\n    <li>a domotics parameter<\/li>\n    <li>an optional maximum value<\/li>\n  <\/ul>\n\n  <p>\n    For BAOS, the important field is the <strong>domotics parameter<\/strong>.\n    This parameter is the datapoint number used by MyURemote.\n  <\/p>\n\n  <p>\n    Example:\n  <\/p>\n\n  <ul>\n    <li><strong>Param: 44<\/strong><\/li>\n    <li><strong>Max: 255<\/strong><\/li>\n  <\/ul>\n\n  <p>\n    This means that the element controls datapoint 44 and that the UI should work on a\n    range from 0 to 255.\n  <\/p>\n\n  <h3>Element types in Home Control<\/h3>\n\n  <p>\n    The Home Control code uses different UI element types:\n  <\/p>\n\n  <ul>\n    <li><strong>type 0<\/strong>: slider for light-like values<\/li>\n    <li><strong>type 1<\/strong>: slider for screen \/ shape-like values<\/li>\n    <li><strong>type 2<\/strong>: small button<\/li>\n    <li><strong>type 3<\/strong>: large button<\/li>\n  <\/ul>\n\n  <p>\n    In practical terms:\n  <\/p>\n\n  <ul>\n    <li>1-bit datapoints are usually linked to button-style controls<\/li>\n    <li>1-byte datapoints are usually linked to slider-style controls<\/li>\n  <\/ul>\n\n  <hr>\n\n  <h2>How writing works<\/h2>\n\n  <p>\n    When a user touches a button or moves a slider in MyURemote, the system builds a BAOS\n    write frame and sends it to the BAOS gateway.\n  <\/p>\n\n  <p>\n    Internally, the important logic is:\n  <\/p>\n\n  <ul>\n    <li>take the datapoint number<\/li>\n    <li>take the requested value<\/li>\n    <li>build a BAOS message<\/li>\n    <li>send it over IP to the configured gateway<\/li>\n  <\/ul>\n\n  <p>\n    For binary datapoints, the values are usually:\n  <\/p>\n\n  <ul>\n    <li>0<\/li>\n    <li>1<\/li>\n  <\/ul>\n\n  <p>\n    For byte datapoints, the values can be:\n  <\/p>\n\n  <ul>\n    <li>0 to 255<\/li>\n  <\/ul>\n\n  <p>\n    MyURemote clamps values safely to a valid byte range, which means values lower than 0\n    become 0 and values higher than 255 become 255.\n  <\/p>\n\n  <hr>\n\n  <h2>How reading and feedback works<\/h2>\n\n  <p>\n    Feedback is one of the most important parts of the BAOS integration.\n  <\/p>\n\n  <p>\n    MyURemote does not simply assume that a sent command succeeded. It also polls status\n    datapoints from the BAOS gateway.\n  <\/p>\n\n  <h3>Polling model<\/h3>\n\n  <p>\n    The current implementation reads feedback datapoints in blocks of 20.\n  <\/p>\n\n  <p>\n    It cycles through the feedback range and reads:\n  <\/p>\n\n  <ul>\n    <li>81 to 100<\/li>\n    <li>101 to 120<\/li>\n    <li>121 to 140<\/li>\n    <li>141 to 160<\/li>\n  <\/ul>\n\n  <p>\n    The returned datapoint IDs are then mapped back to the original main datapoints by\n    subtracting 80.\n  <\/p>\n\n  <p>\n    This is why the feedback range must be programmed consistently in ETS.\n  <\/p>\n\n  <h3>Why feedback is necessary<\/h3>\n\n  <ul>\n    <li>to show the real state of a light<\/li>\n    <li>to show the current dim value<\/li>\n    <li>to update button states correctly<\/li>\n    <li>to keep sliders synchronized<\/li>\n    <li>to reflect changes made outside MyURemote<\/li>\n  <\/ul>\n\n  <p>\n    For example, if a light is switched on by another KNX button or logic rule, MyURemote\n    can still show the correct status if the BAOS feedback datapoint is updated.\n  <\/p>\n\n  <hr>\n\n  <h2>Recommended practical setup in ETS<\/h2>\n\n  <p>\n    When preparing a BAOS gateway for use with MyURemote, it is recommended to define the\n    datapoints in a structured way.\n  <\/p>\n\n  <h3>Suggested layout<\/h3>\n\n  <h4>Binary command datapoints<\/h4>\n  <ul>\n    <li>1 = kitchen light<\/li>\n    <li>2 = pool shutter<\/li>\n    <li>3 = spare<\/li>\n    <li>4 = kitchen speakers<\/li>\n    <li>5 = terrace speakers<\/li>\n    <li>6 = pool speakers<\/li>\n    <li>7 = all kitchen lights<\/li>\n    <li>8 = all outdoor lights<\/li>\n    <li>9 = all off<\/li>\n    <li>10 = small curtain street side<\/li>\n  <\/ul>\n\n  <h4>Byte command datapoints<\/h4>\n  <ul>\n    <li>41 = terrace lights dimmer<\/li>\n    <li>42 = kitchen table dimmer<\/li>\n    <li>43 = stairs dimmer<\/li>\n    <li>44 = bar spots dimmer<\/li>\n    <li>45 = kitchen oven dimmer<\/li>\n    <li>46 = kitchen TV dimmer<\/li>\n    <li>47 = spare<\/li>\n    <li>48 = hallway lights dimmer<\/li>\n    <li>49 = spare<\/li>\n    <li>50 = living dimmer<\/li>\n  <\/ul>\n\n  <h4>Binary feedback datapoints<\/h4>\n  <ul>\n    <li>81 = feedback of datapoint 1<\/li>\n    <li>82 = feedback of datapoint 2<\/li>\n    <li>83 = feedback of datapoint 3<\/li>\n    <li>84 = feedback of datapoint 4<\/li>\n    <li>85 = feedback of datapoint 5<\/li>\n    <li>86 = feedback of datapoint 6<\/li>\n  <\/ul>\n\n  <h4>Byte feedback datapoints<\/h4>\n  <ul>\n    <li>121 = feedback of datapoint 41<\/li>\n    <li>122 = feedback of datapoint 42<\/li>\n    <li>123 = feedback of datapoint 43<\/li>\n    <li>124 = feedback of datapoint 44<\/li>\n    <li>125 = feedback of datapoint 45<\/li>\n    <li>126 = feedback of datapoint 46<\/li>\n  <\/ul>\n\n  <p>\n    Using a fixed structured layout is strongly recommended. It keeps installation,\n    configuration and troubleshooting much easier.\n  <\/p>\n\n  <hr>\n\n  <h2>How commands are configured in MyURemote<\/h2>\n  \n  <h3>Example configuration in MyURemote<\/h3>\n\n<p>\n  Below is an example of how BAOS datapoint commands are configured in the\n  MyURemote configuration panel.\n<\/p>\n\n<div style=\"margin: 20px 0; text-align: center;\">\n  <img \n\tsrc=\"https:\/\/www.myuremote.com\/website\/wp-content\/uploads\/2026\/03\/mur-baos-3.png\" \n    alt=\"MyURemote BAOS command configuration\"\n    style=\"max-width: 100%; height: auto; border: 1px solid #ddd; border-radius: 6px;\"\n  >\n<\/div>\n\n<p>\n  Each datapoint can have multiple command values. For binary datapoints (1-bit),\n  typically two values are defined (0 and 1). For byte datapoints (1-byte), a full\n  range of values (0 to 255) can be available.\n<\/p>\n\n  <p>\n    Once the BAOS gateway is added in MyURemote, commands can be defined for each\n    datapoint.\n  <\/p>\n\n  <h3>For 1-bit datapoints<\/h3>\n\n  <p>\n    Normally, two commands are sufficient:\n  <\/p>\n\n  <ul>\n    <li>Value 0<\/li>\n    <li>Value 1<\/li>\n  <\/ul>\n\n  <p>\n    Example:\n  <\/p>\n\n  <ul>\n    <li><code>Datapunkt 01 Value 0<\/code> \u2192 <code>1-0<\/code><\/li>\n    <li><code>Datapunkt 01 Value 1<\/code> \u2192 <code>1-1<\/code><\/li>\n  <\/ul>\n\n  <h3>For 1-byte datapoints<\/h3>\n\n  <p>\n    A full byte range may be made available.\n  <\/p>\n\n  <p>\n    Example:\n  <\/p>\n\n  <ul>\n    <li><code>Datapunkt 41 Value 000<\/code> \u2192 <code>41-0<\/code><\/li>\n    <li><code>Datapunkt 41 Value 001<\/code> \u2192 <code>41-1<\/code><\/li>\n    <li><code>Datapunkt 41 Value 128<\/code> \u2192 <code>41-128<\/code><\/li>\n    <li><code>Datapunkt 41 Value 255<\/code> \u2192 <code>41-255<\/code><\/li>\n  <\/ul>\n\n  <p>\n    In Home Control, these values are usually not selected one by one by the user. Instead,\n    the slider generates the correct value automatically.\n  <\/p>\n\n  <hr>\n\n  <h2>How slider values are handled<\/h2>\n\n  <p>\n    For slider elements, MyURemote shows a percentage to the user, but internally it can\n    work with a maximum value such as 255.\n  <\/p>\n\n  <p>\n    Example:\n  <\/p>\n\n  <ul>\n    <li>0% \u2192 value 0<\/li>\n    <li>50% \u2192 value about 127 or 128<\/li>\n    <li>100% \u2192 value 255<\/li>\n  <\/ul>\n\n  <p>\n    This allows a simple and user-friendly interface while still working with the BAOS\n    datapoint value range expected by the KNX side.\n  <\/p>\n\n  <hr>\n\n  <h2>Best practices<\/h2>\n\n  <ul>\n    <li>Always keep command datapoints and feedback datapoints clearly separated.<\/li>\n    <li>Use a strict +80 mapping for feedback datapoints when the installation is intended for MyURemote.<\/li>\n    <li>Group binary and byte datapoints logically.<\/li>\n    <li>Use clear descriptions in ETS so every datapoint remains understandable.<\/li>\n    <li>Reserve spare datapoints for future expansion.<\/li>\n    <li>Keep naming consistent between ETS and MyURemote.<\/li>\n    <li>For dimming or variable values, use byte-based datapoints with a defined maximum value.<\/li>\n    <li>For buttons and toggles, use binary datapoints.<\/li>\n  <\/ul>\n\n  <hr>\n\n  <h2>Common mistakes<\/h2>\n\n  <ul>\n    <li>Using feedback datapoints in the same range as command datapoints.<\/li>\n    <li>Forgetting the +80 offset required by the current MyURemote implementation.<\/li>\n    <li>Using a 1-bit datapoint where a byte value is needed.<\/li>\n    <li>Using a byte datapoint where only binary switching is intended.<\/li>\n    <li>Assigning the wrong Home Control parameter number.<\/li>\n    <li>Forgetting to define feedback datapoints, resulting in incorrect UI status.<\/li>\n  <\/ul>\n\n  <hr>\n\n  <h2>Developer notes<\/h2>\n\n  <p>\n    The current MyURemote BAOS implementation builds BAOS write and read frames manually.\n    Write commands send a datapoint number and value to the gateway. Read operations poll\n    blocks of feedback datapoints and then map them back to the original UI elements.\n  <\/p>\n\n  <p>\n    The response parser expects datapoint value responses and returns compact arrays in the\n    format:\n  <\/p>\n\n  <p>\n    <code>[key, value, key, value, ...]<\/code>\n  <\/p>\n\n  <p>\n    For BAOS status reads, the received datapoint number is converted back to the Home\n    Control datapoint using:\n  <\/p>\n\n  <p>\n    <code>mapped datapoint = feedback datapoint - 80<\/code>\n  <\/p>\n\n  <p>\n    This is the reason the ETS structure must match the expected feedback range.\n  <\/p>\n\n  <hr>\n\n  <h2>Conclusion<\/h2>\n\n  <p>\n    MyURemote can work very efficiently with KNX through a BAOS gateway, provided the\n    datapoints are structured correctly.\n  <\/p>\n\n  <p>\n    The most important rule is:\n  <\/p>\n\n  <p>\n    <strong>Use datapoints 1 to 80 for the main functions and datapoints 81 to 160 as the corresponding feedback range.<\/strong>\n  <\/p>\n\n  <p>\n    Within that structure:\n  <\/p>\n\n  <ul>\n    <li>binary functions should use 1-bit datapoints<\/li>\n    <li>variable values should use 1-byte datapoints<\/li>\n    <li>feedback should follow the same numbering with an offset of 80<\/li>\n  <\/ul>\n\n  <p>\n    When this structure is respected, MyURemote can send commands correctly, read back\n    current status, and keep the Home Control interface synchronized with the KNX system.\n  <\/p>\n\n<\/div>\n\n\n","protected":false},"excerpt":{"rendered":"<p>BAOS KNX Integration with MyURemote Example of KNX control through BAOS in the MyURemote Home Control interface This page explains in detail how MyURemote works with a KNX installation through a BAOS gateway, how datapoints should be structured in ETS, how commands and feedback are mapped, and what the practical difference is between 1-bit and [&hellip;]<\/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-126","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\/126","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=126"}],"version-history":[{"count":8,"href":"https:\/\/www.myuremote.com\/website\/wp-json\/wp\/v2\/pages\/126\/revisions"}],"predecessor-version":[{"id":239,"href":"https:\/\/www.myuremote.com\/website\/wp-json\/wp\/v2\/pages\/126\/revisions\/239"}],"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=126"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}