Dutch 'slimme meter'

Homey_Lampje · February 2017

@RamonBaas okay and the reason for not registering is? Please explain I would like to understand / learn.

This is the sensor list...

there is no measuredWatt sensor but there is an actualWatt sensor... puzzled how the bug is different.

Well looking forward to fixes + additions, hopefully I can add my fixes easily into your new master.

RamonBaas · February 2017

The updated version is on GitHub.

Homey_Lampje · February 2017

Running your latest Github version with my changes for DSMR v3, looking good!

Image: https://forum.athom.com/uploads/editor/y5/um99ogqf5cc6.png

Homey_Lampje · February 2017

@RamonBaas I forked your GitHub project... created a branch on the forked one called "DSMRv3-support" and committed my changes. I noticed that the CRC module was not included. For testing my own branch after download from Github I added the CRC code manually. Installed my own Github "DSMRv3-support" version on Homey, so far so good.

What is the next step?? Sorry but this is the first time that I have used Github...

Regards,
Peter

RamonBaas · February 2017

@Homey_Lampje Have a look here: https://help.github.com/articles/creating-a-pull-request/

Homey_Lampje · February 2017

@RamonBaas forked your "4-feb afternoon master"... I included your "Fix gas flow display" into my forked/branched version... then I merged all changes back into my forked master branch... Well this probably not the way it should be done... Do you still want me to make a pull request? Please advice!

RamonBaas · February 2017

@Homey_Lampje You can always make a PR (Pull Request). Can't break anything. I can always reject it if needed.

Homey_Lampje · February 2017

@RamonBaas created a PR.

RamonBaas · February 2017

@Homey_Lampje Unfortunately your code broke the v4 (gas) decoding. Based on your inputs I've made a new version that should support v3 & v4. It should automatically detect the version. Can you give it a try?

Homey_Lampje · February 2017

@RamonBaas thanks for fixing! Sure more than willing to test! Can I download it from GitHub?

Homey_Lampje · February 2017

@RamonBaas Unfortunately your code broke the complete v3 support ;-) stuck in paring process. Turned on debugging mode, is wat you see below.

RamonBaas · February 2017

Do you really get '!:' as end of message? Is that according to the spec (the added ':')?

If so change

|| this.incomingTelegram.slice(-3) === '!\r\n')) // v3

to

|| this.incomingTelegram.slice(-4) === '!:\r\n')) // v3

RamonBaas · February 2017

@Homey_Lampje Try the latest update. I've relaxed the end-of-message check.

Homey_Lampje · February 2017

@RamonBaas Unfortunately its no longer stuck in paring it just stops... Turned debugging on, here is the report (look as it will not decode the v3 telegram...).

Image: https://forum.athom.com/uploads/editor/i6/zy1no1uuj57b.png

Homey_Lampje · February 2017

@RamonBaas I notice that the v3 telegram now ends with a "\:" instead of just "\". The ":" is inserted by your code... attached screenshot is from the v3 specification.

Image: https://forum.athom.com/uploads/editor/1n/a70gl1nsofei.png

RamonBaas · February 2017

Otherwise PM me a valid v3 telegram, then I can see where the error is.

Homey_Lampje · February 2017

Here you go...

Image: https://forum.athom.com/uploads/editor/az/0tqe7ffkcgz8.png

RamonBaas · February 2017

Text please...

Homey_Lampje · February 2017

@RamonBaas text what??? This what I capture from my interface.

Homey_Lampje · February 2017

@RamonBaas sorry you mean a txt file?

/ISk5\2MT382-1004

0-0:96.1.1(removed)

1-0:1.8.1(08119.557*kWh)

1-0:1.8.2(06431.582*kWh)

1-0:2.8.1(00000.003*kWh)

1-0:2.8.2(00000.002*kWh)

0-0:96.14.0(0002)

1-0:1.7.0(0001.02*kW)

1-0:2.7.0(0000.00*kW)

0-0:17.0.0(0999.00*kW)

0-0:96.3.10(1)

0-0:96.13.1()

0-0:96.13.0()

0-1:24.1.0(3)

0-1:96.1.0(removed)

0-1:24.3.0(170124220000)(00)(60)(1)(0-1:24.2.1)(m3)

(04274.714)

0-1:24.4.0(1)

!

Homey_Lampje · February 2017

@RamonBaas a .txt file. If you can not substitute the meter id's with your own please sent me an email I will sent you one without the meter id's removed.

RamonBaas · February 2017

Well, the telegram parses perfectly as long as there is no colon (':') in the end. My code does not insert this (or let me know where that would happen), so you'll have to figure out where it comes from. How do you convert the serial data to Ethernet?

Homey_Lampje · February 2017

@RamonBaas okay will fork and investigate (time permitting this time...).

This ":" is inserted by the software, the telegram I sent you is coming directly from my P1 interface (capture into text file).

I use this http://www.esp8266thingies.nl/wp/ interface.

RamonBaas · February 2017

@Homey_Lampje Ok. For now I've updated the v3 regular expression that it will ignore the colon.

Homey_Lampje · February 2017

@RamonBaas you did it! Working fine now.

Image: https://forum.athom.com/uploads/editor/86/gd6le8wgg5h9.png

Image: https://forum.athom.com/uploads/editor/rg/0c3rnqxsojmg.png

Homey_Lampje · February 2017

@RamonBaas you were right about the ":" it was inserted by my interface, sorry for that! I played to much with the settings of the interface... I corrected it... did a capture direct from interface into file... all back to normal again. Note the <nul> character after the !.

Image: https://forum.athom.com/uploads/editor/h2/9355rzl7npny.png

Then I checked with Homey.log('telegram in',telegram); what the code was capturing, see below...

Image: https://forum.athom.com/uploads/editor/j2/vi56ueegg24u.png

Based on this I changed the telegram validation in in core.js and in index.js of the parser... This are my changes...

core.js

Image: https://forum.athom.com/uploads/editor/t8/8m1xjcgeir9g.png

index.js

Image: https://forum.athom.com/uploads/editor/sh/eq5uejnwmpbp.png

Does this make sence? It does work with these changes at least.

RamonBaas · February 2017

@Homey_Lampje There should also not be a null character according to the spec. It should end with ! CR LF. However, since there is no CRC for v3 the extra character doesn't hurt a lot. The current code should work with or without and extra character there - no need to change it.

Homey_Lampje · February 2017

@RamonBaas when your are fine I am fine, my interface is working thanks for your help.

PBaan93 · February 2017

How are you guys doing with the Homey smart meter p1 app? Can I help by testing the app? Almost got my ESPEasy working with the p1 plugin. Can't wait to try your app.

Homey_Lampje · February 2017

@PBaan93 is working fine for me. Download from GitHub and install via cli.

Dutch 'slimme meter'

Comments