HABmin Sitemaps do not send events to OH2 bus

kuhnan · May 25, 2017, 8:43pm

Hello,

I have checked out many threads but could find the answer.

I have a fresh installation of OpenHAB2 on RPI3 and also installed the KNX Binding 1.9.

To connect to KNX bus I’m using an “EIB KNX IP Schnittstelle PoE” (supports up to 5 tunneling connections)

knx.cfg
ip=192.168.1.81
ignorelocalevents=true
localIp=192.168.1.79
numberOfThreads=1

knxitems.items
Switch Licht_OG_Kinderzimmer1 “Licht Kinderzimmer1” { knx="<1/3/2" }

knx.sitemap
sitemap knx label=“knx test” {
Switch item=Licht_OG_Kinderzimmer1
}

In openhab.log I get
2017-05-25 22:36:03.385 [INFO ] [nx.internal.connection.KNXConnection] - Established connection to KNX bus on 192.168.1.81:3671 in mode TUNNEL.

In HABmin in the sitemap specified above (knx test) I can see the switch moving between on and off when swithing the lamp.
However, when I try to switch the lamp from HABmin nothing happens. In other words, when clicking on the same button I see moving when switching the physical lamp, nothing is happening.
Also I cannot see any messages in the Group Monitor of ETS5.

Can someone please help me to debug?

Would be greatful for any help.

Thanks a lot

Dim · May 26, 2017, 5:04am

Start by putting the KNX Binding and it’s transport layer in DEBUG mode by using the openHAB console (ssh openhab@localhost -p 8101 with password habopen)

log:list
log:set DEBUG org.openhab.binding.knx
log:set DEBUG tuwien.auto.calimero

Monitor /var/log/openhab2/openhab.log for related messages.

Since you have incoming (but no outgoing) communications from (to) the KNX Bus via the IP interface , one possible root-cause could be datagram filtering on the IP interface (although this is mostly applicable to Routing not Tunneling). This can be fixed by changing the configuration of your IP interface with ETS. Before you try this, check out the logs to see if we can find some other possible root-cause.

Have you tried another UI also? (except HABmin)

kuhnan · May 26, 2017, 2:04pm

Thanks a lot for your reply.

Your comment of trying another UI was good. When opening the same sitemap named “knx” in basicui it just worked :-). I had nothing to change.
However, now I’m cuiours what I did wrong for Habmin.

I ran the commands you proposed. Here the content from openhab.log file. It starts fine. And then you can see receiving some messages from the Bus. These are group addresses e.g. of temperatur or weather sensors that are sending updates to the bus. I also pressed on the button in Habmin - however, no effect at all is visible in the log file. Any ideas what might be missing?

2017-05-26 15:30:40.769 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'knxitems.items'
2017-05-26 15:30:45.622 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'knx.sitemap'
2017-05-26 15:30:47.806 [INFO ] [.dashboard.internal.DashboardService] - Started dashboard at /start
2017-05-26 15:30:48.782 [INFO ] [basic.internal.servlet.WebAppServlet] - Started Basic UI at /basicui/app
2017-05-26 15:30:48.919 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui
2017-05-26 15:30:49.291 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
2017-05-26 15:30:49.772 [INFO ] [ui.habmin.internal.servlet.HABminApp] - Started HABmin servlet at /habmin
2017-05-26 15:30:51.206 [INFO ] [nx.internal.connection.KNXConnection] - Established connection to KNX bus on 192.168.1.81:3671 in mode TUNNEL.
2017-05-26 15:34:15.571 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.
2017-05-26 15:34:15.576 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received telegram for unknown group address 7/1/1
2017-05-26 15:34:21.006 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.
2017-05-26 15:34:21.009 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.192.168.1.81:3671: indication from 1.1.105
2017-05-26 15:34:21.030 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.
2017-05-26 15:34:21.030 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.192.168.1.81:3671: indication from 1.1.111
2017-05-26 15:34:21.032 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received telegram for unknown group address 3/0/16
2017-05-26 15:34:25.939 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.
2017-05-26 15:34:25.939 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.192.168.1.81:3671: indication from 1.1.202
2017-05-26 15:34:25.940 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received telegram for unknown group address 3/0/12
2017-05-26 15:34:29.575 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.
2017-05-26 15:34:29.575 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.192.168.1.81:3671: indication from 1.1.18
2017-05-26 15:34:29.577 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received telegram for unknown group address 7/1/1
2017-05-26 15:34:31.567 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.
2017-05-26 15:34:31.567 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.192.168.1.81:3671: indication from 1.1.18
2017-05-26 15:34:31.569 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received telegram for unknown group address 7/1/1
2017-05-26 15:34:35.017 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.
2017-05-26 15:34:35.017 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.192.168.1.81:3671: indication from 1.1.202
2017-05-26 15:34:35.023 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received telegram for unknown group address 3/0/13
2017-05-26 15:34:35.568 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.
2017-05-26 15:34:35.568 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.192.168.1.81:3671: indication from 1.1.18

Then here I also add the log file when pressing the button in Basicui. Does these messages make sense?

2017-05-26 16:01:22.061 [INFO ] [tuwien.auto.calimero                ] - calimero.link.192.168.1.81:3671: send message to 1/3/2, wait for confirmation
2017-05-26 16:01:22.079 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.192.168.1.81:3671: cEMI L-Data.req from 0.0.0 to 1/3/2, low priority hop count 6 repeat tpdu 00 81
2017-05-26 16:01:22.081 [DEBUG] [tuwien.auto.calimero                ] - KNXnet/IP Tunneling 192.168.1.81:3671: sending cEMI frame seq 30, wait for cEMI.con, attempt 1 (channel 117) 06 10 04 20 00 15 04 75 1e 00 11 00 bc e0 00 00 0b 02 01 00 81
2017-05-26 16:01:22.084 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Wrote value 'ON' to datapoint 'command DP 1/3/2 Licht_OG_Kinderzimmer1, DPT main 0 id 1.001, low priority'
2017-05-26 16:01:22.086 [DEBUG] [tuwien.auto.calimero                ] - KNXnet/IP Tunneling 192.168.1.81:3671: received cEMI L-Data.con with req 214
2017-05-26 16:01:22.088 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.192.168.1.81:3671: confirmation of 1/3/2
2017-05-26 16:01:22.089 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.192.168.1.81:3671: send to 1/3/2 succeeded
2017-05-26 16:01:22.093 [DEBUG] [tuwien.auto.calimero                ] - process 192.168.1.81:3671: group write to 1/3/2 succeeded
2017-05-26 16:01:22.098 [INFO ] [tuwien.auto.calimero                ] - calimero.link.192.168.1.81:3671: send message to 1/3/2, wait for confirmation
2017-05-26 16:01:22.099 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.192.168.1.81:3671: cEMI L-Data.req from 0.0.0 to 1/3/2, low priority hop count 6 repeat tpdu 00 81
2017-05-26 16:01:22.100 [DEBUG] [tuwien.auto.calimero                ] - KNXnet/IP Tunneling 192.168.1.81:3671: sending cEMI frame seq 31, wait for cEMI.con, attempt 1 (channel 117) 06 10 04 20 00 15 04 75 1f 00 11 00 bc e0 00 00 0b 02 01 00 81
2017-05-26 16:01:22.118 [DEBUG] [tuwien.auto.calimero                ] - KNXnet/IP Tunneling 192.168.1.81:3671: received cEMI L-Data.con with req 215
2017-05-26 16:01:22.118 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Wrote value 'ON' to datapoint 'command DP 1/3/2 Licht_OG_Kinderzimmer1, DPT main 0 id 1.001, low priority'
2017-05-26 16:01:22.120 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.192.168.1.81:3671: confirmation of 1/3/2
2017-05-26 16:01:22.121 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.192.168.1.81:3671: send to 1/3/2 succeeded
2017-05-26 16:01:22.122 [DEBUG] [tuwien.auto.calimero                ] - process 192.168.1.81:3671: group write to 1/3/2 succeeded
2017-05-26 16:01:22.246 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.
2017-05-26 16:01:22.246 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.192.168.1.81:3671: indication from 1.1.16
2017-05-26 16:01:22.248 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received telegram for unknown group address 1/3/3

Thanks a lot for all your help!

Regards,
Andreas

Dim · May 26, 2017, 2:21pm

Hi Andreas,

So: Your OH2<->KNX communication is working fine. That’s very good news

Logs look good and clean. You can put the log level back to WARN (or INFO) level.

Now… for the HABmin sitemap problem…

I just realized that I have exactly the same issue…If I turn on or off a light (flick a switch) from the Sitemap within HABmin… it does nothing I do get the updates in HABmin if I manually (or if I use BasicUI to) flick the switch.

To be honest, I never used HABmin for anything else than managing my Z-Wave devices (it’s the best tool for this purpose)

I always use HABPanel (awesome) and BasicUI to contol my KNX items and they work perfrectly (commands are executed instantly and status updates come up very fast).

I will try to see what may be wrong with the HABmin sitemaps but since it is low priority for me, it may take some time

Ps1: I checked and this HABmin behavior is true for other bindings also (not only KNX)
Ps2: Since this seems to be an issue with HABmin (not KNX), I will change the title of the thread.
Ps3: Maybe @chris could give us some pointers on how to troubleshoot this one… (if he has time )

kuhnan · May 26, 2017, 6:46pm

In this case I will continue with HABPanel and BasicUI which are working great.
Thanks again for pointing me into the right direction!