Hi everyone 
I’m very happy to release Gladys Assistant 4.66 today, with the new « energy monitoring » integration, which lets you track your electricity consumption precisely!
I talk about it here:
A huge thanks to @Terdious for funding this development.
And this is only the beginning of the specification we validated together — a whole section dedicated to electricity production is coming soon to Gladys 
Thanks @Terdious and @pierre-gilles
Cool
Thanks!
No need to create a feature that does the sum, you can display multiple features in the « Energy consumption » chart, so in my opinion keep peak hours and off-peak hours separate
However, indeed, if your supplier bills you for (consumption - injection), then yes you need to create an « index » feature with the total billed.
You will also need to create 2 features per index for the « 30-minute consumption in kWh » and « 30-minute cost » in kWh, but it’s detailed in the documentation tutorial, which I strongly recommend following
Je m’attendais à une réponse du style “c’est dans la doc”. Je me suis dit que c’est ce que j’aurais répondu à mes collègues 
C’est parce que j’ai voulu hiérarchiser et je ne vois pas comment faire pour placer un congélateur. HP ou HC ?
Eh oui, par ici, pas de Enedis, pas de Linky, pas d’EDF. Raison pour laquelle je pensais faire un index total… Mais je vais d’abord tout lire et explorer 
It’s all in the documentation, indeed 
The logic is that you need to have a device « Meter » at the root that carries the energy contract you define in the « Energy rates » tab.
Then, all the « child » devices of this meter inherit the contract and Gladys calculates consumption using the contract’s prices.
In your somewhat special case, I recommend following the tutorial and letting Gladys automatically create a meter when configuring your rates, then putting all your devices (including your peak hours / off-peak hours) under that meter.
@pierre-gilles
in my case where I retrieve the 6 Tempo indexes via MQTT (6 indexes in a device named Téléinformation), what exactly should I create?
According to the docs, I don’t know if I should have a single or 6 different features (by color/period) of Capteur d’énergie / Index in my device Téléinformation:
4. With a custom MQTT device
If you have an exotic meter or devices that return consumption values in kWh, you can integrate them with Gladys Assistant using the MQTT integration.
For that, you must have devices in the MQTT integration with 3 features:
1. A « Energy sensor / Index » feature, which corresponds to the index of your device in kWh.
2. An « Energy sensor / 30-minute consumption » feature, which corresponds to your device’s consumption in kWh over the last 30 minutes.
3. An « Energy sensor / 30-minute cost » feature, which corresponds to your device’s cost in euros or dollars over the last 30 minutes.The first feature must be populated in MQTT by you. The other two will be derived from the first and calculated automatically by Gladys.
Thanks for the update
However, my Lixee doesn’t show up among the devices in the energy monitoring — Enedis, on the other hand, appears without any problem.
I did update my devices
Great work, another nice integration has arrived.
I’m running some tests; I have the impression that my Lixee TIC is not being correctly detected by the integration.
While I’m writing, @prohand seems to be reporting the same problem
From what I see in your code, you need to have an ENERGY_SENSOR feature (INDEX or ENERGY) or an ENERGY SWITCH for it to work. Yet here are the only features associated with my TIC in the database
My smart plugs, on the other hand, are correctly recognized (I can update them with the two features THIRTY_MINUTES_CONSUMPTION/THIRTY_MINUTES_CONSUMPTION_COST).
Do you have any idea what I might have missed either in the TIC configuration or in this new integration?
It’s a Lixee TIC v1, and the TIC is in standard mode (maybe you only support the historical mode?).
Thanks
For your information, I have the TIC v2 in standard mode 
In your case, since you have 6 indexes, you should have 6 « 30-minute consumptions » (1 per index), and 6 « 30-minute costs »
Then, in the hierarchical view in « Energy monitoring », you should organize it like this:
1. index
2. 30-minute consumption
3. 30-minute cost
I didn’t add automatic creation in the MQTT integration because I wasn’t really sure how many people would be affected; if it’s much requested, I could create a button to automatically create the features
Ah, indeed, I didn’t include those features, but I can add them!
From the list of features you gave me, which ones are kWh indexes?
I only need the « useful » features that will be used to calculate the 30-minute consumption and 30-minute cost
For my part I’m reporting this with my lixee :
So it would be EAST in my case
Small UX remark, I’m in the process of recreating my different subscriptions for the historical calculation but it’s hard to find your way if you have several base contracts for example :
I think it would be nice to be able to rename an energy tariff to give a name to the contract (for example the provider’s name)
Ok I’ll add it!
Indeed, good idea
I think what interests you for the integration are the indexes EASF01 to EASF10, there are 10 of them to cover all tariff periods.
The total sum of all these indexes is reported in EAST
Ok, I’ll add that as well then!
Thanks
Another idea to improve the UX would be to indicate whether it’s peak or off-peak hours, for example here:
Because we have to click to see whether it’s the off-peak or peak rate 
Other questions:
If I modify the date of imported rates and then re-import the Tempo rates, for example, what happens? Are my modified dates overwritten or does it create new rates?
I saw that you can select a subscription:
Is it not being taken into account at the moment?
Is there no point in creating it for now?
Thanks
so I do have indexes (6 tempo + 1 which is EAST) with custom topic :
How do I create items 2 and 3? What should their exact names be?
Hmmm, I think I understand. Actually I would need to create 6x2 energy/cost features and then associate their parent (6x3 levels) up to the main meter.
Uh I’d be very interested in a button for automatic creation because I’d also have to do it for my wallbox and maybe other elements that I get via custom topics.
And cherry on top for later: Z-Wave
If we add a title to each price, could the title include whether it’s peak or off-peak?
Currently, it will create new tariffs.
But in the long run, I’d like to create a system that automatically updates tariffs. It’s not simple, because you have to handle the existing data, notably people who had multiple contracts ^^
For now it’s indeed not taken into account!
Everything is described in the documentation
Ok I’ll take a look!
Yes, I’ll have to check whether it’s not too complicated to add!
[quote=« pierre-gilles, post:19, topic:9854 »]
[quote="mutmut
