{"id":199,"date":"2026-10-01T10:00:00","date_gmt":"2026-10-01T06:30:00","guid":{"rendered":"https:\/\/saeedshariati.net\/en\/?p=199"},"modified":"2026-10-01T12:19:06","modified_gmt":"2026-10-01T08:49:06","slug":"layer-zero-issue-1","status":"publish","type":"post","link":"https:\/\/saeedshariati.net\/en\/posts\/layer-zero-issue-1\/","title":{"rendered":"Layer Zero – Issue #1"},"content":{"rendered":"\n

Monthly Newsletter on Smart Buildings and Energy<\/strong><\/h1>\n\n\n\n

Editorial: KNX Is No Longer Just a Protocol<\/strong><\/h3>\n\n\n\n
\"KNX<\/figure>\n\n\n\n

For years, we knew KNX for being a standard. But this year, three forces are pushing simultaneously: Matter, energy efficiency regulations, and the end-user expectation for app-centric control. The question is no longer “Should KNX stay?” – the question is: where does KNX stand in the architecture of the smart building of the future?<\/p>\n\n\n\n

\n

In this issue, we break down the layers from physical to data, review the month’s trends, and put a real project under the microscope.<\/p>\n<\/blockquote>\n\n\n\n

Technical Deep Dive: From EIB to Matter<\/strong><\/p>\n\n\n\n

The Problem<\/strong><\/p>\n\n\n\n

Installers face a flood of protocols: KNX, BACnet, Modbus, Zigbee, Matter. The client expects “integration,” but each protocol speaks its own language. The result? Projects that fall apart during commissioning and maintenance costs that skyrocket.<\/p>\n\n\n\n

Why Now?<\/strong><\/p>\n\n\n\n

Matter’s newer versions have paved the way for bridging to KNX. For the first time, a common language is forming at the application layer that can connect closed ecosystems. At the same time, pressure from European energy regulations (EPBD) and end-user expectations for app-based control have transformed KNX from a “building control system” into “a node in the data network.”<\/p>\n\n\n\n

How It Works<\/strong><\/p>\n\n\n\n

A gateway plays the role of translator. On one side are KNX telegrams with Group Address structure. On the other side is the Matter data model with Clusters and Attributes. The gateway maps the two.<\/p>\n\n\n\n

But here is the critical point: Group Address architecture must be designed cleanly from day one.<\/strong> If Group Addresses have vague naming, messy structure, and no documentation, migration to any other protocol – Matter, BACnet, or anything future – becomes a nightmare.<\/p>\n\n\n\n

Consider three layers:<\/p>\n\n\n\n

Layer<\/strong><\/td>KNX TP<\/strong><\/td>KNX IP<\/strong><\/td>Matter Bridge<\/strong><\/td><\/tr><\/thead>
Physical<\/td>Twisted pair<\/td>Ethernet<\/td>Wi-Fi \/ Thread<\/td><\/tr>
Transport<\/td>Telegram<\/td>IP<\/td>IP<\/td><\/tr>
Data<\/td>Group Address<\/td>Group Address<\/td>Cluster \/ Attribute<\/td><\/tr>
Application<\/td>Direct control<\/td>Control + monitoring<\/td>Ecosystem integration<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

What This Means for You<\/strong><\/p>\n\n\n\n

If you have a project with a 10+ year lifespan, you need to decide today about migratable data structure<\/strong>, not tomorrow. This decision has three parts:<\/p>\n\n\n\n

    \n
  1. Standard Group Address naming<\/strong> – before the first cable is pulled<\/li>\n\n\n\n
  2. Data structure documentation<\/strong> – as part of project handover, not a forgotten Excel file<\/li>\n\n\n\n
  3. Gateway selection with update capability<\/strong> – not the cheapest option available<\/li>\n<\/ol>\n\n\n\n

    The cost of these three decisions today is negligible. The cost of their absence, three years later, is a full redesign.<\/p>\n\n\n\n

    \n\n\n\n

    Trend Radar<\/strong><\/p>\n\n\n\n

    European Union: EPBD Revision and Pressure on Existing Buildings<\/strong><\/p>\n\n\n\n

    \"Trend<\/figure>\n\n\n\n

    The Energy Performance of Buildings Directive (EPBD) in its new revision has shifted focus from new buildings to existing ones. Reporting and audit requirements have become stricter.<\/p>\n\n\n\n

    What it means for you:<\/em> Consulting opportunities for retrofits. Buildings that didn’t need a BMS yesterday now need one for compliance. This market is not in new buildings – it’s in 20-year-old buildings.<\/p>\n\n\n\n

    Matter 1.4: Support for Energy-Centric Devices<\/strong><\/p>\n\n\n\n

    The new Matter version covers energy management devices such as solar inverters, home batteries, and EV chargers. This means the Matter application layer has now entered the energy domain.<\/p>\n\n\n\n

    What it means for you:<\/em> A gateway for integrating load management into residential and small commercial ecosystems. If you work on residential projects, follow this trend.<\/p>\n\n\n\n

    PropTech Investment Growth in the Middle East<\/strong><\/p>\n\n\n\n

    Regional investment funds have increased their focus on smart building and energy efficiency startups. This means demand for expertise at the intersection of KNX, data, and energy.<\/p>\n\n\n\n

    What it means for you:<\/em> If you’re developing skills, combining KNX + data analysis creates a distinctive career position.<\/p>\n\n\n\n

    \n\n\n\n

    Field Notes<\/strong><\/p>\n\n\n\n

    12-Story Office Building – Northern Europe<\/strong><\/p>\n\n\n\n

    Challenge:<\/strong> Severe cooling load fluctuation during peak hours. The chiller system was adjusted manually based on operator experience. Result: high consumption at peak, and comfort loss during midday hours.<\/p>\n\n\n\n

    Solution:<\/strong> Implementation of predictive control using existing data in the KNX system – temperature sensors, fan coil status, and motorized valve feedback. A simple load prediction algorithm based on past-day patterns began adjusting the setpoint half an hour before peak.<\/p>\n\n\n\n

    Result:<\/strong> 18% reduction in peak-hour consumption, with no comfort loss. Return on investment: less than two cooling seasons.<\/p>\n\n\n\n

    Key Lesson:<\/strong> The data used for control was sufficient for optimization too. No new sensors needed. No new system needed. Only a layer of analytics on the same existing data.<\/p>\n\n\n\n

    \n\n\n\n

    Energy Angle<\/strong><\/p>\n\n\n\n

    Time-of-Use Tariffs Are Changing the Design Equation<\/strong><\/p>\n\n\n\n

    Time-of-Use (ToU) tariffs are expanding. This means energy cost is no longer a fixed number in design. The energy consultant must bring the load profile<\/strong> into the model from the conceptual phase – not just during the audit phase.<\/p>\n\n\n\n

    A practical question: In your next project, do you know the building’s load at 2 PM on summer days? If not, your BMS design is based on guesswork.<\/p>\n\n\n\n

    \n\n\n\n

    Question of the Month<\/strong><\/p>\n\n\n\n

    In your projects, what is the biggest barrier to integrating KNX with IT systems?<\/p>\n\n\n\n

    A)<\/strong> Cultural – teams don’t talk to each other
    B)<\/strong> Technical – protocols and standards are incompatible
    C)<\/strong> Contractual – responsibilities and scope are unclear<\/p>\n\n\n\n

    Send your answer to the newsletter email. Results will be published in the next issue.<\/p>\n\n\n\n

    \n\n\n\n

    This Month’s Action Step<\/strong><\/p>\n\n\n\n

    Create a Group Address documentation file for one of your active projects – even if incomplete. Naming, structure, and description of each group. This file is the foundation of any future migration or expansion. If you do this by the end of the month, you are ahead of 80% of your peers.<\/p>\n\n\n\n

    \n\n\n\n

    Layer Zero – Where infrastructure gets smart.<\/a><\/em><\/p>\n\n\n\n

    Next issue: Digital Twin – Marketing or Tool?<\/em><\/p>\n\n\n\n

    \n\n\n\n

    Sources:<\/strong><\/p>\n\n\n\n