WEBVTT

00:00.000 --> 00:11.960
Okay, hello everyone, so my name is Benoellicadrono, and I'm working for the main French

00:11.960 --> 00:15.280
DSO, which is called Enedis.

00:15.280 --> 00:23.440
So we are in charge of everything related to low and medium voltage grid in France.

00:23.440 --> 00:31.600
And today presentation is how we make and we use open source in public utilities.

00:31.600 --> 00:36.600
And we did it with the community.

00:36.600 --> 00:41.840
So first slide is about what is Enedis.

00:41.840 --> 00:51.200
Enedis is quite a big company, as you can see we have 16.4 billion euros of volume.

00:51.280 --> 00:59.600
41,000 people, 38 million clients, 1.4 million of kilometers of poll line, and lots of

00:59.600 --> 01:05.520
new stuff like when you're born in Nigeria, electric vehicles, image charging, and everything.

01:05.520 --> 01:12.520
And I think our partners quite particular, because it's not business, a company, as you

01:12.520 --> 01:19.280
said, we are ULTT, so we are state company, and we only do public service.

01:19.280 --> 01:26.400
So our aim is not to make money, is to give a service to people.

01:26.400 --> 01:32.920
And I'm going to introduce you to our smart metal, because it's a subject of today,

01:32.920 --> 01:37.800
which is open source with our smart metal, and our smart metal is this one.

01:37.800 --> 01:43.040
It's calling key, it's a little green, a smart metal.

01:43.040 --> 01:49.160
Smart metal, it's one smart metal, I think I need to go a bit far from simply.

01:49.160 --> 01:55.600
It's one meter by two version, the first version is a single phase metal, and the second

01:55.600 --> 02:03.440
one is a free phase, free phase is a metal, and we did a big rollout, so we installed all

02:03.440 --> 02:12.560
the smart metal between 2015 and 2021, and it was quite a huge project, because we did a

02:12.560 --> 02:20.240
rollout of more than 37 million smarter, Mickey matters, and also with a quite a big budget

02:20.240 --> 02:27.720
four million salesman, and for now it's almost finished, so all our matters are on the

02:27.720 --> 02:35.120
field, and it works pretty well, because we have a nice success rate every day, we have

02:35.360 --> 02:45.800
98% of, yeah, perfect, it's for the camera, I guess, 98% and I'm totally so it's

02:45.800 --> 02:51.720
going to be done, I always take it, 98 generation success rate, so we get the data from

02:51.720 --> 03:02.200
the smart metal every day, and I'm going to explain you what this linking metal does,

03:02.200 --> 03:07.560
on the linking metal we have two interfaces, the first one is quite a simple one, it's

03:07.560 --> 03:16.280
a dry contact, it's a switch, on off switch, and in France we have our hot water tank connected

03:16.280 --> 03:22.600
to this switch, and what it does is when the price of electricity is very low, you get

03:22.600 --> 03:28.880
on a hit, and when it's high, you're going to stop hitting your water, and what is nice

03:28.960 --> 03:36.680
is because hot water tank is kind of cheap battery, you drain energy when the grid needs

03:36.680 --> 03:42.680
it, and you release it, yeah, when you need a shower or anything else, and another interface

03:42.680 --> 03:49.360
is a date and face, that's an interface, I'm going to talk a lot in this presentation,

03:49.360 --> 03:54.480
and we call it the tick interface, why so tick and face is because it's a name of the

03:54.560 --> 03:59.840
protocol, the tick protocol, and it's going to give you all the data you need from your

03:59.840 --> 04:05.840
smart metal, so example you're going to get a tariff padded, so you're going to tell you

04:05.840 --> 04:11.280
if you pay a high price or low price of electricity at the moment, you are also also have also

04:11.280 --> 04:16.560
instantly new power, max power available, energy production if you have some solar panel

04:16.640 --> 04:27.520
and you move a lot of different data, and with this smart metal, we do quite great stuff,

04:27.520 --> 04:36.400
I will say, in France for the grid, and that's a slide about most of the use cases we have

04:36.400 --> 04:43.680
with this link meter, the first one is of course dynamic time of use, so the link meter and the

04:43.680 --> 04:50.240
tick interface is going to say how much you pay, so you are able to drain energy when slow price,

04:51.440 --> 04:58.960
we did also something nice, I think it was four years ago when the Ukrainian war started,

04:58.960 --> 05:07.040
you know the price of electricity was to the sky, and air tea is there here, ask us to do a black

05:07.040 --> 05:14.240
out prevention, and what we did is when you get to contract, electricity energy contract in France,

05:14.800 --> 05:23.520
you ask for a contracted power, so you will tell max power, I need is for example six kva of 3kva,

05:23.520 --> 05:30.800
and what we did is for a very short time during the day, so it was two hours, you get less than

05:30.880 --> 05:38.160
your contracted power, so if you ask for six or nine, for two hours you will only get 3kva,

05:39.840 --> 05:47.600
other use case in energy management, so the temperature of your house will adjust depending

05:47.600 --> 05:54.160
of the time of the day and the price of electricity, and also use case is, I will say contracted

05:54.160 --> 06:02.000
power management, so for example you get 6kva contract contract, and you want an electric vehicles,

06:03.280 --> 06:11.600
the two solution, the first one is you get 9 or 12kva, and the second solution is you get the data

06:11.600 --> 06:17.360
from the smart meter, so you get in start in your power, you get your contracted power, and you

06:17.440 --> 06:24.080
going to start your electric charging vehicle only when you are available power, so for example,

06:24.080 --> 06:31.840
if you have something in the heat oven, the charging station will stop, and the charging of your

06:31.840 --> 06:40.240
vehicle will only start after, and last use case in energy display, so you get an up or you get

06:41.200 --> 06:46.960
display and display going to show you all the data you need, so that's a nice part of

06:46.960 --> 06:53.280
flinky, but we are not here to talk about the nice part, the part we are talking about is what does

06:53.280 --> 07:03.520
work, and what does work is, after 10 years of years of our limcimeter, we are not so quite happy

07:03.520 --> 07:12.960
about, I will say, the use of the tick interface, it's not so, so not so many people use it,

07:12.960 --> 07:19.280
and we were thought about why not people use this tick interface, it's so amazing, you have so many

07:19.280 --> 07:25.600
data you can do, so many use case, but at the end not so many people know about it and use it,

07:27.200 --> 07:36.640
I will give you a quick tutorial on how you can get your tick data, and it's quite simple,

07:36.720 --> 07:42.240
so you get a limcimeter, you get a smart domingo, a small domingo, you open a limcimeter,

07:42.960 --> 07:50.320
you plug in your smart domingo and then success, you can broadcast all your data using a protocol

07:50.320 --> 07:57.760
like Wi-Fi, Ziggy, or much or anything else, so if it's so simple why do people don't do it,

07:58.640 --> 08:09.680
and the quick answer is because of the domingo, the domingo is a problem, so another is this

08:09.680 --> 08:18.000
about the problem on this domingo, the first problem we saw is there is no official domingo product,

08:18.960 --> 08:25.920
so if there is no official product domingo it's not market, so a niche market say high

08:25.920 --> 08:32.640
selling price, but low pollution cost, so don't go, I think it costs to make maybe five euros,

08:32.640 --> 08:38.320
probably more or less if you do more, but if you want to buy it on Amazon or anything else,

08:38.320 --> 08:46.080
you will pay it 60 euros, so it's quite high price just for a domingo, so we can tell but

08:46.080 --> 08:51.120
why and it doesn't sell the domingo, it's because we are not allowed to sell the domingo,

08:51.120 --> 08:58.080
we are a UTT, so public service, so only thing we can sell is one of the state ask us to do it,

08:58.080 --> 09:03.680
and further the goal, so don't go, it doesn't, it didn't ask us to do it, and this is the first

09:03.680 --> 09:10.240
solution to our problem, we are not allowed to sell domingo, but we are allowed to share on open

09:10.240 --> 09:17.520
source on no-lage and we know how to make it, and this is also the one source is also the

09:17.520 --> 09:21.120
problem to the first domingo, there is no official product, but we can make another

09:21.120 --> 09:30.720
and the official open source design out of it, and another problem is the tick interface is quite

09:30.720 --> 09:38.400
difficult to read, it's an AM signal on a 50-year scale, so it may sound simple but we are

09:38.400 --> 09:46.480
very specific constraints on a specification, and all the electronic engineers I saw always

09:46.480 --> 09:56.640
struggle to demodulate, I could explain more, it's quite simple, but the thing is a quick answer

09:56.640 --> 10:06.320
is because we have a very specific requirement as a UTT, is we want the domingo to read the signal

10:06.320 --> 10:14.720
even if the signal is below 1.2 volts, and most people when they make it a normal, they use

10:15.680 --> 10:24.720
piece of hardware called unoptocupular, and this kind of hardware has breakdown, and so it will only

10:24.720 --> 10:33.920
works if the attention is 1.5 volts, and the question is why do we ask 1.2 volts is because on

10:33.920 --> 10:42.960
specific, very specific situation, you will get your piece of equipment very far from your

10:43.040 --> 10:50.000
link meter, so you will get cables between your link meter and the piece of equipment, so it will

10:50.000 --> 10:59.200
happen a voltage drop, and the signal will go below 1.2 volts, and the thing is this specific case

10:59.200 --> 11:04.080
use case case, when you get to the piece of equipment very far from your meter, is only for one,

11:04.080 --> 11:12.480
I will say 0.1% of the clients, and when you are a business company, you don't care about 0.1

11:12.560 --> 11:17.280
percent of the clients, you want to sell products, so you don't care, and so you use unoptocupular

11:17.280 --> 11:25.360
because it's very cheap, then when you are public sales, you care about 0.1% of the clients,

11:25.360 --> 11:33.120
you need to make a product for everyone, so if there is only one client that has a signal voltage

11:33.120 --> 11:40.000
of our sales 0.8 volts, you need to create a product for them, and as a reason why on your market,

11:40.000 --> 11:49.120
you will not find good products, good dongles, but reading a signal of 1.2 volts is quite easy,

11:49.120 --> 11:53.200
if you don't use unoptocupular, but not using this piece of hardware is quite difficult when you are

11:53.200 --> 12:02.080
an electronic engineer, and so I will finish my piece, they are very high energy cost, and

12:02.080 --> 12:10.480
the dongles, most of them, have this design flow using unoptocupular, and again, open source is

12:10.480 --> 12:17.200
a solution, if you share a good design, open source design, they will share the energy cost

12:17.200 --> 12:23.760
between them, and it will help them make this kind of product for the 0.1% of the clients,

12:24.240 --> 12:34.160
and the last problem is there is no smart dongle radio protocol standardized, so everyone

12:34.160 --> 12:41.600
using is unoptocuped, so if you buy the dongle from a manufacturer A, I will say, and you buy

12:41.600 --> 12:48.000
a piece of equipment for a manufacturer B, they won't work together, you have to always buy the dongle

12:48.080 --> 12:57.520
from the same manufacturer, and again, solution, open source, because luckily most of the protocol

12:58.320 --> 13:02.320
you will find in smart home, so I think about the G-Matter e-Bus, our open source,

13:04.560 --> 13:13.200
so we saw that open source is a great solution to our problems, but the question is how do we make

13:13.760 --> 13:24.640
open source? The big part is the hardware part, so we went on GitHub, and we looked for a smart

13:24.640 --> 13:30.560
dongle design, and there are a lot of them, so you have to learn how to write, how to write,

13:30.560 --> 13:39.440
how to write, how to write, all open source, and we found on those design, the same design flow,

13:39.440 --> 13:46.800
so the particular, and when we went on Amazon, we bought some dongles, we found the design to be the same

13:46.800 --> 13:54.560
design, the open source design, so if we want to improve the design, the solution is simple,

13:55.680 --> 14:03.200
is we need to be part of the open source community, and by doing this we will improve all design,

14:03.280 --> 14:08.720
manufacture the one you can buy on Amazon, the one you can find on GitHub, and this is a picture,

14:08.720 --> 14:17.120
so we call all the makers, we bought them to our lab in Paris, and we started to talk with them

14:17.120 --> 14:24.080
to see how we can improve together as a design. The second part is a software part,

14:25.280 --> 14:32.560
this one is hard work, but much simple, the way we did it is we joined the CSA,

14:32.560 --> 14:40.000
so that's a association that is working on Matron Ziggy, and we created a new device type

14:40.000 --> 14:49.200
specific to our method for smart medical, smart dongle, we call EOL, and now if you want to create

14:49.200 --> 14:54.960
a smart dongle using Ziggy, it's quite easy because everything is available on open source

14:54.960 --> 15:03.360
for Matron Ziggy, and we also did something with Ebus, Ebus is a protocol, a German protocol

15:03.360 --> 15:11.600
for energy management at home, and we use an open source stack, we'll modify it so it can

15:11.600 --> 15:17.600
work with our smart metal linking, and now it's quite easy if you buy an Ebus

15:18.560 --> 15:29.440
EV Charlie Station to plug it with a smart metal linking. Finally, this is our open source

15:29.440 --> 15:40.560
roadmap, so in September 2025, we'll use our GitHub to software, the first one is Tick for Ebus,

15:40.720 --> 15:51.440
so yeah, it's a help you charging your EV with your Tick data, second one is a Tick to Web

15:51.440 --> 16:01.600
socket, the third one on October 2025 was the mapping Tick to ZB, we're list, on March 2026

16:02.160 --> 16:09.120
we will release the data, data frame, because we realized we have had a lot of different data

16:09.840 --> 16:14.960
in our lab, so that we didn't share, so it would be just sharing the documentation data,

16:14.960 --> 16:24.160
if we could help people and the modulating Tick interface. In May 2026, we will release

16:24.160 --> 16:31.360
the smart metal, don't go out of our design, and at the end of 2026, or maybe at the beginning

16:31.360 --> 16:43.200
of 2026, we will release the Tick to matter a mapping, and that's the last slide,

16:44.640 --> 16:51.440
the question is what is next, this use case is quite a small use case for specific problem,

16:51.440 --> 16:58.960
the Tick interface, but we have so many different problems, I think we can solve together,

16:59.040 --> 17:06.000
at the end it is all as a European DSL, and when what we see is, we have a lot of thousands of

17:06.000 --> 17:16.560
DSL in Europe, they probably working together at standardization, I think, I ECE or SNLK,

17:16.560 --> 17:23.760
but not a lot of them are working together on open source to create a common solution, and the

17:23.760 --> 17:29.840
thing is, we have all the same problem, we have smart metal, we have grids, we have solar panel,

17:29.840 --> 17:35.920
we have electric vehicles, all we have the same problem, but everyone is solving the problem on

17:35.920 --> 17:43.680
then safe, and if we can work together on a person's solution, I think it's a key to bring

17:43.680 --> 17:50.720
a new technology, open technology in Europe for the grid on the DSL, and that's the question,

17:50.800 --> 17:54.960
where do we start? That's it for me, thank you very much for your attention.

18:01.760 --> 18:03.760
Do you have any question? Yeah.

18:13.120 --> 18:20.080
Yeah, we don't know, because there is no way of knowing it, the Tick protocol is always about casting,

18:20.080 --> 18:27.040
so you don't need to call entities to activate it, so how we know is because we talk a lot with

18:27.040 --> 18:33.280
a manufacturer, a manufacturer of setting don't go, so we know how much they sell, and it's not

18:33.280 --> 18:39.760
solid, or I think it's maybe every year, the sell 10,000 don't go, but when we start in the

18:39.760 --> 18:46.320
Lincoln Protocol, the Lincoln Program, we want everyone to analyze their smart metal data,

18:46.320 --> 18:52.560
because it's a key when you want to do energy management at home, but it didn't work as much as we

18:52.560 --> 18:56.400
plan, so people are using it, but yeah, they could do it more.

18:58.800 --> 19:03.200
Do you plan to get connected to a mass system community, for instance, or sort of to a development

19:03.200 --> 19:14.400
because they are developed? Yeah. Yeah. Yeah, you can already find, find where you get the question?

19:14.480 --> 19:19.760
Yeah, as the question is, do we plan to do open source stuff on our mass systems? Our genome,

19:19.760 --> 19:28.560
I guess, with the Lincoln Meta, we could, but we think it was not our main goal because you can

19:28.560 --> 19:33.920
already find a lot of good open source software for the Lincoln Meta on our mass systems.

19:34.560 --> 19:38.960
So we might one day, but for now, I don't know if you did it, I have your accent, so I guess

19:38.960 --> 19:44.080
you are French and you have a little computer. Yeah, but it's quite, it's quite easy to find some software

19:44.080 --> 19:52.000
to do that already on GitHub. So we did open source only when we felt that the open source solution

19:52.000 --> 20:00.080
was not good enough. Yeah, it's just for you, it's always a question, you know.

20:00.640 --> 20:06.760
Yes, you're a quick question. Can you?

20:23.760 --> 20:29.760
You know, it's a real assistive hot water tank.

20:29.760 --> 20:47.760
So the question is, oh yeah, because you need to hear it, and the mic, okay. I guess it's now.

20:49.760 --> 20:56.760
The question is, what kind of, what's it, what's the time we use if it's a resistive of its heat pump?

20:56.760 --> 21:05.760
And the second question is, when the price of XT is low, and if this price is flexibility.

21:06.760 --> 21:10.760
So the first question is, we use resistive hot water tank.

21:11.760 --> 21:18.760
Maybe one day we will go on a heat pump, but for now it's quite expensive, it's cheaper to get hot water tank.

21:18.760 --> 21:26.760
And if you do it when the price of XT is low, as I said, it's like a battery. So during the night or, yeah, you have a low price, so it's perfect.

21:27.760 --> 21:31.760
And it's quite nice for the grid, for them and the response to have a discount of technology.

21:32.760 --> 21:39.760
And for the second question, yes, the price is low, not at the same time for everyone.

21:39.760 --> 21:44.760
So you have different type of energy construct.

21:45.760 --> 21:54.760
One of them is, it's like dynamic tariff, so 20 days a year, you would have a very high price.

21:55.760 --> 21:59.760
And you will know if you have high price the day before.

22:00.760 --> 22:05.760
So it's usually in during the winter, of course, because once you have the amount of response issue,

22:05.760 --> 22:07.760
but the rest of the time it will be the chip.

22:08.760 --> 22:17.760
And there is also a contract, the price is low only during the night and between during the mid of the day.

22:18.760 --> 22:27.760
And it's not the same for everyone, because imagine if you have low price starting at 9 for everyone, in your neighborhood,

22:27.760 --> 22:32.760
hey, we want to start electric vehicle starting station and hit water track at the same time.

22:33.760 --> 22:37.760
So you will have tension issue, voltage issue in the neighborhood.

22:38.760 --> 22:43.760
So we will change a bit, as the time will change a bit, depending on where you are in your neighborhood.

22:44.760 --> 22:52.760
And it's used also, as best used to this low before at the time.

22:52.760 --> 23:01.760
Now it's small and more with a solar production, so we change the low price to match the high production of solar panels.

23:05.760 --> 23:06.760
Yeah?

23:09.760 --> 23:10.760
Yeah, nice.

23:22.760 --> 23:29.760
The question is, from my knee key, the device, don't be over by the link and I didn't think that's wrong.

23:30.760 --> 23:33.760
So I've already confused something in the way on this.

23:34.760 --> 23:39.760
Is there a way to spy it or use the protocol checking on the borderline?

23:41.760 --> 23:49.760
Okay, yeah, the first question is, it didn't know you can open the link key and to answer this, not always.

23:50.760 --> 24:01.760
Yeah. In most cases, you can open it, but in some cases, for example, if you have some very old cables, paper cables or yeah.

24:02.760 --> 24:13.760
So when you get to the link key, they will, I don't know, I don't have the name in English, but they will, but something, you know, to avoid you open it.

24:13.760 --> 24:21.760
So not always, you have to check if you have a very small piece of green plastic on, yeah, you have the name in French, yeah.

24:22.760 --> 24:32.760
And the second question is, here is an incubator, but down the basement, and I guess you are a flat, it's up in the building.

24:32.760 --> 24:52.760
So how can I use the tick data? It's possible doing it using PLC. We are the solution, a long time ago, that you plug a single on the link key and you plug it on the main on the plug, electric plug, a classic electric plug.

24:52.760 --> 25:06.760
And then you plug a PLC receiver in your flat, and you could have the data, I guess. But we made it a long time ago, but nobody is sending it, there is no manufacturer doing it, making it.

25:07.760 --> 25:21.760
And other solution, you could try using the lower protocol, lower protocol, lower one, you could try. I don't know if it will work, depends of the building, but yeah, we, we made some time, it's quite great.

25:22.760 --> 25:24.760
Let's go through the walls.

25:26.760 --> 25:31.760
Time's up, sorry. And thank you very much.

