Windhager Heizung Werte über IP abfragen
Einklappen
X
-
Create a Virtual Input in Loxone. It can have any input range, but I have chosen an arbitrary range of 0 to 5. Importantly, it must have 'Use in User Interface' checked. I have many links to Node-Red under a single Category that contains a wealth of data flow. I don't have any interest in seeing the values but they must visualised to work with Node-Red.
'Save in Miniserver' and check you can alter the value via the Loxone App.
In Node-Red, drag in a Loxone 'control-in' node. Click in the control-in node and select the Miniserver entry and 'add new loxone-miniserver'. Select the edit button and add the credentials for the Miniserver including IP, Port, Loxone Username and Password, Token etc.
Select Update, then do a Deploy in Node-Red. From this point, you should be able to link anything that is visualised within Loxone.
Now select the Room and Category created earlier with the test Virtual Input. A list of Controls will show in the drop-down. Select the desired Control.
Drag a debug onto the Control-in node and Deploy. Then you should see values update in Node-Red as you change the value in the Loxone App.
Note you need to 'Save in Miniserver' before any new controls will be visible in Node-Red. I'll follow-up with the specifics of the Windhager integration when I get a chance.Ich spreche kein Deutsch. Gib Google Translate die Schuld, wenn ich unverständlich bin.Kommentar
-
Try this flow connected to your existing control-in node -
Code:[ { "id": "4606eeeab464f2f0", "type": "inject", "z": "e2778122e634373b", "name": "", "props": [ { "p": "payload" } ], "repeat": "", "crontab": "", "once": false, "onceDelay": 0.1, "topic": "", "payload": "2", "payloadType": "num", "x": 150, "y": 260, "wires": [ [ "3bdb74c4ed8d45c4" ] ] }, { "id": "3bdb74c4ed8d45c4", "type": "change", "z": "e2778122e634373b", "name": "Set OID and Value", "rules": [ { "t": "set", "p": "payload", "pt": "msg", "to": "$string('{\"OID\":\"/1/15/0/3/50/0\",\"value\":\"') & $string(payload) & '\"}'", "tot": "jsonata" } ], "action": "", "property": "", "from": "", "to": "", "reg": false, "x": 340, "y": 260, "wires": [ [ "adc9bb5d3e224e97" ] ] }, { "id": "adc9bb5d3e224e97", "type": "http request", "z": "e2778122e634373b", "name": "", "method": "PUT", "ret": "obj", "paytoqs": "ignore", "url": "http://192.168.178.71/api/1.0/datapoint", "tls": "", "persist": false, "proxy": "", "insecureHTTPParser": false, "authType": "digest", "senderr": false, "headers": [], "x": 540, "y": 260, "wires": [ [ "96ea6ace2ef8df97" ] ] }, { "id": "96ea6ace2ef8df97", "type": "debug", "z": "e2778122e634373b", "active": true, "tosidebar": true, "console": false, "tostatus": false, "complete": "false", "statusVal": "", "statusType": "auto", "x": 740, "y": 260, "wires": [] } ]
Zuletzt geändert von Tico; 16.06.2024, 16:11.Ich spreche kein Deutsch. Gib Google Translate die Schuld, wenn ich unverständlich bin.Kommentar
-
Hello Fendt43 . I'm interested if you could try something else -
The Loxone Virtual Input doesn't work with Windhager because of the Digest Authentication on login. That's what originally required the use of Node-Red for the authentication routine when requesting data.
I haven't tested the Loxone Virtual Output to see whether that is similarly afflicted with non-existent handling of Digest Authentication. There might be a remote chance that outbound commands can be made directly with Loxone.
Can you try setting up a Virtual Output and feed it with a numeric value appropriate to the OID?
The Virtual Output properties would look like this -
Then change the value fed into the Virtual Output and check what response occurs.Ich spreche kein Deutsch. Gib Google Translate die Schuld, wenn ich unverständlich bin.Kommentar
Kommentar