knxd should be running with root privileges inside the container, so this shouldn’t be an issue
Hi
so i installed HA on my RPi 3 and connected this adapter to usb on Rpi and other side to an old GIRA RS232 to KNX
KNX extension is installed but it doesnt get discovered (set on automatic mode)
This is my knxd config:
address: 0.0.1
client_address: 0.0.2:8
interface: usb
device: /dev/ttyAMA0
log_error_level: warning
usb_filters: single
ip_address: ""
dest_port: "99"
custom_config: ""
What am I doing wrong/what to look for?
since you are using RS232, your KNX interface type certainly isn’t USB. You can try switching the interface type of the add-on to “TPUART” and select the correct serial device - maybe this helps. If not, please search the web which protocol the GIRA interface requires and play around with the settings.
edit: in case you speak german, you can give this forum a shot - people there will know more about knxd then me (I only wrapped knxd as a HAOS add-on and have no other deeper knowledge of it, apart from the official docs on the knxd github repo): knxd - KNX-User-Forum
no idea. Link doesn’t work for me (“product not available in your country”). But even if it did, still no idea. As mentioned earlier, I am neither a dev of knxd nor do I know much about it. If you search the web and somebody claims this device is working with knxd, then it should also work with this add-on
I don’t think so. It is certainly a good sign if it was a KNX certified product (it carries the KNX logo). But even some (very old) certified devices won’t work perfectly with todays systems.
I’d always recommend using a certified IP interface over some DIY-USB thing for HA.
Can you recomanded something specific?
Weinzierl, Gira and Enertex are very good imho.
I only used IP Routers though, which I guess you don’t need, but I’m sure their IP interfaces are just as fine.
That is very expensive. I’m not even sure if it will work with the boiler unit I want it for. Unfortunately, there is no one in my area who would help me try it out.
Usually starts at 150€. If your device has a knx logo it should work. Given you have ETS and the application for the device (if irbid not listed in the online catalog).
Do you have KNX already installed in your house?
If not, it needs a bit more than only a cable. If you want to start with KNX, you will need a PSU, Interface, connected devices and the EtS software license, approx. 700 EUR plus in total.
I have KNX installed and bought some stuff for our new boiler, but than switched to EMS-ESP32.
If your Boiler uses EMS bus (Bosch, Buderus etc), I would recommend this way an connect the EMS-ESP32 via MQTT to Home Assistant. Its way cheaper and easier.
If you wand a local KNX USB Stick, I can recommend the TULP Stick from Busware. The addon configuration is easy. The stick is a TPUART based one and I think it is used more often and the chance to get support in this community or at github for knxd or the German KNX User Forum is way better.
The addon itself is more or less only so wrapper stuff to make configuration via UI of HA possible. Everything else is default knxd behaviour.
agreed. @Kutilak if you only have one device you would like to connect via KNX, then it certainly is not worth it, as the entry costs to get a bus running and being able to program it is at ~ 1000 € (software license, PSU, IP-Interface). You might be able to find an electrician that would do the initial programming, which might be cheaper for just one device than buying the ETS software, but I still would not do it. My advice is to stay away from KNX for just one device.
basic MDT IP-Interfaces can be found for ~120 €, but it won’t get much cheaper than that.
used ones? Sure, I got a Gira Secure Router for 135€ used 
I wouldn’t really recommend MDT IP interfaces though.
@Kutilak for up to 5 devices in your KNX System the free ETS Demo may be sufficient. You don’t need to pay 1000€ for that.
That’s still a good advice. Look for ModbusTCP or something alike instead.
nah, new. At least on eibmarkt.com I found one for ~120 €. And my entire house is MDT KNX devices only, except for the interface (which I regret on hindside to not have spent 50€ more and got an IP interface). Couldn’t complain about them. Yes, they might not have all the bells and whistles the more expensive brands have feature wise, but if all you care is a basic KNX setup and move the “nice to have but not really mandatory” smart home logic into HA, I don’t see why one would need more fancy KNX devices. If you otoh do all the fancy stuff entirely in KNX space, then sure, more feature rich devices would certainly help (especially ones with more logic gates)
oh right, forgot about the demo version for up to 5 devices. Yes, then no license fees at least. But still probably wouldn’t go KNX for this one device.
yes, if it has a Modbus TCP interface I would also prefer that. Maybe if you tell us which brand+model of boiler you have @Kutilak we could give better advice which route to go.
Can’t second that. I think MDT suffers massively from feature creep. They have some features most other manufacturers don’t provide (eg. email sending from IP interfaces), but they are also a little bit buggy (eg not reporting free tunnels in discovery) and seem to need frequent firmware updates.
I also have some MDT stuff because it’s price/value is nice, but I don’t really get the hype around these devices.
You can do a 45min online training on the KNX webpage which gives you a 200Euro voucher for a KNX Lite Version. With this one you can run the ETS software with up to 20 devices which should take you pretty far. Will not safe you from getting the hardware that was mentioned though.
To integrate KNX Rf devices, I connected a GIRA 512000 KNX RF data interface to my HA-Rpi and used this addon to make it available for the KNX integration. Communication with the devices also works perfectly.
Unfortunately, I currently have to remove the USB stick to configure the devices and connect it to my PC with the ETS, since the IP interface provided by the KNXD cannot be used for this.
On the one hand, the interface is not even found by Auto Discovery, which is why I had to configure it manually via IP and port 3671.
I can then use the monitor and write to groups, but the programming of the devices keeps aborting with “The device is not responding within a reasonable time.”
Does anyone here have any advice on how to get the discovery to work and the physically addressed packets to work for programming?
Hi 
!
Direct IP RF couplers are not really common in Knx. I don’t think such devices exist (commercialy).
You will have to try with different configurations to get this working.
Also consider trying Calimero instead of knxd as it has a different implementation that may or may not enable that.
As pointed out a few times, here are no knxd developers reading. And afaik they refrain to support unusual use cases and even dockerized installations.