I mostly agree, it doesn’t make sense to apply the subscription fee to levels above 0. In my case, where I detail each electrical panel to get my actual consumption, the subscription is added for each meter, which, in this instance, is not correct.
Oops, good catch 
I think I’ll just add an option that can be enabled or disabled in the interface because Gladys can’t know whether it should be activated or not
1 Like
My proposal:
2 Likes
Perfect 
Disabling it here won’t affect anything else
Otherwise I would have disabled it directly in the integration
No, it’s just on the widget! I rolled out a release, so I’ll be less available over the next few days — this is my last shot 
1 Like
Ok, perfect then 
1 Like
Gladys Assistant v4.66.8 is available with this fix!
Yes, it’s a widget setting, in the dashboard configuration. You only need to check it once during configuration.
2 Likes
Done here:
@pierre-gilles, after several attempts I went with the exact same approach you used for the MQTT integration. So it’s valid for all integrations that have access to modifying features.
Indeed, I looked into automating it the way zigbee2mqtt does, but in the end it didn’t seem appropriate because Tasmota devices create 3 energy metrics when a device is created:
- Total Energy
- Energy today
- Energy yesterday
They are not distinguished by type and therefore the last two are not worth exposing as consumption / cost.
So I decided that we should always create them manually. Is it worth creating a helper when adding a new device that contains at least one Energy feature to prompt creating it manually?
1 Like
Following this development I thought of one thing:
- I will have 8 outlets to update for their consumption / cost once integrated…
- I’ll be too lazy to wait 24 hours to re-run the cost calculations for all devices
- What do you think (do you think) about modifying the Energy Monitoring Settings view
-
To put only a single global calculation button « Calculate consumption and cost of all devices from the beginning »? Because ultimately, we always do both… It doesn’t make sense to do consumption only, and if we decide to run the cost calculation then consumption must necessarily be done as well, right?
-
Add a global recalculation button with a field « Since » and a date selector. Indeed, for those who, like me, have the energy tariff created manually, when the price changes, if I’m late creating the new prices, a shift will occur and we’ll have to rerun everything from the start. If we can recalculate from a date, that’s faster and will relieve the CPU and RAM, which may thank us ^^
-
Add a field for the action for only a list of devices. Similar to the graphs, a multi-select list would allow selecting devices to recalculate from the beginning (for any addition of new functionality) and therefore would not affect other consumption / cost already calculated.
I’m happy to look into taking care of it if that’s relevant for everyone? (It is for me ^^)
1 Like
Hello
I just configured the new energy management (‘énergie) (Enedis and llixee Tic with a Linky in standard TIC mode) and I notice inconsistencies between the consumption values on the EDF & Enedis sites and Gladys.
On the left-hand graph the values match the Enedis values.
On the other graphs (30-minute consumption) I notice that the values for April and March do not correspond to the values shown on the Enedis site.
The annual values in euros and kWh are not correct for 2025, 2024 and 2023.
I restarted the meter synchronization with Gladys but that changes nothing.
On the Enedis graph below, before the end of April 2025 I noticed that there is only one value every two days, but the annual values are higher than my actual consumption!!
For the configuration of off-peak and peak hours I have two periods:
one from 21:00 to 23:00 and another from 1:00 to 7:00
The bar corresponding to 1:00 should be entirely off-peak.
The bar corresponding to 7:00 should be peak and not off-peak.
The bar corresponding to 21:00 should be entirely off-peak.
The bar corresponding to 23:00 should be peak and not off-peak.
But maybe I’m mistaken.
Comparison with the EDF graph
Last topic: I use PZEM-004T & ESP32 via TASMOTA as energy meters
For my heat pump, my hot water tank and my sump pump
Today it is not possible to integrate them into the Energy management — how can I add the 30-minute consumption variables and the 30-minute cost?
Proposal for points 1) and 3) mentioned above :
Here we only recalculate the 2 features selected from the start.
What do you think?
The big advantage: I was able to recreate a new feature that I had forgotten, select it and re-run a recalculation job only for that one
It was positioned after the others and is therefore pending:
3 Likes
Hi @froch,
Indeed, strange what’s happening with your HP/HC (peak/off-peak hours) apparently.
I’ll only reply to the last part
Indeed, that was exactly the subject of my post just above: https://community.gladysassistant.com/t
2 Likes
Hi @Terdious,
I’m replying to your very relevant suggestions:
- merge recalculation of consumption AND cost: YES because we’ll do both anyway UNLESS we don’t yet have the contract from our energy supplier. And NO because in my case (and for Alsatians), we can take EDF for now but the subscription at ES is different (more expensive) than EDF. So we’ll recalculate costs only, not consumptions
→ Have 3 buttons: Recalculate consumption, recalculate cost, recalculate consumption + cost - Start date: YES and I would also add an end date. The goal, in my view for the start of this great development, is to run tests and validate over one month, six months, one year, that the units (my current problem) and the costs match within a short calculation time and not in 12h + 2h (still in my case) before getting… shaky results
- Here I’m 100% FOR it! At my place all Z2M devices that are « consumers » have a consumption of 30 and a cost of 30, both correct. My MQTT virtual devices part for my Tempo indexes isn’t quite there yet and if I can just test for a single one, it will allow me to go much faster in finding what’s wrong. Then I have Z-Wave devices with energy consumption (not yet developed for tracking, same for Tasmota, and what about Matter?) and running calculations only on those would be a big plus.
I’ll toss out an idea: the ability to see information indicating the devices that have already had the calculations done (consumption/cost) and be able to choose the new ones and/or some older ones to recalculate.
1 Like
Hi @mutmut
Very relevant and indeed, I was just thinking the same — cost calculation is much faster I think and this can absolutely be a scenario (adding contracts gradually and rerunning everything will be pretty quick!! ^^
Not wrong ^^ It’s no harm in that, and your example for tests seems pertinent to me
Exactly the goal indeed. We’ll have to see with Z-Wave and Matter, but in itself the dev for Tasmota could easily be opened to those integrations. You just need to open the edit page if that’s not already done!
I’ll let @pierre-gilles look at that part because I see the need, but technically I wouldn’t know how to do that off the top of my head… ^^
I think I’m not wrong in saying that it makes both @pierre-gilles and me very happy to have such enthusiasm for this integration. I admit that for me it was something I had been waiting for a long time but knew would be a mountain to climb!! And moreover it’s rental income for me!!
2 Likes
I fully endorse the proposals you made @Terdious, they seem very relevant indeed.
Regarding @mutmut’s proposal on point 1, I understand the usefulness of recalculating only the costs, in addition to the full consumption+cost calculation. But I don’t really see in which case one would want to recalculate only the consumption without also recalculating the costs?
1 Like
For my part, I must have a unit problem with my Tempo indexes. They are in Wh but the calculation doesn’t seem right in the end. I could thus just have the consumption recalculated and already check if those values are correct before starting the cost calculation.
But on reflection, it wouldn’t take much more time to recalculate consumption+cost — only if we can select a single device independently.
2 Likes
Ok, so a simplification following the feedback :
So, given the impact there may be for some time, I added a confirmation button in case we want to recalculate everything :
I’ll continue with point 2) on the start/end dates
2 Likes
In your screenshot, there’s Confirmer le recalcul complet du coût; is there the same for consumption+cost? on all devices or only the selected ones?
Personally I see it by default all the time and in every situation, that way we don’t have to wonder.
I see that even when @
2 Likes
Indeed, for the moment I have only implemented it when no functionality is selected (but it is implemented for consumption+cost and for cost-only) because it’s the heaviest job and cannot be manually interrupted except by restarting Gladys => This is important because you should know that currently if Gladys restarts, the job does not resume at startup (so you’ll have to start all over again).
I considered that once you’ve selected a functionality, you’re already in control of what you’re doing and in that case the alert becomes « Too much ». Especially since with this dev, you can launch a first functionality whose consumption+cost will be recalculated and immediately afterwards (or 10 minutes later) launch one or several others even if the first isn’t finished — it will just add them to a waiting queue.
For example, I launched a consumption+cost calculation on the Hay purifier (Purificateur de foin) and then added a cost-only recalculation on the consumption of the heat pump (PAC). Everything goes into waiting (thanks @pierre-gilles ^^ I didn’t have to do anything for that ^^) and then all normal calculations over time every 30 minutes get added to the queue so nothing is lost (well, as long as Gladys doesn’t restart I think) :
I admit that after the PR on Tasmota, it made me want to work on this because I’m really too lazy to run the recalculation on everything, with the risks that come with it (as I said before, my recalculation takes about 30 hours; if Gladys stops during that, it can delay the use of the full feature for a long time, whereas it works very well for all devices currently in place ^^)
And for my part, like some others, I launched the primary calculation before having saved all my contracts, so I’ll need to rerun the costs only for the periods before 2025 ^^
4 Likes
Great for the recalculation and the info in the tasks!
And if you happen to have a Docker image to test and validate on another environment, I’m interested 
1 Like