Smart-Meter CII Interoperability with Smart-Home Systems

Connect ten common smart meters to a data broker, establish a common information schema and develop apps and visualizations

#17

⛶  Fullscreen ↓  Download
Demo

Challenge Presentation

In last year's CII -challenge, we have demonstrated how 4 Swiss DSO smart-meter (SM) deliver their energy data through their local Customer Information Interface (CII, like M-BUS oder DSMR) by using specific IoT-Adapters that will publish the data towards a common interoperability layer, the MQTT-broker.

This year, we shall extend the range of SM to include further SM like Ensor, Kamstrup, Sagemcom and explore others. We also intend to deploy some new SM-powered IoT-Adapters to allow DSO-customers easy and reasonably inexpensive local access to their energy data. And we shall report on the issues encountered with MBUS-HDLC-DLMS-COSEM, DSMR and other types of CII.

The second part of the challenge shall investigate and show how the many EMS or smart-home systems (SHS like Loxone, KNX, Homeassistant, openHAB, ioBroker, and more) may obtain the energy-data by subscribing to the MQTT-broker.

We also intend to explore how to integrate the hourly next-day price forecast from ENTSO-E over MQTT. EMS, SHS or even the IoT-Adapters may display this information or take sensible load-shifting decisions to flatten their power use.

Because of much higher energy prices, PV system operatores may lose their previous economic incentive to use as much energy as possible from their own production for their local loads. Instead, local loads may be shifted to times of relativly lower energy prices which also nicely indicate less expected load.

🧑🏼‍🏫 Gantrisch Energie AG and Partner

Event finish

People are heading home. Some of them will pick it up tomorrow.

2 years ago ~ derrickoswald

Edited (version 41)

2 years ago ~ derrickoswald

Edited (version 39)

2 years ago ~ derrickoswald

Edited (version 37)

2 years ago ~ derrickoswald

Murmurs of technical discussions. Serious concentration.

2 years ago ~ derrickoswald

Edited (version 33)

2 years ago ~ derrickoswald

Edited (version 31)

2 years ago ~ derrickoswald

Just the clicking of keys and mice...

2 years ago ~ derrickoswald

There was a long wide-ranging discussion about the achievable goal for the Hackdays. The general gist was to establish a middleware layer handling each meter's unique format to "re-publish" the data in a common format, but there was no agreement yet on what that format would be.

2 years ago ~ derrickoswald

Edited (version 25)

2 years ago ~ derrickoswald

Currently setting up smart meters with loads, the MQTT broker; publisher; subscriber etc., Slack sign-in, documentation review and all the other tasks that starting up a Hackdays involve.

2 years ago ~ derrickoswald

Joined the team

2 years ago ~ derrickoswald

Start

Edited (version 16)

2 years ago ~ GEAG

Edited (version 14)

2 years ago ~ GEAG

Edited (version 12)

2 years ago ~ GEAG

Edited (version 10)

2 years ago ~ darienne_hunziker

Joined the team

2 years ago ~ GEAG

Edited (version 7)

2 years ago ~ darienne_hunziker

Edited (version 5)

2 years ago ~ darienne_hunziker

Edited (version 3)

2 years ago ~ darienne_hunziker

Challenge shared
Tap here to review.

2 years ago ~ darienne_hunziker
 
All attendees, sponsors, partners, volunteers and staff at our hackathon are required to agree with the Hack Code of Conduct. Organisers will enforce this code throughout the event. We expect cooperation from all participants to ensure a safe environment for everybody.

Creative Commons LicenceThe contents of this website, unless otherwise stated, are licensed under a Creative Commons Attribution 4.0 International License.