Testevents in 2026
In order to optimally support the development of communication between FEIDs and HEMS, ElaadNL has expanded on the proven concept of testivals for EVs and chargers to domestic FEIDs and HEMS. In a series of three, with a doubling of participants between the first and second event, 2026 sees the start of what is likely to be an ongoing journey for the coming years.
What to expect
At the first event in February 2026 we welcomed 16 manufacturers and developers of FEID and HEMS. At the second event in 2028, the number of participants was 28, with testing going on until the final hour of the event and lots of lessons learned. So be prepared to meet around 50 manufacturers at event 3!
Register for the third testevent.
During each test event, the current performance and remaining research areas of hardware and software brought by participants can be tested against other market products in an easy to enter environment. The aim is to reach an official certification for interoperable FEIDs and HEMS by the end of 2026 and an attractive offer of interoperable devices in shops by mid 2027.
We offer tailor made matchmaking for optimal test conditions in each test slot, with three test slots per day and interactive, informative and fun intermezzo’s.
You can see a video register of the last event here:
The run through of each test slot will be this:
- Setup and connectivity – Exchange endpoint details with other participants, configure device addresses, and verify network reachability. Ensure both HEMS and device are on the same subnet with mDNS/multicast traffic allowed.
- Pairing and capability exchange – Establish the protocol-specific connection and complete the handshake. Verify the HEMS correctly identifies the device type, supported use cases, and power constraints.
- Telemetry baseline – Where the protocol supports it, confirm that live measurements are flowing from device to HEMS before issuing any control commands. For S2 and Matter this is a requirement in the residential flexibility project. For EEBUS, telemetry (via the MPC use case) is not (yet) required for participation, but if your device and HEMS both support it, please test it as part of this step.
- Use case execution – Run each applicable use case in sequence (see Use Cases). Between use cases, return the device to an uncontrolled state.
- Failsafe verification (optional) – Deliberately interrupt the HEMS connection and observe whether the device autonomously enters its configured failsafe state within the expected timeout.
- Wrap-up – Debrief, document observed gaps, and note any open interoperability questions.
For whom?
If you’re a manufacturer of HEMS or FEID(s), you’re welcome to register. For new products, we focus exclusively on the protocols EEbus, Matter, OCPP, S2 and OpenADR. Legacy FEIDs operating on Modbus can also be tested, since we are developing a Modbus converter that translates Modbus into S2, with further improvements to include EEbus and Matter in progress.
Interested?
