Leneda just launched their website but the API has existed for a while. I cant use the P1 port readers because the meter is in the basement and has no network connectivity. It doesnt look like there are any generic regional HACS/official integrations for BENELUX providers so something would have to be developed. I reached out to the dev and they responded with the following:
Currently, there are no plans for a direct integration of Lenede into other systems.
I see that there are nearly 500 users of HA in Luxemburg. Any interest to collaborate on an integration? #luxembourg#creos#sĂĽdstrom
I’m one of the HA users in Luxembourg.
I had a look at the API, and it is rather straightforward to use.
But, as far as I could see, Leneda only provides data up to the previous calendar day.
As I already have real-time access to consumption data via my PV installation, that makes Leneda rather useless to me.
The RESTful integration should still allow you to put something together. When I have a spare moment, I’ll give it a try and post a sample yaml here.
But, as I wrote, I’m not really much use to this integration.
I would be very interested in a YAML sample to integrate the Leneda API into Home Assistant.
Use case: Reading consumption statistics from an energy community (AC1) so that I can showcase the consumption of other members in my energy community.
May I ask @fedus, if the leneda integration will correct the time of measurements, or just record them with one hour delay? If homeassistant is down for a couple of hours, the data of those two hours will still be fetched, or will just be aggregated in the last hour?
I think both things can currently be done, although I am not aware of any “correct” way.
So, as it stands the integration will provide 2 things per metering point (and selected measurement value):
a sensor showing the aggregated data for the current year (like a running total of your electricity consumption or production for example)
a statistics object that contains the aggregated hourly data
Both get updated as soon as the Leneda API provides data, but both lag behind by 1 day. Meaning that the sensor shows the current running total from the 1st January of the current year up until D-1. The statistics object will fetch historical data for the whole past year on first run and then update to include data until D-1 as well. The statistics objects take the data as-is from the Leneda API, meaning that no transformation is done locally.
I hope this answers your question, if not I am happy to provide more details.
As far as the development is going, everything is still on its way, but the review process takes a long time.
That seems great, thank you for the detailed answer @fedus . I am aware that the process to make an integration official is quite slow, I hope it gets done eventually.
I only have one doubt regarding the statistics object. If I understand correctly, that’s the one that should be used in the energy dashboard, right? And on that one, the measurements are registered with the correct timestamp, and not the 1 day delay? My question comes from the need to align the measurement provided by leneda with energy measurements coming from other sensors I have locally.
Yes, you are correct, the statistics object should be used for the energy dashboard.
The measurements will have the correct timestamp, ie the timestamps will be just like they are recorded by Leneda itself. One consequence of this is that the energy dashboard will be empty for the current day, but will have data if you skip to the previous day.
In the meantime, the consumption recorded on the day of 16th August 2025 was 13.951 kwh on Leneda, but it was registered into Home Assistant for 1th August 2025 between 4AM to 5AM. Not sure if this was intended or a side effect of Home Assistant recorder setup.
