knx-easy-out node not working with Siemens SWG1 148-1AB22 IP Interface

[gh-user-1]

Hi, I guess it is this problem: https://bitbucket.org/ekarak/knx.js/issues/51/cant-write-through-siemens-swg1-148-1ab22

I solved it by adding a line to the knxEasy-config.js (but to be honest ... I'm an abslout beginner with node red and also with javascript):

        node.connect = () => {
            node.setStatus("disconnected")
            node.knxConnection = new knx.Connection({
                //begin: fix
		suppress_ack_ldatareq: true,
		//end: fix
                ipAddr: node.host,
                ipPort: node.port,

I don't know if a firmware update of the Siemens SWG1 148-1AB22 IP Interface would also solve the issue, because I currently don't have the ETS software to update it.

It would be nice to have an option in the knxEasy-config node to switch this flag (suppress_ack_ldatareq) on or off.

[SpeedyBlade]

Same Problem with the Weinzierl IP Interface 732 I was already in contact with the manufacture and they give me following information:

"Da scheint ein Fehler im Treiber von Node Red zu sein: im 3. Byte ist die Priorität kodiert im hinteren Halbbyte: in den vorderen zwei Bit sind die 4 Prioritäten, die hinteren müssen immer 0 sein; 0xBE darf also eigentlich nicht vorkommen"

The priority must also be normal and not low. Few devices needs normal bytes, so also the Weinzierl and Siemens IP Interface.

So please change this in the node and provide an update...

in the attachment the comparison between the communiction direktly in knx and the data which come from node red

[mthauth]

Same problem using Babtec eibport v3. Node sents telegram to groupaddress, but is ignored by listening communication objects.

[MavelGitter]

Same problem using Babtec eibport v3. Node sents telegram to groupaddress, but is ignored by listening communication objects.

Same here with my eibport v3; has this problem been resolved? I've tried a lot during the last 24 hours and can't get it working. Reading is fine, writing arrives on the bus but is ignored. The telegram's 3rd byte is 0xBE, which it shouldn't be. I've also tried various other KNX implementations in Node Red, but either they don't work at all have exactly the same issue (e.g. KNX Ultimate).

I'm also curious why my telegrams get sent as L_Data.con instead of L_Data.ind?

Thanks for any help, I'm desperate... (-:

Klaus

[danube]

Same problem with Loxone Miniserver Gen. 1. The proposed fix by @gh-user-1 worked for me.