Tipps für eine neue Implantation

[Balteck]

Hallo zusammen, ich baue ein Haus und möchte KNX als Hausautomation nutzen.
In Italien ist es schwierig, KNX-Experten zu finden, sondern nur Techniker, die ihre Geräte verkaufen wollen.

Ich möchte die Experten des Forums um Rat fragen, welche Geräte besser zu kaufen sind.

Das Haus befindet sich im Erdgeschoss von 125 Quadratmetern und einem Dachgeschoss von 60 Quadratmetern. Außengarten und Garage.

Da ich neben KNX einen Supervisor zu Hause haben werde (wahrscheinlich Home Assistant), die Heizung / Kühlung Modbus / RS485 für Befehle verwenden wird und ich auch Geräte haben werde, die MQTT verwenden, frage ich mich, was der richtigste Ansatz (und auch wirtschaftlich) ist.

Ich könnte kaufen:

Lösung A:
1) 640mA oder 1280mA Stromversorgung (Beispiel: Meanwell KNX-40E-1280)
2) KNX IP/Router-Schnittstelle mit MQTT gateway (Beispiel: Arcus KNX-GW2-IP-2TE)
3) Modbus Gateway (Beispiel: Arcus KNX-GW-MODBUS-REG)
4) VM mit Home Assistant

Lösung B:
1) 640mA Stromversorgung mit IP-Schnittstelle und MQTT (Biespiel: Eelectron IPSBA01KNX)
2) Raspberry PI mit KNXD das die IP-Schnittstelle in einen Router verwandelt
3) Modbus Gateway (Beispiel: Arcus KNX-GW-MODBUS-REG) ober Modbus HAT für Raspberry PI
4) VM mit Home Assistant

Lösung C:
1) 640mA oder 1280mA Stromversorgung (Beispiel: Meanwell KNX-40E-1280)
2) Kostengünstige KNX-IP-Schnittstelle (oder USB)
3) Raspberry PI mit KNXD das die IP-Schnittstelle in einen Router verwandelt, Mosquitto für MQTT und Modbus HAT für RS485
4) VM mit Home Assistant

Lösung D:
1) 640mA Stromversorgung mit IP/Router-Schnittstelle (Biespiel: Weinzierl KNX IP LineMaster 762)
2) Modbus Gateway (Beispiel: Arcus KNX-GW-MODBUS-REG) ober Raspberry PI mit Modbus HAT und Mosquitto MQTT
3) VM mit Home Assistant

Was ist besser oder schlechter? Zu Hause habe ich bereits mehrere Raspberry und einen ESXi-Cluster für virtuelle Maschinen. Ich habe kein Problem damit, Programme unter Linux zu programmieren oder zu installieren. Ich frage mich, ob KNXD so zuverlässig ist wie ein kommerzieller KNX IP/Router oder ob die Verwendung von MQTT und Modbus wirklich ein dediziertes Gateway erfordert oder ob ich Telegramme zwischen MODBUS, KNX, TASMOTA mit einem MQTT-Server und -Client unter Linux austauschen kann

Diese Nachricht wurde automatisch übersetzt. Leider spreche ich nur Italienisch oder Englisch. Ich entschuldige mich für die Fehler
This message is translated automatically in german. I'm sorry for any mistake. I speak only in English or Italian.

[meti]

ob ich Telegramme zwischen MODBUS, KNX, TASMOTA mit einem MQTT-Server und -Client unter Linux austauschen kann

What do you plan to use that Home Assistant installation for, if not exactly that?

[sewi]

I can't really help you with Modbus / RS485, since I use MQTT and KNX only.

But FWIW I had some issues with KNXD, and while I can't guarantee it's not my fault, KNXUltimate on a node-red instance has worked from the start, with stellar performance, and I've never looked back. KNXUltimate has a universal receiver/sender mode, and with that I simply send all values to MQTT, and write what's published to MQTT back on the KNX bus. I also think node-red flows are intuitive to understand, so I count that as a bonus, in case someone else has to take over my work at some point.

Whether you use a RPI for that is up to you; the newer models appear to work stably for a long period of time, it's just running everything from a single SD card as a point of failure that'd irk me. I use one of the HP microservers, because I have to run a bunch of virtual machines anyway, and there one of them is the node-red VM.

As for individual KNX gateways for Modbus / RS485, read through the documentation and see if they can do what you need them to do. The big advantage of KNX gateways is that even if your RPI / VMs are down (which, granted, on an ESXi cluster should barely ever happen), anything that's modelled directly into KNX will continue to function, and should the gateway ever die, you can just replace it with an identical one, reprogram it over ETS, and be done with it.

For the power supply, getting one with diagnostics can be useful. I use MDT, MEANWELL appears to indicate the power supplies with diagnostics with a "D" at the end of the product number.

[Balteck]

What do you plan to use that Home Assistant installation for, if not exactly that?

I plan to use Home Assistant to integrate smart things like Bosch Induction cooktop with Baraldi cooker hood or to supervise energy, Media Players, Ip cameras and so on. Because I need to update and restart HA often is not a good idea to have critical things that depend on it.

That's why a mosquitto installation on a different VM is better to have a more reliable system.

I can't really help you with Modbus / RS485, since I use MQTT and KNX only.

Anyway I dont deeply understand if I need a MQTT gateway (like Eelectron one) or if I can use a Linux machine that have a client that reads/write MQTT from/to KNX BUS using KNXnet IP/router.

Is there a big difference from a commercial gateway instead of having a machine with more CPU/RAM resources, with a open source software that I can update or configure with every options and maybe having with less limitation (for example typical KNX IP Interface has only 4 or 5 tunnel or Modbus Gateway has 100 datapoints)?

Looking at the future, a commercial gateway will be updated? Or if I need some changes in communication (for example SSL 2.0 to 3.0 to TLS 1.0 to 1.1 and now 1.2 is the minimum usable on many systems), do I must replace it with another expensive one?

[sewi]

Anyway I dont deeply understand if I need a MQTT gateway (like Eelectron one) or if I can use a Linux machine that have a client that reads/write MQTT from/to KNX BUS using KNXnet IP/router.

Well, I'm doing exactly that with nodered (on Debian) and KNXUltimate, which publishes everything to a Mosquitto server.
Looks like this:
image.png

Obviously you need to connect your Linux machine to the KNX bus somehow - that's why I use a KNX IP Interface, to get access to the KNX bus. Of the 4-5 tunnels I have, KNXUltimate uses one, and I use another one when I program a device over ETS (you need to somehow be able to connect to the KNX bus, so you can configure the devices, so unless you use a USB interface, you'll need an IP interface anyway). Leaves 2-3 tunnels that I don't ever use.

Someone else might be able to chime in about what's best to do for Modbus, but for getting KNX stuff into MQTT, I don't see much of a problem using a gateway on a Linux machine, seeing that your Mosquitto server is likely going to be on a Linux VM anyway.