KNX node for node-red

[TheMax74]

Hi @TheMax74,
Hi all,

I am lost. I tried to implement the KNX Ultimate with node-red-contrib-homekit-bridged in my installation. I want to control the brigthness in my rooms with my apple devices (Homekit). Unfortunately your example is not rly clear for me. I tried to implement it in my system but failed. Attached you find my last try.. its just work with ON/OFF, no Brightness and no feedback in % in Homekit.

Maybe someone can give me his code or send me a photo of his construction?!
Or explain to me what I have to do.

THANK YOU!
BR

Hi
First of all, you're using a GA with 3.007, that's a relative dimming datapoint. You need to use an absolute dimmer GA, like 5.001.
Homekit sends the value as absolute dim, not relative.
Then, you maybe need to convert the output homekit node's value, from 0-255 scale to 0-100. But this after you succesfully set the correct GA and datapoints.

[Strobel2k]

Thank you for the fast response. Is there no other solution to transfer the output into my knx installation without changing the GA from relative dimming to absolute? Otherwise I have to change my complete knx installation.

[TheMax74]

Hi Strobel
nope.
Relative dimming is when you press and hold a button and the light slowly fades. Absolute dimming is when you tell "hey light, set yourself to 40%".
They are different things. Homekit doesn't support relative dimming yet. You should be able to simply add a group address to KNX. All actuators does have the absolute dimming group address. ;-)

[Elektroarzt]

Hi Massimo
works like a charm and I promise to never pressing the merge button again 😊.

1000 grazie e tanti saluti all'italia.

[Elektroarzt]

Is there no other solution to transfer the output into my knx installation without changing the GA from relative dimming to absolute? Otherwise I have to change my complete knx installation.

Hi Strobel2k ... you don't have to decide whether to use relative or absolute dimming. I also have HomeKit running with my existing KNX installation in relative dimming mode. Just add some GAs for the absolute dimming from HomeKit or any other Visu in your ETS project. Both works beside each other as this is the advantage of the separate "Rückmeldeobjekt".
Best regards

[geieraffe]

Hi TheMax74 and the rest of the community,

since a few weeks I get the same problem as described here (or could be).
But as said, it should be solved with v1.1.9.

I tried to solve it with all the community posts here, but I still keep getting the
connection_warning.PNG
Warning message.

Also the watchdog gives me
watchdog_error.PNG
Even though the unicast ethernet watchdog never fails.
It may be that a connection is established again after a while. But only very unreliable.

In configuration I have the IP Adress (192.x.x.200) of the Module itself and I thought I give the KNX physical adress of a tunneling connection directly (1.1.3) to avoid opening all tunnels.
config.PNG
It seems the multicast way is more unstable.

Could it be, the "old error" is back for some reason since a few updates?
Any ideas?


Ah, yes, I'm using the MTD Router 3rd Generation (SCN-IP100.03)
Node-Red v1.2.6 and KNX-Ultimate v1.1.99

[TheMax74]

Hello
No, the connection part hasn't be touched since.
Have you already seen here?
https://github.com/Supergiovane/node...mate/issues/39
With this device, i suggest to use the multicast IP 224.0.23.12.

[t81s]

Hi Massimo,
just had the chance to check the RBE filter fix for datapoint 242.600 in version 1.1.99. It seams to me that the RBE has now no effect at all. The same payload wont be blocked if it’s send out two or more times in a row.

[TheMax74]

Hi T81s
Not having devices with 242.600 i'm unable to properly test the function, but trying to a "blind" group address (i haven't such as devices, so i set a fake GA), it works.
Node-RED 2.png
Node-RED.png

[TheMax74]

..but... i'll try again tomorrow, maybe i can go to buy a 242.600 capable device.

[TheMax74]

Hi T81s
i found the issue and working for a fix that'll be out this morning.

[TheMax74]

V 1.2.1 with fix for RBE is out. You need to add validity for color and brighness, like this:

msg.payload={x:500, y:500, brightness:80, isColorValid:true, isBrightnessValid:true};

[atbs]

Hi Massimo,
is it possible to implement DPT 249.600? I'd like to send color temperature and brightness simultaneously to my MDT LED Controller AKD-0424R2.02. I found a specification here: https://www.symcon.de/forum/threads/...703#post375703
Best regards
Alex

[TheMax74]

Hello Alex
Tomorrow i’ll take a look.

[atbs]

Hello Alex
Tomorrow i’ll take a look.

Thank you!
The MDT spec of the LED controller (version 2019) mentions 2 bits in the last byte while the table from the symcon thread (2015!) mentions 3 bits.
I tried out some values in the ETS and I can verify that the 3rd bit also works. The table in the symcon thread seems to be accurate...
To support this DPT the node should accept an object with the following items:

• transition time (x100msec): 0...65535 = 2 byte (byte 0+1)
• color temperature (in Kelvin): 0...6535 = 2 byte (byte 2+3)
• brightness (in %) 0...100% mapped to 0...255 = 1 byte (byte 4)
• validity of brightness (boolean)
• validity of color temperature (boolean)
• validity of transition time (boolean)

If a validity flag is set to 0 the device uses the default values (transition time) or the previous values (color temperature or brightness). The usable range of the last byte is 0...7 (bits 0 to 2). I was quite amazed how well that worked . I never used that object before because i had no corresponding KNX devices. NODE-RED is awesome! If you could make that work i'd be able to implement an alternative HCL algorithm...