KNX node for node-red

[Alloc]

Hm, I must admit I didn't fully consider how this would work
I thought about using the list of GAs for an ETS device, but the devices only have the KOs, so you'd still have to manually make the connections from the GA to the KO of the dummy device.

Looking at the GIRA dummy device I think the best format would be to have a list of all GAs per data size. Like a line "1 bit" and then N columns for all the 1 bit GAs used in Node-RED. Or maybe better as header "1 bit", then each GA on a single line as the list propably can get quite long. Then you could at least simply go through the list of 1 bit GAs and assign them to the 1 bit KO of the dummy (rinse and repeat for the other data sizes of course).

Another possible way would be all used GAs in one list, followed by the data size (like "1/3/2<tab>1 bit").

The list (per data size or total, depending on the format) should be sorted by GA though, as it's easier to go through ETS's GA tree.

[TheMax74]

Hello
do you absolutely need to link GA to dummy device’s communication object (KO)?
I had dummy devices, for use with EibPC (i remember i had otherwise issues with GA export), that i then ditched as soon i had put the EibPC out of service.

Maybe changing the .knxproj directly, to link GA and KO do the trick. But i need to ditch into this.

[TheMax74]

Hi Alloc
Inside the knxproj, that is a simple "zipped" file, there is te knx_master.xml file, containing all the bells and whistles.
But i think that it's simpler to put a headphone on your head with some good music, and do it by hands.

[Alloc]

Hi Massimo,

do you absolutely need to link GA to dummy device’s communication object (KO)?

Yeah, if you want to use the GA filter on the KNX IP Router you need to either have all the used GAs linked to a dummy device on the IP line or set those GAs to always forward. The latter is even worse as not using the GA filter IMHO as this will also forward all these GAs through all other couplers, especially the KNX RF couplers.

Inside the knxproj, that is a simple "zipped" file, there is te knx_master.xml file, containing all the bells and whistles.
But i think that it's simpler to put a headphone on your head with some good music, and do it by hands.

I agree, fiddling with that data directly doesn't sound very safe. Still a list like I said above would be nice, so you can easily go through all the GAs in that list instead of having to manually go through all Node-RED KNX nodes on all flows to see which GAs are in use

[TheMax74]

Hi
So can i go with that?

Another possible way would be all used GAs in one list, followed by the data size (like "1/3/2<tab>1 bit").

or do you prefer something else?

[Alloc]

No, I think this would be perfect

[TheMax74]

Hello Alloc
The config-node will gives you this.
GA, DPT, Node ID, Name (each field is separated by a tabulation and will be ordered by GA)

"0/1/8" "1.001" "d9d9b17f.6441e8" "Constrosoffitto taverna [switch]"
"0/1/20" "3.007" "55f8efa1.92756" "Constrosoffitto taverna [switch]"
"15/0/1" "1.001" "9fa2b51.051e348" "Light Status"
"0/0/26" "1.001" "6436297e.12f3b" "Light Status"
"Universal Node" "Any" "acce1dd9.03a75" "All"
"0/0/26" "1.001" "8cc4944b.ec868" "Date"
"0/0/26" "1.001" "713a1cdc.4ab3ec" "Time"
"0/0/10" "1.001" "2436d78a.f1c9b" "Plafoniera soggiorno [switch]"
"0/1/1" "1.001" "20ebf383.94d3a4" "Theatre Room Ceiling LEDs"

V. 1.1.29 will be out shortly.

[TheMax74]

Hey Alloc
you find it in the advanced options of the config node.

[Alloc]

Wow, cool, that was quick
Thanks, will give it a go in a moment. Now I just need to memorize what data size each DPT is

[Alloc]

Oh, almost forgot (had some issues with my Node-RED install last night ...): Seems to work fine, thank you!

[droid]

TheMax74

Should the KNX node work with KNX IP routers (like the latest from MDT) that have IP Secure enabled? I'm able to write messages to the bus, but receiving messages leads to something like:

[debug] 2020-02-15 18:18:17.818 Inbound multicast message from 192.168.2.114: 0610095500240000011d0c98008370400a110e9fe230d70e4c 4d960b8c52da8bb26d2bd5
[warn] 2020-02-15 18:18:17.818 read KNXNetHeader: unhandled serviceType = undefined

[TheMax74]

Hello droid
secure tunneling is not implemented yet. Please don’t use the IP address of the router, use the standard multicast ip address instead.

[droid]

Mmh I have used the standard multicast one as well. With that one I couldn't even write telegrams to the bus. Should this work even when having ip secure in the ip router enabled?

[TheMax74]

Please consult the wiki, FAQ and troubleshoot page. Do you have maybe two ethernet cards?

[droid]

Mmh ok. No I only got one ethernet card. When using the standard multicast address I am receiving the sent packages on the listening node but they never reach the bus as I can see in the group address monitor in the ETS. With the ip address of the router the telegrams reach the bus but I don't receive them on the listening node.