Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tam
Daro1003 wrote:A little further like 100km
I think redirects or Anydesk and would take care of the subject.
michal.zd wrote:I can also write a program for rpi
michal.zd wrote:only it needs time for that, and testing time at daro.
Daro1003 wrote:.I wonder if anyone is already using your inverter program besides me.
Daro1003 wrote:.I set
Daro1003 wrote:I don't understand why exactly.
Daro1003 wrote:.It is ok however:
michal.zd wrote:Identical json, you can just copy this node and replace the idx and svalue.
[
{
"id": "9faeea04b2b50403",
"type": "function",
"z": "c03666d911c02a8f",
"name": "Prepare for Domoticz",
"func": "// Declaration of variables\n\nlet idx1 = 123;\nlet idx2 = 456;\nlet idx3 = 789;\n\nlet msg1 = {};\nlet msg2 = {};\nlet msg3 = {};\n\nmsg1.payload = { \"command\": \"udevice\", \"idx\": idx1, \"svalue\": msg.payload.P.toString() + \";0\"};\nmsg2.payload = { \"command\": \"udevice\", \"idx\": idx2, \"svalue\": msg.payload.GP.toString() + \";0\" };\nmsg3.payload = { \"command\": \"udevice\", \"idx\": idx3, \"svalue\": msg.payload.CP.toString() + \";0\" };\n\nreturn[[msg1,msg2,msg3]];",
"outputs": 1,
"timeout": 0,
"noerr": 0,
"initialize": "",
"finalize": "",
"libs": [],
"x": 460,
"y": 180,
"wires": [
[
"85eb0898c7979634",
"5b94fc5b22b41f4e"
]
]
},
{
"id": "5b94fc5b22b41f4e",
"type": "mqtt out",
"z": "c03666d911c02a8f",
"name": "MQTT Domoticz",
"topic": "",
"qos": "",
"retain": "",
"respTopic": "",
"contentType": "",
"userProps": "",
"correl": "",
"expiry": "",
"broker": "175c3dc01f359e9d",
"x": 710,
"y": 180,
"wires": []
},
{
"id": "175c3dc01f359e9d",
"type": "mqtt-broker",
"name": "Raspberry Pi 1B",
"broker": "192.168.10.51",
"port": 1883,
"clientid": "",
"autoConnect": true,
"usetls": false,
"protocolVersion": 4,
"keepalive": 60,
"cleansession": true,
"autoUnsubscribe": true,
"birthTopic": "",
"birthQos": "0",
"birthRetain": "false",
"birthPayload": "",
"birthMsg": {},
"closeTopic": "",
"closeQos": "0",
"closeRetain": "false",
"closePayload": "",
"closeMsg": {},
"willTopic": "",
"willQos": "0",
"willRetain": "false",
"willPayload": "",
"willMsg": {},
"userProps": "",
"sessionExpiry": ""
}
]
Daro1003 wrote:.I wonder if other devices that have a modbus can also be read this way
[
{
"id": "e03d6e55aef23111",
"type": "function",
"z": "972c9476422a46d9",
"name": "Prepare for Domoticz",
"func": "// Declaration of variables\n\nlet idx1 = 123;\nlet idx2 = 456;\nlet idx3 = 789;\nlet idx4 = 158;\n\nlet msg1 = {};\nlet msg2 = {};\nlet msg3 = {};\nlet msg4 = {};\n\nmsg1.payload = { \"command\": \"udevice\", \"idx\": idx1, \"svalue\": (msg.payload[1] / 10).toString() };\nmsg2.payload = { \"command\": \"udevice\", \"idx\": idx2, \"svalue\": (msg.payload[2] / 10).toString() };\nmsg3.payload = { \"command\": \"udevice\", \"idx\": idx3, \"svalue\": (msg.payload[3] / 10).toString() };\nmsg4.payload = { \"command\": \"udevice\", \"idx\": idx4, \"svalue\": (msg.payload[4] / 10).toString() };\n\nreturn[[msg1,msg2,msg3,msg4]];",
"outputs": 1,
"timeout": 0,
"noerr": 0,
"initialize": "",
"finalize": "",
"libs": [],
"x": 1060,
"y": 180,
"wires": [
[]
]
}
]
[
{
"id": "e03d6e55aef23111",
"type": "function",
"z": "972c9476422a46d9",
"name": "Rekuperator do Domoticz",
"func": "// Declaration of variables\n\nlet idx1 = 123;\nlet idx2 = 456;\nlet idx3 = 789;\nlet idx4 = 158;\nlet idx5 = 413;\n\nlet msg1 = {};\nlet msg2 = {};\nlet msg3 = {};\nlet msg4 = {};\nlet msg5 = {};\n\nmsg1.payload = { \"command\": \"udevice\", \"idx\": idx1, \"svalue\": (msg.payload[1] / 10).toString() };\nmsg2.payload = { \"command\": \"udevice\", \"idx\": idx2, \"svalue\": (msg.payload[2] / 10).toString() };\nmsg3.payload = { \"command\": \"udevice\", \"idx\": idx3, \"svalue\": (msg.payload[3] / 10).toString() };\nmsg4.payload = { \"command\": \"udevice\", \"idx\": idx4, \"svalue\": (msg.payload[4] / 10).toString() };\nmsg5.payload = { \"command\": \"udevice\", \"idx\": idx5, \"svalue\": (msg.payload[5] / 10).toString() };\n\nreturn[[msg1,msg2,msg3,msg4,msg5]];",
"outputs": 1,
"timeout": 0,
"noerr": 0,
"initialize": "",
"finalize": "",
"libs": [],
"x": 1060,
"y": 180,
"wires": [
[]
]
}
]
Daro1003 wrote:.recuperator to make it not 199 just 19.9
Daro1003 wrote:.I just don't know what ID and Z mean
.
.
Daro1003 wrote:Cool.
I didn't think it would go so smoothly with that recuperator data I was sure it was a much more complicated affair.
I wonder if other devices that have modbus can also be read this way.
TL;DR: For 15 FAQ answers, "read 90 registers" is the practical breakthrough for Domoticz users integrating a Vents VUT R 600 VE EC A21 via Raspberry Pi, Node-RED, Modbus TCP on port 502, MQTT, and JSON temperature publishing. [#21454785] Why it matters: This lets a Raspberry Pi turn recuperator data into usable Domoticz temperature devices without relying on unstable Modbus plugins.
| Path | Thread setting | Best use | Key limitation |
|---|---|---|---|
| Modbus TCP over LAN/Wi-Fi | IP + port 502 | Direct A21 network access | Needs fixed IP |
| RTU over TCP | LAN converter | RS485 converter path | Serial defined in converter |
| USB RS485 RTU | USB adapter | Direct A+/B- testing | More wiring and port setup |
| Node-RED + MQTT | JSON to broker on port 1883 | Domoticz integration | Needs flow formatting |
Key insight: The Vents A21 path works once the network Modbus read returns real registers. Then Node-RED only has to scale values, map Domoticz IDX numbers, and publish JSON.
command, idx, and svalue. [#21454831]command: "udevice", a Domoticz idx, and an svalue. The MQTT broker example used IP 192.168.10.51 and port 1883. For more readings, add more idx variables and return more message objects. [#21454831](msg.payload[1] / 10).toString() for this conversion. This keeps Domoticz from displaying raw register values instead of real temperatures. [#21456142]idx variable per Domoticz device, then set svalue from the selected msg.payload array element. For example, idx1, idx2, and idx3 can represent three temperature sensors. Replace placeholder values like 123, 456, and 789 with real Domoticz IDX numbers. [#21454831]id and z fields with Domoticz IDX values. [#21456951]