Skip to content

upgrade to DSMR5.1 especially powerpeak support#30

Open
jellevervloessem wants to merge 68 commits intodaniel-jong:masterfrom
jellevervloessem:master
Open

upgrade to DSMR5.1 especially powerpeak support#30
jellevervloessem wants to merge 68 commits intodaniel-jong:masterfrom
jellevervloessem:master

Conversation

@jellevervloessem
Copy link
Copy Markdown

@jellevervloessem jellevervloessem commented Mar 28, 2023

Extension of the P1meter:

  • upgrade to DSMR5.1
    • eMUC 1.7.1 and powerpeak support for Belgian Meters
      • process 15min powerpeaks
      • process maximum monthly powerpeak
      • process average monthly powerpeak /12 months
      • send the 12 values as JSON over MQTT.

_Lost of commits are included because of issues with forks/branches and cleanup afterwards... _

Roosted7 and others added 30 commits January 5, 2020 00:13
feat: Add parsing for RETURNDELIVERY_*_TARIF
Some changes after reading improvements made by jhockx in his fork.
Thanks to @geerdkakes for the idea
Always use the default pin, changing it would make no sense.
Fix compatibility with latest SoftwareSerial and DSMR 4.2.2
Jelle Vervloessem and others added 28 commits August 2, 2021 17:14
Have these sensor show up in the energydashboard configuration
Changed device class and state class of some sensors so they can be integrated in energy management. This also gets rid of unknown unit of measurement errors.
Fix daniel-jong#13 Removed unused reference to SoftwareSerial.h libary
change deprecated mqtt sensor yaml format
@daniel-jong
Copy link
Copy Markdown
Owner

daniel-jong commented Mar 30, 2023

Thanks for the PR, looks good!

I think the following points are blocking

  • Inversion of the Day and Night tariffs. Even if the current setup is incorrect users might depend on its. So I'll try to work on a way to offer old and new behaviour with some setting. This is something I could add in a follow up commit on this PR, but needs some time to prep.
  • The Gasmeter's equipment id's. This also something I could work on after merging this back.

I just noticed that I have completely missed out on #21 that contains logic for both issues and should be able to merge that logic into these changes with not to much effort. Great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants