-
Notifications
You must be signed in to change notification settings - Fork 1
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
Comments
I have the same problem with this meter. Got it 4 weeks ago from Westnetz (Germany). 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... |
@rapkin61, for sure, you can only parse data, that is send by the meter. |
I'm not sure if the meter sends "167" data. esp8266 ... surely a good idea. I always wanted to get into this topic, but the time is somehow always missing ... |
@rapkin61, I assume you have verified, that your meter is sending ascii data and not binary, didn't you? |
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 in energy.logger.txt we see this: 2021-06-07 11:59:20;167;0;1b1b1b1b010101017607000b0000b18d620062007263010176010107000b00003b2f0b0901454d480000a28ad4010163e7d9007607000b0000b18e620062007263070177010b0901454d480000a28ad4070100620affff72620165000033377977078181c78203ff0101010104454d480177070100000009ff010101010b0901454d480000a28ad40177070100010800ff640101a201621e52035600000000000177070100020800ff640101a201621e52035600000000040177070100010801ff0101621e52035600000000000177070100020801ff0101621e52035600000000040177070100010802ff0101621e52035600000000000177070100020802ff0101621e52035600000000000177078181c78205ff010101018302c9f4982ecd54257e4e0152610c2b2d87b501ccb40b480425e63e2c5beea2433e64725931af757e59b21f8b87e5e583910101016365e1007607000b0000b19162006200726302017101634834001b1b1b1b1a00cdd81b1b1b1b010101017607000b0000b193620062007263010176010107000b00003b310b0901454d480000a28ad40101631738007607000b0000b194620062007263070177010b0901454d480000a28ad4070100620affff72620165000033397977078181c78203ff0101010104454d480177070100000009ff010101010b0901454d480000a28ad40177070100010800ff640101a201621e52035600000000000177070100020800ff640101a201621e52035600000000040177070100010801ff0101621e52035600000000000177070100020801ff0101621e52035600000000040177070100010802ff0101621e52035600000000000177070100020802ff0101621e52035600000000000177078181c78205ff010101018302c9f4982ecd54257e4e0152610c2b2d87b501ccb40b480425e63e2c 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. |
@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 070100100700ff --> 1.6.7 not available 2021-06-07 11:59:20;167;0;1b1b1b1b010101017607000b0000b18d620062007263010176010107000b00003b2f0b0901454d480000a28ad4010163e7d9007607000b0000b18e620062007263070177010b0901454d480000a28ad4070100620affff72620165000033377977078181c78203ff0101010104454d480177070100000009ff010101010b0901454d480000a28ad40177070100010800ff640101a201621e52035600000000000177070100020800ff640101a201621e52035600000000040177070100010801ff0101621e52035600000000000177070100020801ff0101621e52035600000000040177070100010802ff0101621e52035600000000000177070100020802ff0101621e52035600000000000177078181c78205ff010101018302c9f4982ecd54257e4e0152610c2b2d87b501ccb40b480425e63e2c5beea2433e64725931af757e59b21f8b87e5e583910101016365e1007607000b0000b19162006200726302017101634834001b1b1b1b1a00cdd81b1b1b1b010101017607000b0000b193620062007263010176010107000b00003b310b0901454d480000a28ad40101631738007607000b0000b194620062007263070177010b0901454d480000a28ad4070100620affff72620165000033397977078181c78203ff0101010104454d480177070100000009ff010101010b0901454d480000a28ad40177070100010800ff640101a201621e52035600000000000177070100020800ff640101a201621e52035600000000040177070100010801ff0101621e52035600000000000177070100020801ff0101621e52035600000000040177070100010802ff0101621e52035600000000000177070100020802ff0101621e52035600000000000177078181c78205ff010101018302c9f4982ecd54257e4e0152610c2b2d87b501ccb40b480425e63e2c |
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. |
... und woher bekommt man diese PIN? |
Vom jeweiligen Messstellenbetreiber, z.B. der örtliche Versorger. Ich hab meine schlicht per Telefon angefordert und direkt mitgeteilt bekommen. |
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
The text was updated successfully, but these errors were encountered: