My meter has not been able to communicate with Fluvius’ network for a couple years now, I also have old firmware.
Did your meter update by itself or how did you solve this?
via fluvius helpdesk, they updated it remotely, took a few days. But if your meter cannot communicate, then that won’t work obviously…
Thanks, that’s indeed what I expected, I recently also got a digital water meter and I’d kind of like to be able to read it out. I’ll reach out to their helpdesk, see if they maybe send somebody to manually update it without adding 1 of those ugly external antennas…
What plugin are you exactly using? Can’t find any information in the docs 
.
Hi, Can you share the graph code?
Hi, sure …
The firstone:
type: custom:apexcharts-card
graph_span: 24h
update_interval: 1min
cache: true
span:
start: day
header:
show: true
title: Kwartierpiek vandaag
standard_format: true
show_states: true
colorize_states: true
apex_config:
yaxis:
- id: first
forceNiceScale: true
decimalsInFloat: 0
min: 0
opposite: false
name: Piekverbruik
series:
- entity: sensor.electricity_meter_huidig_gemiddelde_vraag
unit: kW
type: column
name: Actueel piekverbruik
color: rgba(72,143,194,255)
float_precision: 2
group_by:
duration: 15m
func: max
show:
datalabels: false
extremas: max
legend_value: false
- entity: sensor.electricity_meter_maximale_vraag_huidige_maand
unit: kW
type: line
name: Maandpiek
float_precision: 2
color: orange
stroke_width: 2
group_by:
duration: 15m
func: last
show:
datalabels: false
extremas: max
legend_value: false
The second one:
type: custom:apexcharts-card
graph_span: 1month
update_interval: 1h
span:
start: month
header:
show: true
title: Piekverbruik per dag
standard_format: true
apex_config:
yaxis:
- id: first
forceNiceScale: true
decimalsInFloat: 0
min: 0
opposite: false
name: Piekverbruik maand
series:
- entity: sensor.piekverbruik_gem_kwartier
unit: kW
type: column
statistics:
type: max
period: day
align: middle
name: Dagpiek
color: rgba(72,143,194,255)
float_precision: 2
group_by:
duration: 1d
func: max
show:
datalabels: false
extremas: max
legend_value: true
- entity: sensor.piekverbruik_maand
unit: kW
type: line
statistics:
type: max
period: day
align: middle
name: Maandpiek
float_precision: 2
color: orange
stroke_width: 2
group_by:
duration: 1d
func: max
show:
datalabels: false
extremas: max
legend_value: true
Hi, Thx for these! Just tried them. The first one works great, the second one keeps loading… any thoughts on what might be wrong?
Also, I’m looking for a way to ‘predict’ the next peak based on past x minutes of power use, but so far I came up with nothing that works. Did you try something liek this…
Hi,
The 2 standard sensors created by DSMR Slimme Meter integration were initially not long term statistics. That’s why I created LTS for them using the following:
template:
- sensor:
# Piekverbruik gem kwartier
- name: "Piekverbruik gem kwartier"
unit_of_measurement: 'kW'
device_class: 'power'
state_class: 'measurement'
state: "{{ (states('sensor.electricity_meter_huidig_gemiddelde_vraag') | float ) | round (3) }}"
# Piekverbruik maand
- name: "Piekverbruik maand"
unit_of_measurement: 'kW'
device_class: 'power'
state_class: 'measurement'
state: "{{ (states('sensor.electricity_meter_maximale_vraag_huidige_maand') | float ) | round (3) }}"
The second graph is using my own created long term statistics sensors. So that’s maybe why it’s not working for you?
I just checked and it seems that the DSMR Slimme Meter integration apparently also included LTS for it’s own sensors since March '24:
- sensor.electricity_meter_huidig_gemiddelde_vraag
- sensor.electricity_meter_maximale_vraag_huidige_maand
So you should be able to use these sensor themself like this:
type: custom:apexcharts-card
graph_span: 1month
update_interval: 1h
span:
start: month
header:
show: true
title: Piekverbruik per dag
standard_format: true
apex_config:
yaxis:
- id: first
forceNiceScale: true
decimalsInFloat: 0
min: 0
opposite: false
name: Piekverbruik maand
series:
- entity: sensor.electricity_meter_huidig_gemiddelde_vraag
unit: kW
type: column
statistics:
type: max
period: day
align: middle
name: Dagpiek
color: rgba(72,143,194,255)
float_precision: 2
group_by:
duration: 1d
func: max
show:
datalabels: false
extremas: max
legend_value: true
- entity: sensor.electricity_meter_maximale_vraag_huidige_maand
unit: kW
type: line
statistics:
type: max
period: day
align: middle
name: Maandpiek
float_precision: 2
color: orange
stroke_width: 2
group_by:
duration: 1d
func: max
show:
datalabels: false
extremas: max
legend_value: true
Hi, I’m using a homewizard p1meter, so the sensors are sensor.p1meter_average_demand and sensor.p1meter_peak_demand_current_month.
I tried your latest graph with them, but the graph remains ‘loading’…
Update: Looks like for the p1meter these aren’t LTS sensors either. I guess I’ll make those then like in your example…
Update2: That doesn’t seem to make a difference. Graph stays ‘loading’…
We are getting an Electric car. I want to do the ‘load balancing’ myself using HomeAssistant and nodered.
I am on the latest version (2024.11) of HomeAssistant. I recreated the ‘DSMR Smart Meter’ integration… But i do not get the 2 peak sensors?
In the debug i can see the values are there:
1-0:1.4.0(00.000kW)
1-0:1.6.0(241103140000W)(04.697kW)
So what I am missing? they do not appear in this integration / I can not find them in my entities…
EDIT:
i selected the wrong dsmr version (you need to select the ‘5B’ for Belgium)