NEWS
Adapter "smartmeter"
-
Guten morgen zusammen,
bei mir gab es das Problem mit dem Bidirektionalen senden. Ich hatte das damals umgestellt und die Daten trudelten ein. Allerdings lediglich einmal, danach standen diese fest.
Zwischenzeitig hatte ich alles nochmal neu aufgesetzt und diese Einstellungen eingetragen.
Das Ergebnis liegt im LOG bei. Irgendwie taucht auch hier ein "OBIS" Problem auf.
Unter Objekte ist allerdings auch nichts zu finden. Der Ordner verschwand nachdem ich in den Einstellungen auf "Even" in der Parität gewechselt habe.
Gruß
Markus
2624_einstellungen2.jpg -
Hier noch der LOG
2624_log2.txt -
@joergg: Hm … mach mal bitte den d0-mode-overwrite der hier auf A steht weg. Fangen wir mal "Standard" an wie der Zähler es will. Dann bitte nochmal Debug.
@easymeter:Bei dir alles ok oder immer noch Probleme? Falls ja, dann mal die Frage, kommt immer das wenn Du den Adapter neu startest? oder kommt teilweise gar nichts
-
Hallo Apollon,
bei mir trudelt nichts mehr ein, bzw. weiß ich nicht direkt, wo ich suchen soll, weil der Ordner "Smartmeter" nicht mehr unter den Objekten ist.
zwischen jedem Restart besteht immer das gleiche Bild. Anbei der LOG
Gruß
Markus
2624_log3.txt -
Aaah jetzt seh ich … versuch mal als D0-Mode-Overwrite "B" zu setzen ... ändert das was ? Sonst muss ich gleich nochmal tief in den code schauen
-
Ich habe es einmal auf "B" gestellt.
Anbei der aktuelle Log
In Objekte fehlt noch immer der Ordner.
Gruß
Markus
2624_log4.txt -
jetzt kapier ichs nimmer … Beende den Adapter bitte mal und schaue das auch wirklich alle "io.smartmeter" prozesse weg sind!! (also kommandozeile mit "ps" und so.
Man sieht das er scheinbar Daten sendet wie diese "1" nach der Signon-Message aber dann wenn er wieder lauschen soll kommt nix ... kapiere ich nicht
Die Datenpunkte werden immer erst angelegt wenn die erste vollständige Message empfangen wurde ...
-
so, smartmeter angehalten und PI (mit deaktivierten Adapter) rebootet, leider ohne erfolg.
2624_log5.txt -
Dann alle overwrites raus, Request Response (bidirektional) als Transport und dann nochmal log. Fangen wir nochmal bei 0 an
-
ich habe die Änderungen eingetragen anbei einmal die Screenshots.
Der LOG liegt auch bei
2624_einstellungen1.jpg
2624_einstellungen2.jpg
2624_log6.txt -
Versuch bitte jetzt mal Mode-Override wieder auf B zu setzen, aber nur das ändern!
-
Guten Morgen,
habe eben folgendes getestet:
D0: Mode Overwrite = Use Mode defined by device
Debug-Log hierzu:
! D0: Mode Overwrite = Use Mode defined by device
! host.HomeServer 2017-05-08 08:34:57.519 info Restart adapter system.adapter.smartmeter.0 because enabled
! host.HomeServer 2017-05-08 08:34:57.519 error instance system.adapter.smartmeter.0 terminated with code 0 (OK)
! smartmeter.0 2017-05-08 08:34:56.987 debug SERIALPORT CLOSE
! smartmeter.0 2017-05-08 08:34:56.987 warn Exception: Error: SerialResponseTransport do not support sending of Data!
! smartmeter.0 2017-05-08 08:34:56.987 error Error: SerialResponseTransport do not support sending of Data! at Error (native) at SerialPort. (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\transports\SerialResponseTransport.js:77:27) at emitOne (events.js:96:13) at SerialPort.emit (events.js:188:7) at SerialPort.raw (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\serialport\lib\parsers.js:7:13)
! smartmeter.0 2017-05-08 08:34:56.987 error uncaught exception: SerialResponseTransport do not support sending of Data!
! smartmeter.0 2017-05-08 08:34:56.987 debug CURRENT PROCESS STEP 3 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-08 08:34:56.987 debug CURRENT PROCESS STEP 2 IN HANDLEMESSAGE
! smartmeter.0 2017-05-08 08:34:56.987 debug PAUSE READING SERIALPORT TO HANDLE MESSAGE
! smartmeter.0 2017-05-08 08:34:56.987 debug MATCH-RESULT SIGNON: '/EMH5–--eHZ-E0018E\r\n\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032941.' -> ['/EMH5–--eHZ-E0018E\r\n','/EMH5----eHZ-E0018E']
! smartmeter.0 2017-05-08 08:34:56.987 debug CURRENT PROCESS STEP 0 IN CHECKMESSAGE
! smartmeter.0 2017-05-08 08:34:54.955 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-08 08:34:54.955 debug SERIALPORT OPEN
! smartmeter.0 2017-05-08 08:34:54.877 debug CREATE SERIALPORT: 9600 7 1 even
! smartmeter.0 2017-05-08 08:34:54.877 debug SmartmeterObis options: {'debug':2,'protocol':'D0Protocol','transport':'SerialResponseTransport','requestInterval':'60','transportSerialPort':'COM3','transportSerialBaudrate':9600,'transportSerialDataBits':7,'transportSerialStopBits':1,'transportSerialParity':'even','transportSerialMessageTimeout':null,'protocolD0WakeupCharacters':0,'obisFallbackMedium':1}
! smartmeter.0 2017-05-08 08:34:54.877 info starting. Version 0.5.8 in C:/ioBroker/node_modules/iobroker.smartmeter, node: v6.10.2
! host.HomeServer 2017-05-08 08:34:53.361 info instance system.adapter.smartmeter.0 started with pid 4964Gruß joergg
-
Bitte alle beide Update vom Github installieren
@easymeter: ggf ohne den protocol-Overwrite
-
Kann es sein, dass Du nicht alle Dateien eingequellt hast.
Wenn ich wie folgt mit npm abrufe, habe ich immer noch die 0.5.8 mit den Fehlern.
Abruf aus GitHub:
npm install iobroker.smartmeter –production --prefix "C:/ioBroker"
Gruß joergg
-
Version vom Github installieren ist was anderes als com npm!
Admin, das dritte Icon von Links, dann dort smartmeter auswählen
-
Ich habe die Webseite auf (localhost:8081).
Aktiviere die Karte "Adapters".
Klicke auf das dritte Icon von Links mit dem GitHub-Logo.
In der Dropdownbox finde ich kein "smartmeter"-Adapter.
Sorry, aber was mache ich falsch?
Gruß joergg
-
Habe den Adapter jetzt manuell von GitHub aktualisiert.
Der Adapter hat jetzt die Versionsnummer 0.5.9.
Der Fehler kommt aber immer noch vor, seltener, aber es gibt ihn noch.
Debug-Log:
! Press Ctrl+A and Ctrl+C to copy log to clipboard and click with mouse anywhere to close.
! host.HomeServer 2017-05-08 10:37:54.873 info Restart adapter system.adapter.smartmeter.0 because enabled
! host.HomeServer 2017-05-08 10:37:54.873 error instance system.adapter.smartmeter.0 terminated with code 0 (OK)
! smartmeter.0 2017-05-08 10:37:54.859 info terminating
! smartmeter.0 2017-05-08 10:37:54.308 debug SERIALPORT CLOSE
! smartmeter.0 2017-05-08 10:37:54.293 warn 1-0:0.0.0255
! smartmeter.0 2017-05-08 10:37:54.293 warn
! smartmeter.0 2017-05-08 10:37:54.293 warn Exception: Error: Invalid Obis String EMH5–--eHZ-E0018E
! smartmeter.0 2017-05-08 10:37:54.293 error at SerialPort.raw (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\serialport\lib\parsers.js:7:13)
! smartmeter.0 2017-05-08 10:37:54.293 error at SerialPort.emit (events.js:188:7)
! smartmeter.0 2017-05-08 10:37:54.293 error at emitOne (events.js:96:13)
! smartmeter.0 2017-05-08 10:37:54.293 error at SerialPort. (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\transports\SerialResponseTransport.js:63:41)
! smartmeter.0 2017-05-08 10:37:54.293 error at D0Protocol.handleMessage (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\protocols\D0Protocol.js:157:27)
! smartmeter.0 2017-05-08 10:37:54.293 error at D0Protocol.prepareResult (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\protocols\D0Protocol.js:198:31)
! smartmeter.0 2017-05-08 10:37:54.293 error at new ObisMeasurement (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\ObisMeasurement.js:46:23)
! smartmeter.0 2017-05-08 10:37:54.293 error 1-0:0.0.0255
! smartmeter.0 2017-05-08 10:37:54.293 error
! smartmeter.0 2017-05-08 10:37:54.293 error Error: Invalid Obis String EMH5----eHZ-E0018E
! smartmeter.0 2017-05-08 10:37:54.293 error 1-0:0.0.0255
! smartmeter.0 2017-05-08 10:37:54.293 error
! smartmeter.0 2017-05-08 10:37:54.293 error uncaught exception: Invalid Obis String EMH5----eHZ-E0018E
! smartmeter.0 2017-05-08 10:37:54.277 debug CURRENT PROCESS STEP 4 IN HANDLEMESSAGE
! smartmeter.0 2017-05-08 10:37:54.277 debug PAUSE READING SERIALPORT TO HANDLE MESSAGE
! smartmeter.0 2017-05-08 10:37:54.277 debug MATCH-RESULT DATA: '\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032942.0358)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n!\r\n/EMH5----eHZ-E0018E\r\n\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032942.0361)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n!\r\n' -> ['EMH5–--eHZ-E0018E\r\n\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032942.0361)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n!\r\n','EMH5----eHZ-E0018E\r\n\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032942.0361)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n']
! smartmeter.0 2017-05-08 10:37:54.277 debug CURRENT PROCESS STEP 4 IN CHECKMESSAGE
! smartmeter.0 2017-05-08 10:37:51.998 debug
! smartmeter.0 2017-05-08 10:37:51.998 debug !
! smartmeter.0 2017-05-08 10:37:51.998 debug 0-0:96.1.255255(0000680476)
! smartmeter.0 2017-05-08 10:37:51.998 debug 1-0:96.5.5255(80)
! smartmeter.0 2017-05-08 10:37:51.998 debug 1-0:1.8.1255(032942.0358)
! smartmeter.0 2017-05-08 10:37:51.998 debug 1-0:0.0.0255(331200-5009810)
! smartmeter.0 2017-05-08 10:37:51.998 debug REMAINING DATA AFTER MESSAGE HANDLING:
! smartmeter.0 2017-05-08 10:37:51.998 debug CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-08 10:37:51.998 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-08 10:37:51.998 debug CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-08 10:37:51.998 debug OVERWRITE D0-MODE C WITH A
! smartmeter.0 2017-05-08 10:37:51.998 debug CURRENT PROCESS STEP 2 IN HANDLEMESSAGE
! smartmeter.0 2017-05-08 10:37:51.998 debug PAUSE READING SERIALPORT TO HANDLE MESSAGE
! smartmeter.0 2017-05-08 10:37:51.998 debug MATCH-RESULT SIGNON: '/EMH5–--eHZ-E0018E\r\n\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032942.0358)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n!\r\n' -> ['/EMH5–--eHZ-E0018E\r\n','/EMH5----eHZ-E0018E']
! smartmeter.0 2017-05-08 10:37:51.998 debug CURRENT PROCESS STEP 0 IN CHECKMESSAGE
! smartmeter.0 2017-05-08 10:37:50.818 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-08 10:37:50.818 debug SERIALPORT OPEN
! smartmeter.0 2017-05-08 10:36:50.724 debug SERIALPORT CLOSE
! smartmeter.0 2017-05-08 10:36:50.718 debug REMAINING DATA AFTER MESSAGE HANDLING:
! smartmeter.0 2017-05-08 10:36:50.717 debug SCHEDULE NEXT RUN IN 60s
! smartmeter.0 2017-05-08 10:36:50.717 debug CURRENT PROCESS STEP 10 IN ISPROCESSCOMPLETE: true
! smartmeter.0 2017-05-08 10:36:50.716 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-08 10:36:50.716 debug CURRENT PROCESS STEP 10 IN ISPROCESSCOMPLETE: true
! smartmeter.0 2017-05-08 10:36:50.716 info Received 4 values, 4 updated
! smartmeter.0 2017-05-08 10:36:50.716 debug Set State 0-0:96_1_255255.value = 0000680476
! smartmeter.0 2017-05-08 10:36:50.715 debug Set State 0-0:96_1_255255.rawvalue = 0000680476
! smartmeter.0 2017-05-08 10:36:50.715 debug Create State 0-0:96_1_255255.value
! smartmeter.0 2017-05-08 10:36:50.715 debug Create State 0-0:96_1_255255.rawvalue
! smartmeter.0 2017-05-08 10:36:50.714 debug Create Channel 0-0:96_1_255255 with name Factory number
! smartmeter.0 2017-05-08 10:36:50.713 debug 0-0:96.1.255255: Factory number = 0000680476
! smartmeter.0 2017-05-08 10:36:50.711 debug Set State 1-0:96_5_5255.value = 80
! smartmeter.0 2017-05-08 10:36:50.710 debug Set State 1-0:96_5_5255.rawvalue = 80
! smartmeter.0 2017-05-08 10:36:50.709 debug Create State 1-0:96_5_5255.value
! smartmeter.0 2017-05-08 10:36:50.708 debug Create State 1-0:96_5_5255.rawvalue
! smartmeter.0 2017-05-08 10:36:50.708 debug Create Channel 1-0:96_5_5255 with name Status
! smartmeter.0 2017-05-08 10:36:50.708 debug 1-0:96.5.5255: Status = 80
! smartmeter.0 2017-05-08 10:36:50.707 debug Set State 1-0:1_8_1255.value = 032942.0282
! smartmeter.0 2017-05-08 10:36:50.707 debug Set State 1-0:1_8_1255.rawvalue = 032942.0282
! smartmeter.0 2017-05-08 10:36:50.706 debug Create State 1-0:1_8_1255.value
! smartmeter.0 2017-05-08 10:36:50.706 debug Create State 1-0:1_8_1255.rawvalue
! smartmeter.0 2017-05-08 10:36:50.706 debug Create Channel 1-0:1_8_1255 with name Zählerstand 1 Summe Wirkarbeit Bezug + (T1)
! smartmeter.0 2017-05-08 10:36:50.705 debug 1-0:1.8.1255: Zählerstand 1 Summe Wirkarbeit Bezug + (T1) = 032942.0282
! smartmeter.0 2017-05-08 10:36:50.704 debug Set State 1-0:0_0_0255.value = 331200-5009810
! smartmeter.0 2017-05-08 10:36:50.702 debug Set State 1-0:0_0_0255.rawvalue = 331200-5009810
! smartmeter.0 2017-05-08 10:36:50.701 debug Create State 1-0:0_0_0255.value
! smartmeter.0 2017-05-08 10:36:50.701 debug Create State 1-0:0_0_0255.rawvalue
! smartmeter.0 2017-05-08 10:36:50.699 debug Create Channel 1-0:0_0_0255 with name Meter owner number
! smartmeter.0 2017-05-08 10:36:50.699 debug 1-0:0.0.0255: Meter owner number = 331200-5009810
! smartmeter.0 2017-05-08 10:36:50.696 debug STORE DATA
! smartmeter.0 2017-05-08 10:36:50.691 debug CURRENT PROCESS STEP 4 IN HANDLEMESSAGE
! smartmeter.0 2017-05-08 10:36:50.691 debug PAUSE READING SERIALPORT TO HANDLE MESSAGE
! smartmeter.0 2017-05-08 10:36:50.691 debug MATCH-RESULT DATA: '\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032942.0282)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n!\r\n' -> ['1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032942.0282)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n!\r\n','1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032942.0282)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n']
! smartmeter.0 2017-05-08 10:36:50.690 debug CURRENT PROCESS STEP 4 IN CHECKMESSAGE
! smartmeter.0 2017-05-08 10:36:50.577 debug
! smartmeter.0 2017-05-08 10:36:50.577 debug REMAINING DATA AFTER MESSAGE HANDLING:
! smartmeter.0 2017-05-08 10:36:50.577 debug CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-08 10:36:50.576 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-08 10:36:50.576 debug CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-08 10:36:50.575 debug OVERWRITE D0-MODE C WITH A
! smartmeter.0 2017-05-08 10:36:50.574 debug CURRENT PROCESS STEP 2 IN HANDLEMESSAGE
! smartmeter.0 2017-05-08 10:36:50.573 debug PAUSE READING SERIALPORT TO HANDLE MESSAGE
! smartmeter.0 2017-05-08 10:36:50.572 debug MATCH-RESULT SIGNON: '/EMH5–--eHZ-E0018E\r\n\r\n' -> ['/EMH5–--eHZ-E0018E\r\n','/EMH5----eHZ-E0018E']
! smartmeter.0 2017-05-08 10:36:50.571 debug CURRENT PROCESS STEP 0 IN CHECKMESSAGE
! smartmeter.0 2017-05-08 10:36:49.623 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-08 10:36:49.620 debug SERIALPORT OPEN
! smartmeter.0 2017-05-08 10:36:49.541 debug CREATE SERIALPORT: 9600 7 1 even
! smartmeter.0 2017-05-08 10:36:49.536 debug SmartmeterObis options: {'debug':2,'protocol':'D0Protocol','transport':'SerialResponseTransport','requestInterval':'60','transportSerialPort':'com3','transportSerialBaudrate':9600,'transportSerialDataBits':7,'transportSerialStopBits':1,'transportSerialParity':'even','transportSerialMessageTimeout':null,'protocolD0WakeupCharacters':0,'protocolD0ModeOverwrite':'A','obisFallbackMedium':1}
! smartmeter.0 2017-05-08 10:36:49.532 info starting. Version 0.5.9 in C:/ioBroker/node_modules/iobroker.smartmeter, node: v6.10.3
! smartmeter.0 2017-05-08 10:36:49.492 debug statesDB connected
! smartmeter.0 2017-05-08 10:36:49.450 debug objectDB connected
! host.HomeServer 2017-05-08 10:36:41.372 info instance system.adapter.smartmeter.0 started with pid 5312
! host.HomeServer 2017-05-08 10:36:11.144 info Restart adapter system.adapter.smartmeter.0 because enabled
! host.HomeServer 2017-05-08 10:36:11.144 error instance system.adapter.smartmeter.0 terminated with code 0 (OK)
! smartmeter.0 2017-05-08 10:36:11.108 info terminating
! smartmeter.0 2017-05-08 10:36:10.606 debug SERIALPORT CLOSE
! smartmeter.0 2017-05-08 10:36:10.590 warn 1-0:0.0.0255
! smartmeter.0 2017-05-08 10:36:10.590 warn
! smartmeter.0 2017-05-08 10:36:10.590 warn Exception: Error: Invalid Obis String EMH5–--eHZ-E0018E
! smartmeter.0 2017-05-08 10:36:10.590 error at SerialPort.raw (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\serialport\lib\parsers.js:7:13)
! smartmeter.0 2017-05-08 10:36:10.590 error at SerialPort.emit (events.js:188:7)
! smartmeter.0 2017-05-08 10:36:10.590 error at emitOne (events.js:96:13)
! smartmeter.0 2017-05-08 10:36:10.590 error at SerialPort. (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\transports\SerialResponseTransport.js:63:41)
! smartmeter.0 2017-05-08 10:36:10.590 error at D0Protocol.handleMessage (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\protocols\D0Protocol.js:157:27)
! smartmeter.0 2017-05-08 10:36:10.590 error at D0Protocol.prepareResult (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\protocols\D0Protocol.js:198:31)
! smartmeter.0 2017-05-08 10:36:10.590 error at new ObisMeasurement (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\ObisMeasurement.js:46:23)
! smartmeter.0 2017-05-08 10:36:10.590 error 1-0:0.0.0255
! smartmeter.0 2017-05-08 10:36:10.590 error
! smartmeter.0 2017-05-08 10:36:10.590 error Error: Invalid Obis String EMH5----eHZ-E0018E
! smartmeter.0 2017-05-08 10:36:10.590 error 1-0:0.0.0255
! smartmeter.0 2017-05-08 10:36:10.590 error
! smartmeter.0 2017-05-08 10:36:10.590 error uncaught exception: Invalid Obis String EMH5----eHZ-E0018E
! smartmeter.0 2017-05-08 10:36:10.575 debug CURRENT PROCESS STEP 4 IN HANDLEMESSAGE
! smartmeter.0 2017-05-08 10:36:10.575 debug PAUSE READING SERIALPORT TO HANDLE MESSAGE
! smartmeter.0 2017-05-08 10:36:10.575 debug MATCH-RESULT DATA: '\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032942.0231)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n!\r\n/EMH5----eHZ-E0018E\r\n\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032942.0234)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n!\r\n' -> ['EMH5–--eHZ-E0018E\r\n\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032942.0234)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n!\r\n','EMH5----eHZ-E0018E\r\n\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032942.0234)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n']
! smartmeter.0 2017-05-08 10:36:10.575 debug CURRENT PROCESS STEP 4 IN CHECKMESSAGE
! smartmeter.0 2017-05-08 10:36:08.078 debug
! smartmeter.0 2017-05-08 10:36:08.078 debug !
! smartmeter.0 2017-05-08 10:36:08.078 debug 0-0:96.1.255255(0000680476)
! smartmeter.0 2017-05-08 10:36:08.078 debug 1-0:96.5.5255(80)
! smartmeter.0 2017-05-08 10:36:08.078 debug 1-0:1.8.1255(032942.0231)
! smartmeter.0 2017-05-08 10:36:08.078 debug 1-0:0.0.0255(331200-5009810)
! smartmeter.0 2017-05-08 10:36:08.078 debug REMAINING DATA AFTER MESSAGE HANDLING:
! smartmeter.0 2017-05-08 10:36:08.078 debug CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-08 10:36:08.078 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-08 10:36:08.078 debug CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-08 10:36:08.078 debug OVERWRITE D0-MODE C WITH A
! smartmeter.0 2017-05-08 10:36:08.078 debug CURRENT PROCESS STEP 2 IN HANDLEMESSAGE
! smartmeter.0 2017-05-08 10:36:08.078 debug PAUSE READING SERIALPORT TO HANDLE MESSAGE
! smartmeter.0 2017-05-08 10:36:08.078 debug MATCH-RESULT SIGNON: '/EMH5–--eHZ-E0018E\r\n\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032942.0231)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n!\r\n' -> ['/EMH5–--eHZ-E0018E\r\n','/EMH5----eHZ-E0018E']
! smartmeter.0 2017-05-08 10:36:08.078 debug CURRENT PROCESS STEP 0 IN CHECKMESSAGE
! smartmeter.0 2017-05-08 10:36:07.216 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-08 10:36:07.216 debug SERIALPORT OPEN
! smartmeter.0 2017-05-08 10:35:07.121 debug SERIALPORT CLOSE
! smartmeter.0 2017-05-08 10:35:07.120 debug REMAINING DATA AFTER MESSAGE HANDLING:
! smartmeter.0 2017-05-08 10:35:07.119 debug SCHEDULE NEXT RUN IN 60s
! smartmeter.0 2017-05-08 10:35:07.119 debug CURRENT PROCESS STEP 10 IN ISPROCESSCOMPLETE: true
! smartmeter.0 2017-05-08 10:35:07.119 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-08 10:35:07.119 debug CURRENT PROCESS STEP 10 IN ISPROCESSCOMPLETE: true
! smartmeter.0 2017-05-08 10:35:07.118 info Received 4 values, 1 updated
! smartmeter.0 2017-05-08 10:35:07.118 debug Data for 0-0:96_1_255255 unchanged
! smartmeter.0 2017-05-08 10:35:07.118 debug 0-0:96.1.255255: Factory number = 0000680476
! smartmeter.0 2017-05-08 10:35:07.117 debug Data for 1-0:96_5_5255 unchanged
! smartmeter.0 2017-05-08 10:35:07.117 debug 1-0:96.5.5255: Status = 80
! smartmeter.0 2017-05-08 10:35:07.116 debug Set State 1-0:1_8_1255.value = 032942.0159
! smartmeter.0 2017-05-08 10:35:07.115 debug Set State 1-0:1_8_1255.rawvalue = 032942.0159
! smartmeter.0 2017-05-08 10:35:07.115 debug 1-0:1.8.1255: Zählerstand 1 Summe Wirkarbeit Bezug + (T1) = 032942.0159
! smartmeter.0 2017-05-08 10:35:07.115 debug Data for 1-0:0_0_0255 unchanged
! smartmeter.0 2017-05-08 10:35:07.114 debug 1-0:0.0.0255: Meter owner number = 331200-5009810
! smartmeter.0 2017-05-08 10:35:07.114 debug STORE DATA
! smartmeter.0 2017-05-08 10:35:07.113 debug CURRENT PROCESS STEP 4 IN HANDLEMESSAGE
! smartmeter.0 2017-05-08 10:35:07.113 debug PAUSE READING SERIALPORT TO HANDLE MESSAGE
! smartmeter.0 2017-05-08 10:35:07.112 debug MATCH-RESULT DATA: '\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032942.0159)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n!\r\n' -> ['1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032942.0159)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n!\r\n','1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032942.0159)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n']
! smartmeter.0 2017-05-08 10:35:07.112 debug CURRENT PROCESS STEP 4 IN CHECKMESSAGE
! smartmeter.0 2017-05-08 10:35:07.077 debug MATCH-RESULT DATA: '\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032942.0159)\r\n1-0:96.5.5255(80)\r\n' -> null
! smartmeter.0 2017-05-08 10:35:07.076 debug CURRENT PROCESS STEP 4 IN CHECKMESSAGE
! smartmeter.0 2017-05-08 10:35:07.062 debug 1-0:96.5.
! smartmeter.0 2017-05-08 10:35:07.062 debug 1-0:1.8.1255(032942.0159)
! smartmeter.0 2017-05-08 10:35:07.062 debug 1-0:0.0.0255(331200-5009810)
! smartmeter.0 2017-05-08 10:35:07.062 debug REMAINING DATA AFTER MESSAGE HANDLING:
! smartmeter.0 2017-05-08 10:35:07.062 debug CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-08 10:35:07.062 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-08 10:35:07.062 debug CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-08 10:35:07.062 debug OVERWRITE D0-MODE C WITH A
! smartmeter.0 2017-05-08 10:35:07.062 debug CURRENT PROCESS STEP 2 IN HANDLEMESSAGE
! smartmeter.0 2017-05-08 10:35:07.062 debug PAUSE READING SERIALPORT TO HANDLE MESSAGE
! smartmeter.0 2017-05-08 10:35:07.062 debug MATCH-RESULT SIGNON: '/EMH5–--eHZ-E0018E\r\n\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032942.0159)\r\n1-0:96.5.' -> ['/EMH5–--eHZ-E0018E\r\n','/EMH5----eHZ-E0018E']
! smartmeter.0 2017-05-08 10:35:07.062 debug CURRENT PROCESS STEP 0 IN CHECKMESSAGE
! smartmeter.0 2017-05-08 10:35:06.049 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-08 10:35:06.047 debug SERIALPORT OPEN
! smartmeter.0 2017-05-08 10:34:05.985 debug SERIALPORT CLOSE
! smartmeter.0 2017-05-08 10:34:05.967 debug REMAINING DATA AFTER MESSAGE HANDLING:
! smartmeter.0 2017-05-08 10:34:05.966 debug SCHEDULE NEXT RUN IN 60s
! smartmeter.0 2017-05-08 10:34:05.966 debug CURRENT PROCESS STEP 10 IN ISPROCESSCOMPLETE: true
! smartmeter.0 2017-05-08 10:34:05.966 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-08 10:34:05.965 debug CURRENT PROCESS STEP 10 IN ISPROCESSCOMPLETE: true
! smartmeter.0 2017-05-08 10:34:05.965 info Received 4 values, 4 updated
! smartmeter.0 2017-05-08 10:34:05.964 debug Set State 0-0:96_1_255255.value = 0000680476
! smartmeter.0 2017-05-08 10:34:05.964 debug Set State 0-0:96_1_255255.rawvalue = 0000680476
! smartmeter.0 2017-05-08 10:34:05.964 debug Create State 0-0:96_1_255255.value
! smartmeter.0 2017-05-08 10:34:05.964 debug Create State 0-0:96_1_255255.rawvalue
! smartmeter.0 2017-05-08 10:34:05.963 debug Create Channel 0-0:96_1_255255 with name Factory number
! smartmeter.0 2017-05-08 10:34:05.963 debug 0-0:96.1.255255: Factory number = 0000680476
! smartmeter.0 2017-05-08 10:34:05.963 debug Set State 1-0:96_5_5255.value = 80
! smartmeter.0 2017-05-08 10:34:05.962 debug Set State 1-0:96_5_5255.rawvalue = 80
! smartmeter.0 2017-05-08 10:34:05.962 debug Create State 1-0:96_5_5255.value
! smartmeter.0 2017-05-08 10:34:05.962 debug Create State 1-0:96_5_5255.rawvalue
! smartmeter.0 2017-05-08 10:34:05.961 debug Create Channel 1-0:96_5_5255 with name Status
! smartmeter.0 2017-05-08 10:34:05.960 debug 1-0:96.5.5255: Status = 80
! smartmeter.0 2017-05-08 10:34:05.960 debug Set State 1-0:1_8_1255.value = 032942.0081
! smartmeter.0 2017-05-08 10:34:05.959 debug Set State 1-0:1_8_1255.rawvalue = 032942.0081
! smartmeter.0 2017-05-08 10:34:05.959 debug Create State 1-0:1_8_1255.value
! smartmeter.0 2017-05-08 10:34:05.958 debug Create State 1-0:1_8_1255.rawvalue
! smartmeter.0 2017-05-08 10:34:05.956 debug Create Channel 1-0:1_8_1255 with name Zählerstand 1 Summe Wirkarbeit Bezug + (T1)
! smartmeter.0 2017-05-08 10:34:05.955 debug 1-0:1.8.1255: Zählerstand 1 Summe Wirkarbeit Bezug + (T1) = 032942.0081
! smartmeter.0 2017-05-08 10:34:05.954 debug Set State 1-0:0_0_0255.value = 331200-5009810
! smartmeter.0 2017-05-08 10:34:05.952 debug Set State 1-0:0_0_0255.rawvalue = 331200-5009810
! smartmeter.0 2017-05-08 10:34:05.951 debug Create State 1-0:0_0_0255.value
! smartmeter.0 2017-05-08 10:34:05.950 debug Create State 1-0:0_0_0255.rawvalue
! smartmeter.0 2017-05-08 10:34:05.948 debug Create Channel 1-0:0_0_0255 with name Meter owner number
! smartmeter.0 2017-05-08 10:34:05.947 debug 1-0:0.0.0255: Meter owner number = 331200-5009810
! smartmeter.0 2017-05-08 10:34:05.944 debug STORE DATA
! smartmeter.0 2017-05-08 10:34:05.939 debug CURRENT PROCESS STEP 4 IN HANDLEMESSAGE
! smartmeter.0 2017-05-08 10:34:05.938 debug PAUSE READING SERIALPORT TO HANDLE MESSAGE
! smartmeter.0 2017-05-08 10:34:05.938 debug MATCH-RESULT DATA: '\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032942.0081)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n!\r\n' -> ['1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032942.0081)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n!\r\n','1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032942.0081)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n']
! smartmeter.0 2017-05-08 10:34:05.937 debug CURRENT PROCESS STEP 4 IN CHECKMESSAGE
! smartmeter.0 2017-05-08 10:34:05.900 debug MATCH-RESULT DATA: '\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032942.0081)\r\n1-0:96.5.5255(80)\r\n' -> null
! smartmeter.0 2017-05-08 10:34:05.900 debug CURRENT PROCESS STEP 4 IN CHECKMESSAGE
! smartmeter.0 2017-05-08 10:34:05.822 debug
! smartmeter.0 2017-05-08 10:34:05.822 debug REMAINING DATA AFTER MESSAGE HANDLING:
! smartmeter.0 2017-05-08 10:34:05.822 debug CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-08 10:34:05.822 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-08 10:34:05.821 debug CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-08 10:34:05.820 debug OVERWRITE D0-MODE C WITH A
! smartmeter.0 2017-05-08 10:34:05.819 debug CURRENT PROCESS STEP 2 IN HANDLEMESSAGE
! smartmeter.0 2017-05-08 10:34:05.818 debug PAUSE READING SERIALPORT TO HANDLE MESSAGE
! smartmeter.0 2017-05-08 10:34:05.818 debug MATCH-RESULT SIGNON: '200-5009810)\r\n1-0:1.8.1255(032942.0078)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n!\r\n/EMH5–--eHZ-E0018E\r\n\r\n' -> ['/EMH5–--eHZ-E0018E\r\n','/EMH5----eHZ-E0018E']
! smartmeter.0 2017-05-08 10:34:05.816 debug CURRENT PROCESS STEP 0 IN CHECKMESSAGE
! host.HomeServer 2017-05-08 10:34:04.157 warn instance system.adapter.smartmeter.0 already running with pid 7784
! smartmeter.0 2017-05-08 10:34:03.666 debug MATCH-RESULT SIGNON: '200-5009810)\r\n1-0:1.8.1255(032942.0078)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255*255(0000680476)\r\n!\r\n' -> null
! smartmeter.0 2017-05-08 10:34:03.666 debug CURRENT PROCESS STEP 0 IN CHECKMESSAGE
! smartmeter.0 2017-05-08 10:34:03.561 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-08 10:34:03.559 debug SERIALPORT OPEN
! smartmeter.0 2017-05-08 10:34:03.474 debug CREATE SERIALPORT: 9600 7 1 even
! smartmeter.0 2017-05-08 10:34:03.474 debug SmartmeterObis options: {'debug':2,'protocol':'D0Protocol','transport':'SerialResponseTransport','requestInterval':'60','transportSerialPort':'com3','transportSerialBaudrate':9600,'transportSerialDataBits':7,'transportSerialStopBits':1,'transportSerialParity':'even','transportSerialMessageTimeout':null,'protocolD0WakeupCharacters':0,'protocolD0ModeOverwrite':'A','obisFallbackMedium':1}
! smartmeter.0 2017-05-08 10:34:03.474 info starting. Version 0.5.9 in C:/ioBroker/node_modules/iobroker.smartmeter, node: v6.10.3
! smartmeter.0 2017-05-08 10:34:03.442 debug statesDB connected
! smartmeter.0 2017-05-08 10:34:03.396 debug objectDB connected
! host.HomeServer 2017-05-08 10:34:01.938 info instance system.adapter.smartmeter.0 started with pid 7784
! host.HomeServer 2017-05-08 10:34:01.663 info instance system.adapter.smartmeter.0 terminated with code null ()
! host.HomeServer 2017-05-08 10:34:01.662 warn instance system.adapter.smartmeter.0 terminated due to SIGTERM
! host.HomeServer 2017-05-08 10:34:01.647 info stopInstance system.adapter.smartmeter.0 killing pid 7772
! host.HomeServer 2017-05-08 10:34:01.646 info stopInstance system.adapter.smartmeter.0Gruß joergg
-
Anpassung der Datei "ObisMeasurement.js" lässt die Werteermittelung funktionieren:
Zeile 23 & 37: "^" aus der RegEx entfernt.
Offensichtlich wird hier ein reiner OBIS-String erwartet, was aber nicht ankommt.
Gruß joergg
-
Diese Änderung ist etwas zu kurz gedacht
Ich hab nochmal was geändert: Please Update from GitHub
Es lag daran das dein Zähler zu schnell sendet …
Ingo F
-
Hallo, jetzt kommen Daten, aber lediglich die Zählernummer.
Diese habe ich mittlerweile jetzt 10 mal unter den Objekten, immer in einem anderen Ordner.
Gruß
Markus
2624_objekte.jpg
2624_log.txt