After an evening full of aaarrgh,… I made it work!
I think,… the problem is in the IP address as openhab_knx suggested.
My code is now (where you can see that the IP addresses are in the same range = 169.254.):
I’ve seen similar behaviour in my system. For me to get things working I’ve had to set the gateway to “router” and did not set the address of the actuator things. I don’t think it matters because unless you are trying to fetch the channel setup from the device, the local address of your KNX equipment is not used in the communication.
I’m actually rethinking my OH setup such that follows the ontology more. E.g. defining the channels into different things, with each thing corresponding to an “equipment”. Not quite sure how to do it yet. Any input is appreciated.
(the default knx router IP is 220.127.116.11, as documented here, that why it looks to be in a different subnet)
I had (have) a similar Problem and it was (almost) working in OH 2.5.
In OH3.0 I lose my KNX-Gateway all the time (offline / online) and the KNX device is allways offline. Now I can switch off the light but not on anymore ;-(
I am wondering about your “localSourceAddr: 15.15.249” - seems to be still the default.
If I know it right the adress should match to your topologie (Busline). In your case something with 4.0.xxx.
Why is in ga the seperator a “.” and not “/”?
For a router configuration you do not need to specify much. Routers use IP multicast communication and for knx these addresses are all default presets and need not be given in the configuration. So for a router it is sufficient to have such a config:
I cant seem to get it working properly. It works on and off, sometimes with a lag, sometimes not at all. Polling knx-status is also sketchy for my dimmers.
I am using the same setup as with OH2. Also I get the feeling OH3 affects the actors as some lost connection to Ets and I had to make the Knx-bus powerless for a reset.
In channel setup, what difference does the actor address do?
When adding half of my actors show offline.
If the physical address is given, the KNX bridge tries to ping/read the actor via physical address. Also there is described, that either all or no device should be reachable (online) because KNX is a bus. If you reach the bus, you will reach the devices.
Yes ok, thanx. I read it several times but dont seem to get it
I think the items gets updated booth good and bad either way I try. And some actors online, others offline. Maybe Im not consequent enough thru my testing although Im trying to be.
After more test it seem to be my knx weather station that disturb my knx bus. Very strange errors increased since Christmas and my work with OH3. OH2 have been very stable before that. But when ETS5 couldn’t reach or update some actors I first thought it was because OH. But I guess just my weather sensor lived on the edge. It sends values but also error messages that disturb to much. This is my research right now . Thanx for support.
Hi @djoope , I have the same problem as you. Once I removed the individual address from thing, the device came online. Can you make screenshots on how you did the setup of channel and points? Here is my KNX Thing (actuator), I use it to control all some of the lights (On/Off) and dimming functions. I find the documentation not really clear so I am stuck at this step. I wanted to try editing the config files, I can’t get to create a token. Another error, that I don’t get. My setup is on RPI4
I simply cannot get it work, but I am also fairly new to KNX & ETS, so that might be the problem. I have one single actuator (on/off) in ETS which is controlled by a touchpanel, and it is working fine. I have only one Group Address, where I simply link the touch panel and the actuator.
In openhab I can get a bridge and device online, but no communication to or from the bus via item in OH.
You have mentioned 2 Group Addresses on the switch, and I can also see that in the examples. What is the functionality of these 2? (I have only 1)
If I change status of an item in OH, should I then be able to see a telegram in ETS Diagnostics? (Currently I do not see these - I only see a telegram when using the physical touchpanel for a state change)
EDIT: It is working. I found out that my IP Gateway had a filter, which blocked telegrams. After changing this setting, everything works as intended.