Bel_RV
November 23, 2022, 4:36pm
1
Starting on 1/1/2023, in Belgium, Flanders region users with a digital meter will be billed by an average monthly peak value. It is calculated like this:
For a 15 minute time frame the average consumption is used. The highest peak in a month is used to calculate a part of the electricity costs.
The 15 minute frame starts at (hh:mm:ss) ??:00:00, ??:15:00, ??:30:00, ??:45:00 and ends at ??:14:59 and so on.
See also:
I was wondering if DSMR could provide this feature?
@frenck @RobBie1221
Dr-know
(Dr Know)
December 29, 2022, 5:00pm
2
I am also a user in Flanders, i would also need this update. (P1 cable connected with HA)
The monthly peak value is with the OBIS Code 1.6.0 (Current calculated peak of running month)
OBIS codes 1.6.0 is visual from firmware 1.99 (OBIS code 1.2.0), i did not find any OBIS code that is showing current 15 minute peak … and in favor of the electricity company they will use a " *moving average" , so turn of appliance for the last 5 minutes will less infect the 15 minute peak measurement …
So for the moment i think the DSMR P1 Kabel needs a update for showing the OBIS code 1.6.0 Current month peak
In the DSMR PARSER everything is ready:
3 Likes
knockaert
(Knockaert)
December 31, 2022, 1:25pm
5
When wil this be released or is this active already? If so where can we find this?
@knockaert . This is a feature request for the “DSMR Slimme meter” integration to read the new values used to calculate the capacity tariff, measured by the digital meter. The integration uses the DSMR Parser. In the parser, everything is ready to extract these new values from the telegram of the P1 port of the digital meter. Now this integration needs a few changes too, to have these values in Home Assistant.
This capacity tariff is used from now on (1/1/2023).
This would be nice if present in the next release
tvds
(Tim)
January 2, 2023, 10:36am
9
+1 for thisone. Would be great to have this available in HA.
+1
Also might need to be added to ESPHome for the custom P1 readers:
opened 07:24PM - 01 Jan 23 UTC
integration: dsmr
<!-- READ THIS FIRST:
- This is for feature requests only, for issues please g… o to the issues repository.
- Please be as descriptive as possible, especially use-cases that can otherwise not be solved boost the problem's priority.
DO NOT DELETE ANY TEXT from this template! Otherwise the issue may be closed without a comment.
-->
**Describe the problem you have/What new integration you would like**
Add sensors related to the peak tarrif in Belgium.
See https://github.com/ndokter/dsmr_parser/commit/d05fe2692bce9da5bca4103008a6327b4901106a
**Please describe your use case for this integration and alternatives you've tried:**
Peak tarrif is based on the highest peak per day, where peaks are calculated based on the average power consumption over 15 minutes.
The utility provider that is responsible for installing the digital energy meters, Fluvius, has added extra fields to the DSMR datastream that hold data on the current 15min avg, highest peak for the month and highest peak over 13 months.
**Additional context**
https://m.facebook.com/groups/makeinbelgium/permalink/5788013861284159/
1 Like
Y4nnickB
(Yannick Buelens)
January 4, 2023, 8:59am
12
@frenck can you have a look at this feature request?
Can you implement this?
You would help a lot of people in Belgium/Flanders…
Thanks!
Got a pull request ready for it:
home-assistant:dev
← dupondje:add_dsmr_peak
opened 10:44AM - 16 Dec 22 UTC
## Breaking change
The gas sensor's name might change. Also for 5B users there … are some unused sensors removed.
## Proposed change
A new version of dsmr_parser will get released with some changes for 'Peak Usage'.
So this needs to be implemented into HA
https://github.com/ndokter/dsmr_parser/pull/113
## Type of change
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [X] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request:
## Checklist
- [ ] The code change is tested and works locally.
- [ ] Local tests pass. **Your PR cannot be merged unless tests pass**
- [X] There is no commented out code in this PR.
- [ ] I have followed the [development checklist][dev-checklist]
- [ ] The code has been formatted using Black (`black --fast homeassistant tests`)
- [X] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
The code was NOT tested yet in production. But I would like to know if the changes already look fine or not :)
When the new dsmr_parser will be released this can be tested and merged then.
Next to that, there is also a new DSMR field that contains 13 values (timestamp and value). It might be cool/nice to have it visual in HA, but the question is how to do that. Cause you will have to create 13 entities?
The values are the last 13 peak usage values for the last 13 months.
3 Likes
drizzle
January 16, 2023, 10:09am
14
+1 . With the “capaciteitstarief” for Belgium already in place from Jan, 1st, it would be nice to see this implemented.
Any progress on this? Was this tested by anyone?
EiDrk
January 23, 2023, 7:56pm
15
In the ‘telegram’ file it is already readable, together with the timestamp.
The time adjusts with every reload of the page.
http://your_P1_IPadress/api/v1/telegram
/FLU5\253770234_A
0-0:96.1.4(50217)
0-0:96.1.1(xx)
0-0:1.0.0(230129081407W)
1-0:1.8.1(001892.840*kWh)
1-0:1.8.2(002547.841*kWh)
1-0:2.8.1(005085.615*kWh)
1-0:2.8.2(002037.365*kWh)
0-0:96.14.0(0002)
1-0:1.4.0(00.381*kW)
1-0:1.6.0(230127074500W)(02.777*kW)
0-0:98.1.0(1)(1-0:1.6.0)(1-0:1.6.0)(230101000000W)(221231154500W)(03.713*kW)
1-0:1.7.0(00.037*kW)
1-0:2.7.0(00.000*kW)
1-0:21.7.0(00.037*kW)
1-0:22.7.0(00.000*kW)
1-0:32.7.0(232.6*V)
1-0:31.7.0(002.11*A)
0-0:96.3.10(1)
0-0:17.0.0(999.9*kW)
1-0:31.4.0(999*A)
0-0:96.13.0()
0-1:24.1.0(003)
0-1:96.1.1(37464C4F32313230313038393938)
0-1:24.4.0(1)
0-1:24.2.3(230129081005W)(04206.660*m3)
!4ECC
1 Like
Any hopes of seeing this being added to #ESPHome and Home Assistant any time soon?
The new Capacity Tarrif in Belgium has quite an impact and monitoring peaks is an important part of energy consumption monitoring now.
Irnixim
February 5, 2023, 5:22pm
18
+100. We all need this in Belgium. Please put this in the next release.
I need this to tell Google my wife each time she uses to much power at once
No, really, this would be a huge help to arm us against this unfair calculation from the federal goverment…
1 Like
cosmos1978
(Cosmos1978)
February 6, 2023, 4:04pm
19
Someone already did the work.
opened 07:24PM - 01 Jan 23 UTC
integration: dsmr
<!-- READ THIS FIRST:
- This is for feature requests only, for issues please g… o to the issues repository.
- Please be as descriptive as possible, especially use-cases that can otherwise not be solved boost the problem's priority.
DO NOT DELETE ANY TEXT from this template! Otherwise the issue may be closed without a comment.
-->
**Describe the problem you have/What new integration you would like**
Add sensors related to the peak tarrif in Belgium.
See https://github.com/ndokter/dsmr_parser/commit/d05fe2692bce9da5bca4103008a6327b4901106a
**Please describe your use case for this integration and alternatives you've tried:**
Peak tarrif is based on the highest peak per day, where peaks are calculated based on the average power consumption over 15 minutes.
The utility provider that is responsible for installing the digital energy meters, Fluvius, has added extra fields to the DSMR datastream that hold data on the current 15min avg, highest peak for the month and highest peak over 13 months.
**Additional context**
https://m.facebook.com/groups/makeinbelgium/permalink/5788013861284159/
I compiled it and its working perfectly. I just had to create a custom sensor to extract the 13 month peak since the dsmr parser does not support this format.
tvds
(Tim)
March 6, 2023, 7:59pm
20
Hi,
Any idea if it will be available in the following HA update 2033.3.2 update?
If you have the Smart Gateways device you can already see the current peak:
https://www.connectix.nl/capaciteitsrarief-nu-ook-beschikbaar-in-home-assistant/?mc_cid=eaaee27069&mc_eid=ed317c6634
In the Rest Api you can also find this data:
PeakConsumptionRunningMonth":“2.73”,“PeakConsumptionLast13Months”:…
I will try to make a template sensor for it