Wenn dies dein erster Besuch hier ist, lies bitte zuerst die Hilfe - Häufig gestellte Fragen durch. Du musst dich vermutlich registrieren, bevor du Beiträge verfassen kannst. Klicke oben auf 'Registrieren', um den Registrierungsprozess zu starten. Du kannst auch jetzt schon Beiträge lesen. Suche dir einfach das Forum aus, das dich am meisten interessiert.
Also just noticed that the "msg.devicename" property is set up differently depending on if the node is in universal mode or not: With universal mode it's as described above, including the names of main and middle group. In non-universal mode it only contains the actual GA name. Would obviously be nice if the new data would always have all three elements
I use knx-ultimate for a while now and it works great. Thanks a lot for that.
Now I'm trying to connect some HueBulbs to the KNX-Bus and the Hue-Part in knx-ultimate looks perfert for that.
My Problem is, that I use DeConz, espacialy Phoscon as a HueBridge and it looks like the HueNodes won't connect to that kind of Bridge.
The Node is looking for a api on https://ip/api/config, my DeConz Bridge offers some on http://ip/api/config, so i thought i was lucky but the connections isn't fully established:
Hey. I'm using the NodeRed plugin (great work!) in a project to connect multiple KNX worlds with different multicast 239.x.x.x addresses. However, we're experiencing an issue where it seems that different multicast addresses aren't connecting properly. For instance, we want to forward GA 8/3/2 from multicast 239.0.23.6 to 239.0.23.100, which works. BUT even though there's no node for it, GA 8/3/2 from another multicast address 239.0.23.8 is also being forwarded to 239.0.23.100. 100% reproducible.
Do you have any idea or are you familiar with this?
Hi Axel
if you open an issue on GitHub and paste there your flow, I could take a look a it, but i know, that using multiple multicast addresses on the same machine, may cause some issues. If you’re able, you can use unicast addresses.
Hope this is still active seeing that the last posting is from Dec. 23. I am trying to get your plugin in Nodered to run. In fact, I am really just starting with Nodered, watching your videos and loving them. One thing though: I do not get past configuring a hue bridge. I add a hue light (since that is my main motivation, I have a lot of hue lights I want to control with KNX switches via Home Assistant and Nodered), but when it gets to connecting the hue bridge, I will get an error message:
I am using KNX secure, but that seems to work, although I cannot select "TCP Tunneling" as suggested, since it is simply not available. Still, I am adding my KNX IP interface with all settings, but it fails with above error message.
Any idea what I am doing wrong here? Do I have to disable KNX secure?
Thanks a lot
S.
P.S. Great plugin btw, at least from what I can see in the videos.
<EDIT> And I solved the problem. I did not know I need to deploy after configuring things, like the gateway for example. Did that, works. Now to create the first flow
Zuletzt geändert von sunstarfire; 14.01.2024, 07:57.
Haha Grazie Mille Massimo I got two more things now though. First, my mdt Glasstaster smart nicely dims my office lights, and it shows the percentage. What it does not is show the lights as off when I do switch them off. Cosmetic, but not perfect, and I wonder if I am doing something wrong.
Second: How do I control the color of the hue lights. I have not found that trick yet... And your video just shows "you take the group address, put it here and voila".... Not working for me.
Any hints? Maybe another one of your fantastic videos?
I'm using KNX Ultimate for more than one year now and it's pretty awesome!
However, the update to 2.4.5-beta.3 failed today and below log doesn't help a lot (at least for me).
Could you please have a look into that and help me to get it up and running again?
Thanks a lot!
Code:
-----------------------------------------------------------
2024-02-13T13:00:34.551Z Installieren : node-red-contrib-knx-ultimate 2.4.5-beta.3
2024-02-13T13:00:34.641Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-contrib-knx-ultimate@2.4.5-beta.3
2024-02-13T13:00:37.640Z [err] npm
2024-02-13T13:00:37.643Z [err] WARN
2024-02-13T13:00:37.643Z [err] config production Use `--omit=dev` instead.
2024-02-13T13:00:48.786Z [out]
2024-02-13T13:00:48.786Z [out] up to date in 11s
2024-02-13T13:00:48.844Z rc=0
Hi
if you're able to execute npm i --omit=dev node-red-contrib-knx-utlimate from within the .node-red/node_modules folder, you'll be able to install the beta3.
If you don't want to do so, just install a previous stable version npm i node-red-contrib-knx-utlimate@2.4.4 from within the .node-red/node_modules folder.
Hello, I am really trying hard to use NodeRed, but I fail at the simplest task, since I do not really find an example.
I have an injector, that can inject on or off. Then I have a switch, which sends to an output, depending on whether it got an on or an off. And maybe you already spotted the problem. I then want to control blinds via a KNX node, but I cannot find how to send the repsective information to the KNX node. The switch will determine if I send an on or off, and then send something to the KNX node, but I do not find the place where I can control WHAT it is sending, or how I can then tell the KNX node whether the shutter is supposed to open or close.
Basically, the KNX ultimate documentation is a collection of unconnected things, that do not make any sense at all, because the basic info is missing. Sad, I really like it, and it works fine with hue. But everything else is just too complicated.
Anyone can help, maybe with an example flow showing the nodes and the config?
Hast denn irgendwelche Ahnung wie ein Rollo im KNX funktioniert und welche Datentypen da benötigt werden und warum ein AN AUS da nur bedingt funktioniert?
Und dann schaue Dir die Tutorials und Hilfen zum Inject Node an, dem kann man alles Beibringen vom AN/AUS bis zu x%
Das sind alles keine Fragen die mir dem KNX Ultimate Node zu tun haben. Da wäre der Beitrag in einem separaten Thread viel sinnvoller aufgehoben.
----------------------------------------------------------------------------------
"Der Hauptgrund für Stress ist der tägliche Kontakt mit Idioten."
Albert Einstein
Wir verarbeiten personenbezogene Daten über die Nutzer unserer Website mithilfe von Cookies und anderen Technologien, um unsere Dienste bereitzustellen. Weitere Informationen findest Du in unserer Datenschutzerklärung.
Indem Du unten auf "ICH stimme zu" klickst, stimmst Du unserer Datenschutzerklärung und unseren persönlichen Datenverarbeitungs- und Cookie-Praktiken zu, wie darin beschrieben. Du erkennst außerdem an, dass dieses Forum möglicherweise außerhalb Deines Landes gehostet wird und bist damit einverstanden, dass Deine Daten in dem Land, in dem dieses Forum gehostet wird, gesammelt, gespeichert und verarbeitet werden.
Kommentar