UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[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

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

[apollon77]

@firefighter166 Ja... und dann? Das sieht erstmal ok aus .. Er senden Sign-On, dein Zähler ANtwortet und sagt "switche mal auf 4800baud" ... das tun wird. Dann sollte der Zähler kurz darauf weiter senden ... da ist Dein Log aber zuende :-)

[firefighter166]

@apollon77 Ich bekomme den Adapter nicht grün und es werden halt auch keine Werte heraus gegeben. Wo liegt hier denn der Fehler ?

Hier nochmal die vollständige Log:

smartmeter.0
2022-07-09 15:29:52.153	debug	END FINALIZE

smartmeter.0
2022-07-09 15:29:52.153	debug	REMAINING DATA AFTER MESSAGE HANDLING:

smartmeter.0
2022-07-09 15:29:52.152	debug	CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false

smartmeter.0
2022-07-09 15:29:52.151	debug	SET MESSAGE TIMEOUT TIMER: 120000

smartmeter.0
2022-07-09 15:29:52.150	debug	RESUME READING SERIALPORT IN FINALIZE

smartmeter.0
2022-07-09 15:29:52.149	debug	DONE SEND 0

smartmeter.0
2022-07-09 15:29:52.147	debug	TO SEND 1:

smartmeter.0
2022-07-09 15:29:52.146	debug	BAUD CHANGEOVER DONE

smartmeter.0
2022-07-09 15:29:52.142	debug	BAUD CHANGEOVER TO 4800 baud

smartmeter.0
2022-07-09 15:29:52.140	debug	CURRENT PROCESS STEP 4 IN GETNEXTMESSAGE

smartmeter.0
2022-07-09 15:29:51.888	debug	DONE SEND 2

smartmeter.0
2022-07-09 15:29:51.685	debug	TO SEND 2: 040

smartmeter.0
2022-07-09 15:29:51.682	debug	CURRENT PROCESS STEP 3 IN GETNEXTMESSAGE

smartmeter.0
2022-07-09 15:29:51.431	debug	ALL MESSAGES TO SEND: 2

smartmeter.0
2022-07-09 15:29:51.430	debug	CURRENT PROCESS STEP 3 IN ISPROCESSCOMPLETE: false

smartmeter.0
2022-07-09 15:29:51.429	debug	LEFT AFTER HANDLE-MESSAGE 0

smartmeter.0
2022-07-09 15:29:51.427	debug	CURRENT PROCESS STEP 2 IN HANDLEMESSAGE

smartmeter.0
2022-07-09 15:29:51.426	debug	CLEAR MESSAGE TIMEOUT TIMER

smartmeter.0
2022-07-09 15:29:51.425	debug	PAUSE READING SERIALPORT TO HANDLE MESSAGE

smartmeter.0
2022-07-09 15:29:51.424	debug	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"]

smartmeter.0
2022-07-09 15:29:51.423	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:29:51.422	debug	NEW DATA

smartmeter.0
2022-07-09 15:29:51.388	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF.16-2\r" -> null

smartmeter.0
2022-07-09 15:29:51.387	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:29:51.385	debug	NEW DATA

smartmeter.0
2022-07-09 15:29:51.351	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF.16-2" -> null

smartmeter.0
2022-07-09 15:29:51.350	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:29:51.348	debug	NEW DATA

smartmeter.0
2022-07-09 15:29:51.314	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF.16-" -> null

smartmeter.0
2022-07-09 15:29:51.313	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:29:51.311	debug	NEW DATA

smartmeter.0
2022-07-09 15:29:51.278	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF.16" -> null

smartmeter.0
2022-07-09 15:29:51.277	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:29:51.275	debug	NEW DATA

smartmeter.0
2022-07-09 15:29:51.242	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF.1" -> null

smartmeter.0
2022-07-09 15:29:51.241	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:29:51.239	debug	NEW DATA

smartmeter.0
2022-07-09 15:29:51.205	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF." -> null

smartmeter.0
2022-07-09 15:29:51.204	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:29:51.202	debug	NEW DATA

smartmeter.0
2022-07-09 15:29:51.169	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF" -> null

smartmeter.0
2022-07-09 15:29:51.168	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:29:51.166	debug	NEW DATA

smartmeter.0
2022-07-09 15:29:51.131	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.T" -> null

smartmeter.0
2022-07-09 15:29:51.130	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:29:51.128	debug	NEW DATA

smartmeter.0
2022-07-09 15:29:51.096	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL." -> null

smartmeter.0
2022-07-09 15:29:51.095	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:29:51.094	debug	NEW DATA

smartmeter.0
2022-07-09 15:29:51.058	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL" -> null

smartmeter.0
2022-07-09 15:29:51.057	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:29:51.055	debug	NEW DATA

smartmeter.0
2022-07-09 15:29:51.022	debug	MATCH-RESULT SIGNON: "/AEL4<1>AE" -> null

smartmeter.0
2022-07-09 15:29:51.021	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:29:51.019	debug	NEW DATA

smartmeter.0
2022-07-09 15:29:50.985	debug	MATCH-RESULT SIGNON: "/AEL4<1>A" -> null

smartmeter.0
2022-07-09 15:29:50.984	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:29:50.983	debug	NEW DATA

smartmeter.0
2022-07-09 15:29:50.949	debug	MATCH-RESULT SIGNON: "/AEL4<1>" -> null

smartmeter.0
2022-07-09 15:29:50.948	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:29:50.946	debug	NEW DATA

smartmeter.0
2022-07-09 15:29:50.911	debug	MATCH-RESULT SIGNON: "/AEL4<1" -> null

smartmeter.0
2022-07-09 15:29:50.910	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:29:50.909	debug	NEW DATA

smartmeter.0
2022-07-09 15:29:50.901	debug	SET MESSAGE TIMEOUT TIMER2: 120000

smartmeter.0
2022-07-09 15:29:50.900	debug	DONE SEND 0

smartmeter.0
2022-07-09 15:29:50.875	debug	MATCH-RESULT SIGNON: "/AEL4<" -> null

smartmeter.0
2022-07-09 15:29:50.874	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:29:50.872	debug	NEW DATA

smartmeter.0
2022-07-09 15:29:50.839	debug	MATCH-RESULT SIGNON: "/AEL4" -> null

smartmeter.0
2022-07-09 15:29:50.838	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:29:50.836	debug	NEW DATA

smartmeter.0
2022-07-09 15:29:50.802	debug	MATCH-RESULT SIGNON: "/AEL" -> null

smartmeter.0
2022-07-09 15:29:50.801	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:29:50.800	debug	NEW DATA

smartmeter.0
2022-07-09 15:29:50.766	debug	MATCH-RESULT SIGNON: "/AE" -> null

smartmeter.0
2022-07-09 15:29:50.765	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:29:50.763	debug	NEW DATA

smartmeter.0
2022-07-09 15:29:50.729	debug	MATCH-RESULT SIGNON: "/A" -> null

smartmeter.0
2022-07-09 15:29:50.727	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:29:50.726	debug	NEW DATA

smartmeter.0
2022-07-09 15:29:50.693	debug	MATCH-RESULT SIGNON: "/" -> null

smartmeter.0
2022-07-09 15:29:50.692	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:29:50.689	debug	NEW DATA

smartmeter.0
2022-07-09 15:29:50.648	debug	DONE SEND 1

smartmeter.0
2022-07-09 15:29:50.488	debug	TO SEND 1: /?!

smartmeter.0
2022-07-09 15:29:50.487	debug	CURRENT PROCESS STEP 1 IN GETNEXTMESSAGE

smartmeter.0
2022-07-09 15:29:50.486	debug	TO SEND 2:

smartmeter.0
2022-07-09 15:29:50.484	debug	CURRENT PROCESS STEP 0 IN GETNEXTMESSAGE

smartmeter.0
2022-07-09 15:29:50.483	debug	INITIAL MESSAGES TO SEND: 2

smartmeter.0
2022-07-09 15:29:50.480	debug	SERIALPORT RESET BAUDRATE TO 300

smartmeter.0
2022-07-09 15:29:50.476	debug	SERIALPORT OPEN

smartmeter.0
2022-07-09 15:29:50.466	debug	CREATE SERIALPORT: 300 7 1 even

smartmeter.0
2022-07-09 15:26:50.446	debug	END FINALIZE

smartmeter.0
2022-07-09 15:26:50.445	debug	REMAINING DATA AFTER MESSAGE HANDLING:

smartmeter.0
2022-07-09 15:26:50.444	debug	CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false

smartmeter.0
2022-07-09 15:26:50.443	debug	SET MESSAGE TIMEOUT TIMER: 120000

smartmeter.0
2022-07-09 15:26:50.442	debug	RESUME READING SERIALPORT IN FINALIZE

smartmeter.0
2022-07-09 15:26:50.441	debug	DONE SEND 0

smartmeter.0
2022-07-09 15:26:50.440	debug	TO SEND 1:

smartmeter.0
2022-07-09 15:26:50.438	debug	BAUD CHANGEOVER DONE

smartmeter.0
2022-07-09 15:26:50.434	debug	BAUD CHANGEOVER TO 4800 baud

smartmeter.0
2022-07-09 15:26:50.432	debug	CURRENT PROCESS STEP 4 IN GETNEXTMESSAGE

smartmeter.0
2022-07-09 15:26:50.179	debug	DONE SEND 2

smartmeter.0
2022-07-09 15:26:49.983	debug	TO SEND 2: 040

smartmeter.0
2022-07-09 15:26:49.981	debug	CURRENT PROCESS STEP 3 IN GETNEXTMESSAGE

smartmeter.0
2022-07-09 15:26:49.730	debug	ALL MESSAGES TO SEND: 2

smartmeter.0
2022-07-09 15:26:49.729	debug	CURRENT PROCESS STEP 3 IN ISPROCESSCOMPLETE: false

smartmeter.0
2022-07-09 15:26:49.727	debug	LEFT AFTER HANDLE-MESSAGE 0

smartmeter.0
2022-07-09 15:26:49.726	debug	CURRENT PROCESS STEP 2 IN HANDLEMESSAGE

smartmeter.0
2022-07-09 15:26:49.725	debug	CLEAR MESSAGE TIMEOUT TIMER

smartmeter.0
2022-07-09 15:26:49.724	debug	PAUSE READING SERIALPORT TO HANDLE MESSAGE

smartmeter.0
2022-07-09 15:26:49.723	debug	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"]

smartmeter.0
2022-07-09 15:26:49.722	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:26:49.720	debug	NEW DATA

smartmeter.0
2022-07-09 15:26:49.686	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF.16-2\r" -> null

smartmeter.0
2022-07-09 15:26:49.685	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:26:49.683	debug	NEW DATA

smartmeter.0
2022-07-09 15:26:49.650	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF.16-2" -> null

smartmeter.0
2022-07-09 15:26:49.649	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:26:49.647	debug	NEW DATA

smartmeter.0
2022-07-09 15:26:49.614	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF.16-" -> null

smartmeter.0
2022-07-09 15:26:49.613	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:26:49.611	debug	NEW DATA

smartmeter.0
2022-07-09 15:26:49.576	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF.16" -> null

smartmeter.0
2022-07-09 15:26:49.575	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:26:49.573	debug	NEW DATA

smartmeter.0
2022-07-09 15:26:49.540	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF.1" -> null

smartmeter.0
2022-07-09 15:26:49.539	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:26:49.537	debug	NEW DATA

smartmeter.0
2022-07-09 15:26:49.503	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF." -> null

smartmeter.0
2022-07-09 15:26:49.502	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:26:49.500	debug	NEW DATA

smartmeter.0
2022-07-09 15:26:49.467	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF" -> null

smartmeter.0
2022-07-09 15:26:49.466	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:26:49.464	debug	NEW DATA

smartmeter.0
2022-07-09 15:26:49.431	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.T" -> null

smartmeter.0
2022-07-09 15:26:49.430	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:26:49.428	debug	NEW DATA

smartmeter.0
2022-07-09 15:26:49.394	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL." -> null

smartmeter.0
2022-07-09 15:26:49.393	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:26:49.391	debug	NEW DATA

smartmeter.0
2022-07-09 15:26:49.357	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL" -> null

smartmeter.0
2022-07-09 15:26:49.355	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:26:49.353	debug	NEW DATA

smartmeter.0
2022-07-09 15:26:49.323	debug	MATCH-RESULT SIGNON: "/AEL4<1>AE" -> null

smartmeter.0
2022-07-09 15:26:49.321	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:26:49.317	debug	NEW DATA

smartmeter.0
2022-07-09 15:26:49.284	debug	MATCH-RESULT SIGNON: "/AEL4<1>A" -> null

smartmeter.0
2022-07-09 15:26:49.283	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:26:49.281	debug	NEW DATA

smartmeter.0
2022-07-09 15:26:49.248	debug	MATCH-RESULT SIGNON: "/AEL4<1>" -> null

smartmeter.0
2022-07-09 15:26:49.246	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:26:49.244	debug	NEW DATA

smartmeter.0
2022-07-09 15:26:49.213	debug	MATCH-RESULT SIGNON: "/AEL4<1" -> null

smartmeter.0
2022-07-09 15:26:49.211	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:26:49.209	debug	NEW DATA

smartmeter.0
2022-07-09 15:26:49.204	debug	SET MESSAGE TIMEOUT TIMER2: 120000

smartmeter.0
2022-07-09 15:26:49.203	debug	DONE SEND 0

smartmeter.0
2022-07-09 15:26:49.174	debug	MATCH-RESULT SIGNON: "/AEL4<" -> null

smartmeter.0
2022-07-09 15:26:49.172	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:26:49.170	debug	NEW DATA

smartmeter.0
2022-07-09 15:26:49.137	debug	MATCH-RESULT SIGNON: "/AEL4" -> null

smartmeter.0
2022-07-09 15:26:49.136	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:26:49.134	debug	NEW DATA

smartmeter.0
2022-07-09 15:26:49.101	debug	MATCH-RESULT SIGNON: "/AEL" -> null

smartmeter.0
2022-07-09 15:26:49.100	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:26:49.098	debug	NEW DATA

smartmeter.0
2022-07-09 15:26:49.064	debug	MATCH-RESULT SIGNON: "/AE" -> null

smartmeter.0
2022-07-09 15:26:49.063	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:26:49.061	debug	NEW DATA

smartmeter.0
2022-07-09 15:26:49.028	debug	MATCH-RESULT SIGNON: "/A" -> null

smartmeter.0
2022-07-09 15:26:49.027	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:26:49.025	debug	NEW DATA

smartmeter.0
2022-07-09 15:26:48.993	debug	MATCH-RESULT SIGNON: "/" -> null

smartmeter.0
2022-07-09 15:26:48.991	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:26:48.989	debug	NEW DATA

smartmeter.0
2022-07-09 15:26:48.949	debug	DONE SEND 1

smartmeter.0
2022-07-09 15:26:48.785	debug	TO SEND 1: /?!

smartmeter.0
2022-07-09 15:26:48.783	debug	CURRENT PROCESS STEP 1 IN GETNEXTMESSAGE

smartmeter.0
2022-07-09 15:26:48.782	debug	TO SEND 2:

smartmeter.0
2022-07-09 15:26:48.781	debug	CURRENT PROCESS STEP 0 IN GETNEXTMESSAGE

smartmeter.0
2022-07-09 15:26:48.779	debug	INITIAL MESSAGES TO SEND: 2

smartmeter.0
2022-07-09 15:26:48.776	debug	SERIALPORT RESET BAUDRATE TO 300

smartmeter.0
2022-07-09 15:26:48.772	debug	SERIALPORT OPEN

smartmeter.0
2022-07-09 15:26:48.762	debug	CREATE SERIALPORT: 300 7 1 even

smartmeter.0
2022-07-09 15:25:48.758	debug	SCHEDULE NEXT RUN IN 60000s

smartmeter.0
2022-07-09 15:25:48.757	debug	DELETE rest of data (0) because new Message start with a new Request Message

smartmeter.0
2022-07-09 15:25:48.756	debug	CURRENT SIGNON MESSAGE COUNTER 1 OF 1

smartmeter.0
2022-07-09 15:25:48.752	debug	SERIALPORT REMOVE LISTENERS

smartmeter.0
2022-07-09 15:25:48.750	debug	SERIALPORT CLOSE

smartmeter.0
2022-07-09 15:25:48.743	debug	CLEAR MESSAGE TIMEOUT TIMER

smartmeter.0
2022-07-09 15:25:48.742	debug	STOP

smartmeter.0
2022-07-09 15:25:48.740	debug	Transport Reset!! Restart = true

smartmeter.0
2022-07-09 15:25:48.739	debug	Error: No or too long answer from Serial Device after last request.

smartmeter.0
2022-07-09 15:25:48.737	warn	No or too long answer from Serial Device after last request.

smartmeter.0
2022-07-09 15:25:48.732	debug	Error: No or too long answer from Serial Device after last request.

smartmeter.0
2022-07-09 15:25:48.728	debug	MESSAGE TIMEOUT TRIGGERED

smartmeter.0
2022-07-09 15:23:48.729	debug	END FINALIZE

smartmeter.0
2022-07-09 15:23:48.728	debug	REMAINING DATA AFTER MESSAGE HANDLING:

smartmeter.0
2022-07-09 15:23:48.727	debug	CURRENT PROCESS STEP 4 IN ISPROCESSCOMPLETE: false

smartmeter.0
2022-07-09 15:23:48.725	debug	SET MESSAGE TIMEOUT TIMER: 120000

smartmeter.0
2022-07-09 15:23:48.724	debug	RESUME READING SERIALPORT IN FINALIZE

smartmeter.0
2022-07-09 15:23:48.722	debug	DONE SEND 0

smartmeter.0
2022-07-09 15:23:48.721	debug	TO SEND 1:

smartmeter.0
2022-07-09 15:23:48.719	debug	BAUD CHANGEOVER DONE

smartmeter.0
2022-07-09 15:23:48.714	debug	BAUD CHANGEOVER TO 4800 baud

smartmeter.0
2022-07-09 15:23:48.712	debug	CURRENT PROCESS STEP 4 IN GETNEXTMESSAGE

smartmeter.0
2022-07-09 15:23:48.459	debug	DONE SEND 2

smartmeter.0
2022-07-09 15:23:48.260	debug	TO SEND 2: 040

smartmeter.0
2022-07-09 15:23:48.257	debug	CURRENT PROCESS STEP 3 IN GETNEXTMESSAGE

smartmeter.0
2022-07-09 15:23:48.005	debug	ALL MESSAGES TO SEND: 2

smartmeter.0
2022-07-09 15:23:48.004	debug	CURRENT PROCESS STEP 3 IN ISPROCESSCOMPLETE: false

smartmeter.0
2022-07-09 15:23:48.001	debug	LEFT AFTER HANDLE-MESSAGE 0

smartmeter.0
2022-07-09 15:23:47.989	debug	CURRENT PROCESS STEP 2 IN HANDLEMESSAGE

smartmeter.0
2022-07-09 15:23:47.987	debug	CLEAR MESSAGE TIMEOUT TIMER

smartmeter.0
2022-07-09 15:23:47.985	debug	PAUSE READING SERIALPORT TO HANDLE MESSAGE

smartmeter.0
2022-07-09 15:23:47.984	debug	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"]

smartmeter.0
2022-07-09 15:23:47.982	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:23:47.980	debug	NEW DATA

smartmeter.0
2022-07-09 15:23:47.947	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF.16-2\r" -> null

smartmeter.0
2022-07-09 15:23:47.946	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:23:47.944	debug	NEW DATA

smartmeter.0
2022-07-09 15:23:47.911	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF.16-2" -> null

smartmeter.0
2022-07-09 15:23:47.910	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:23:47.908	debug	NEW DATA

smartmeter.0
2022-07-09 15:23:47.874	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF.16-" -> null

smartmeter.0
2022-07-09 15:23:47.873	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:23:47.870	debug	NEW DATA

smartmeter.0
2022-07-09 15:23:47.838	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF.16" -> null

smartmeter.0
2022-07-09 15:23:47.836	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:23:47.834	debug	NEW DATA

smartmeter.0
2022-07-09 15:23:47.801	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF.1" -> null

smartmeter.0
2022-07-09 15:23:47.799	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:23:47.797	debug	NEW DATA

smartmeter.0
2022-07-09 15:23:47.764	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF." -> null

smartmeter.0
2022-07-09 15:23:47.763	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:23:47.761	debug	NEW DATA

smartmeter.0
2022-07-09 15:23:47.728	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.TF" -> null

smartmeter.0
2022-07-09 15:23:47.726	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:23:47.725	debug	NEW DATA

smartmeter.0
2022-07-09 15:23:47.691	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL.T" -> null

smartmeter.0
2022-07-09 15:23:47.690	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:23:47.688	debug	NEW DATA

smartmeter.0
2022-07-09 15:23:47.654	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL." -> null

smartmeter.0
2022-07-09 15:23:47.652	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:23:47.651	debug	NEW DATA

smartmeter.0
2022-07-09 15:23:47.617	debug	MATCH-RESULT SIGNON: "/AEL4<1>AEL" -> null

smartmeter.0
2022-07-09 15:23:47.616	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:23:47.614	debug	NEW DATA

smartmeter.0
2022-07-09 15:23:47.581	debug	MATCH-RESULT SIGNON: "/AEL4<1>AE" -> null

smartmeter.0
2022-07-09 15:23:47.580	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:23:47.578	debug	NEW DATA

smartmeter.0
2022-07-09 15:23:47.544	debug	MATCH-RESULT SIGNON: "/AEL4<1>A" -> null

smartmeter.0
2022-07-09 15:23:47.543	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:23:47.541	debug	NEW DATA

smartmeter.0
2022-07-09 15:23:47.508	debug	MATCH-RESULT SIGNON: "/AEL4<1>" -> null

smartmeter.0
2022-07-09 15:23:47.507	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:23:47.505	debug	NEW DATA

smartmeter.0
2022-07-09 15:23:47.475	debug	MATCH-RESULT SIGNON: "/AEL4<1" -> null

smartmeter.0
2022-07-09 15:23:47.474	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:23:47.472	debug	NEW DATA

smartmeter.0
2022-07-09 15:23:47.466	debug	SET MESSAGE TIMEOUT TIMER2: 120000

smartmeter.0
2022-07-09 15:23:47.463	debug	DONE SEND 0

smartmeter.0
2022-07-09 15:23:47.434	debug	MATCH-RESULT SIGNON: "/AEL4<" -> null

smartmeter.0
2022-07-09 15:23:47.433	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:23:47.431	debug	NEW DATA

smartmeter.0
2022-07-09 15:23:47.398	debug	MATCH-RESULT SIGNON: "/AEL4" -> null

smartmeter.0
2022-07-09 15:23:47.397	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:23:47.395	debug	NEW DATA

smartmeter.0
2022-07-09 15:23:47.362	debug	MATCH-RESULT SIGNON: "/AEL" -> null

smartmeter.0
2022-07-09 15:23:47.360	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:23:47.358	debug	NEW DATA

smartmeter.0
2022-07-09 15:23:47.325	debug	MATCH-RESULT SIGNON: "/AE" -> null

smartmeter.0
2022-07-09 15:23:47.324	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:23:47.322	debug	NEW DATA

smartmeter.0
2022-07-09 15:23:47.289	debug	MATCH-RESULT SIGNON: "/A" -> null

smartmeter.0
2022-07-09 15:23:47.288	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:23:47.286	debug	NEW DATA

smartmeter.0
2022-07-09 15:23:47.259	debug	MATCH-RESULT SIGNON: "/" -> null

smartmeter.0
2022-07-09 15:23:47.257	debug	CURRENT PROCESS STEP 2 IN CHECKMESSAGE

smartmeter.0
2022-07-09 15:23:47.253	debug	NEW DATA

smartmeter.0
2022-07-09 15:23:47.209	debug	DONE SEND 1

smartmeter.0
2022-07-09 15:23:47.073	debug	connected set to false

smartmeter.0
2022-07-09 15:23:47.042	debug	TO SEND 1: /?!

smartmeter.0
2022-07-09 15:23:47.040	debug	CURRENT PROCESS STEP 1 IN GETNEXTMESSAGE

smartmeter.0
2022-07-09 15:23:47.039	debug	TO SEND 2:

smartmeter.0
2022-07-09 15:23:47.036	debug	CURRENT PROCESS STEP 0 IN GETNEXTMESSAGE

smartmeter.0
2022-07-09 15:23:47.033	debug	INITIAL MESSAGES TO SEND: 2

smartmeter.0
2022-07-09 15:23:47.023	debug	SERIALPORT RESET BAUDRATE TO 300

smartmeter.0
2022-07-09 15:23:46.979	debug	SERIALPORT OPEN

smartmeter.0
2022-07-09 15:23:46.957	debug	CREATE SERIALPORT: 300 7 1 even

smartmeter.0
2022-07-09 15:23:46.947	debug	SmartmeterObis options: {"debug":2,"protocol":"D0Protocol","transport":"SerialRequestResponseTransport","requestInterval":"60","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}

smartmeter.0
2022-07-09 15:23:46.822	info	starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.smartmeter, node: v12.22.11, js-controller: 4.0.21

smartmeter.0
2022-07-09 15:23:45.937	debug	Plugin sentry Initialize Plugin (enabled=true)

smartmeter.0
2022-07-09 15:23:09.021	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

smartmeter.0
2022-07-09 15:23:09.020	debug	Plugin sentry destroyed

smartmeter.0
2022-07-09 15:23:09.019	info	terminating

smartmeter.0
2022-07-09 15:23:09.017	info	Got terminate signal TERMINATE_YOURSELF

smartmeter.0
2022-07-09 15:22:59.213	debug	connected set to false

smartmeter.0
2022-07-09 15:22:59.120	error	Serial port device is undefined, check your configuration!

smartmeter.0
2022-07-09 15:22:59.077	info	starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.smartmeter, node: v14.19.0, js-controller: 4.0.19

smartmeter.0
2022-07-09 15:22:58.524	debug	Plugin sentry Initialize Plugin (enabled=true)

smartmeter.0
2022-07-09 15:22:58.299	debug	States connected to redis: 0.0.0.0:9000

smartmeter.0
2022-07-09 15:22:58.172	debug	States create User PubSub Client

smartmeter.0
2022-07-09 15:22:58.171	debug	States create System PubSub Client

smartmeter.0
2022-07-09 15:22:58.152	debug	Redis States: Use Redis connection: 0.0.0.0:9000

smartmeter.0
2022-07-09 15:22:58.113	debug	Objects connected to redis: 0.0.0.0:9001

smartmeter.0
2022-07-09 15:22:58.105	debug	Objects client initialize lua scripts

smartmeter.0
2022-07-09 15:22:58.041	debug	Objects create User PubSub Client

smartmeter.0
2022-07-09 15:22:58.039	debug	Objects create System PubSub Client

smartmeter.0
2022-07-09 15:22:58.036	debug	Objects client ready ... initialize now

smartmeter.0
2022-07-09 15:22:57.976	debug	Redis Objects: Use Redis connection: 0.0.0.0:9001

smartmeter.0
2022-07-09 15:22:48.649	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

smartmeter.0
2022-07-09 15:22:48.648	debug	Plugin sentry destroyed

smartmeter.0
2022-07-09 15:22:48.647	info	terminating

smartmeter.0
2022-07-09 15:22:48.644	info	Got terminate signal TERMINATE_YOURSELF

smartmeter.0
2022-07-09 15:22:21.273	info	List of port: [{"path":"/dev/ttyS2"},{"path":"/dev/ttyS3"},{"path":"/dev/ttyS0"},{"path":"/dev/ttyS1"}]

smartmeter.0
2022-07-09 15:22:20.355	debug	Message received = {"command":"listUart","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":450,"ack":false,"time":1657372940353},"_id":99950159}

smartmeter.0
2022-07-09 15:22:13.067	debug	connected set to false

smartmeter.0
2022-07-09 15:22:12.968	error	Serial port device is undefined, check your configuration!

smartmeter.0
2022-07-09 15:22:12.921	info	starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.smartmeter, node: v14.19.0, js-controller: 4.0.19

smartmeter.0
2022-07-09 15:22:11.958	debug	Plugin sentry Initialize Plugin (enabled=true)

smartmeter.0
2022-07-09 15:22:11.779	debug	States connected to redis: 0.0.0.0:9000

smartmeter.0
2022-07-09 15:22:11.741	debug	States create User PubSub Client

smartmeter.0
2022-07-09 15:22:11.739	debug	States create System PubSub Client

smartmeter.0
2022-07-09 15:22:11.717	debug	Redis States: Use Redis connection: 0.0.0.0:9000

smartmeter.0
2022-07-09 15:22:11.681	debug	Objects connected to redis: 0.0.0.0:9001

smartmeter.0
2022-07-09 15:22:11.673	debug	Objects client initialize lua scripts

smartmeter.0
2022-07-09 15:22:11.614	debug	Objects create User PubSub Client

smartmeter.0
2022-07-09 15:22:11.613	debug	Objects create System PubSub Client

smartmeter.0
2022-07-09 15:22:11.611	debug	Objects client ready ... initialize now

smartmeter.0
2022-07-09 15:22:11.560	debug	Redis Objects: Use Redis connection: 0.0.0.0:9001

smartmeter.0
2022-07-09 15:22:06.990	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

smartmeter.0
2022-07-09 15:22:06.986	info	terminating

smartmeter.0
2022-07-09 15:22:06.983	info	Got terminate signal TERMINATE_YOURSELF

[Thomas Braun]

@firefighter166 sagte in Adapter "smartmeter":

2022-07-09 15:22:12.968 error Serial port device is undefined, check your configuration!

Da fehlt was beim Serial port.

[MichMein]

@thomas-braun
Deine Aussage scheint, so glaube ich, nicht ganz korrekt zu sein wenn man sich das ganze Log anschaut.

smartmeter.0
2022-07-09 15:23:46.957	debug	CREATE SERIALPORT: 300 7 1 even

smartmeter.0
2022-07-09 15:23:46.947	debug	SmartmeterObis options: {"debug":2,"protocol":"D0Protocol","transport":"SerialRequestResponseTransport","requestInterval":"60","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}

smartmeter.0
2022-07-09 15:23:46.822	info	starting. Version 3.3.4 in /opt/iobroker/node_modules/iobroker.smartmeter, node: v12.22.11, js-controller: 4.0.21

Es scheint da wohl eher anderes Problem vorzuliegen, dazu kann apollon77 hoffentlich mehr sagen.

[Thomas Braun]

@michmein sagte in Adapter "smartmeter":

Deine Aussage ist, so glaube ich, nicht ganz korrekt

Das ist keine Aussage von mir, das ist eine Zeile aus deinem Log.

[MichMein]

@thomas-braun sagte in Adapter "smartmeter":

Da fehlt was beim Serial port.

Aber das hier ist deine Aussage!

[Thomas Braun]

@michmein

Ja, ist die Übersetzung von

Serial port device is undefined, check your configuration!

[MichMein]

@thomas-braun
Sag mal, verstehst du mich nicht? Hast du dir das Log komplett angeschaut?

Wenn man sich das Log komplett anschaut wird man erkennen können das es irgendwann klappt einen Serial Port zu öffnen und zu nutzen. Deine Aussage ist selbstverständlich nicht falsch, es steht ja so im Log, aber in diesem Fall nicht hilfreich.

Und es handelt sich auch nicht um mein Log.

[apollon77]

Jetzt mal ruhig Leute.

Ja beim allerersten Start war kein port gesetzt und damit gabs diese Meldung. Danach wurde ja einer gesetzt. Locker bleiben.

[MichMein]

@apollon77 sagte in Adapter "smartmeter":

Jetzt mal ruhig Leute.

Ja beim allerersten Start war kein port gesetzt und damit gabs diese Meldung. Danach wurde ja einer gesetzt. Locker bleiben.

Ich bin ganz locker! Und nichts anderes als du es geschrieben hast war meine Aussage, denn das Problem scheint nicht der Serial Port zu sein wie Thomas es ausgesagt hat.

[firefighter166]

@apollon77 vielen Dank nochmal für deine Bemühungen, reicht dir der mitgelieferte Log jetzt aus oder wird noch was benötigt?

[apollon77]

@firefighter166 sagte in Adapter "smartmeter":

Schellcount EZZ3

Also dazu findet man ja nicht wirklich viel ... auch das Datenblatt lässt sich zu den Abfragemöglichkeiten nicht wirklich aus.

In meinen Augen ists so das der Zähler nachdem er sich identifiziert hat und wir sagt "mach mal Baudrate changeover" weil er es so wollte nichts mehr tut und nichts mehr von sich gibt.

Schreib den Hersteller an und frag was sache ist bevor wir hier weiter rumraten. Kannst ja sagen das er sich mit

/AEL4<1>AEL.TF.16-2

meldet und das bedeutet: 4 -> 4800 baud

[firefighter166]

@apollon77 Ich werde dem Hersteller heute mal eine E-Mail schreiben.

AEL..TF.16-2 ist der Zählertyp soviel kann ich schon einmal sagen, dieser wird in Deutschland von der Firma Zeco GmbH unter dem Namen Schellcount EZZ3 vertrieben. Dieser Zähler kommt eigentlich von der Firma Köhler Elektrik aus der Türkei.

Folgende Antwort habe ich von Zeco erhalten:

Hallo,
laut Hersteller können die Daten mit einem optischen Lesekopf abgelesen werden.
Dazu benötigen Sie die „ Meter Reading Program V2“ dieses finden Sie unter Documents & Programs auf
der Webseite vom Hersteller www.kohlersayac.com.tr

[firefighter166]

@apollon77

habe eben nochmal mit einem Kumpel gesprochen, der die selben Zähler im Haus benutzt, er ließt diese ebenfalls aus und zwar über Node-Red er hat mir mal kurz die Befehle geschickt. Vlt. können wir damit was anfangen.

Initialisierung:
msg.payload = "/?!\r\n";
msg.baudrate = 300;

Umschalten auf 4800 Baud:
msg.payload = "\x06041\r\n";
msg.baudrate = 300;

Zählerstand abrufen:
msg.payload = "\x01R2\x021.8.0()\x03\x59";
msg.baudrate = 4800;

Zählernummer abrufen:
msg.payload = "\x01R2\x020.0.0()\x03\x50";
msg.baudrate = 4800;

[apollon77]

@firefighter166 hmm ok. Also das erklärt ggf was. Was dein Kumpel hier nutzt ist das er im „Programming Mode“ einzelne datenpunkte abfragt. Das kann der Adapter nicht weilendes bisher noch nie nötig war (und Programming Node wieder Hersteller spezifisch ist.

Wir senden ein 040 … er ein 041

Die 4 ist die baudrate. Die 0 danach beim Adapter ist der sog. „Readout Mode“ und die 1 der Programming Mode.

Wenn der Zähler also nur im Programming Mode ausgelesen werde kann nimm lieber Node-red.

Bzw jetzt kennst du die Frage an den Hersteller: warum kommt im
Readout node keine Daten? ;-))

[firefighter166]

@apollon77 E-Mail an den Hersteller ist raus, mal gucken was dort zurück kommt.

[Chris M]

Hi,
so langsam nervt mich das Thema "Smartmeter".
ich hab einen IR Leser an meinen EMH ED300S Stromzähler verbunden. Der IR Leser wird vom Raspberry auch erkannt und mittels Befehl```

screen /dev/ttyUSB0

sehe ich auch, dass er Daten empfängt:

aber unter der SmartMeter Instance wird dieser nie "grün"

Kann mir einer die Einstellungen dafür posten?

Er ging mal aber mittlerweile hab ich verschieden Einstellungen immer mal wieder getestet aber kein Erfolg:

No or too long answer from Serial Device after last request.

[Thomas Braun]

@chris-m sagte in Adapter "smartmeter":

aber unter der SmartMeter Instance wird dieser nie "grün"

Falsche Unzureichende Rechte? Du eimerst da als root herum, der hat natürlich Zugriff auf das Gerät. Für den user iobroker muss das nicht der Fall sein. Check die User/Gruppen-Rechte am device.

Eine root shell ist ohnehin tabu, auch und gerade auf einem Raspberry.