After a power failure on my OPenHAB (3.2.0 Release) server, the connection to one of my KNX device things is lost and ends up in ERROR: HANDLER, Status UNINITIALIZED and HANDLER_CONFIGURATION_PENDING. The KNX-bus is functional and I can still operate the device “locally” using push-buttons. I have tried to restart everything several times but it doesn’t come up again. tHe same problem has occcured twice before (the thread below) and a workaround I have used is to create a new thing with the same KNX individual adress which comes online immediately. This workaround is very annoying since I have to copy all 24 channels to the new thing (easy using the code tab) and then connect the new 24 channels to existing items and disconnect te items from the malfunctioning thing/channels.
Any thoughts on what’s causing this and/or if there is another, better workaround?
What are you using as an interface to connect to knx tunnel router usb … Show configuration and device model. Sometimes tunnel devices they just break connexion without reason but in general a reboot of the devices solves the problem. Other times is the networking etc.
I’m using a Schneider Electric SpaceLogic KNX IP Router - see configuration below.
Not really sure how to move forward but since all other devices worked just fine even after the OpenHAB power failure reboot, I doubt there is an issue with the gateway. The KNX to OpenHAB integration has also been 100% rock solid between these issues so I don’t think there is a network issue either.
If you have a knx router just use routing. If you insist on tunnel then make sure you are using adress available for openhab to connect sometimes ets etc can fill it up. You can use Wireshark to get more details.
Sorry, I meant my KNX things in OH, representing my actuators, binary interfaces etc.
I thought that status “ONLINE” on a KNX thing in OH meant that a connection is established and that OH can communicate with it through the group adress definition on the channels?
It`s strange, because thing without this address is always online, when bridge online.
At least, you can transfer all chanels to another working knx thing (do not forget make changes in other places of OH, because it will be new chanels).
But before it, let`s try this:
0) Save configuration of OH (may be full copy OH folder)
Delete all individual addresses of all knx things. If it will do not help, then
Put localSourceAddr in brifge which OH connected to KNX (with help of ETS).
Sometimes when OH is rebooting and ETS is connecting in this time, this address is changing by phisical KNX gateway (1.1.3 instead 1.1.2 for example) and OH has a lot of bugs with communications.
You can try to update to OH 3.3, for example.
After rebooting, you must wait some time to OH conection to KNX bus.
Finally I found out what’s causing this. After an upgrade to 3.4.3 earlier today, the problem still existed, but a better error message was presented:
Translated it says {ga=parameter is required}. I then realized that I had a few channels representing unused channels in my switch actuator without a group adress and apparently this was causing the error.