Talk:EEBUS

This article is rated C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects:

Science Low‑importance This article is within the scope of WikiProject Science, a collaborative effort to improve the coverage of Science on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ScienceWikipedia:WikiProject ScienceTemplate:WikiProject Sciencescience Low This article has been rated as Low-importance on the project's importance scale. Technology This article is within the scope of WikiProject Technology, a collaborative effort to improve the coverage of technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.TechnologyWikipedia:WikiProject TechnologyTemplate:WikiProject TechnologyTechnology

The user below has a request that an edit be made to EEBUS. That user has an actual or apparent conflict of interest. The requested edits backlog is very high. Please be extremely patient. There are currently 654 requests waiting for review. Please read the instructions for the parameters used by this template for accepting and declining them, and review the request below and make the edit if it is well sourced, neutral, and follows other Wikipedia guidelines and policies.

Hello, and full disclosure per WP:PAID first: I work in communications for EEBus Initiative e.V., the association behind the EEBUS standard, and I am posting this as part of my job. Because of the conflict of interest I will not edit the article myself. Instead, here are specific change requests with sources – I would appreciate review by uninvolved editors. The disclosure is also on my user page. The article carries a "promotional content" tag from 2020, and several figures and sections are outdated (much of the content reflects the state of around 2019/2020). Requests, roughly in order of importance:

1. Membership figure (section "Adoption > Membership") The current paragraph lists conflicting historical counts ("more than 50" in 2019, "about 60" in 2016, 70 in 2019, 61 as of 2020). Please replace the paragraph with:

As of September 2025, the initiative has 76 members, up from around 60 the year before.^[1]

2. Membership fee (section "Reception/criticism > Entry barrier") The article states "10,000 EUR per year; 5,000 EUR ...". Per the current contribution rules (January 2026), please change to: annual fee EUR 14,000; companies with at most 50 employees or annual turnover up to EUR 5 million may apply for a reduced fee of EUR 7,000.^[2]

3. New subsection "Regulatory adoption in Germany" (suggested placement: under "Adoption") This is currently the article's biggest gap: EEBUS has become the designated digital control path in German grid regulation, which is not mentioned at all. Suggested text:

Since 1 January 2024, Section 14a of the German Energy Industry Act (EnWG) requires operators of controllable consumption devices such as heat pumps, EV charging points and battery storage systems to allow distribution grid operators to temporarily reduce their power consumption in case of grid congestion. The control path runs via a smart metering system with a control box; alongside simple relay-based control, digital control via EEBUS is provided for.^[3] The EEBUS use case "Limitation of Power Consumption" (LPC) is regarded as a central mechanism for implementing Section 14a, and trade analyses expect EEBUS to establish itself as the de facto minimum standard for device communication under the regulation, with the German FNN control-box specification building on it.^[4][5] The underlying use cases LPC and LPP (Limitation of Power Production, for curtailing generation under Section 9 of the Renewable Energy Sources Act) were developed in the publicly funded ARNi project (2021–2024) and incorporated into the German VDE application rule VDE-AR-E 2829-6 (part 6-1 published July 2022, parts 6-2 to 6-4 September 2023) as well as submitted to international standardisation (IEC 62746-2).^[6] In 2024, the German association of electrical trades (ZVEH) joined the initiative;^[7] in 2026 both organisations published an online tool supporting electrical contractors in setting up controllable devices under Section 14a.^[8]

4. New paragraph on grid-related use cases (suggested placement: end of section "Structure of EEBUS") The article describes SHIP and SPINE but none of the use cases that dominate current deployment. Suggested text:

For grid interaction, four use cases are central: LPC (Limitation of Power Consumption) for throttling controllable loads, LPP (Limitation of Power Production) for curtailing generation, MPC (Monitoring of Power Consumption) for device-level metering data, and MGCP (Monitoring of Grid Connection Point) for monitoring the building's grid connection.^[1] In 2025 the initiative additionally introduced the SHIP Pairing Service, a QR-code-based commissioning procedure intended to let control boxes and home energy management systems establish a trusted connection without manual on-site configuration.^[1]

5. New subsection "Testing and certification" (suggested placement: under "Adoption" or after "Standardization") Suggested text:

Within the ARNi project, the initiative established the Living Lab Cologne at its Cologne headquarters as a test environment where manufacturers can test device implementations against the EEBUS specifications, including interoperability events (plugfests) held there since 2022.^[6] Since 2025, a pilot qualification programme has verified conformity of devices and energy management systems with the LPC, LPP, MPC and MGCP use cases; early qualified products included a home energy management platform by TQ-Group and an AC charge controller by Bender.^[9][10] In 2025 the initiative founded a subsidiary, EEBUService GmbH, to operate commercial testing and certification services, and announced a three-tier certification programme for EEBUS-capable devices starting in early 2026, with the first tier verifying basic SHIP/SPINE conformity and the higher tiers validating specific use cases.^[1]

6. Update (not remove) the criticism on reference implementations The "No royalty-free reference implementation" concern is sourced to 2019. It should stay as historical criticism, but the situation has changed and the article itself already cites NIBE's open-source OpenEEBUS release (November 2025, current ref [20]). Suggested addition after the existing sentence:

Open-source implementations have since become available, including the Go library eebus-go and NIBE's OpenEEBUS, released in November 2025. (reusing existing ref [20]; eebus-go: ^[11])

7. Research/academia (small addition to the existing section) Recent academic work exists on bridging EEBUS with legacy protocols, e.g. a Fraunhofer study developing an EEBus–Modbus protocol converter for the LPC use case.^[5] Could be appended as one sentence if editors consider it due weight. Most sources above are German-language, which WP:NONENG permits; independent English-language coverage of this topic is unfortunately thin outside trade press, but I am happy to look for further sources on request. I will stay out of the article itself. Thanks for taking a look! --Andres - EEBus (talk) 08:35, 17 July 2026 (UTC)Reply

Andres - EEBus (talk) 08:35, 17 July 2026 (UTC)Reply