Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Telegrams w/o CRC, Kilo, *255 #7

Open
Aeroid opened this issue Jan 20, 2024 · 0 comments
Open

Telegrams w/o CRC, Kilo, *255 #7

Aeroid opened this issue Jan 20, 2024 · 0 comments

Comments

@Aeroid
Copy link

Aeroid commented Jan 20, 2024

Is your feature request related to a problem? Please describe.
The DSMR parser currently seems to

  • require CRCs
  • assumes "kW" only (i.e. ignores "W" units) and
  • stumbles over "*255" suffix to the OBIS code

Telegrams like this don't work:

 /ESY5Q3DB1024 V3.04

1-0:0.0.0*255(0272031312565)
1-0:1.8.0*255(00066982.7369255*kWh)
1-0:2.8.0*255(00025261.5976087*kWh)
1-0:21.7.0*255(000210.92*W)
1-0:41.7.0*255(000225.08*W)
1-0:61.7.0*255(000144.75*W)
1-0:1.7.0*255(000580.75*W)
1-0:96.5.5*255(80)
0-0:96.1.255*255(1ESY1313002565)
!

Describe the solution you'd like

  • Parse units w/o kilo correctly
  • Accept CRC-less telegrams
  • Accept "*255" suffix to the OBIS codes

Describe alternatives you've considered
My current workaround is parsing above telegrams and re-assembiling them in evcc-dsmr
The workaround can be found here: https://github.com/Aeroid/dsmr-tools as a python tcp bridge. It also includes a few more dumped telegrams.

Additional context
see also ndokter/dsmr_parser#92
and evcc-io/evcc#11772

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

No branches or pull requests

1 participant