Yes, if the price can include whether it’s peak or off-peak that would be perfect ![]()
Yes, it’s not easy to manage the existing setup
Do you know when this will be taken into account regarding the subscription? I suppose there’s quite a bit of work to do ![]()
The name isn’t important, put whatever you want ![]()
I don’t have a date to give; for now I’ll focus on the existing feedback so that everyone can have an integration that works!
That’s it, I understood the concept of exotic devices ![]()
So I tested with my BBRHCJB by adding 1 30-min consumption and 1 30-min cost.
By the way, to add manually, just type 30 in the feature search:

![
Great if you were able to test!
Ah, that’s not normal — can you send me the logs? There might be an unhandled case.
Have you properly configured the unit for your index and your « 30-minute Consumption » in your MQTT features?
You need to specify whether it’s in Wh or in kWh — that allows Gladys to calculate correctly ![]()
No, Gladys only calculates the difference between the previous value and the next one, so it should be fine.
You can create 2 graphs on your dashboard:
- Index
- 30-minute Consumption
So we can see what your data looks like?
Here:




I left everything at default so no unit. I’ll change to Wh for my BBRHCJB and kWh for the 30-min consumption.
For now I restarted the consumption calculation and it seems to be running. I’m monitoring.
I added these 11 features in this PR : Add TELEINFORMATION features to Energy monitoring by Pierre-Gilles · Pull Request #2384 · GladysAssistant/Gladys · GitHub
Tell me if that seems good ![]()
Hi @mutmut, I worked on this topic this morning!
I propose a new button that will be displayed on the index features in the MQTT integration if they are not yet linked to a 30-minute consumption / 30-minute cost:

By clicking this button, it creates the two features and places the index under the « meter » defined in the « Energy tracking » integration.

I also took the opportunity to add a small « Show advanced settings » button to hide the MQTT topics by default, otherwise this view was really too long ![]()
What do you think?
The PR:
Hello,
In the energy monitoring, the hierarchy seems to have built itself it seems and at 2 or 3 levels. Is it possible and/or necessary to change the settings?
Is it also normal that the 30-minute duration always appears?

I assume it is normal to see the synchronization with values that vary from 0% to Success.

Hi @Jluc, everything looks good on your end ![]()
Don’t change anything!
Everything is normal, let all the tasks finish, the tasks related to energy monitoring are deliberately executed sequentially so they don’t step on each other’s toes.
As long as they’re pending, they’ll stay at 0% until it’s their turn ![]()
It works, thanks.
Just a quick check on the hierarchy: since there are several indexes, EAST is the one that has children EASF01, EASF02…
And all the outlets, we put them as children of EAST as well, not as children of the EASF indexes, right?
[quote=« bertrandda, post:30, topic:9854 »]
And all the entries, we
I’ve improved the overall UX of the energy tariff creation tab.
Now the view looks like this:

The name is configurable when importing the contract (or when creating an individual price):

When opening an item from the list:

To detect peak and off-peak hours, I simply count the « night » hours; it’s a bit of a dumb calculation ^^
For example, for Tempo:

The big plus is that you can click the trash icon to delete all prices of a contract in one click!
The PR:
What do you think?
Another proposal following feedback from @Terdious: now that the MQTT integration automatically creates the « 30-minute consumption » and « 30-minute cost » features, it
That’s perfect ![]()
Thanks for the PR
I’ve merged all the proposed changes and I’m releasing today with the fixes ![]()
Gladys Assistant 4.66.2 is available with all these new features:
Energy monitoring:
- Ability to use a Lixee TIC in standard mode
- One-click creation of features in the MQTT integration
- Improved contracts list
Bonus:
- Fixed a bug in the scene trigger « Receive an MQTT message » that didn’t work correctly when the message was empty
- Scene: It is now possible to compare a « text » feature with a text in the trigger « Device state change »
- Scene: It is now possible to compare a variable with a text in the condition « Condition on variables »
The CHANGELOG is available here.
Documentation has been updated: Surveillez votre consommation énergétique avec Gladys Assistant | Gladys Assistant
Thanks everyone for your feedback ![]()
Thank you, it works perfectly ^^ And wow… what a time saver, it took me barely 5 minutes whereas it would have taken me hours by hand, thanks :



Indeed, much better!! Even if not completely to my taste yet ^^ But it’s functional and that’s the main thing ^^ Thanks as well
Great!
Features created in the MQTT integration with one click, it’s magic!
Is it possible to implement it on Tasmota as well? Feature request?
Thank you!
For Tasmota, I’ll see if I can do it, but for now my priorities are:
- Widget « Energy consumption » → Ability to switch from euros to kWh
- Add the subscription (fixed cost)
I’ll try to look into Tasmota — in that case it might be identical to what you’ve already done… ^^