-
Notifications
You must be signed in to change notification settings - Fork 8
Description
I am trying to continously read the info output from a EMH eHZ P-Series smartmeter. The meter puts out an info message every second. This goes to a raspberry pi via a USB-IEC optical to USB serial interface. The setup works in principle, i.e. I see the msg object, I can split out the values I care about and display them. However, it does not work continously. Every few messages the readout pauses for a few minutes, then I get an error, then it continues.
The Error is not always the same and neither is the timeout.
examples:
This Error always pauses for exactly 2mins:
1/13/2025, 1:28:53 PMnode: full_msg
msg : Object
{ payload: object, _msgid: "7dae87cc.5159b8" }
1/13/2025, 1:30:53 PM
msg : string[90]
"smartmeter-obis error: Error: No or too long answer from Serial Device after last request."
1/13/2025, 1:31:12 PMnode: full_msg
msg : Object
{ payload: object, _msgid: "dd2cb063.0e807" }
This one has variable pause times:
1/13/2025, 1:31:23 PMnode: full_msg
msg : Object
{ payload: object, _msgid: "df64e3a8.32fc9" }
1/13/2025, 1:33:20 PM
msg : string[614]
"smartmeter-obis error: Error: Error while parsing SML message: Error: Wrong TL-Field 0x60 for Choice!: Message: 1b1b1b1b01010101760548faef6200620072630101760107ffffffffffff05016da8fb0b0a01454d480000a984de72620165734e7d620163236900760548faf062006200726307017707ffffffffffff0b0a01454d480000a984de070100620affff72620165734e7d75770701006032010101010101454d480177070100600100ff010101010b0a01454d480000a984de0177070100010800ff64080172620165734e7d621e52ff6503cb76600177070100020800ff0172620165734e7d621e52ff643ea75c0177070100100700ff0101621b520053012d01010163766500760548faf1620062007263020171016344f300001b1b1b1b1a01c612"
1/13/2025, 1:33:21 PMnode: full_msg
msg : Object
{ payload: object, _msgid: "c0a4ce78.4951f" }
I suspect some transmission error causes the underlying code to not recognize the message and then it waits until some buffer overflows or a timeout occurs. Is it possible to make that timeout configurable, since in this application it should always be below 1.5s?
I am running node-red-contrib-smartmeter 0.5.1 on redmatic 7.2.1
