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

obis code 167 not found #1

Open
rapkin61 opened this issue Jun 7, 2021 · 9 comments
Open

obis code 167 not found #1

rapkin61 opened this issue Jun 7, 2021 · 9 comments

Comments

@rapkin61
Copy link

rapkin61 commented Jun 7, 2021

code line 200:

sml167 = parseSML(data_hex, "167", '070100100700ff', 28, 8)

does not seem to find any data, probably because '070100100700ff' cannot be found in the data stream.
Got a new meter today: eHZ-KW8E2A5L0EQ2P

@soenkegissel
Copy link

soenkegissel commented Jun 7, 2021

I have the same problem with this meter. Got it 4 weeks ago from Westnetz (Germany).
Had another meter since 2011, worked perfectly with optical sensor and OBIS. Now the eHZ-KW8E2A5L0EQ2P only sends a anonymous OBIS block.
After entering the pin, the menu entry "InF" is not to find. (https://www.manualslib.de/manual/216737/Emh-Metering-Ehz-K-Bia-D-1-00.html?page=24#manual)

I am in contact with Westnetz, hope they send a new meter with complete OBIS block.

The whole smart meter exchange program in Germany is initiated for letting customers know about their consumption. Not even slightly possible with eHZ-KW8E2A5L0EQ2P. Just sad...

@dirkclemens
Copy link
Owner

@rapkin61, for sure, you can only parse data, that is send by the meter.
Is eHZ-KW8E2A5L0EQ2P sending "167" data? maybe you should check the whole stream, what kind of data/values are being send by the meter.
by the way, I do no longer use this python script on a raspberry, instead I use an esp8266 device with a customized Tasmota software, which uses less power: https://tasmota.github.io/docs/Smart-Meter-Interface/

@rapkin61
Copy link
Author

rapkin61 commented Jun 8, 2021

I'm not sure if the meter sends "167" data.
When I look into that energy.logger.txt file, where the the hex data is written to - I can't find the obis code "070100100700ff" at all.
Maybe I could dig further into this, if I had a chance to read that documents on volkszaehler.org, but the site is offline once again.
Do you have an idea how I could check the whole stream?

esp8266 ... surely a good idea. I always wanted to get into this topic, but the time is somehow always missing ...

@dirkclemens
Copy link
Owner

@rapkin61, I assume you have verified, that your meter is sending ascii data and not binary, didn't you?
Can you please post a sample snapshot from the data that you read from your meter?

@rapkin61
Copy link
Author

rapkin61 commented Jun 8, 2021

I suppose the data format is correct, the other values ("180", "280") are parsed very well and the output matches the values on the display of the meter.

this is a short snippet of the data stream:

cat /dev/ttyUSB0 | od -tx1

0000000 07 01 00 01 08 01 ff 01 01 62 1e 52 03 56 00 00
0000020 00 00 06 01 77 07 01 00 02 08 01 ff 01 01 62 1e
0000040 52 03 56 00 00 00 00 14 01 77 07 1b 1b 1b 1b 01
0000060 01 01 01 76 07 00 0b 00 04 8e 0a 62 00 62 00 72
0000100 63 01 01 76 01 01 07 00 0b 00 01 84 ae 0b 09 01
0000120 45 4d 48 00 00 a2 8a d4 01 01 63 60 0f 00 76 07
0000140 00 0b 00 04 8e 0b 62 00 62 00 72 63 07 01 77 01
0000160 0b 09 01 45 4d 48 00 00 a2 8a d4 07 01 00 62 0a
0000200 ff ff 72 62 01 65 00 01 4f 11 79 77 07 81 81 c7
0000220 82 03 ff 01 01 01 01 04 45 4d 48 01 77 07 01 00
0000240 00 00 09 ff 01 01 01 01 0b 09 01 45 4d 48 00 00
0000260 a2 8a d4 01 77 07 01 00 01 08 00 ff 64 01 01 a2
0000300 01 62 1e 52 03 56 00 00 00 00 06 01 77 07 01 00
0000320 02 08 00 ff 64 01 01 a2 01 62 1e 52 03 56 00 00
0000340 00 00 14 01 77 07 01 00 01 08 01 ff 01 01 62 1e
0000360 52 03 56 00 00 00 00 06 01 77 07 01 00 02 08 01
0000400 ff 01 01 62 1e 52 03 56 00 00 00 00 14 01 77 07
0000420 01 00 01 08 02 ff 01 01 62 1e 52 03 56 00 00 00
0000440 00 00 01 77 07 01 00 02 08 02 ff 01 01 62 1e 52
0000460 03 56 00 00 00 00 00 01 77 07 81 81 c7 82 05 ff
0000500 01 01 01 01 83 02 c9 f4 98 2e cd 54 25 7e 4e 01

in energy.logger.txt we see this:

2021-06-07 11:59:20;167;0;1b1b1b1b010101017607000b0000b18d620062007263010176010107000b00003b2f0b0901454d480000a28ad4010163e7d9007607000b0000b18e620062007263070177010b0901454d480000a28ad4070100620affff72620165000033377977078181c78203ff0101010104454d480177070100000009ff010101010b0901454d480000a28ad40177070100010800ff640101a201621e52035600000000000177070100020800ff640101a201621e52035600000000040177070100010801ff0101621e52035600000000000177070100020801ff0101621e52035600000000040177070100010802ff0101621e52035600000000000177070100020802ff0101621e52035600000000000177078181c78205ff010101018302c9f4982ecd54257e4e0152610c2b2d87b501ccb40b480425e63e2c5beea2433e64725931af757e59b21f8b87e5e583910101016365e1007607000b0000b19162006200726302017101634834001b1b1b1b1a00cdd81b1b1b1b010101017607000b0000b193620062007263010176010107000b00003b310b0901454d480000a28ad40101631738007607000b0000b194620062007263070177010b0901454d480000a28ad4070100620affff72620165000033397977078181c78203ff0101010104454d480177070100000009ff010101010b0901454d480000a28ad40177070100010800ff640101a201621e52035600000000000177070100020800ff640101a201621e52035600000000040177070100010801ff0101621e52035600000000000177070100020801ff0101621e52035600000000040177070100010802ff0101621e52035600000000000177070100020802ff0101621e52035600000000000177078181c78205ff010101018302c9f4982ecd54257e4e0152610c2b2d87b501ccb40b480425e63e2c
2021-06-07 12:01:45;180;0;1b1b1b1b010101017607000b0000b3a3620062007263010176010107000b00003be10b0901454d480000a28ad40101634e79007607000b0000b3a4620062007263070177010b0901454d480000a28ad4070100620affff72620165000033c97977078181c78203ff0101010104454d480177070100000009ff010101010b0901454d480000a28ad40177070100010800ff640101a201621e52035600000000000177070100020800ff640101a201621e52035600000000040177070100010801ff0101621e52035600000000000177070100020801ff0101621e52035600000000040177070100010802ff0101621e52035600000000000177070100020802ff0101621e52035600000000000177078181c78205ff010101018302c9f4982ecd54257e4e0152610c2b2d87b501ccb40b480425e63e2c5beea2433e64725931af757e59b21f8b87e5e58391010101634cd7007607000b0000b3a5620062007263020171016369fb001b1b1b1b1a0023c61b1b1b1b010101017607000b0000b3a9620062007263010176010107000b00003be30b0901454d480000a28ad40101637dc9007607000b0000b3aa620062007263070177010b0901454d480000a28ad4070100620affff72620165000033ca7977078181c78203ff0101010104454d480177070100000009ff010101010b0901454d480000a28ad40177070100010800ff640101a201621e52035600000000000177070100020800ff640101a201621e52035600000000040177070100010801ff0101621e52035600000000000177070100020801ff0101621e52035600000000040177070100010802ff0101621e52035600000000000177070100020802ff0101621e52035600000000000177078181c78205ff010101018302c9f4982ecd54257e4e0152610c2b2d87b501ccb40b480425e63e2c5beea2433e64725931af757e59b21f8b87e5e5839101010163a82f007607000b0000b3ab6200620072630201710163b4b2001b1b1b1b1a00f383

For "180" this was correct (it indicates a value of 0) as the meter was new, but the value of "167" remains 0 up to now. That is not plausible.

@dirkclemens
Copy link
Owner

@rapkin61, you are right, the "1.6.7" value is not included in the data you receive. So it seems that your meter is not capable of sending it. Not every meter is sending every value, depending of internal capabilities or other aspects. My meter e.g. sends only 1.8.0, 2.8.0 and 1.6.7 values.

070100010800ff --> 1.8.0
070100020800ff --> 2.8.0
070100010801ff -->1.8.1
070100020801ff --> 2.8.1
070100010802ff --> 1.8.2
070100020802ff --> 2.8.2

070100100700ff --> 1.6.7 not available

2021-06-07 11:59:20;167;0;1b1b1b1b010101017607000b0000b18d620062007263010176010107000b00003b2f0b0901454d480000a28ad4010163e7d9007607000b0000b18e620062007263070177010b0901454d480000a28ad4070100620affff72620165000033377977078181c78203ff0101010104454d480177070100000009ff010101010b0901454d480000a28ad40177070100010800ff640101a201621e52035600000000000177070100020800ff640101a201621e52035600000000040177070100010801ff0101621e52035600000000000177070100020801ff0101621e52035600000000040177070100010802ff0101621e52035600000000000177070100020802ff0101621e52035600000000000177078181c78205ff010101018302c9f4982ecd54257e4e0152610c2b2d87b501ccb40b480425e63e2c5beea2433e64725931af757e59b21f8b87e5e583910101016365e1007607000b0000b19162006200726302017101634834001b1b1b1b1a00cdd81b1b1b1b010101017607000b0000b193620062007263010176010107000b00003b310b0901454d480000a28ad40101631738007607000b0000b194620062007263070177010b0901454d480000a28ad4070100620affff72620165000033397977078181c78203ff0101010104454d480177070100000009ff010101010b0901454d480000a28ad40177070100010800ff640101a201621e52035600000000000177070100020800ff640101a201621e52035600000000040177070100010801ff0101621e52035600000000000177070100020801ff0101621e52035600000000040177070100010802ff0101621e52035600000000000177070100020802ff0101621e52035600000000000177078181c78205ff010101018302c9f4982ecd54257e4e0152610c2b2d87b501ccb40b480425e63e2c

@mdk2412
Copy link

mdk2412 commented Nov 11, 2022

Das könnte auch daran liegen, dass für einige Werte der PIN beim Stromzähler eingegeben werden muss, vorher rückt der die Daten nicht raus. War bei mir auch so, ich habe einen ISKRA MT681 von Westnetz. Nach PIN-Eingabe sind 167, 367, 576 und 767 verfügbar, für Gesamtleistung und L1, L2 und L3.

@rapkin61
Copy link
Author

... und woher bekommt man diese PIN?

@mdk2412
Copy link

mdk2412 commented Nov 13, 2022

Vom jeweiligen Messstellenbetreiber, z.B. der örtliche Versorger. Ich hab meine schlicht per Telefon angefordert und direkt mitgeteilt bekommen.

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

4 participants