Hello
I’m trying to set up energy monitoring based on my Tempo subscription (Historical), I think I’ve followed the documentation correctly but it’s not working.
- Creation of a virtual MQTT energy meter
- Creation of the 6 TEMPO indexes (Index, 30-minute Consumption, 30-minute Cost) and the Base index always Null but the info is sent by Lixee
- Import of Tempo rates on the virtual MQTT energy meter
- Recalculation of consumption and then costs
Here’s what I’ve configured
I asked Claude, sending him my logs, here is his summary
# Energy Monitoring: "Found 0 INDEX/thirty-minutes-consumption feature pairs" after modifying the hierarchy
## Context
- Linky meter in historical mode, EDF Tempo contract (BBR)
- Lixee ZLinky TIC via Zigbee2mqtt, 7 features Index (Base + 6 Tempo indexes), each with its "30-minute Consumption" and "30-minute Cost" features
- Gladys timezone: Europe/Paris
- Tempo rates imported via Energy Monitoring > Energy Rates > Import, with "Create an electric meter" (MQTT meter)
- The ZLinky indexes are attached to the electric meter in the hierarchy (Level 0: meter, Level 1: Index, Level 2: 30-minute Consumption, Level 3: 30-minute Cost)
- Gladys version: <to be completed>
- What I modified just before 00:30 (Paris time): <to be completed>
## Problem
After modifying the hierarchy, the 30-minute consumption calculation no longer finds any INDEX / 30-minute consumption pairs. No consumption or cost is calculated. The two recalculation buttons in the Settings tab also fail.
The log hours are in UTC (Paris = UTC+2).
## Log excerpt
### 1. Last working calculation (08/10 22:00 UTC = 09/10 00:00 Paris)
2026-10-08T22:00:00+0000 energy-monitoring.calculateEnergyFromIndex.js:26 (EnergyMonitoringHandler.calculateEnergyFromIndex) Calculating consumption from index in timezone Europe/Paris for window Thu Oct 08 2026 22:00:00 GMT+0000 (Coordinated Universal Time)
2026-10-08T22:00:00+0000 energy-monitoring.calculateEnergyFromIndex.js:35 (EnergyMonitoringHandler.calculateEnergyFromIndex) Found 5 energy devices
2026-10-08T22:00:00+0000 energy-monitoring.calculateEnergyFromIndex.js:68 (EnergyMonitoringHandler.calculateEnergyFromIndex) Found 14 INDEX/thirty-minutes-consumption feature pairs
2026-10-08T22:00:00+0000 energy-monitoring.calculateEnergyFromIndex.js:155 () Saved consumption 0 for device Z_Linky_TIC at Thu Oct 08 2026 22:00:00 GMT+0000 (Coordinated Universal Time)
2026-10-08T22:00:00+0000 energy-monitoring.calculateEnergyFromIndex.js:155 () Saved consumption 0.09999999999854481 for device Z_Linky_TIC at Thu Oct 08 2026 22:00:00 GMT+0000 (Coordinated Universal Time)
2026-10-08T22:00:01+0000 energy-monitoring.calculateEnergyFromIndex.js:166 (EnergyMonitoringHandler.calculateEnergyFromIndex) Finished calculating consumption from index for 14 devices
2026-10-08T22:00:02+0000 energy-monitoring.calculateCostFrom.js:38 (EnergyMonitoringHandler.calculateCostFrom) Calculating cost in timezone Europe/Paris
2026-10-08T22:00:02+0000 energy-monitoring.calculateCostFrom.js:50 (EnergyMonitoringHandler.calculateCostFrom) Found 2 energy devices
2026-10-08T22:00:02+0000 energy-monitoring.calculateCostFrom.js:162 () Device a5c83f0b-c8cb-4d85-afdf-056a9492dd11 has tempo prices and Map is empty, getting EDF tempo historical
2026-10-08T22:00:04+0000 index.js:371 () DuckDB: Inserting chunk 0 for deviceFeature = 7d9f085c-ef5c-4a0c-9be1-b00656785794.
(7 lines "DuckDB: Inserting chunk 0" in total, one per cost feature.)
### 2. First failed calculation (08/10 22:30 UTC = 09/10 00:30 Paris)
2026-10-08T22:30:00+0000 energy-monitoring.calculateEnergyFromIndex.js:26 (EnergyMonitoringHandler.calculateEnergyFromIndex) Calculating consumption from index in timezone Europe/Paris for window Thu Oct 08 2026 22:30:00 GMT+0000 (Coordinated Universal Time)
2026-10-08T22:30:00+0000 energy-monitoring.calculateEnergyFromIndex.js:35 (EnergyMonitoringHandler.calculateEnergyFromIndex) Found 5 energy devices
2026-10-08T22:30:00+0000 energy-monitoring.calculateEnergyFromIndex.js:68 (EnergyMonitoringHandler.calculateEnergyFromIndex) Found 0 INDEX/thirty-minutes-consumption feature pairs
2026-10-08T22:30:00+0000 energy-monitoring.calculateEnergyFromIndex.js:166 (EnergyMonitoringHandler.calculateEnergyFromIndex) Finished calculating consumption from index for 0 devices
### 3. Manual recalculation from the Settings tab (09/10 01:00 and 01:07 Paris)
2026-10-08T23:00:53+0000 energy-monitoring.calculateEnergyFromIndexFromBeginning.js:27 () Calculating consumption from index from beginning in timezone Europe/Paris
2026-10-08T23:00:53+0000 energy-monitoring.calculateEnergyFromIndexFromBeginning.js:34 () Found 5 energy devices
2026-10-08T23:00:53+0000 energy-monitoring.calculateEnergyFromIndexFromBeginning.js:76 () Found 0 devices with both INDEX and thirty-minutes-consumption features
2026-10-08T23:00:53+0000 energy-monitoring.calculateEnergyFromIndexFromBeginning.js:81 () No devices found with both features, nothing to process
2026-10-08T23:07:34+0000 energy-monitoring.calculateEnergyFromIndexFromBeginning.js:27 () Calculating consumption from index from beginning in timezone Europe/Paris
2026-10-08T23:07:34+0000 energy-monitoring.calculateEnergyFromIndexFromBeginning.js:34 () Found 5 energy devices
2026-10-08T23:07:34+0000 energy-monitoring.calculateEnergyFromIndexFromBeginning.js:76 () Found 0 devices with both INDEX and thirty-minutes-consumption features
2026-10-08T23:07:34+0000 energy-monitoring.calculateEnergyFromIndexFromBeginning.js:81 () No devices found with both features, nothing to process
### 4. The following calculations have the same result (excerpt: 09/10 05:30 UTC = 07:30 Paris)
2026-10-09T05:30:00+0000 energy-monitoring.calculateEnergyFromIndex.js:35 (EnergyMonitoringHandler.calculateEnergyFromIndex) Found 5 energy devices
2026-10-09T05:30:00+0000 energy-monitoring.calculateEnergyFromIndex.js:68 (EnergyMonitoringHandler.calculateEnergyFromIndex) Found 0 INDEX/thirty-minutes-consumption feature pairs
2026-10-09T05:30:00+0000 energy-monitoring.calculateEnergyFromIndex.js:166 (EnergyMonitoringHandler.calculateEnergyFromIndex) Finished calculating consumption from index for 0 devices
## Questions
1. Why doesn't Gladys find the INDEX / 30-minute consumption pairs anymore even though the hierarchy is correct on screen?
2. Is there a condition on the hierarchy (for example an index attached to an MQTT meter created by the import of the rates) that would exclude these pairs from the calculation?
3. What procedure do you recommend to properly rebuild the hierarchy?
Thank you for your help