Node Red Fragen

[TheMax74]

You need to use either a multicast address 224.0.23.12 if you’ve an IP router (that is reserved by the KNX associations), or the ip of the IP interface, in case you use the ip interface.
Don’t use the ip of the proServ.

I never ever had any connectivity problem with the node. The resilency is the most important part of the knx-ultimate node.

[PhilW]

Ähm no, I've just the proServ as IP Interface so I can only use it / its IP as host.
The local Interface is the IP of the realKNX

[TheMax74]

KNX needs a stable connection, either a router (preferred) or an ip interface.
The connection between KNX and Ethernet uses UDP multicast by design, that means that there’s not all the stuffs that TCP connection has (ack, resend of the packet when lost, etc...)
This is valid for router and for interface (the interface mimics the TCP stack, but in facts it is UDP and due to “mimic” we can have issues.
Other than that, i had an user having issues with a lan switch, non properly handling multicast. This user loose some udp messages, like you.
For example, i use an ip router directly connected to one interface of my nodered server (i have two interfaces, one reserved for knx and one for lan).
The connection between KNX and nodered is too important, so important that everyone should have a knx ip router that makes only one thing: ip routing between KNX TP bus and Ethernet. :-)

Beside that, i normally use the dpt 14.056 for Watt.

[multimedia]

Don’t use the ip of the proServ.

KNX needs a stable connection, either a router (preferred) or an ip interface.

That's strange as proServ is also a standard IP interface.

[TheMax74]

I don’t know how many tunnels proServ can instantiate and it may not be the problem. You said Hausverbrauch has problems. Monday i’ll try to reproduce your flow and to find out if there’s something else that comes in play!

[PhilW]

proServ can up to 5 tunnels

Beside that, i normally use the dpt 14.056 for Watt.

I know, i'm still in the configuration phase, after it all works I clean up

THX for your efforts

[TheMax74]

Thank you to you, but i’m now really concerned, because i never had a connection issue and i have near as 600 group addresses. I must dive into your issue to find out more!

[TheMax74]

Sorry Phil, a question: do you have more than one node Hausverbrauch (or another node with the same group address)? If yes, can you check if the other node does have the same datapoint as Hausverbrauch?

[PhilW]

Here is the complete picture with the GAs. The red one has no GA implementet
no double Group Addresses:

5.PNG
I cannot send you the whole flow via the forum. It's to big

[TheMax74]

In Hauskonsum (ich glaube ex Hausverbrauch) are you sure that this row msg.payload.siteCurrentPowerFlow.LOAD.currentPower *1000 always return a valid value? Can you put a debug node direct behind it and monitor it for some time? My ABB inverter outputs sometime a null value, whenever the sun goes down.

[PhilW]

Good Morning Massimo,

I'm pretty sure, cause the debug behind the http request puts out every value correct.

I marked the matching debug nodes /values with the same color.
Unfortunatelly I did not switch on the first 2 debug nodes the first time.
The debug nodes behind the"writes" have not receive any value.

5.PNG

In the next cycle (6 Minutes) the "Hauskonsum" wrotes its value.
"Monatsproduktion" & "Tagesproduktion" again not.
As I said sometimes they write there values sometimes not.
6.PNG

[PhilW]

And a 3rd cycle again without the "Hauskonsum"
9.PNG

[TheMax74]

Hallo Phil
thank you for your effort in clearing me the issue.
The payload you obtain from the HTTP Request node is an object. It doesn't mean that one of the objects inside the chain msg.payload.siteCurrentPowerFlow.LOAD.currentPower cannot be null.

Is for you a problem to kindly do this test for me?
1) Disconnect Hauskonsum input from your function.
2) Put this inject node before the Hauskonsum and link it to Hauskonsum

[{"id":"40424191.b44318","type":"inject","z":"5635003e.2d70f","name":"Phil","topic":"","payload":"50","payloadType":"num","repeat":"2","crontab":"","once":true,"onceDelay":"1","x":590,"y":660,"wires":[[]]}]

3) Deploy and run it for a while, then tell me if you see "Write" again in the node status.
Thanks.

[PhilW]

As expected it always shows "50" without "write" in the status.

The "overview" http request result in
Overview.PNG

and the "flow":
flow.PNG
So they are all "objects".

I realize that the problematic Items are always:
"PV Monatsproduktion"
"PV Tagesproduktion"
"Hauskonsum"

If I compare the function Jahresproduktion & Monatsproduktion they looked the same:
msg.payload=msg.payload.overview.lastYearData.ener gy/1000;
return msg;

msg.payload=msg.payload.overview.lastMonthData.ene rgy/1000;
return msg;

The first works, the second not

multimedia Christian ich hoffe es nervt nicht wenn wir in deinem Forum posten!

[TheMax74]

Phil, if you wish, we can continue by opening an issue on github.

Can you paste this node into your flow?

[{"id":"cf44ad3c.5230e8","type":"function","z":"74e1976c.3232c","name":"","func":"var Ret=-999;\nnode.status({fill:\"green\",shape:\"dot\",text: \"currentPower\" + \" (no values)\"});\n\n\nif (msg.hasOwnProperty(\"payload\"))\n{\n    node.send({payload:\"Payload found\"});\n    \n    if (msg.payload.hasOwnProperty(\"siteCurrentPowerFlow\"))\n    {\n        node.send({payload:\"siteCurrentPowerFlow found\"});\n        \n        if (msg.payload.siteCurrentPowerFlow.hasOwnProperty(\"LOAD\"))\n        {\n            \n            node.send({payload:\"LOAD found\"});\n       \n            if (msg.payload.siteCurrentPowerFlow.LOAD.hasOwnProperty(\"currentPower\"))\n            {\n                node.send({payload:\"currentPower found\"});\n       \n                Ret=Number(msg.payload.siteCurrentPowerFlow.LOAD.currentPower);\n            }\n            \n        }\n    }\n}\n\n\n// Avoid send something to the bus if some error\nif (Ret==-999) return null;\n\nnode.status({fill:\"green\",shape:\"dot\",text: \"currentPower\" + \" (\" + Ret+ \")\"});\n\nmsg.payload=Ret;\nreturn msg;","outputs":1,"noerr":0,"x":154,"y":652,"wires":[["82b697b8.a6454"]]}]

Then connect the Http Request output to this node's input, then connect this node's output to a debug node.
Then let me know what do you see in the debug window, as soon as the knxultimate node shows "Write".
Thanks and sorry, we need to go step by step.

PS: is there a way i can login into your node-red flow? That will help me solve your issue faster.