Adapter "smartmeter"

apollon77

@fanatikz zeig mal Screenshot der konfig bitte

Fanatikz

@apollon77
Gestartet bin ich hiermit:

Zuletzt hab ich diese Einstellungen probiert, da die nach meinem Verständnis den Anforderungen entsprechen.
Zusätzlich hab ich auch versucht /?! (hex: 2F 3F 21) (plus CR LF) als SignOn Nachricht mitzugeben.

apollon77

@fanatikz hast du da werte rausgelöscht die als default drin waren?? Kommt mir so vor.

Also ein leeres datenabfrageinterval ist auch mal nicht sinnvoll.

Also am besten instanz nochmal löschen und neu anlegen. Dann nur das obige setzen und ggf die baudrate auf 300 setzen.

Signon ist immer im Standard schon das was du willst. Da musst du nichts eintragen.

Und dann nur Anzahl wake-up Zeichen setzen. Keiner hat was von einem „D0 Modus override auf A“ geschrieben ;-)

Und bitte debug log davon dann.

Es wird hier immer wild rumprobiert und am Ende soll ich raten woran es liegt ;-))

Fanatikz

@apollon77 said in Adapter "smartmeter":

nabfrageinterval ist auch mal nicht sinnvoll.
Also am besten instanz nochmal löschen und neu anlegen. Dann nur das obige setzen und ggf die baudrate auf 300 setzen.
Signon ist immer im Standard schon das was du willst. Da musst du nichts eintragen.

Alles klar, hab ich versucht, feedback schaut jetzt etwas anders aus aber noch immer "false".
Auch mit 300bd.

smartmeter.0
20992	2022-06-16 19:15:06.574	debug	Error: No match for Message ""

smartmeter.0
20992	2022-06-16 19:15:06.573	warn	No match for Message ""

smartmeter.0
20992	2022-06-16 19:15:06.274	debug	connected set to false

smartmeter.0
20992	2022-06-16 19:15:06.263	debug	SmartmeterObis options: {"debug":0,"protocol":"D0Protocol","transport":"SerialRequestResponseTransport","requestInterval":"300","anotherQueryDelay":"1000","transportSerialPort":"/dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_c60c2517e68fec118343a88043a0c072-if00-port0","transportSerialBaudrate":300,"transportSerialMessageTimeout":null,"protocolD0WakeupCharacters":15}

smartmeter.0
20992	2022-06-16 19:15:06.251	info	starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.smartmeter, node: v14.18.2, js-controller: 4.0.23

smartmeter.0
20992	2022-06-16 19:15:06.201	info	Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system

smartmeter.0
20992	2022-06-16 19:15:06.199	debug	Plugin sentry Initialize Plugin (enabled=true)

Hier aus der Datei:

06-16 22:49:29.916  - ^[[32minfo^[[39m: host.nostromo stopInstance system.adapter.smartmeter.0 (force=false, process=true)
2022-06-16 22:49:29.921  - ^[[35msilly^[[39m: smartmeter.0 (20478) States system redis pmessage system.adapter.smartmeter.0.sigKill/system.adapter.smartmeter.0.sigKill:{"val":-1,"ack":false,"ts":1655412569918,"q":0,"from":"system.host.nostromo","lc":1655412569918}
2022-06-16 22:49:29.922  - ^[[32minfo^[[39m: smartmeter.0 (20478) Got terminate signal TERMINATE_YOURSELF
2022-06-16 22:49:29.926  - ^[[32minfo^[[39m: smartmeter.0 (20478) terminating
2022-06-16 22:49:29.927  - ^[[34mdebug^[[39m: smartmeter.0 (20478) Plugin sentry destroyed
2022-06-16 22:49:29.927  - ^[[32minfo^[[39m: smartmeter.0 (20478) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-06-16 22:49:29.974  - ^[[32minfo^[[39m: host.nostromo stopInstance system.adapter.smartmeter.0 send kill signal
2022-06-16 22:49:30.498  - ^[[32minfo^[[39m: host.nostromo instance system.adapter.smartmeter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-06-16 22:49:33.049  - ^[[32minfo^[[39m: host.nostromo instance system.adapter.smartmeter.0 started with pid 20988
2022-06-16 22:49:33.458  - ^[[34mdebug^[[39m: smartmeter.0 (20988) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-06-16 22:49:33.476  - ^[[34mdebug^[[39m: smartmeter.0 (20988) Objects client ready ... initialize now
2022-06-16 22:49:33.477  - ^[[34mdebug^[[39m: smartmeter.0 (20988) Objects create System PubSub Client
2022-06-16 22:49:33.477  - ^[[34mdebug^[[39m: smartmeter.0 (20988) Objects create User PubSub Client
2022-06-16 22:49:33.510  - ^[[34mdebug^[[39m: smartmeter.0 (20988) Objects client initialize lua scripts
2022-06-16 22:49:33.512  - ^[[34mdebug^[[39m: smartmeter.0 (20988) Objects connected to redis: 127.0.0.1:9001
2022-06-16 22:49:33.513  - ^[[35msilly^[[39m: smartmeter.0 (20988) redis psubscribe cfg.o.system.user.*
2022-06-16 22:49:33.526  - ^[[35msilly^[[39m: smartmeter.0 (20988) redis psubscribe cfg.o.enum.*
2022-06-16 22:49:33.527  - ^[[35msilly^[[39m: smartmeter.0 (20988) objectDB connected
2022-06-16 22:49:33.528  - ^[[34mdebug^[[39m: smartmeter.0 (20988) Redis States: Use Redis connection: 127.0.0.1:9000
2022-06-16 22:49:33.539  - ^[[34mdebug^[[39m: smartmeter.0 (20988) States create System PubSub Client
2022-06-16 22:49:33.539  - ^[[34mdebug^[[39m: smartmeter.0 (20988) States create User PubSub Client
2022-06-16 22:49:33.603  - ^[[34mdebug^[[39m: smartmeter.0 (20988) States connected to redis: 127.0.0.1:9000
2022-06-16 22:49:33.604  - ^[[35msilly^[[39m: smartmeter.0 (20988) statesDB connected
2022-06-16 22:49:33.726  - ^[[34mdebug^[[39m: smartmeter.0 (20988) Plugin sentry Initialize Plugin (enabled=true)
2022-06-16 22:49:33.727  - ^[[32minfo^[[39m: smartmeter.0 (20988) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
2022-06-16 22:49:33.770  - ^[[32minfo^[[39m: smartmeter.0 (20988) starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.smartmeter, node: v14.18.2, js-controller: 4.0.23
2022-06-16 22:49:33.783  - ^[[34mdebug^[[39m: smartmeter.0 (20988) SmartmeterObis options: {"debug":0,"protocol":"D0Protocol","transport":"SerialRequestResponseTransport","requestInterval":"300","anotherQueryDelay":"1000","transportSerialPort":"/dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_c60c2517e68fec118343a88043a0c072-if00-port0","transportSerialBaudrate":300,"transportSerialMessageTimeout":120000,"protocolD0WakeupCharacters":20,"obisFallbackMedium":1}
2022-06-16 22:49:33.789  - ^[[35msilly^[[39m: smartmeter.0 (20988) States system redis pmessage system.adapter.smartmeter.0.logLevel/system.adapter.smartmeter.0.logLevel:{"val":"silly","ack":true,"ts":1655412573785,"q":0,"from":"system.adapter.smartmeter.0","lc":1655399448678}
2022-06-16 22:49:33.794  - ^[[34mdebug^[[39m: smartmeter.0 (20988) connected set to false
2022-06-16 22:51:35.086  - ^[[33mwarn^[[39m: smartmeter.0 (20988) No or too long answer from Serial Device after last request.
2022-06-16 22:51:35.087  - ^[[34mdebug^[[39m: smartmeter.0 (20988) Error: No or too long answer from Serial Device after last request.
2022-06-16 22:58:36.393  - ^[[33mwarn^[[39m: smartmeter.0 (20988) No or too long answer from Serial Device after last request.
2022-06-16 22:58:36.394  - ^[[34mdebug^[[39m: smartmeter.0 (20988) Error: No or too long answer from Serial Device after last request.

apollon77

@fanatikz DIe Instanz steht aber nicht auf Lolevel "debug" oder??? Ich brauche bitte "debug" ... nicht "silly". Sorry aber bitte nochmal ein Log :-)

Fanatikz

@apollon77 Hi, hat ein paar Tage gedauert, hier das Log.

2022-06-22 21:30:53.606 - info: smartmeter.0 (26156) starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.smartmeter, node: v14.18.2, js-controller: 4.0.23
2022-06-22 21:30:53.618 - error: smartmeter.0 (26156) Serial port device is undefined, check your configuration!
2022-06-22 21:30:54.636 - info: smartmeter.0 (26156) List of port: [{"path":"/dev/ttyACM0","manufacturer":"dresden elektronik ingenieurtechnik GmbH","serialNumber":"DE2191817","pnpId":"usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2191817-if00","vendorId":"1cf1","productId":"0030"},{"path":"/dev/ttyUSB0","manufacturer":"Silicon Labs","serialNumber":"c60c2517e68fec118343a88043a0c072","pnpId":"usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_c60c2517e68fec118343a88043a0c072-if00-port0","vendorId":"10c4","productId":"ea60"},{"path":"/dev/ttyS0"},{"path":"/dev/ttyS1"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS3"}]
2022-06-22 21:32:29.339 - info: host.nostromo stopInstance system.adapter.smartmeter.0 (force=false, process=true)
2022-06-22 21:32:29.341 - info: smartmeter.0 (26156) Got terminate signal TERMINATE_YOURSELF
2022-06-22 21:32:29.342 - info: smartmeter.0 (26156) terminating
2022-06-22 21:32:29.342 - info: smartmeter.0 (26156) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-06-22 21:32:29.410 - info: host.nostromo stopInstance system.adapter.smartmeter.0 send kill signal
2022-06-22 21:32:29.889 - info: host.nostromo instance system.adapter.smartmeter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-06-22 21:32:32.479 - info: host.nostromo instance system.adapter.smartmeter.0 started with pid 26544
2022-06-22 21:32:33.133 - info: smartmeter.0 (26544) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
2022-06-22 21:32:33.170 - info: smartmeter.0 (26544) starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.smartmeter, node: v14.18.2, js-controller: 4.0.23
2022-06-22 21:32:49.899 - info: host.nostromo stopInstance system.adapter.smartmeter.0 (force=false, process=true)
2022-06-22 21:32:49.901 - info: smartmeter.0 (26544) Got terminate signal TERMINATE_YOURSELF
2022-06-22 21:32:49.903 - info: smartmeter.0 (26544) terminating
2022-06-22 21:32:49.904 - info: smartmeter.0 (26544) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-06-22 21:32:49.941 - info: host.nostromo stopInstance system.adapter.smartmeter.0 send kill signal
2022-06-22 21:32:50.473 - info: host.nostromo instance system.adapter.smartmeter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-06-22 21:32:53.010 - info: host.nostromo instance system.adapter.smartmeter.0 started with pid 26633
2022-06-22 21:32:53.431 - debug: smartmeter.0 (26633) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-06-22 21:32:53.450 - debug: smartmeter.0 (26633) Objects client ready ... initialize now
2022-06-22 21:32:53.451 - debug: smartmeter.0 (26633) Objects create System PubSub Client
2022-06-22 21:32:53.451 - debug: smartmeter.0 (26633) Objects create User PubSub Client
2022-06-22 21:32:53.484 - debug: smartmeter.0 (26633) Objects client initialize lua scripts
2022-06-22 21:32:53.486 - debug: smartmeter.0 (26633) Objects connected to redis: 127.0.0.1:9001
2022-06-22 21:32:53.502 - debug: smartmeter.0 (26633) Redis States: Use Redis connection: 127.0.0.1:9000
2022-06-22 21:32:53.512 - debug: smartmeter.0 (26633) States create System PubSub Client
2022-06-22 21:32:53.513 - debug: smartmeter.0 (26633) States create User PubSub Client
2022-06-22 21:32:53.576 - debug: smartmeter.0 (26633) States connected to redis: 127.0.0.1:9000
2022-06-22 21:32:53.680 - debug: smartmeter.0 (26633) Plugin sentry Initialize Plugin (enabled=true)
2022-06-22 21:32:53.681 - info: smartmeter.0 (26633) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
2022-06-22 21:32:53.764 - info: smartmeter.0 (26633) starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.smartmeter, node: v14.18.2, js-controller: 4.0.23
2022-06-22 21:32:53.776 - debug: smartmeter.0 (26633) SmartmeterObis options: {"debug":2,"protocol":"D0Protocol","transport":"SerialRequestResponseTransport","requestInterval":"300","anotherQueryDelay":"1000","transportSerialPort":"/dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_c60c2517e68fec118343a88043a0c072-if00-port0","transportSerialBaudrate":null,"transportSerialMessageTimeout":null,"protocolD0WakeupCharacters":0}
2022-06-22 21:32:53.777 - debug: smartmeter.0 (26633) CREATE SERIALPORT: 300 7 1 even
2022-06-22 21:32:53.780 - debug: smartmeter.0 (26633) SERIALPORT OPEN
2022-06-22 21:32:53.782 - debug: smartmeter.0 (26633) SERIALPORT RESET BAUDRATE TO 300
2022-06-22 21:32:53.784 - debug: smartmeter.0 (26633) INITIAL MESSAGES TO SEND: 2
2022-06-22 21:32:53.784 - debug: smartmeter.0 (26633) CURRENT PROCESS STEP 0 IN GETNEXTMESSAGE
2022-06-22 21:32:53.785 - debug: smartmeter.0 (26633) TO SEND 2:
2022-06-22 21:32:53.785 - debug: smartmeter.0 (26633) CURRENT PROCESS STEP 1 IN GETNEXTMESSAGE
2022-06-22 21:32:53.785 - debug: smartmeter.0 (26633) TO SEND 1: /?!
2022-06-22 21:32:53.788 - debug: smartmeter.0 (26633) connected set to false
2022-06-22 21:32:53.930 - debug: smartmeter.0 (26633) DONE SEND 1
2022-06-22 21:32:54.183 - debug: smartmeter.0 (26633) DONE SEND 0
2022-06-22 21:32:54.184 - debug: smartmeter.0 (26633) SET MESSAGE TIMEOUT TIMER2: 120000
2022-06-22 21:32:57.157 - debug: smartmeter.0 (26633) NEW DATA
2022-06-22 21:32:57.159 - debug: smartmeter.0 (26633) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-06-22 21:32:57.159 - debug: smartmeter.0 (26633) MATCH-RESULT SIGNON: "" -> null
2022-06-22 21:33:03.647 - debug: smartmeter.0 (26633) NEW DATA
2022-06-22 21:33:03.648 - debug: smartmeter.0 (26633) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-06-22 21:33:03.648 - debug: smartmeter.0 (26633) MATCH-RESULT SIGNON: "" -> null
2022-06-22 21:33:10.122 - debug: smartmeter.0 (26633) NEW DATA
2022-06-22 21:33:10.122 - debug: smartmeter.0 (26633) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-06-22 21:33:10.123 - debug: smartmeter.0 (26633) MATCH-RESULT SIGNON: "" -> null
2022-06-22 21:33:16.781 - debug: smartmeter.0 (26633) NEW DATA
2022-06-22 21:33:16.782 - debug: smartmeter.0 (26633) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-06-22 21:33:16.782 - debug: smartmeter.0 (26633) MATCH-RESULT SIGNON: "" -> null
2022-06-22 21:33:24.187 - debug: smartmeter.0 (26633) NEW DATA
2022-06-22 21:33:24.187 - debug: smartmeter.0 (26633) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-06-22 21:33:24.188 - debug: smartmeter.0 (26633) MATCH-RESULT SIGNON: "" -> null
2022-06-22 21:33:38.689 - debug: smartmeter.0 (26633) NEW DATA
2022-06-22 21:33:38.690 - debug: smartmeter.0 (26633) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-06-22 21:33:38.690 - debug: smartmeter.0 (26633) MATCH-RESULT SIGNON: "" -> null
2022-06-22 21:33:45.867 - debug: smartmeter.0 (26633) NEW DATA
2022-06-22 21:33:45.868 - debug: smartmeter.0 (26633) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-06-22 21:33:45.868 - debug: smartmeter.0 (26633) MATCH-RESULT SIGNON: "" -> null
2022-06-22 21:34:00.308 - debug: smartmeter.0 (26633) NEW DATA
2022-06-22 21:34:00.309 - debug: smartmeter.0 (26633) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-06-22 21:34:00.309 - debug: smartmeter.0 (26633) MATCH-RESULT SIGNON: "" -> null
2022-06-22 21:34:07.474 - debug: smartmeter.0 (26633) NEW DATA
2022-06-22 21:34:07.475 - debug: smartmeter.0 (26633) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-06-22 21:34:07.475 - debug: smartmeter.0 (26633) MATCH-RESULT SIGNON: "" -> null
2022-06-22 21:34:14.680 - debug: smartmeter.0 (26633) NEW DATA
2022-06-22 21:34:14.681 - debug: smartmeter.0 (26633) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-06-22 21:34:14.681 - debug: smartmeter.0 (26633) MATCH-RESULT SIGNON: "" -> null
2022-06-22 21:34:21.858 - debug: smartmeter.0 (26633) NEW DATA
2022-06-22 21:34:21.858 - debug: smartmeter.0 (26633) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-06-22 21:34:21.859 - debug: smartmeter.0 (26633) MATCH-RESULT SIGNON: "" -> null
2022-06-22 21:34:27.942 - info: deconz.0 (2025) State value to set for "deconz.0.sensors.00158d0004447da4.pending" has to be stringified but received type "object"
2022-06-22 21:34:29.043 - debug: smartmeter.0 (26633) NEW DATA
2022-06-22 21:34:29.043 - debug: smartmeter.0 (26633) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-06-22 21:34:29.044 - debug: smartmeter.0 (26633) MATCH-RESULT SIGNON: "" -> null
2022-06-22 21:34:43.433 - debug: smartmeter.0 (26633) NEW DATA
2022-06-22 21:34:43.434 - debug: smartmeter.0 (26633) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-06-22 21:34:43.434 - debug: smartmeter.0 (26633) MATCH-RESULT SIGNON: "" -> null
2022-06-22 21:34:54.185 - debug: smartmeter.0 (26633) MESSAGE TIMEOUT TRIGGERED
2022-06-22 21:34:54.186 - debug: smartmeter.0 (26633) Error: No or too long answer from Serial Device after last request.
2022-06-22 21:34:54.187 - warn: smartmeter.0 (26633) No or too long answer from Serial Device after last request.
2022-06-22 21:34:54.187 - debug: smartmeter.0 (26633) Error: No or too long answer from Serial Device after last request.
2022-06-22 21:34:54.188 - debug: smartmeter.0 (26633) Transport Reset!! Restart = true
2022-06-22 21:34:54.188 - debug: smartmeter.0 (26633) STOP
2022-06-22 21:34:54.189 - debug: smartmeter.0 (26633) CLEAR MESSAGE TIMEOUT TIMER
2022-06-22 21:34:54.192 - debug: smartmeter.0 (26633) SERIALPORT CLOSE
2022-06-22 21:34:54.192 - debug: smartmeter.0 (26633) SERIALPORT REMOVE LISTENERS
2022-06-22 21:34:54.193 - debug: smartmeter.0 (26633) CURRENT SIGNON MESSAGE COUNTER 1 OF 1
2022-06-22 21:34:54.194 - debug: smartmeter.0 (26633) DELETE rest of data (0) because new Message start with a new Request Message
2022-06-22 21:34:54.194 - debug: smartmeter.0 (26633) SCHEDULE NEXT RUN IN 300000s

apollon77

@fanatikz Ok, also am Ende antwortet das gerät aktuell nichts .. aber das kann ja sein weil Du oben noch was von ner besonderen Logon Message geschrieben hattest. Diese "000" ... jetzt ist nur die Frage was das ist.

Du kannst mal versuchen in Wake up Zeichen eine 3 zu schreiben das sollte 3x0 sein was er dann sendet. Dann Debug zeigen nochmal.

Alternativ schreib die 000 in "Device address". Leider sind da die Volksaehler infos alles andere als eindeutig

Stoffel

Hallo Zusammen,

kurze Frage gibt es auch eine Möglichkeit den Smart Meter Interface von Tasmota mit dem Adapter auszulesen?

Grüße

Stoffel

klassisch

@stoffel Ich kenne die Tasmota Smartmeter-Geschichte nicht aus eigener Ansicht. Aber so weit ich das bisher gelesen habe, wird dort auf MQTT ausgegeben. Dann sind die Daten ja auch im ioBroker und der Smartmeter Adapter wird in dieser Konfiguration nicht gebraucht.
Es gibt wohl auch die Möglichkeiten ser2net auf ESPEasy oder auch Tasmota zu betreiben. Damit könnte man auch via TCP an den smartmeter-Adapter einzuliefern. Bei der ESPEasy-Lösung steht ein Stabilitätsvorbehalt in den Unterlagen.
So ähnlich mache ich das, aber mit Geräten von USRIOT und über LAN. Das ist sehr stabil.

Stoffel

Danke für deine Rückmeldung, ja ich habe die Daten bereits per MQTT im IOBroker.

Was mir aktuell nur sehr schwer fällt ist das parsen um den String in einzelne Daten Objekte zu bekommen, da würde mir der Adapter die Arbeit abnehmen :).

Grüße

Stoffel

klassisch

@stoffel Welche Form hat der String? Ist das ein JSON, wie man das bei MQTT ab und an sieht, z.B.

{
  "value": 49.93000030517578
}

Dann gäbe es eine JScript Funktion

JSON.parse()

Einige Hinweise dazu bei https://wiki.selfhtml.org/wiki/JSON/parse
oder https://www.smarthome-tricks.de/software-iobroker/iobroker-javascript-json-verarbeiten/

Scheint es auch in Blockly zu geben, sagt zumindest eine Suchmaschine.

Stoffel

@klassisch jupp

{
  "Time": "2022-06-27T17:30:36",
  "PV ": {
    "total_in": 189799.2,
    "Power_curr": -1085
  },
  "Haus": {
    "total_in2": 142935.78,
    "Power_curr2": 31
  }
}

klassisch

@stoffel Dann viel Erfolg mit JSON.parse()
Notfalls noch etwas im Forum suchen oder einen anderen Thread eröffnen etwa: "MQTT JSON parsen - wie?"

apollon77

@stoffel bei dem Format wäre der Adapter null Hilfe weil das kennt er nicht. Und ja: simples json. Ist besser via JavaScript Adapter.

disaster123

Moin moin ihr lieben - wie finde ich denn rau welche HW ich für meinen EMH eHZ Zähler brauche?

klassisch

@disaster123 sagte in Adapter "smartmeter":

Moin moin ihr lieben - wie finde ich denn rau welche HW ich für meinen EMH eHZ Zähler brauche?

Falls es sich um eine moderne Meßeinrichtung mit optischer Infoschnittstelle handelt, gibt es einen recht ausführlichen Guide mit einigen verschiedenen aber konkreten Lösungswegen. Selbstbau, Fertiggeräte, USB, Netzwerk (TCP) alles drin.

firefighter166

Hallo zusammen,

ich versuche seit einigen Stunden hier einen Schellcount EZZ3 Drehstromzähler auszulesen und bin echt am verzweifeln.

Kann mir jemand die Konfiguration für diesen Zähler bereitstellen ?

Ich weiß nur das der Zähler aktiv angesprochen werden muss um das er seine aktuellen Werte heraus gibt.

apollon77

@firefighter166 Ok, was hast Du denn eingestellt bisher?

Also Wenn er angesprochen werden muss ist es wohl D0 als Proptokoll, genauso bidirektionale konfiguration. Mach mal eine neue Instanz (also ggf löschen - will verhindern das Du was verstellt hast!)
Dann dort NUR die zwei genannten Settings ändern.

Dann bitte Log zeigen

firefighter166

@apollon77 said in Adapter "smartmeter":

Dann dort NUR die zwei genannten Settings ändern.

Hier mal der Log und die aktuelle Konfiguration:

2022-07-08 11:49:48.777 - info: smartmeter.0 (1210) starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.smartmeter, node: v12.22.11, js-controller: 4.0.21
2022-07-08 11:49:48.904 - error: smartmeter.0 (1210) Serial port device is undefined, check your configuration!
2022-07-08 11:49:48.975 - debug: smartmeter.0 (1210) connected set to false
2022-07-08 11:49:49.809 - debug: smartmeter.0 (1210) Message received = {"command":"listUart","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":326,"ack":false,"time":1657273783753},"_id":99950031}
2022-07-08 11:49:50.455 - info: smartmeter.0 (1210) List of port: [{"path":"/dev/ttyAMA0"},{"path":"/dev/ttyUSB1","manufacturer":"Silicon Labs","serialNumber":"0030","pnpId":"usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0030-if00-port0","vendorId":"10c4","productId":"ea60"},{"path":"/dev/ttyUSB0","manufacturer":"Silicon Labs","serialNumber":"0023","pnpId":"usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0023-if00-port0","vendorId":"10c4","productId":"ea60"}]
2022-07-08 11:50:16.559 - info: host.slavestrom stopInstance system.adapter.smartmeter.0 (force=false, process=true)
2022-07-08 11:50:16.568 - info: host.slavestrom stopInstance system.adapter.smartmeter.0 send kill signal
2022-07-08 11:50:16.569 - info: smartmeter.0 (1210) Got terminate signal TERMINATE_YOURSELF
2022-07-08 11:50:16.575 - info: smartmeter.0 (1210) terminating
2022-07-08 11:50:16.579 - debug: smartmeter.0 (1210) Plugin sentry destroyed
2022-07-08 11:50:16.581 - info: smartmeter.0 (1210) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-07-08 11:50:17.327 - info: host.slavestrom instance system.adapter.smartmeter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-07-08 11:50:19.794 - info: host.slavestrom instance system.adapter.smartmeter.0 started with pid 1229
2022-07-08 11:50:24.994 - debug: smartmeter.0 (1229) Redis Objects: Use Redis connection: 10.0.1.126:9001
2022-07-08 11:50:25.106 - debug: smartmeter.0 (1229) Objects client ready ... initialize now
2022-07-08 11:50:25.113 - debug: smartmeter.0 (1229) Objects create System PubSub Client
2022-07-08 11:50:25.118 - debug: smartmeter.0 (1229) Objects create User PubSub Client
2022-07-08 11:50:25.197 - debug: smartmeter.0 (1229) Objects client initialize lua scripts
2022-07-08 11:50:25.216 - debug: smartmeter.0 (1229) Objects connected to redis: 10.0.1.126:9001
2022-07-08 11:50:25.295 - debug: smartmeter.0 (1229) Redis States: Use Redis connection: 10.0.1.126:9000
2022-07-08 11:50:25.325 - debug: smartmeter.0 (1229) States create System PubSub Client
2022-07-08 11:50:25.330 - debug: smartmeter.0 (1229) States create User PubSub Client
2022-07-08 11:50:25.371 - debug: smartmeter.0 (1229) States connected to redis: 10.0.1.126:9000
2022-07-08 11:50:25.586 - debug: smartmeter.0 (1229) Plugin sentry Initialize Plugin (enabled=true)
2022-07-08 11:50:26.437 - info: smartmeter.0 (1229) starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.smartmeter, node: v12.22.11, js-controller: 4.0.21
2022-07-08 11:50:26.564 - debug: smartmeter.0 (1229) SmartmeterObis options: {"debug":2,"protocol":"D0Protocol","transport":"SerialRequestResponseTransport","requestInterval":"300","anotherQueryDelay":"1000","transportSerialPort":"/dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0030-if00-port0","transportSerialBaudrate":null,"transportSerialMessageTimeout":null,"protocolD0WakeupCharacters":0}
2022-07-08 11:50:26.573 - debug: smartmeter.0 (1229) CREATE SERIALPORT: 300 7 1 even
2022-07-08 11:50:26.593 - debug: smartmeter.0 (1229) SERIALPORT OPEN
2022-07-08 11:50:26.635 - debug: smartmeter.0 (1229) SERIALPORT RESET BAUDRATE TO 300
2022-07-08 11:50:26.643 - debug: smartmeter.0 (1229) INITIAL MESSAGES TO SEND: 2
2022-07-08 11:50:26.646 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 0 IN GETNEXTMESSAGE
2022-07-08 11:50:26.649 - debug: smartmeter.0 (1229) TO SEND 2:
2022-07-08 11:50:26.650 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 1 IN GETNEXTMESSAGE
2022-07-08 11:50:26.652 - debug: smartmeter.0 (1229) TO SEND 1: /?!
2022-07-08 11:50:26.702 - debug: smartmeter.0 (1229) connected set to false
2022-07-08 11:50:26.819 - debug: smartmeter.0 (1229) DONE SEND 1
2022-07-08 11:50:26.863 - debug: smartmeter.0 (1229) NEW DATA
2022-07-08 11:50:26.867 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-07-08 11:50:26.869 - debug: smartmeter.0 (1229) MATCH-RESULT SIGNON: "/" -> null
2022-07-08 11:50:26.897 - debug: smartmeter.0 (1229) NEW DATA
2022-07-08 11:50:26.899 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-07-08 11:50:26.900 - debug: smartmeter.0 (1229) MATCH-RESULT SIGNON: "/A" -> null
2022-07-08 11:50:26.933 - debug: smartmeter.0 (1229) NEW DATA
2022-07-08 11:50:26.935 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-07-08 11:50:26.937 - debug: smartmeter.0 (1229) MATCH-RESULT SIGNON: "/AE" -> null
2022-07-08 11:50:26.970 - debug: smartmeter.0 (1229) NEW DATA
2022-07-08 11:50:26.972 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-07-08 11:50:26.973 - debug: smartmeter.0 (1229) MATCH-RESULT SIGNON: "/AEL" -> null
2022-07-08 11:50:27.006 - debug: smartmeter.0 (1229) NEW DATA
2022-07-08 11:50:27.008 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-07-08 11:50:27.009 - debug: smartmeter.0 (1229) MATCH-RESULT SIGNON: "/AEL4" -> null
2022-07-08 11:50:27.042 - debug: smartmeter.0 (1229) NEW DATA
2022-07-08 11:50:27.044 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-07-08 11:50:27.046 - debug: smartmeter.0 (1229) MATCH-RESULT SIGNON: "/AEL4<" -> null
2022-07-08 11:50:27.073 - debug: smartmeter.0 (1229) DONE SEND 0
2022-07-08 11:50:27.076 - debug: smartmeter.0 (1229) SET MESSAGE TIMEOUT TIMER2: 120000
2022-07-08 11:50:27.082 - debug: smartmeter.0 (1229) NEW DATA
2022-07-08 11:50:27.083 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-07-08 11:50:27.085 - debug: smartmeter.0 (1229) MATCH-RESULT SIGNON: "/AEL4<1" -> null
2022-07-08 11:50:27.115 - debug: smartmeter.0 (1229) NEW DATA
2022-07-08 11:50:27.117 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-07-08 11:50:27.118 - debug: smartmeter.0 (1229) MATCH-RESULT SIGNON: "/AEL4<1>" -> null
2022-07-08 11:50:27.153 - debug: smartmeter.0 (1229) NEW DATA
2022-07-08 11:50:27.154 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-07-08 11:50:27.156 - debug: smartmeter.0 (1229) MATCH-RESULT SIGNON: "/AEL4<1>A" -> null
2022-07-08 11:50:27.189 - debug: smartmeter.0 (1229) NEW DATA
2022-07-08 11:50:27.191 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-07-08 11:50:27.192 - debug: smartmeter.0 (1229) MATCH-RESULT SIGNON: "/AEL4<1>AE" -> null
2022-07-08 11:50:27.225 - debug: smartmeter.0 (1229) NEW DATA
2022-07-08 11:50:27.227 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-07-08 11:50:27.229 - debug: smartmeter.0 (1229) MATCH-RESULT SIGNON: "/AEL4<1>AEL" -> null
2022-07-08 11:50:27.262 - debug: smartmeter.0 (1229) NEW DATA
2022-07-08 11:50:27.264 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-07-08 11:50:27.265 - debug: smartmeter.0 (1229) MATCH-RESULT SIGNON: "/AEL4<1>AEL." -> null
2022-07-08 11:50:27.298 - debug: smartmeter.0 (1229) NEW DATA
2022-07-08 11:50:27.300 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-07-08 11:50:27.301 - debug: smartmeter.0 (1229) MATCH-RESULT SIGNON: "/AEL4<1>AEL.T" -> null
2022-07-08 11:50:27.334 - debug: smartmeter.0 (1229) NEW DATA
2022-07-08 11:50:27.336 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-07-08 11:50:27.338 - debug: smartmeter.0 (1229) MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF" -> null
2022-07-08 11:50:27.372 - debug: smartmeter.0 (1229) NEW DATA
2022-07-08 11:50:27.374 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-07-08 11:50:27.375 - debug: smartmeter.0 (1229) MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF." -> null
2022-07-08 11:50:27.408 - debug: smartmeter.0 (1229) NEW DATA
2022-07-08 11:50:27.410 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-07-08 11:50:27.412 - debug: smartmeter.0 (1229) MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF.1" -> null
2022-07-08 11:50:27.445 - debug: smartmeter.0 (1229) NEW DATA
2022-07-08 11:50:27.447 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-07-08 11:50:27.448 - debug: smartmeter.0 (1229) MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF.16" -> null
2022-07-08 11:50:27.481 - debug: smartmeter.0 (1229) NEW DATA
2022-07-08 11:50:27.483 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-07-08 11:50:27.484 - debug: smartmeter.0 (1229) MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF.16-" -> null
2022-07-08 11:50:27.518 - debug: smartmeter.0 (1229) NEW DATA
2022-07-08 11:50:27.519 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-07-08 11:50:27.521 - debug: smartmeter.0 (1229) MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF.16-2" -> null
2022-07-08 11:50:27.555 - debug: smartmeter.0 (1229) NEW DATA
2022-07-08 11:50:27.557 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-07-08 11:50:27.558 - debug: smartmeter.0 (1229) MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF.16-2\r" -> null
2022-07-08 11:50:27.592 - debug: smartmeter.0 (1229) NEW DATA
2022-07-08 11:50:27.593 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 2 IN CHECKMESSAGE
2022-07-08 11:50:27.595 - debug: smartmeter.0 (1229) MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF.16-2\r\n" -> ["/AEL4<1>AEL.TF.16-2\r\n","/AEL4<1>AEL.TF.16-2"]
2022-07-08 11:50:27.596 - debug: smartmeter.0 (1229) PAUSE READING SERIALPORT TO HANDLE MESSAGE
2022-07-08 11:50:27.598 - debug: smartmeter.0 (1229) CLEAR MESSAGE TIMEOUT TIMER
2022-07-08 11:50:27.601 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 2 IN HANDLEMESSAGE
2022-07-08 11:50:27.604 - debug: smartmeter.0 (1229) LEFT AFTER HANDLE-MESSAGE 0
2022-07-08 11:50:27.606 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 3 IN ISPROCESSCOMPLETE: false
2022-07-08 11:50:27.608 - debug: smartmeter.0 (1229) ALL MESSAGES TO SEND: 2
2022-07-08 11:50:27.860 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 3 IN GETNEXTMESSAGE
2022-07-08 11:50:27.863 - debug: smartmeter.0 (1229) TO SEND 2: 040
2022-07-08 11:50:28.069 - debug: smartmeter.0 (1229) DONE SEND 2
2022-07-08 11:50:28.321 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 4 IN GETNEXTMESSAGE
2022-07-08 11:50:28.323 - debug: smartmeter.0 (1229) BAUD CHANGEOVER TO 4800 baud
2022-07-08 11:50:28.328 - debug: smartmeter.0 (1229) BAUD CHANGEOVER DONE
2022-07-08 11:50:28.329 - debug: smartmeter.0 (1229) TO SEND 1:
2022-07-08 11:50:28.331 - debug: smartmeter.0 (1229) DONE SEND 0
2022-07-08 11:50:28.333 - debug: smartmeter.0 (1229) RESUME READING SERIALPORT IN FINALIZE
2022-07-08 11:50:28.334 - debug: smartmeter.0 (1229) SET MESSAGE TIMEOUT TIMER: 120000
2022-07-08 11:50:28.335 - debug: smartmeter.0 (1229) CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false
2022-07-08 11:50:28.336 - debug: smartmeter.0 (1229) REMAINING DATA AFTER MESSAGE HANDLING:
2022-07-08 11:50:28.338 - debug: smartmeter.0 (1229) END FINALIZE

2022-07-08 11_54_14-instances - slavestrom.png

klassisch

[Teil-OT]
Für alle, die beim Einblinken der PIN in die moderne Messeinrichtung keine große Freude haben: Mittlerweile gibt es eine App "mME Stromzähler - praktisches Blinken" von Jan Wittler, mit der man die PIN automatisiert einblinken kann. Allerdings muß man immer noch manuell kontrollieren, ob die Info Schnittstelle auch freigeschaltet ist. Etliche Zähler erfordern noch diesen Schritt.

Community Forum

NEWS

Adapter "smartmeter"

Support us

741

32.4k

81.4k

1.3m