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

Three ignored OBIS String #152

Open
j0scha1 opened this issue Sep 11, 2020 · 5 comments
Open

Three ignored OBIS String #152

j0scha1 opened this issue Sep 11, 2020 · 5 comments

Comments

@j0scha1
Copy link

j0scha1 commented Sep 11, 2020

Describe the bug
OBIS String 1-1:30D, 1-1:7D, 1-1:1D are ignored by the adapter.

To Reproduce
Steps to reproduce the behavior:

  1. Have an Elster AS1440 (in my case I have two, one for household electricity and one for the heating (heating pump)
    a. Also have a Master/Slave iobroker setup. The slave has two optical devices attached via USB (IR-Schreib-Lesekopf by Volkszaehler).
  2. Install adapter as described with D0
  3. All values of the electricity meter are shown by smartmeter.
  4. Observe the only error regarding the aforementioned OBIS Strings. All other strings are reported correctly.

Expected behavior
The OBIS Strings represent the total energy consumed as per 30 days, 7 days and day.

Screenshots & Logfiles
iobroker log lines in short:

smartmeter.0 2020-09-11 10:57:24.008 info (2666) Received 256 values, 7 updated
smartmeter.0 2020-09-11 10:57:23.863 warn (2666) Error while parsing D0 content: ignore complete part Error: Invalid Obis String 1-1:30D
smartmeter.0 2020-09-11 10:57:23.863 info (2666) Error: Error while parsing D0 content: ignore complete part Error: Invalid Obis String 1-1:30D
smartmeter.0 2020-09-11 10:57:23.862 warn (2666) Error while parsing D0 content: ignore complete part Error: Invalid Obis String 1-1:7D
smartmeter.0 2020-09-11 10:57:23.861 info (2666) Error: Error while parsing D0 content: ignore complete part Error: Invalid Obis String 1-1:7D
smartmeter.0 2020-09-11 10:57:23.860 warn (2666) Error while parsing D0 content: ignore complete part Error: Invalid Obis String 1-1:1D
smartmeter.0 2020-09-11 10:57:23.859 info (2666) Error: Error while parsing D0 content: ignore complete part Error: Invalid Obis String 1-1:1D

Versions:
On both master and slave

  • Adapter version: 3.1.2
  • JS-Controller version: 3.1.6
  • Node version: 12.8.3
  • Operating system: Linux iobroker 5.4.51-v7+ #1327 SMP Thu Jul 23 10:58:46 BST 2020 armv7l GNU/Linux
    iobroker.2020-09-11.log

Additional context
I tried to reinstall the adapter but the log shows the same outcome.
Is it possible to just ignore certain OBIS strings, so that no errors are shown?
Unter https://www.stadtwerke-muenster.de/fileadmin/stwms/strom/kundencenter/dokumente/Flyer_Elster_AS1440.pdf
auf der zweiten Seite unter "Übersicht Ablese-Daten" steht es.

@Apollon77
Copy link
Owner

Apollon77 commented Sep 11, 2020

Lets say it that way ... these OBIS strings are "out of specs" :-( I need to see what I can do. Why ever smart meter manufactorers need to invent something which is already defined .... gggmmppffff

@j0scha1
Copy link
Author

j0scha1 commented Sep 13, 2020

Thanks for your replay and your awesome work. Looking forward to a solution, however it is just really a minor issue.

@stale
Copy link

stale bot commented Dec 12, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions.
Dieses Problem wurde automatisch als veraltet markiert, da es in letzter Zeit keine Aktivitäten gab. Es wird geschlossen, wenn nicht innerhalb der nächsten 7 Tage weitere Aktivitäten stattfinden. Bitte überprüft, ob das Problem auch in der aktuellsten Version des Adapters noch relevant ist, und teilt uns dies mit. Überprüft auch, ob alle relevanten Details, Logs und Reproduktionsschritte enthalten sind bzw. aktualisiert diese. Vielen Dank für Eure Unterstützung.

@pjo12345
Copy link

Habe das Problem auch. Wird es Abhilfe geben?

@Apollon77
Copy link
Owner

Am liebsten würde ich sagen "zwingt doch mal die Hersteller endlich Spec-Konform zu arbeiten und nicht immer wieder Bugs oder unspezifizierte Erweiterungen einzubauen", aber tja ... die würden sich nur zurücklehnen und sagen "mir doch egal" ... Mal schauen wie ich das ausbaden werde

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

No branches or pull requests

3 participants