rbe filter seems not be working

[supergiovane]

rbe filter seems not be working

[Supergiovane]

Ok, let me some time to work this out. I revert to you.

[Supergiovane]

Hello,
yes, you're right.
A fix will be out shortly.
Thank you for the feedback!
Don't forget to subscribe, if you wish, to my channel, for news about my nodes.
http://eepurl.com/gJm095

[Supergiovane]

Fixed in 1.1.14
Out in minutes.
Sorry for that!

[egs2003]

The error is still present

[Supergiovane]

Hello,
the issue has been fixed and tested on 1.1.14. Are you sure? Can you paste here your nodes so i can try directly? Thanks.

[egs2003]

[{"id":"7d1a870f.532b08","type":"knxUltimate","z":"3fd3b2c6.bef68e","server":"e4d5887b.163c28","topic":"1/1/1","dpt":"1.001","initialread":true,"notifyreadrequest":false,"notifyresponse":false,"notifywrite":true,"notifyreadrequestalsorespondtobus":false,"notifyreadrequestalsorespondtobusdefaultvalueifnotinitialized":"0","listenallga":false,"name":"","outputtype":"write","outputRBE":false,"inputRBE":false,"x":950,"y":2140,"wires":[[]]},{"id":"7fd9b91c.0f2318","type":"inject","z":"3fd3b2c6.bef68e","name":"","topic":"","payload":"true","payloadType":"bool","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":750,"y":2240,"wires":[["7d1a870f.532b08"]]},{"id":"e4d5887b.163c28","type":"knxUltimate-config","z":"","host":"192.168.178.100","port":"3671","physAddr":"1.1.3","suppressACKRequest":false,"csv":"","KNXEthInterface":"Auto","KNXEthInterfaceManuallyInput":"","statusDisplayLastUpdate":true,"statusDisplayDeviceNameWhenALL":true,"statusDisplayDataPoint":false}]

[egs2003]

Sorry, I sent you the wrong code. This checkbox was active and it still doesn't work.

[egs2003]

I'm checking the bus with ETS. Whenever I trigger the node by inject true is output on the BUS

[egs2003]

I get it. I wrote that I accidentally sent you the wrong code. But it doesn't work even if the checkbox is activated.

[Supergiovane]

Here your code. It works for me.
On the 1/1/1, do you have a real KNX device or not?

[egs2003]

I have a real KNX system

[Supergiovane]

What do you read on the status, below the node?
Have you restarted your node-red after updating the node?

[egs2003]

[egs2003]

yes, of course I did a restart, too.

[Supergiovane]

Hmm.... What appens if you change the group address?

[egs2003]

The problem can be reproduced with other group addresses.

[Supergiovane]

Do you have more than one Ethernet interface on your PC?

[egs2003]

WLAN and Ethernet

[Supergiovane]

Try to disable the Wifi.

[egs2003]

Oh, I know what you mean. NodeRed runs on a Raspberry Pi. It is only connected with Ethernet.

[Supergiovane]

Or at least, select the ethernet interface in the config node.

[Supergiovane]

Try to manually select the interface in the config node and try again.

[egs2003]

Ok I tested it. But it stays with the PRoblem

[Supergiovane]

Try to give a name to the node

[egs2003]

That didn't work either

[Supergiovane]

What's the make/model of your ETH/KNX interface? Is this a router or an ip interface?

[egs2003]

ip interface

[Supergiovane]

What version of node-red do you have?
Are you able to tell me the node.js version as well? In a terminal window, please type
node -v
Thanks.

[egs2003]

node.js v10.17.0
node-red v1.0.2

[egs2003]

node-red-contrib-knx-ultimate
1.1.14

[Supergiovane]

It seems to be fine.
Maybe some problem while updating the knx-ultimate to 1.1.14?
I need to view what you have in .node-red/node_modules/node-red-contrib-knx-ultimate/knxUltimate-config.js
Are you able to upload here this file?

[egs2003]

There were no questionable messages during update

[Supergiovane]

The code is OK. There should be another issue. I need you again to paste here the nodes, so i have your exact configuration. Then i'll test with an IP interface (i have an ip router here)

[Supergiovane]

Hello again. Are you able to paste this file into .node-red/node_modules/node-red-contrib-knx-ultimate/ folder and restart nodered?
Then try again.

knxUltimate-config.js.zip

[egs2003]

nothing has changed

[Supergiovane]

Holy crap.

[egs2003]

I'm sorry. So I'd get along alternatively, too. But of course it would still be cool if it worked.

[Supergiovane]

Have had no messages from users about this issue. I need to try with an ip interface, but i can try it only tomorrow.
Can you do something like this, and try to send a payload to the first node? I need to know what the debug message says. Thanks.

[egs2003]

I'm not getting any debug news. Even not if I alternate true and fals send. But in ETS the messages are displayed

[Supergiovane]

That's clear. The node value is updated as soon it receives the value from the KNX bus. In you case, the RBE is not the problem. The problem is that the node doesn't receive anything from the bus.

[Supergiovane]

Do you have maybe a DDOS protection or UDP flood protection set on any switch or router in your net?

[egs2003]

I'm not familiar with that. I deliberately did not set it up or see it anywhere.

[Supergiovane]

How many IP tunnels can instantiate your IP interface? You use currently two, one for ETS and one for the knx-ultimate. It can be an issue with the max tunnel number allowed by your interface.
If you have netgear managed switches, check it out.

[Supergiovane]

What appens to the debug msg node, if you send a value from the ETS itself?

[egs2003]

{"topic":"0/1/2","payload":false,"knx":{"event":"GroupValue_Write","dpt":"1.001","source":"1.1.250","destination":"0/1/2","rawValue":[0]},"devicename":"","_msgid":"e2368303.0d35d"}

[egs2003]

I use a fritzbox. My interface can have 4 or 5 tunnels.

[Supergiovane]

Fritzbox doesn't do any flood protection. So you're ok.
Try this:

Close ETS.
Reboot your ip interface (what model of ip interface do you have?).
Don't open ETS
Try to send a payload to the node and let me know what the debug node says.

[egs2003]

I'm afraid I can't find the time today.
The used interface is from mdt
https://www.mdt.de/download/Archiv/MDT_THB_IP_Interface_02.pdf

[Supergiovane]

We'll continue tomorrow! Bye

[egs2003]

However, the plant was only completely restarted this morning.

[egs2003]

However, the system was only completely restarted this morning.

[Supergiovane]

i need to go step by step to find what you problem is. Tomorrow!

[Supergiovane]

but... still suspect your double ethernet on the PI.
Tomorrow, try to DISABLE the wifi. Bye.

[egs2003]

Disabling WiFi did not help

[Supergiovane]

Hmmm. Your problem seems to be beyond what i can do for you.

If the problem persists, you can try to:

1. Connect the MDT direclty to your node-red machine, or at least, node-red machine and MDT on the same switch.
2. You can also watch the config of your MDT, maybe there is something preventing the forwarding of the KNX ip messages again to the ethernet interface, or there's some set of filtering on the device ID (Quelleadress) you set in the knx-ultimate
3. Change your Quelleadresse of the knx-ultimate Gateway node; try to set it on 15.15.1 for example, out of the scope of other devices, on another Line.
4. You can try using others knx nodes, for example knxjs or knxeasy.

One of the above solutions must for sure work. Please tell me wich of these. Thanks!

[egs2003]

Sorry, it's a productive system. I will not make such changes. Unfortunately I can't help you there

[Supergiovane]

I wish to help you, because with more than 1.000 knx-ultimate installations working 24h, i cannot find the issue for your problem. This is very frustrating but i'm pretty sure, that the knx-ultimate is working correctly. One of the above solutions (apart from 4.) will for sure work.

[egs2003]

For myself I have found a working solution. I use my own RBE filter in front of your node. I didn't look at your implementation either. I assumed that you were checking the payload on the software side.

[Supergiovane]

Yes but this is a workaround. In fact, the node cannot receive any telegram sent by another knx-ultimate node itself. The RBE filter built into knx-ultimate, take cares of the real value of the node.
At a last chance, you can try to check "suppress ACK Request" in the knx-ultimate Gateway config node. This option suppresses the ACK request coming from old KNX/IP interfaces.

[Supergiovane]

Do you have restarted node-red after changing the Ethernet Interface or disable the wifi?

[egs2003]

yes i did

[Supergiovane]

V1.1.15 is out. Try that, but for sure it's an ethernet related issue.