Good evening,
I have installed OPENHAB version 4.3.2 on a Raspberry Pi and am using the KNX binding to control my KNX devices via openhab. I am using the following hardware for this:
KNX/IP Item No. N000401 from eibmarkt.com
Everything works, but I always get a message saying that my bridge is OFFLINE.
Here is a picture and my configuration of the thing:
Bridge knx:ip:bridge [
ipAddress="xxx.xxx.xxx.10", // this is the ip KNX/IP eibmarkt.com
portNumber=3671,
localIp="xxx.xxx.xxx.9", //openhab-server
type="TUNNEL",
readingPause=50,
responseTimeout=10,
readRetriesLimit=3,
autoReconnectPeriod=60,
localSourceAddr="0.0.0"
] {
Thing device generic [
address="15.15.250",
fetch=true,
pingInterval=300,
readInterval=3600
] {
Channels:
//Datum und Uhrzeit
Type datetime-control : Datum "Datum" [ ga="11.001:30/0/38" ]
Type datetime-control : Zeit "Zeit" [ ga="10.001:30/0/39" ]
}
}
I know that the internet is full of this problem, but I have tried some of the solutions without success, or the users are using different hardware. But maybe someone can give me a decisive tip.
My first recommendation is to set fetch to false. There is absolutely no benefit in fetch=true.
Second: Please don’t set the readInterval if not absolutely needed (i.e. the device is not capable to send cyclic or by change - this might be true for some really old sensors) and please be aware that this parameter should have no impact at all if there is no GA which is readable at all (i.e. < in front of the GA, the flags are set and there is only one device which will answer the read request)
I have never used file-based configuration, instead created my configuration in the UI. From this perspective, my expected view is that the physical equipment is accurately reflected in the Things defined, each with the data objects it “owns”. The KNX interface is just one Thing which doesn’t have any channels of its own; every KNX actuator is a Thing with the electrical circuits it controls as channels, the weather sensor is a Thing with its own channels, the heat pump is another Thing, and so on.
So to me, the screenshot you posted where you have one Thing for the interface and underneath you have another generic thing which has a bunch of KNX addresses belonging to other devices (like date and time which probably are from a time module), that’s just… very very weird.
Could I propose that you remove the KNX definition from .thing file and from openHAB, and try to add the KNX devices as Things in the UI, just to see if that changes anything?
[edit] Something like this:
Also don’t forget that the KNX interface needs to be configured in openHAB’s localSourceAddress with one of the tunneling addresses, not with its physical address. And ideally, those tunneling addresses should be changed with ETS to match the area and line of the rest of the KNX bus.
The configuration is ok, especially if the thing is working as expected (aside from the false offline state).
Please be aware that the thing state is only about the answer of the device to the bus ping. The ping is of very low priority.
The individual address (or in german “physikalische Adresse”) is specific to the configuration of knx, it’s the address of the device itself. This is set during initial configuration of the device.
You don’t need this address to use it other than configuration of the device, so if you don’t know the correct address, leave the address empty.
Of course openHAB then will show the device online, regardless if it’s online or not But for TP (twisted pair) devices it’s at least unlikely that they go offline for real.
But for TP (twisted pair) devices it’s at least unlikely that they go offline for real.