Adapter "smartmeter"

oldi-2000

Iskra Mt174

Adapter installiert, Udos Lesekopf in Virtualbox durchgeschliffen, eingestellt … funktioniert!!!!!

Echt super Arbeit!!!

Vielen Dank!!!

Gesendet von meinem LG-H815 mit Tapatalk

joergg

Hallo allerseits,

ich habe ein Problem mit dem smartmeter-Adapter in der Version 0.5.8.

Ich würde mich freuen, wenn ihr mir behilflich sein könntet.

Ich nutze einen NUC mit Windows 10 und einem IR-Schreib-Lese-Kopf (IR-SLK) von Udo um meinen Strommesser ehz-ew8e2ad00a00 auszulesen.

Der aktuelle Treiber für den IR-SLK ist installiert:

https://www.silabs.com/products/develop … cp-drivers

Unter Windows ist die COM3-Schnittstelle mit 9600 BPS und 7E1 für den IR-SLK eingerichtet.

Der smartmeter-Adapter ist wie folgt konfiguriert:

General Settings

Data request interval: 60s

Data transfer: Serial Device with Bi-dir. comm.

Data Protocol: D0 (WakeUp, SingOn, Data)

Language for Datapoint Names: German

Data Transfer Settings

Serial Device Name: COM3

Serial Device Badrate: 9600 baud

Serial Device DataBits: 7

Serial Device StopBits: 1

Serial Device Parity: even

Serial-Response Timeout: <empty>Data Protocol Settings

D0: Number of WakeUp-Characters: 0

D0: Device Address: <empty>D0: SignOn-Message Command: <empty>D0: Mode Overwrite: A

D0: Baudrate Changeover Overwrite: <empty>Do: Fallback OBIS-Medium: 1: Electricity

Grundsätzlich funktioniert das Auslesen.

Allerdings erhalte ich eine Fehlermeldung wegen eines Problems mit einer OBIS-Meldung.

Es folgt ein Debug-Log mit Fehlermeldungen.

! host.HomeServer 2017-05-06 10:31:52.237 info Restart adapter system.adapter.smartmeter.0 because enabled
! host.HomeServer 2017-05-06 10:31:52.237 error instance system.adapter.smartmeter.0 terminated with code 0 (OK)
! smartmeter.0 2017-05-06 10:31:51.677 debug SERIALPORT CLOSE
! smartmeter.0 2017-05-06 10:31:51.677 warn Exception: Error: Invalid Obis String EMH5–--eHZ-E0018E 1-0:0.0.0255
! smartmeter.0 2017-05-06 10:31:51.677 error Error: Invalid Obis String EMH5----eHZ-E0018E 1-0:0.0.0255 at new ObisMeasurement (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\ObisMeasurement.js:46:23) a
! smartmeter.0 2017-05-06 10:31:51.677 error uncaught exception: Invalid Obis String EMH5----eHZ-E0018E 1-0:0.0.0255
! smartmeter.0 2017-05-06 10:31:51.677 debug CURRENT PROCESS STEP 4 IN HANDLEMESSAGE
! smartmeter.0 2017-05-06 10:31:51.677 debug MATCH-RESULT DATA: "\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032914.6669)\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-500981
! smartmeter.0 2017-05-06 10:31:51.677 debug CURRENT PROCESS STEP 4 IN CHECKMESSAGE
! smartmeter.0 2017-05-06 10:31:51.505 debug MATCH-RESULT DATA: "\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032914.6669)\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-" -> null
! smartmeter.0 2017-05-06 10:31:51.505 debug CURRENT PROCESS STEP 4 IN CHECKMESSAGE
! smartmeter.0 2017-05-06 10:31:49.771 debug REMAINING DATA AFTER MESSAGE HANDLING: 1-0:0.0.0255(331200-5009810) 1-0:1.8.1255(032914.6669) 1-0:96.5.5255(80) 0-0:96.1.255255(0000680476) !
! smartmeter.0 2017-05-06 10:31:49.771 debug CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-06 10:31:49.771 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-06 10:31:49.771 debug DONE SEND 0
! smartmeter.0 2017-05-06 10:31:49.505 debug MESSAGES TO SEND: 0
! smartmeter.0 2017-05-06 10:31:49.505 debug CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-06 10:31:49.505 debug OVERWRITE D0-MODE C WITH A
! smartmeter.0 2017-05-06 10:31:49.505 debug CURRENT PROCESS STEP 2 IN HANDLEMESSAGE
! smartmeter.0 2017-05-06 10:31:49.505 debug MATCH-RESULT SIGNON: "/EMH5----eHZ-E0018E\r\n\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032914.6669)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n!\r\n" -> ["/EMH5----eHZ-E0018E\r
! smartmeter.0 2017-05-06 10:31:49.505 debug CURRENT PROCESS STEP 2 IN CHECKMESSAGE
! smartmeter.0 2017-05-06 10:31:49.005 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-06 10:31:49.005 debug DONE SEND 0
! smartmeter.0 2017-05-06 10:31:48.739 debug DONE SEND 1
! smartmeter.0 2017-05-06 10:31:48.739 debug TO SEND 1: /?!
! smartmeter.0 2017-05-06 10:31:48.739 debug CURRENT PROCESS STEP 1 IN GETNEXTMESSAGE
! smartmeter.0 2017-05-06 10:31:48.739 debug TO SEND 2:
! smartmeter.0 2017-05-06 10:31:48.739 debug CURRENT PROCESS STEP 0 IN GETNEXTMESSAGE
! smartmeter.0 2017-05-06 10:31:48.739 debug INITIAL MESSAGES TO SEND: 2
! smartmeter.0 2017-05-06 10:31:48.724 debug SERIALPORT RESET BAUDRATE TO 9600
! smartmeter.0 2017-05-06 10:31:48.724 debug SERIALPORT OPEN
! smartmeter.0 2017-05-06 10:31:48.646 debug CREATE SERIALPORT: 9600 7 1 even
! smartmeter.0 2017-05-06 10:31:48.631 debug SmartmeterObis options: {"debug":2,"protocol":"D0Protocol","transport":"SerialRequestResponseTransport","requestInterval":"60","transportSerialPort":"COM3","transportSerialBaudrate":9600,"transportSer
! smartmeter.0 2017-05-06 10:31:48.631 info starting. Version 0.5.8 in C:/ioBroker/node_modules/iobroker.smartmeter, node: v6.10.2
! host.HomeServer 2017-05-06 10:31:47.122 info instance system.adapter.smartmeter.0 started with pid 2724
! host.HomeServer 2017-05-06 10:31:17.097 info Restart adapter system.adapter.smartmeter.0 because enabled
! host.HomeServer 2017-05-06 10:31:17.097 error instance system.adapter.smartmeter.0 terminated with code 0 (OK)
! smartmeter.0 2017-05-06 10:31:16.567 debug SERIALPORT CLOSE
! smartmeter.0 2017-05-06 10:31:16.567 warn Exception: Error: Invalid Obis String EMH5–--eHZ-E0018E 1-0:0.0.0255
! smartmeter.0 2017-05-06 10:31:16.567 error Error: Invalid Obis String EMH5–--eHZ-E0018E 1-0:0.0.0255 at new ObisMeasurement (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\ObisMeasurement.js:46:23) a
! smartmeter.0 2017-05-06 10:31:16.567 error uncaught exception: Invalid Obis String EMH5----eHZ-E0018E 1-0:0.0.0255
! smartmeter.0 2017-05-06 10:31:16.551 debug CURRENT PROCESS STEP 4 IN HANDLEMESSAGE
! smartmeter.0 2017-05-06 10:31:16.551 debug MATCH-RESULT DATA: "\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032914.6614)\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-500981
! smartmeter.0 2017-05-06 10:31:16.551 debug CURRENT PROCESS STEP 4 IN CHECKMESSAGE
! smartmeter.0 2017-05-06 10:31:14.270 debug REMAINING DATA AFTER MESSAGE HANDLING: 1-0:0.0.0255(331200-5009810) 1-0:1.8.1255(032914.6614) 1-0:96.5.5255(80) 0-0:96.1.255255(0000680476) !
! smartmeter.0 2017-05-06 10:31:14.270 debug CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-06 10:31:14.270 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-06 10:31:14.270 debug DONE SEND 0
! smartmeter.0 2017-05-06 10:31:14.004 debug MESSAGES TO SEND: 0
! smartmeter.0 2017-05-06 10:31:14.004 debug CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-06 10:31:14.004 debug OVERWRITE D0-MODE C WITH A
! smartmeter.0 2017-05-06 10:31:14.004 debug CURRENT PROCESS STEP 2 IN HANDLEMESSAGE
! smartmeter.0 2017-05-06 10:31:14.004 debug MATCH-RESULT SIGNON: "/EMH5----eHZ-E0018E\r\n\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032914.6614)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n!\r\n" -> ["/EMH5----eHZ-E0018E\r
! smartmeter.0 2017-05-06 10:31:14.004 debug CURRENT PROCESS STEP 2 IN CHECKMESSAGE
! smartmeter.0 2017-05-06 10:31:13.410 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-06 10:31:13.410 debug DONE SEND 0
! smartmeter.0 2017-05-06 10:31:13.145 debug DONE SEND 1
! smartmeter.0 2017-05-06 10:31:13.145 debug TO SEND 1: /?!
! smartmeter.0 2017-05-06 10:31:13.145 debug CURRENT PROCESS STEP 1 IN GETNEXTMESSAGE
! smartmeter.0 2017-05-06 10:31:13.145 debug TO SEND 2:
! smartmeter.0 2017-05-06 10:31:13.145 debug CURRENT PROCESS STEP 0 IN GETNEXTMESSAGE
! smartmeter.0 2017-05-06 10:31:13.145 debug INITIAL MESSAGES TO SEND: 2
! smartmeter.0 2017-05-06 10:31:13.129 debug SERIALPORT RESET BAUDRATE TO 9600
! smartmeter.0 2017-05-06 10:31:13.129 debug SERIALPORT OPEN
! smartmeter.0 2017-05-06 10:31:13.051 debug CREATE SERIALPORT: 9600 7 1 even
! smartmeter.0 2017-05-06 10:31:13.051 debug SmartmeterObis options: {"debug":2,"protocol":"D0Protocol","transport":"SerialRequestResponseTransport","requestInterval":"60","transportSerialPort":"COM3","transportSerialBaudrate":9600,"transportSer
! smartmeter.0 2017-05-06 10:31:13.051 info starting. Version 0.5.8 in C:/ioBroker/node_modules/iobroker.smartmeter, node: v6.10.2
! host.HomeServer 2017-05-06 10:31:11.517 info instance system.adapter.smartmeter.0 started with pid 5572
! host.HomeServer 2017-05-06 10:30:41.504 info Restart adapter system.adapter.smartmeter.0 because enabled
! host.HomeServer 2017-05-06 10:30:41.504 error instance system.adapter.smartmeter.0 terminated with code 0 (OK)
! smartmeter.0 2017-05-06 10:30:40.958 debug SERIALPORT CLOSE
! smartmeter.0 2017-05-06 10:30:40.958 warn Exception: Error: Invalid Obis String EMH5–--eHZ-E0018E 1-0:0.0.0255
! smartmeter.0 2017-05-06 10:30:40.958 error Error: Invalid Obis String EMH5----eHZ-E0018E 1-0:0.0.0255 at new ObisMeasurement (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\ObisMeasurement.js:46:23) a
! smartmeter.0 2017-05-06 10:30:40.958 error uncaught exception: Invalid Obis String EMH5----eHZ-E0018E 1-0:0.0.0255
! smartmeter.0 2017-05-06 10:30:40.958 debug CURRENT PROCESS STEP 4 IN HANDLEMESSAGE
! smartmeter.0 2017-05-06 10:30:40.958 debug MATCH-RESULT DATA: "\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032914.6558)\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-500981
! smartmeter.0 2017-05-06 10:30:40.958 debug CURRENT PROCESS STEP 4 IN CHECKMESSAGE
! smartmeter.0 2017-05-06 10:30:38.676 debug REMAINING DATA AFTER MESSAGE HANDLING: 1-0:0.0.0255(331200-5009810) 1-0:1.8.1255(032914.6558) 1-0:96.5.5255(80) 0-0:96.1.255255(0000680476) !
! smartmeter.0 2017-05-06 10:30:38.676 debug CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-06 10:30:38.676 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-06 10:30:38.676 debug DONE SEND 0
! smartmeter.0 2017-05-06 10:30:38.411 debug MESSAGES TO SEND: 0
! smartmeter.0 2017-05-06 10:30:38.411 debug CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-06 10:30:38.411 debug OVERWRITE D0-MODE C WITH A
! smartmeter.0 2017-05-06 10:30:38.411 debug CURRENT PROCESS STEP 2 IN HANDLEMESSAGE
! smartmeter.0 2017-05-06 10:30:38.411 debug MATCH-RESULT SIGNON: "/EMH5----eHZ-E0018E\r\n\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032914.6558)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n!\r\n" -> ["/EMH5----eHZ-E0018E\r
! smartmeter.0 2017-05-06 10:30:38.411 debug CURRENT PROCESS STEP 2 IN CHECKMESSAGE
! smartmeter.0 2017-05-06 10:30:38.114 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-06 10:30:38.114 debug DONE SEND 0
! smartmeter.0 2017-05-06 10:30:37.848 debug DONE SEND 1
! smartmeter.0 2017-05-06 10:30:37.848 debug TO SEND 1: /?!
! smartmeter.0 2017-05-06 10:30:37.832 debug CURRENT PROCESS STEP 1 IN GETNEXTMESSAGE
! smartmeter.0 2017-05-06 10:30:37.832 debug TO SEND 2:
! smartmeter.0 2017-05-06 10:30:37.832 debug CURRENT PROCESS STEP 0 IN GETNEXTMESSAGE
! smartmeter.0 2017-05-06 10:30:37.832 debug INITIAL MESSAGES TO SEND: 2
! smartmeter.0 2017-05-06 10:30:37.817 debug SERIALPORT RESET BAUDRATE TO 9600
! smartmeter.0 2017-05-06 10:30:37.817 debug SERIALPORT OPEN
! host.HomeServer 2017-05-06 10:29:51.390 warn instance system.adapter.smartmeter.0 already running with pid 4864
! host.HomeServer 2017-05-06 10:29:44.264 warn instance system.adapter.smartmeter.0 already running with pid 4864
! smartmeter.0 2017-05-06 10:29:37.704 debug SERIALPORT ERROR: Error: Port is not open
! smartmeter.0 2017-05-06 10:29:37.704 debug SCHEDULE NEXT RUN IN 60s
! smartmeter.0 2017-05-06 10:29:37.704 debug CURRENT PROCESS STEP 10 IN ISPROCESSCOMPLETE: true
! smartmeter.0 2017-05-06 10:29:37.704 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-06 10:29:37.704 debug DONE SEND 0
! smartmeter.0 2017-05-06 10:29:37.610 debug SERIALPORT CLOSE
! smartmeter.0 2017-05-06 10:29:37.610 debug REMAINING DATA AFTER MESSAGE HANDLING:
! smartmeter.0 2017-05-06 10:29:37.610 debug SCHEDULE NEXT RUN IN 60s
! smartmeter.0 2017-05-06 10:29:37.610 debug CURRENT PROCESS STEP 10 IN ISPROCESSCOMPLETE: true
! smartmeter.0 2017-05-06 10:29:37.610 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-06 10:29:37.610 debug CURRENT PROCESS STEP 10 IN ISPROCESSCOMPLETE: true
! smartmeter.0 2017-05-06 10:29:37.610 info Received 4 values, 4 updated
! smartmeter.0 2017-05-06 10:29:37.610 debug Set State 0-0:96_1_255255.value = 0000680476
! smartmeter.0 2017-05-06 10:29:37.610 debug Set State 0-0:96_1_255255.rawvalue = 0000680476
! smartmeter.0 2017-05-06 10:29:37.610 debug Create State 0-0:96_1_255255.value
! smartmeter.0 2017-05-06 10:29:37.610 debug Create State 0-0:96_1_255255.rawvalue
! smartmeter.0 2017-05-06 10:29:37.610 debug Create Channel 0-0:96_1_255255 with name Factory number
! smartmeter.0 2017-05-06 10:29:37.610 debug 0-0:96.1.255255: Factory number = 0000680476
! smartmeter.0 2017-05-06 10:29:37.610 debug Set State 1-0:96_5_5255.value = 80
! smartmeter.0 2017-05-06 10:29:37.610 debug Set State 1-0:96_5_5255.rawvalue = 80
! smartmeter.0 2017-05-06 10:29:37.610 debug Create State 1-0:96_5_5255.value
! smartmeter.0 2017-05-06 10:29:37.610 debug Create State 1-0:96_5_5255.rawvalue
! smartmeter.0 2017-05-06 10:29:37.610 debug Create Channel 1-0:96_5_5255 with name Status
! smartmeter.0 2017-05-06 10:29:37.610 debug 1-0:96.5.5255: Status = 80
! smartmeter.0 2017-05-06 10:29:37.610 debug Set State 1-0:1_8_1255.value = 032914.6458
! smartmeter.0 2017-05-06 10:29:37.610 debug Set State 1-0:1_8_1255.rawvalue = 032914.6458
! smartmeter.0 2017-05-06 10:29:37.610 debug Create State 1-0:1_8_1255.value
! smartmeter.0 2017-05-06 10:29:37.610 debug Create State 1-0:1_8_1255.rawvalue
! smartmeter.0 2017-05-06 10:29:37.610 debug Create Channel 1-0:1_8_1255 with name Zählerstand 1 Summe Wirkarbeit Bezug + (T1)
! smartmeter.0 2017-05-06 10:29:37.610 debug 1-0:1.8.1255: Zählerstand 1 Summe Wirkarbeit Bezug + (T1) = 032914.6458
! smartmeter.0 2017-05-06 10:29:37.610 debug Set State 1-0:0_0_0255.value = 331200-5009810
! smartmeter.0 2017-05-06 10:29:37.610 debug Set State 1-0:0_0_0255.rawvalue = 331200-5009810
! smartmeter.0 2017-05-06 10:29:37.610 debug Create State 1-0:0_0_0255.value
! smartmeter.0 2017-05-06 10:29:37.610 debug Create State 1-0:0_0_0255.rawvalue
! smartmeter.0 2017-05-06 10:29:37.610 debug Create Channel 1-0:0_0_0255 with name Meter owner number
! smartmeter.0 2017-05-06 10:29:37.610 debug 1-0:0.0.0255: Meter owner number = 331200-5009810
! smartmeter.0 2017-05-06 10:29:37.610 debug STORE DATA
! smartmeter.0 2017-05-06 10:29:37.610 debug CURRENT PROCESS STEP 4 IN HANDLEMESSAGE
! smartmeter.0 2017-05-06 10:29:37.610 debug MATCH-RESULT DATA: "\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032914.6458)\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(
! smartmeter.0 2017-05-06 10:29:37.610 debug CURRENT PROCESS STEP 4 IN CHECKMESSAGE
! smartmeter.0 2017-05-06 10:29:37.438 debug MESSAGES TO SEND: 0
! smartmeter.0 2017-05-06 10:29:37.438 debug CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-06 10:29:37.438 debug OVERWRITE D0-MODE C WITH A
! smartmeter.0 2017-05-06 10:29:37.438 debug CURRENT PROCESS STEP 2 IN HANDLEMESSAGE
! smartmeter.0 2017-05-06 10:29:37.438 debug MATCH-RESULT SIGNON: "/EMH5----eHZ-E0018E\r\n\r\n1-0:0.0.0*255(331200-5009810" -> ["/EMH5–--eHZ-E0018E\r\n","/EMH5----eHZ-E0018E"]
! smartmeter.0 2017-05-06 10:29:37.438 debug CURRENT PROCESS STEP 2 IN CHECKMESSAGE
! smartmeter.0 2017-05-06 10:29:36.719 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-06 10:29:36.719 debug DONE SEND 0
! smartmeter.0 2017-05-06 10:29:36.454 debug DONE SEND 1
! smartmeter.0 2017-05-06 10:29:36.454 debug TO SEND 1: /?!
! smartmeter.0 2017-05-06 10:29:36.454 debug CURRENT PROCESS STEP 1 IN GETNEXTMESSAGE
! smartmeter.0 2017-05-06 10:29:36.454 debug TO SEND 2:
! smartmeter.0 2017-05-06 10:29:36.454 debug CURRENT PROCESS STEP 0 IN GETNEXTMESSAGE
! smartmeter.0 2017-05-06 10:29:36.454 debug INITIAL MESSAGES TO SEND: 2
! smartmeter.0 2017-05-06 10:29:36.438 debug SERIALPORT RESET BAUDRATE TO 9600
! smartmeter.0 2017-05-06 10:29:36.438 debug SERIALPORT OPEN
! smartmeter.0 2017-05-06 10:29:36.360 debug CREATE SERIALPORT: 9600 7 1 even
! smartmeter.0 2017-05-06 10:29:36.360 debug SmartmeterObis options: {"debug":2,"protocol":"D0Protocol","transport":"SerialRequestResponseTransport","requestInterval":"60","transportSerialPort":"COM3","transportSerialBaudrate":9600,"transportSer
! smartmeter.0 2017-05-06 10:29:36.360 info starting. Version 0.5.8 in C:/ioBroker/node_modules/iobroker.smartmeter, node: v6.10.2
! host.HomeServer 2017-05-06 10:29:34.828 info instance system.adapter.smartmeter.0 started with pid 4864

Ich bin für jeden Tipp dankbar.

Gruß joergg</empty></empty></empty></empty>

apollon77

Gleicher Tipp Wie beim letzten User.

Kann es sein das der Zähler die Daten von sich aus liefert und gar nicht angefragt werden muss?

Dann Transport auf serial response ( nicht bidirektional) umstellen. Was passiert dann? ;-)

joergg

Also der Strommesser scheint unaufgefordert seine Daten zu senden.

Habe den Transfer auf Read-Only eingestellt.

Problem bleibt bestehen.

Hier ein Debug-Log:

! Press Ctrl+A and Ctrl+C to copy log to clipboard and click with mouse anywhere to close.
! host.HomeServer 2017-05-07 08:28:10.107 info Restart adapter system.adapter.smartmeter.0 because enabled
! host.HomeServer 2017-05-07 08:28:10.107 error instance system.adapter.smartmeter.0 terminated with code 0 (OK)
! smartmeter.0 2017-05-07 08:28:09.559 debug SERIALPORT CLOSE
! smartmeter.0 2017-05-07 08:28:09.559 warn Exception: Error: Invalid Obis String EMH5–--eHZ-E0018E 1-0:0.0.0255
! smartmeter.0 2017-05-07 08:28:09.559 error Error: Invalid Obis String EMH5----eHZ-E0018E 1-0:0.0.0255 at new ObisMeasurement (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\ObisMeasurement.js:46:23) at D0Protocol.prepareResult (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\protocols\D0Protocol.js:198:31) at D0Protocol.handleMessage (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\protocols\D0Protocol.js:157:27) at SerialPort. (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\transports\SerialResponseTransport.js:63:41) 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-07 08:28:09.559 error uncaught exception: Invalid Obis String EMH5----eHZ-E0018E 1-0:0.0.0255
! smartmeter.0 2017-05-07 08:28:09.559 debug CURRENT PROCESS STEP 4 IN HANDLEMESSAGE
! smartmeter.0 2017-05-07 08:28:09.559 debug PAUSE READING SERIALPORT TO HANDLE MESSAGE
! smartmeter.0 2017-05-07 08:28:09.559 debug MATCH-RESULT DATA: '\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032927.9884)\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(032927.9888)\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(032927.9888)\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(032927.9888)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n']
! smartmeter.0 2017-05-07 08:28:09.559 debug CURRENT PROCESS STEP 4 IN CHECKMESSAGE
! smartmeter.0 2017-05-07 08:28:06.965 debug REMAINING DATA AFTER MESSAGE HANDLING: 1-0:0.0.0255(331200-5009810) 1-0:1.8.1255(032927.9884) 1-0:96.5.5255(80) 0-0:96.1.255255(0000680476) !
! smartmeter.0 2017-05-07 08:28:06.965 debug CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-07 08:28:06.965 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-07 08:28:06.965 debug CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-07 08:28:06.965 debug OVERWRITE D0-MODE C WITH A
! smartmeter.0 2017-05-07 08:28:06.965 debug CURRENT PROCESS STEP 2 IN HANDLEMESSAGE
! smartmeter.0 2017-05-07 08:28:06.950 debug PAUSE READING SERIALPORT TO HANDLE MESSAGE
! smartmeter.0 2017-05-07 08:28:06.950 debug MATCH-RESULT SIGNON: '/EMH5–--eHZ-E0018E\r\n\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032927.9884)\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-07 08:28:06.950 debug CURRENT PROCESS STEP 0 IN CHECKMESSAGE
! smartmeter.0 2017-05-07 08:28:06.528 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-07 08:28:06.528 debug SERIALPORT OPEN
! smartmeter.0 2017-05-07 08:28:06.528 debug CREATE SERIALPORT: 9600 7 1 even
! smartmeter.0 2017-05-07 08:28:06.528 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-07 08:28:06.528 info starting. Version 0.5.8 in C:/ioBroker/node_modules/iobroker.smartmeter, node: v6.10.2
! host.HomeServer 2017-05-07 08:28:05.003 info instance system.adapter.smartmeter.0 started with pid 8148
! host.HomeServer 2017-05-07 08:28:02.344 info Restart adapter system.adapter.smartmeter.0 because enabled
! host.HomeServer 2017-05-07 08:28:02.344 error instance system.adapter.smartmeter.0 terminated with code 0 (OK)
! smartmeter.0 2017-05-07 08:28:01.804 debug SERIALPORT CLOSE
! smartmeter.0 2017-05-07 08:28:01.804 warn Exception: Error: Invalid Obis String EMH5–--eHZ-E0018E 1-0:0.0.0255
! smartmeter.0 2017-05-07 08:28:01.804 error Error: Invalid Obis String EMH5----eHZ-E0018E 1-0:0.0.0255 at new ObisMeasurement (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\ObisMeasurement.js:46:23) at D0Protocol.prepareResult (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\protocols\D0Protocol.js:198:31) at D0Protocol.handleMessage (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\protocols\D0Protocol.js:157:27) at SerialPort. (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\transports\SerialResponseTransport.js:63:41) 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-07 08:28:01.804 error uncaught exception: Invalid Obis String EMH5----eHZ-E0018E 1-0:0.0.0255
! smartmeter.0 2017-05-07 08:28:01.804 debug CURRENT PROCESS STEP 4 IN HANDLEMESSAGE
! smartmeter.0 2017-05-07 08:28:01.804 debug PAUSE READING SERIALPORT TO HANDLE MESSAGE
! smartmeter.0 2017-05-07 08:28:01.804 debug MATCH-RESULT DATA: '\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032927.9872)\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(032927.9876)\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(032927.9876)\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(032927.9876)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n']
! smartmeter.0 2017-05-07 08:28:01.804 debug CURRENT PROCESS STEP 4 IN CHECKMESSAGE
! smartmeter.0 2017-05-07 08:27:59.272 debug REMAINING DATA AFTER MESSAGE HANDLING: 1-0:0.0.0255(331200-5009810) 1-0:1.8.1255(032927.9872) 1-0:96.5.5255(80) 0-0:96.1.255255(0000680476) !
! smartmeter.0 2017-05-07 08:27:59.272 debug CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-07 08:27:59.272 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-07 08:27:59.272 debug CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-07 08:27:59.272 debug OVERWRITE D0-MODE C WITH A
! smartmeter.0 2017-05-07 08:27:59.272 debug CURRENT PROCESS STEP 2 IN HANDLEMESSAGE
! smartmeter.0 2017-05-07 08:27:59.272 debug PAUSE READING SERIALPORT TO HANDLE MESSAGE
! smartmeter.0 2017-05-07 08:27:59.272 debug MATCH-RESULT SIGNON: '/EMH5–--eHZ-E0018E\r\n\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032927.9872)\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-07 08:27:59.272 debug CURRENT PROCESS STEP 0 IN CHECKMESSAGE
! smartmeter.0 2017-05-07 08:27:58.928 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-07 08:27:58.928 debug SERIALPORT OPEN
! smartmeter.0 2017-05-07 08:27:58.928 debug CREATE SERIALPORT: 9600 7 1 even
! smartmeter.0 2017-05-07 08:27:58.928 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-07 08:27:58.928 info starting. Version 0.5.8 in C:/ioBroker/node_modules/iobroker.smartmeter, node: v6.10.2
! host.HomeServer 2017-05-07 08:27:57.398 info instance system.adapter.smartmeter.0 started with pid 4820
! host.HomeServer 2017-05-07 08:27:52.546 info Restart adapter system.adapter.smartmeter.0 because enabled
! host.HomeServer 2017-05-07 08:27:52.546 error instance system.adapter.smartmeter.0 terminated with code 0 (OK)
! smartmeter.0 2017-05-07 08:27:52.006 debug SERIALPORT CLOSE
! smartmeter.0 2017-05-07 08:27:52.006 warn Exception: Error: Invalid Obis String EMH5–--eHZ-E0018E 1-0:0.0.0255
! smartmeter.0 2017-05-07 08:27:52.006 error Error: Invalid Obis String EMH5----eHZ-E0018E 1-0:0.0.0255 at new ObisMeasurement (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\ObisMeasurement.js:46:23) at D0Protocol.prepareResult (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\protocols\D0Protocol.js:198:31) at D0Protocol.handleMessage (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\protocols\D0Protocol.js:157:27) at SerialPort. (C:\ioBroker\node_modules\iobroker.smartmeter\node_modules\smartmeter-obis\lib\transports\SerialResponseTransport.js:63:41) 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-07 08:27:52.006 error uncaught exception: Invalid Obis String EMH5----eHZ-E0018E 1-0:0.0.0255
! smartmeter.0 2017-05-07 08:27:52.006 debug CURRENT PROCESS STEP 4 IN HANDLEMESSAGE
! smartmeter.0 2017-05-07 08:27:52.006 debug PAUSE READING SERIALPORT TO HANDLE MESSAGE
! smartmeter.0 2017-05-07 08:27:52.006 debug MATCH-RESULT DATA: '\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032927.9856)\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(032927.9860)\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(032927.9860)\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(032927.9860)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255255(0000680476)\r\n']
! smartmeter.0 2017-05-07 08:27:52.006 debug CURRENT PROCESS STEP 4 IN CHECKMESSAGE
! smartmeter.0 2017-05-07 08:27:49.486 debug REMAINING DATA AFTER MESSAGE HANDLING: 1-0:0.0.0255(331200-5009810) 1-0:1.8.1255(032927.9856) 1-0:96.5.5255(80) 0-0:96.1.255255(0000680476) !
! smartmeter.0 2017-05-07 08:27:49.486 debug CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-07 08:27:49.486 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-07 08:27:49.486 debug CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
! smartmeter.0 2017-05-07 08:27:49.486 debug OVERWRITE D0-MODE C WITH A
! smartmeter.0 2017-05-07 08:27:49.471 debug CURRENT PROCESS STEP 2 IN HANDLEMESSAGE
! smartmeter.0 2017-05-07 08:27:49.471 debug PAUSE READING SERIALPORT TO HANDLE MESSAGE
! smartmeter.0 2017-05-07 08:27:49.471 debug MATCH-RESULT SIGNON: '/EMH5–--eHZ-E0018E\r\n\r\n1-0:0.0.0255(331200-5009810)\r\n1-0:1.8.1255(032927.9856)\r\n1-0:96.5.5255(80)\r\n0-0:96.1.255*255(0000680476)\r\n!\r\n' -> ['/EMH5–--eHZ-E0018E\r\n','/EMH5----eHZ-E0018E']
! smartmeter.0 2017-05-07 08:27:49.471 debug CURRENT PROCESS STEP 0 IN CHECKMESSAGE
! smartmeter.0 2017-05-07 08:27:48.689 debug SET MESSAGE TIMEOUT TIMER: 120000
! smartmeter.0 2017-05-07 08:27:48.689 debug SERIALPORT OPEN
! smartmeter.0 2017-05-07 08:27:48.596 debug CREATE SERIALPORT: 9600 7 1 even
! smartmeter.0 2017-05-07 08:27:48.596 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-07 08:27:48.596 info starting. Version 0.5.8 in C:/ioBroker/node_modules/iobroker.smartmeter, node: v6.10.2
! host.HomeServer 2017-05-07 08:27:47.065 info instance system.adapter.smartmeter.0 started with pid 8080

Danke für weitere Vorschläge…

Gruß joergg

easymeter

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

easymeter

Hier noch der LOG
2624_log2.txt

apollon77

@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

easymeter

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

apollon77

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

easymeter

Ich habe es einmal auf "B" gestellt.

Anbei der aktuelle Log

In Objekte fehlt noch immer der Ordner.

Gruß

Markus
2624_log4.txt

apollon77

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 ...

easymeter

so, smartmeter angehalten und PI (mit deaktivierten Adapter) rebootet, leider ohne erfolg.
2624_log5.txt

apollon77

Dann alle overwrites raus, Request Response (bidirektional) als Transport und dann nochmal log. Fangen wir nochmal bei 0 an

easymeter

ich habe die Änderungen eingetragen anbei einmal die Screenshots.

Der LOG liegt auch bei
2624_einstellungen1.jpg
2624_einstellungen2.jpg
2624_log6.txt

apollon77

Versuch bitte jetzt mal Mode-Override wieder auf B zu setzen, aber nur das ändern!

joergg

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 4964

Gruß joergg

apollon77

Bitte alle beide Update vom Github installieren

@easymeter: ggf ohne den protocol-Overwrite

joergg

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

apollon77

Version vom Github installieren ist was anderes als com npm!

Admin, das dritte Icon von Links, dann dort smartmeter auswählen

joergg

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

Community Forum

NEWS

Adapter "smartmeter"

Support us

308

32.4k

81.4k

1.3m