Value 'ON' could not be sent to the KNX bus

Add-ons Bindings
,
1

Hi OpenHAB Forum,

i tryed to install openhab2 with a KNX Binding (binding-knx1 - 1.9.0.SNAPSHOT) today. The Connection to my Weinzierl KNX IP BAOS 771 works find.

2016-12-29 03:09:53.835 [INFO ] [nx.internal.connection.KNXConnection] - Established connection to KNX bus on 192.168.5.4:3671 in mode TUNNEL.

i made a small testfile with only one item

Switch  knx_licht_OG_Arbeitszimmer      "Licht" <light> (rOG_Office)    { knx="2/0/20" }

and geht a lot of Errors in my Logfile

2016-12-29 03:09:53.835 [INFO ] [nx.internal.connection.KNXConnection] - Established connection to KNX bus on 192.168.5.4:3671 in mode TUNNEL.
2016-12-29 03:11:50.461 [WARN ] [tuwien.auto.calimero                ] - KNXnet/IP Tunneling 192.168.5.4:3671: response timeout waiting for confirmation
tuwien.auto.calimero.exception.KNXTimeoutException: no confirmation reply received for L-Data.req from 1.1.21 to 2/0/20, low priority hop count 6 repeat tpdu 00 81
        at tuwien.auto.calimero.knxnetip.ClientConnection.doExtraBlockingModes(ClientConnection.java:236)[202:org.openhab.binding.knx:1.9.0.201612281657]
        at tuwien.auto.calimero.knxnetip.ConnectionBase.send(ConnectionBase.java:269)[202:org.openhab.binding.knx:1.9.0.201612281657]
        at tuwien.auto.calimero.knxnetip.KNXnetIPTunnel.send(KNXnetIPTunnel.java:149)[202:org.openhab.binding.knx:1.9.0.201612281657]
        at tuwien.auto.calimero.link.KNXNetworkLinkIP.onSend(KNXNetworkLinkIP.java:263)[202:org.openhab.binding.knx:1.9.0.201612281657]
        at tuwien.auto.calimero.link.AbstractLink.send(AbstractLink.java:304)[202:org.openhab.binding.knx:1.9.0.201612281657]
        at tuwien.auto.calimero.link.KNXNetworkLinkIP.sendRequestWait(KNXNetworkLinkIP.java:240)[202:org.openhab.binding.knx:1.9.0.201612281657]
        at tuwien.auto.calimero.process.ProcessCommunicatorImpl.write(ProcessCommunicatorImpl.java:466)[202:org.openhab.binding.knx:1.9.0.201612281657]
        at tuwien.auto.calimero.process.ProcessCommunicatorImpl.write(ProcessCommunicatorImpl.java:438)[202:org.openhab.binding.knx:1.9.0.201612281657]
        at org.openhab.binding.knx.internal.bus.KNXBinding.writeToKNX(KNXBinding.java:149)[202:org.openhab.binding.knx:1.9.0.201612281657]
        at org.openhab.binding.knx.internal.bus.KNXBinding.internalReceiveUpdate(KNXBinding.java:126)[202:org.openhab.binding.knx:1.9.0.201612281657]
        at org.openhab.core.binding.AbstractBinding.receiveUpdate(AbstractBinding.java:119)[204:org.openhab.core.compat1x:2.0.0.201612281318]
        at org.openhab.core.events.AbstractEventSubscriber.handleEvent(AbstractEventSubscriber.java:38)[204:org.openhab.core.compat1x:2.0.0.201612281318]
        at org.apache.felix.eventadmin.impl.handler.EventHandlerProxy.sendEvent(EventHandlerProxy.java:415)[6:org.apache.karaf.services.eventadmin:4.0.8]
        at org.apache.felix.eventadmin.impl.tasks.HandlerTask.run(HandlerTask.java:90)[6:org.apache.karaf.services.eventadmin:4.0.8]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_65]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_65]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_65]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_65]
        at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]
2016-12-29 03:11:50.461 [WARN ] [.binding.knx.internal.bus.KNXBinding] - Value 'ON' could not be sent to the KNX bus using datapoint 'command DP 2/0/20 knx_licht_OG_Arbeitszimmer, DPT main 0 id 1.001, low priority' - retrying one time: no confirmation reply received for L-Data.req from 1.1.21 to 2/0/20, low priority hop count 6 repeat tpdu 00 81
2016-12-29 03:11:53.468 [WARN ] [tuwien.auto.calimero                ] - KNXnet/IP Tunneling 192.168.5.4:3671: response timeout waiting for confirmation
tuwien.auto.calimero.exception.KNXTimeoutException: no confirmation reply received for L-Data.req from 1.1.21 to 2/0/20, low priority hop count 6 repeat tpdu 00 81
        at tuwien.auto.calimero.knxnetip.ClientConnection.doExtraBlockingModes(ClientConnection.java:236)[202:org.openhab.binding.knx:1.9.0.201612281657]
        at tuwien.auto.calimero.knxnetip.ConnectionBase.send(ConnectionBase.java:269)[202:org.openhab.binding.knx:1.9.0.201612281657]
        at tuwien.auto.calimero.knxnetip.KNXnetIPTunnel.send(KNXnetIPTunnel.java:149)[202:org.openhab.binding.knx:1.9.0.201612281657]
        at tuwien.auto.calimero.link.KNXNetworkLinkIP.onSend(KNXNetworkLinkIP.java:263)[202:org.openhab.binding.knx:1.9.0.201612281657]
        at tuwien.auto.calimero.link.AbstractLink.send(AbstractLink.java:304)[202:org.openhab.binding.knx:1.9.0.201612281657]
        at tuwien.auto.calimero.link.KNXNetworkLinkIP.sendRequestWait(KNXNetworkLinkIP.java:240)[202:org.openhab.binding.knx:1.9.0.201612281657]
        at tuwien.auto.calimero.process.ProcessCommunicatorImpl.write(ProcessCommunicatorImpl.java:466)[202:org.openhab.binding.knx:1.9.0.201612281657]
        at tuwien.auto.calimero.process.ProcessCommunicatorImpl.write(ProcessCommunicatorImpl.java:438)[202:org.openhab.binding.knx:1.9.0.201612281657]
        at org.openhab.binding.knx.internal.bus.KNXBinding.writeToKNX(KNXBinding.java:149)[202:org.openhab.binding.knx:1.9.0.201612281657]
        at org.openhab.binding.knx.internal.bus.KNXBinding.internalReceiveUpdate(KNXBinding.java:126)[202:org.openhab.binding.knx:1.9.0.201612281657]
        at org.openhab.core.binding.AbstractBinding.receiveUpdate(AbstractBinding.java:119)[204:org.openhab.core.compat1x:2.0.0.201612281318]
        at org.openhab.core.events.AbstractEventSubscriber.handleEvent(AbstractEventSubscriber.java:38)[204:org.openhab.core.compat1x:2.0.0.201612281318]
        at org.apache.felix.eventadmin.impl.handler.EventHandlerProxy.sendEvent(EventHandlerProxy.java:415)[6:org.apache.karaf.services.eventadmin:4.0.8]
        at org.apache.felix.eventadmin.impl.tasks.HandlerTask.run(HandlerTask.java:90)[6:org.apache.karaf.services.eventadmin:4.0.8]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_65]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_65]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_65]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_65]
        at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]
2016-12-29 03:11:53.468 [WARN ] [.binding.knx.internal.bus.KNXBinding] - Value 'ON' could not be sent to the KNX bus using datapoint 'command DP 2/0/20 knx_licht_OG_Arbeitszimmer, DPT main 0 id 1.001, low priority' - retrying one time: no confirmation reply received for L-Data.req from 1.1.21 to 2/0/20, low priority hop count 6 repeat tpdu 00 81
2016-12-29 03:11:56.477 [ERROR] [.binding.knx.internal.bus.KNXBinding] - Value 'ON' could not be sent to the KNX bus using datapoint 'command DP 2/0/20 knx_licht_OG_Arbeitszimmer, DPT main 0 id 1.001, low priority' - giving up after second try: no confirmation reply received for L-Data.req from 1.1.21 to 2/0/20, low priority hop count 6 repeat tpdu 00 81

.. more and more and more...

the ETS Group Monitor Shows a lot of write requests fom OpenHAB

ets.png1852×481 91.1 KB

i want only read the KNX message/Value and set Modbus IO`s.
Why write openHAB something back to the KNX?

2

Hi,

Here is my example based on bind a item to knx:
I’ve defined in the ETS two GAs:: the first one for command (ON/OFF) => 0/2/18 (called mainGA in OpenHAB) and the second one for the status => 0/3/18 (called listener in OpenHAB)
And the OpenHAB item definition looks like:

Switch swLampePorteChambre7 "lampe porte chambre 7" <light> (grPM_Rez_CH7,grLights) {knx="0/2/18+<0/3/18"}

But, If in your KNX project you’re using the same GA some command and status, I think you should add the ‘<’ symbol in your items configuration to tell OpenHAB that he can READ on that GA as well as sending command.

Switch  knx_licht_OG_Arbeitszimmer      "Licht" <light> (rOG_Office)    { knx="<2/0/20" }
3

It seems to be the problem using “IP-Tunneling” as communication protokoll. If the same device (“192.168.5.4”) is used for ETS - maybe the device is blocked! Only some “IP-Router” devices are able to connect more than one IP-Tunnel connection.

Solution (physical): Weinzierl has “IP-Router”-devices that support 5 IP-Tunnel connections!

Solution (software): Use IP-Routing. IP-Routing communicates via Multicast adresses (for example 224.0.23.12:3671). A device broadcasts the message via a multicast-adress. All “listening devices” are able to read that multicast. Depending on the configuration (‘filter’) of that device the message will be written to the phisical (tp-side) KNX-Bus.

4

thx for your Feedback

@yphyph01
In my screenshot:
Nummer 6 is the button for ON and Number 8 is the Button for OFF on my Touchdisplay Z38i
i have a 3rd registe with Groupaddress 6/5 to read the State
so i changed the command to

Switch  knx_licht_OG_Arbeitszimmer      "Licht" <light> (rOG_Office)    { knx="2/0/20+<6/0/5" }

but i have still the Problem

@DirkSander
i have enabeld 4 IP-Tunnel and i can see the message on ETS groupmonitor so i think the Connection works but nobody say`s “your message is OK (waiting for CONFIRMATION)” and so OpenHAB sends more and more and more


but the question is, WAY OpenHAB sends something back after pressing the button

5

sorry - I didn’t saw your screenshot.

As I see you do have (at least) two several knx lines? 1.1.xxx and 1.3.xxx?

openHAB is 1.1.21 => But openHAB is not physically connected to line 1.1 (via copper)! openHAB is a network device.

So it maybe a result of filtering within the knx-ip-routers / line-couplers.

Solution 1 (short term and easy way to check): disable filters on both (all) IP-Routers / line-couplers.

Solution 2 (long term): You should add a “dummy”-device to the 1.1.xxx-knx-line. (for example use “Gira Dummy”-Application within ETS. And then drag the groupadresses uses in other lines to that dummy. After that be shure to reprogramm the IP-Router-Device of line 1.1 and 1.3! Now the filters should be set and your used groupadresses can pass the filter.

If your lines are connected with IP-Routers and not via line-couplers I would solve it with an additional solution:
Solution 3:

  1. Add another additional knx-line.
    Use that line for all knx-network-devices that are not physically connected to the knx-bus (TP)
  2. Use a IP-Router (multicast)-connection.
  3. add a dummy application (for example “GIRA Dummy”) and drag all the group addresses you need to communicate with to that dummy application
    => by that way all IP-Routers gain automatically configured groupadress-tables by ETS5
  4. reprogram all IP-Routers witch host devices that use your groupaddresses in that TP-line.

Due to the written info after reading the value from knx I have the same problem!

regards,
Dirk

6

one more thing:

your group-adress in your item is: “2/0/20”

But within ETS Group Monitor there is “Zieladresse” => “2/20”

It seems that you use different settings for ETS and openHAB!

Use main/middle/sub level (2/0/20 respectively) or main/sub levels (2/20 respectively). But it should be the same! I would prefer a 3-level-scheme

Dirk

7

Hi there,

I have exactly the same problem here. I use a BleuComm 'Azur proServ IP Gateway.

@DirkSander at least in my case there’s no problem with the line-couplers.

If i remember correctly, there once was a problem in the knx binding related to messages sent back to the knx bus. Maybe the problem still exists?

Thanks.

8

Hi MikeFo!

Yes - that problem still exists. In my environment (OH2b5 with KNX1.9) all reading-actions will produce a GroupValueWrite to the knx-bus. That is a real problem if you do not deal with that. It could lead to traffic-flood and will tear down your knx-bus if you do not handle it and use a workaround,

As workaround I used additional “reading-addresses”. The idear is that a GroupValueWrite from OH2 will not produce a change on the knx side and will not be monitored by OH2 itself. But you will need extra groupadresses and it is hard to understand after some weeks why “you have done such a mess” :wink:

I hope they will fix it soon. In complex knx-projects this is a no-go


Regards,
Dirk

1 Like
9

Hi all

i think i have found my problem. the BOAS 771 Firmware has one (or more) Bugs. i made a small exmaple Project with ETS5 and i needed over 4 Houers for Programming one Interface! (with ETS4 less then 5 minutes)
I found in knx-user-forum.de a post with this message:

Nach Mailkontakt mit Weinzierl hat sich das Thema erledigt, es handelt sich um ein Firmwareproblem der KNX IP BAOS 771:

...... hierbei handelt es sich um die Art und Weise des Confirm im LinkLayer.
Dies wurde bereits in Firmware Version V06 angepasst (Seit Juni 2013).
Das Confirm wurde von den bisherigen ETS Versionen (2, 3, 4) nicht berĂŒcksichtigt und fĂŒhrte somit auch nicht zu Problemen.
Erst ab ETS 5 wird dies berĂŒcksichtigt und beeinflusst den Applikationsdownload.
Das PhÀnomen tritt bei GerÀten mit Firmware Version V05 (Produktionsstempel Àlter als 2413) auf.
Leider ist ein Firmware Update nur bei uns im Labor möglich und ich dafĂŒr 50,00€ netto + Versandkosten berechnen.
Sollten Sie ein Firmware Update wĂŒnschen .....

My Log say`s

tuwien.auto.calimero.exception.KNXTimeoutException: no confirmation reply received for  ...

Looks like this is no OpenHAB problem.
know someone a Parameter to disable confirm waiting?

10

I have the same issue. My installation has been working many months and was working fine until I moved to openhab-binding-knx1/1.9.0.b5 or 1.9.0.SNAPSHOT

If I revert to 1.9.0.b4 it works fine again.

Have been using the Gira IP Coupler all along.

Regards Mark.

11

@crystollic

I have read in one post the colimero backand was updated and i think since this time we have our problems. But i think openhab works nie in spec and our Gateway habe problems. In my case i need a Firmware Update .

Btw
Some day ago i read a Post in openhab with a Gira Interface an the Problem was solved by changing Settings
Link

12

So, i have a new Firmware on my BOAS 771 and installed a new clean openhab2 final but still the same Problem.
I get a message from knx bus and Openhup sends something back


and with the new Installation i get some new Errors


2017-02-12 22:33:26.423 [WARN ] [eclipse.jetty.servlet.ServletHandler] - 
javax.servlet.ServletException: A MultiException has 1 exceptions.  They are:
1. java.lang.IllegalStateException: ServiceLocatorImpl(__HK2_Generated_5,6,15108875) has been shut down

	at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:489)[155:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427)[155:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388)[155:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341)[155:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228)[155:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at com.eclipsesource.jaxrs.publisher.internal.ServletContainerBridge.service(ServletContainerBridge.java:76)[10:com.eclipsesource.jaxrs.publisher:5.3.1.201602281253]
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)[81:org.eclipse.jetty.servlet:9.2.19.v20160908]
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)[81:org.eclipse.jetty.servlet:9.2.19.v20160908]
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71)[172:org.ops4j.pax.web.pax-web-jetty:4.3.0]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)[80:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)[79:org.eclipse.jetty.security:9.2.19.v20160908]
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)[80:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)[80:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:287)[172:org.ops4j.pax.web.pax-web-jetty:4.3.0]
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)[81:org.eclipse.jetty.servlet:9.2.19.v20160908]
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)[80:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)[80:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)[80:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80)[172:org.ops4j.pax.web.pax-web-jetty:4.3.0]
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)[80:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.server.Server.handle(Server.java:499)[80:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311)[80:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)[80:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)[72:org.eclipse.jetty.io:9.2.19.v20160908]
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)[83:org.eclipse.jetty.util:9.2.19.v20160908]
	at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)[83:org.eclipse.jetty.util:9.2.19.v20160908]
	at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]
Caused by: A MultiException has 1 exceptions.  They are:
1. java.lang.IllegalStateException: ServiceLocatorImpl(__HK2_Generated_5,6,15108875) has been shut down

	at org.jvnet.hk2.internal.FactoryCreator.getFactoryHandle(FactoryCreator.java:106)[150:org.glassfish.hk2.locator:2.4.0.b34]
	at org.jvnet.hk2.internal.FactoryCreator.dispose(FactoryCreator.java:173)[150:org.glassfish.hk2.locator:2.4.0.b34]
	at org.jvnet.hk2.internal.SystemDescriptor.dispose(SystemDescriptor.java:526)[150:org.glassfish.hk2.locator:2.4.0.b34]
	at org.glassfish.jersey.process.internal.RequestScope$Instance.remove(RequestScope.java:532)[157:org.glassfish.jersey.core.jersey-common:2.22.2]
	at org.glassfish.jersey.process.internal.RequestScope$Instance.release(RequestScope.java:549)[157:org.glassfish.jersey.core.jersey-common:2.22.2]
	at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:319)[157:org.glassfish.jersey.core.jersey-common:2.22.2]
	at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305)[158:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154)[158:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473)[155:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	... 26 more
Caused by: java.lang.IllegalStateException: ServiceLocatorImpl(__HK2_Generated_5,6,15108875) has been shut down
	at org.jvnet.hk2.internal.ServiceLocatorImpl.checkState(ServiceLocatorImpl.java:2288)[150:org.glassfish.hk2.locator:2.4.0.b34]
	at org.jvnet.hk2.internal.ServiceLocatorImpl.getServiceHandleImpl(ServiceLocatorImpl.java:629)[150:org.glassfish.hk2.locator:2.4.0.b34]
	at org.jvnet.hk2.internal.ServiceLocatorImpl.getServiceHandle(ServiceLocatorImpl.java:622)[150:org.glassfish.hk2.locator:2.4.0.b34]
	at org.jvnet.hk2.internal.ServiceLocatorImpl.getServiceHandle(ServiceLocatorImpl.java:640)[150:org.glassfish.hk2.locator:2.4.0.b34]
	at org.jvnet.hk2.internal.FactoryCreator.getFactoryHandle(FactoryCreator.java:103)[150:org.glassfish.hk2.locator:2.4.0.b34]
	... 34 more
2017-02-12 22:33:26.448 [WARN ] [org.eclipse.jetty.server.HttpChannel] - /rest/sitemaps/nima/nima?_=76c0509a83dd2
javax.servlet.ServletException: javax.servlet.ServletException: A MultiException has 1 exceptions.  They are:
1. java.lang.IllegalStateException: ServiceLocatorImpl(__HK2_Generated_5,6,15108875) has been shut down

	at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:88)[172:org.ops4j.pax.web.pax-web-jetty:4.3.0]
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)[80:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.server.Server.handle(Server.java:499)[80:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311)[80:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)[80:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)[72:org.eclipse.jetty.io:9.2.19.v20160908]
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)[83:org.eclipse.jetty.util:9.2.19.v20160908]
	at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)[83:org.eclipse.jetty.util:9.2.19.v20160908]
	at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]
Caused by: javax.servlet.ServletException: A MultiException has 1 exceptions.  They are:
1. java.lang.IllegalStateException: ServiceLocatorImpl(__HK2_Generated_5,6,15108875) has been shut down

	at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:489)[155:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427)[155:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388)[155:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341)[155:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228)[155:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	at com.eclipsesource.jaxrs.publisher.internal.ServletContainerBridge.service(ServletContainerBridge.java:76)[10:com.eclipsesource.jaxrs.publisher:5.3.1.201602281253]
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)[81:org.eclipse.jetty.servlet:9.2.19.v20160908]
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)[81:org.eclipse.jetty.servlet:9.2.19.v20160908]
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71)[172:org.ops4j.pax.web.pax-web-jetty:4.3.0]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)[80:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)[79:org.eclipse.jetty.security:9.2.19.v20160908]
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)[80:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)[80:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:287)[172:org.ops4j.pax.web.pax-web-jetty:4.3.0]
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)[81:org.eclipse.jetty.servlet:9.2.19.v20160908]
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)[80:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)[80:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)[80:org.eclipse.jetty.server:9.2.19.v20160908]
	at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80)[172:org.ops4j.pax.web.pax-web-jetty:4.3.0]
	... 8 more
Caused by: A MultiException has 1 exceptions.  They are:
1. java.lang.IllegalStateException: ServiceLocatorImpl(__HK2_Generated_5,6,15108875) has been shut down

	at org.jvnet.hk2.internal.FactoryCreator.getFactoryHandle(FactoryCreator.java:106)[150:org.glassfish.hk2.locator:2.4.0.b34]
	at org.jvnet.hk2.internal.FactoryCreator.dispose(FactoryCreator.java:173)[150:org.glassfish.hk2.locator:2.4.0.b34]
	at org.jvnet.hk2.internal.SystemDescriptor.dispose(SystemDescriptor.java:526)[150:org.glassfish.hk2.locator:2.4.0.b34]
	at org.glassfish.jersey.process.internal.RequestScope$Instance.remove(RequestScope.java:532)[157:org.glassfish.jersey.core.jersey-common:2.22.2]
	at org.glassfish.jersey.process.internal.RequestScope$Instance.release(RequestScope.java:549)[157:org.glassfish.jersey.core.jersey-common:2.22.2]
	at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:319)[157:org.glassfish.jersey.core.jersey-common:2.22.2]
	at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305)[158:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154)[158:org.glassfish.jersey.core.jersey-server:2.22.2]
	at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473)[155:org.glassfish.jersey.containers.jersey-container-servlet-core:2.22.2]
	... 26 more
Caused by: java.lang.IllegalStateException: ServiceLocatorImpl(__HK2_Generated_5,6,15108875) has been shut down
	at org.jvnet.hk2.internal.ServiceLocatorImpl.checkState(ServiceLocatorImpl.java:2288)[150:org.glassfish.hk2.locator:2.4.0.b34]
	at org.jvnet.hk2.internal.ServiceLocatorImpl.getServiceHandleImpl(ServiceLocatorImpl.java:629)[150:org.glassfish.hk2.locator:2.4.0.b34]
	at org.jvnet.hk2.internal.ServiceLocatorImpl.getServiceHandle(ServiceLocatorImpl.java:622)[150:org.glassfish.hk2.locator:2.4.0.b34]
	at org.jvnet.hk2.internal.ServiceLocatorImpl.getServiceHandle(ServiceLocatorImpl.java:640)[150:org.glassfish.hk2.locator:2.4.0.b34]
	at org.jvnet.hk2.internal.FactoryCreator.getFactoryHandle(FactoryCreator.java:103)[150:org.glassfish.hk2.locator:2.4.0.b34]
	... 34 more
2017-02-12 22:33:26.464 [WARN ] [org.eclipse.jetty.server.HttpChannel] - Could not send response error 500: javax.servlet.ServletException: javax.servlet.ServletException: A MultiException has 1 exceptions.  They are:
1. java.lang.IllegalStateException: ServiceLocatorImpl(__HK2_Generated_5,6,15108875) has been shut down

can someone translate this looooong error to a short easy Information?

13

Have you tried:

ignorelocalevents=true

in the `/etc/openhab2/services/knc.cfg ?

The other jetty (web server) errors
 I don’t know what this could be
 :frowning:
They come up only at OH2 startup or also after?

14

Thanks for Feedback.
i have just a simple test “running” with this config:

knx.cfg

ip=192.168.5.4
busaddr=1.1.202
ignorelocalevents=true
type=TUNNEL
readRetries = 1

knx.items

Switch		knx_licht_Schalter					"Licht"					<light>				(Licht, rOG_Office)						{ knx="1.001:4/0/5" }

nima.sitemap

sitemap nima label="Main Menu" {
    Frame label="test" {
		Switch item=knx_licht_Schalter label="knx_licht_Schalter"
		Text item=wetter_Temperature label="wetter_Temperature"
		}
	}

and get this logs:
openhab.log

2017-02-13 21:44:26.087 [INFO ] [ore.internal.i18n.LocaleProviderImpl] - Locale set to de_DE
2017-02-13 21:44:31.511 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'weather.items'
2017-02-13 21:44:31.703 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'knx.items'
2017-02-13 21:44:35.789 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'nima.sitemap'
2017-02-13 21:44:37.688 [INFO ] [.dashboard.internal.DashboardService] - Started dashboard at /start
2017-02-13 21:44:39.428 [INFO ] [basic.internal.servlet.WebAppServlet] - Started Basic UI at /basicui/app
2017-02-13 21:44:39.769 [INFO ] [assic.internal.servlet.WebAppServlet] - Started Classic UI at /classicui/app
2017-02-13 21:44:40.002 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui
2017-02-13 21:44:40.285 [INFO ] [ui.habmin.internal.servlet.HABminApp] - Started HABmin servlet at /habmin
2017-02-13 21:44:40.375 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
2017-02-13 21:44:41.050 [INFO ] [nx.internal.connection.KNXConnection] - Established connection to KNX bus on 192.168.5.4:3671 in mode TUNNEL.
2017-02-13 21:44:41.283 [INFO ] [eather.internal.common.WeatherConfig] - ProviderConfig[providerName=OPENWEATHERMAP,apiKey=d750daed61cc46dd99e33b23504c75cb]
2017-02-13 21:44:45.622 [INFO ] [eather.internal.common.WeatherConfig] - ProviderConfig[providerName=WORLDWEATHERONLINE,apiKey=e7b92e7354194ff9a2b61927162705]
2017-02-13 21:44:45.624 [INFO ] [eather.internal.common.WeatherConfig] - LocationConfig[providerName=OPENWEATHERMAP,language=de,updateInterval=15,latitude=49.403091,longitude=11.75807,woeid=701860,locationId=ursensollen,name=Ursensollen]
2017-02-13 21:44:44.288 [INFO ] [ternal.scheduler.WeatherJobScheduler] - Starting and scheduling weatherJob-ursensollen with interval of 15 minutes
2017-02-13 21:44:48.628 [INFO ] [ternal.scheduler.WeatherJobScheduler] - Deleting weatherJob-ursensollen
2017-02-13 21:44:48.632 [INFO ] [ternal.scheduler.WeatherJobScheduler] - Starting and scheduling weatherJob-ursensollen with interval of 15 minutes
2017-02-13 21:45:11.146 [WARN ] [.binding.knx.internal.bus.KNXBinding] - Value 'ON' could not be sent to the KNX bus using datapoint 'command DP 4/0/5 knx_licht_Schalter, DPT main 0 id 1.001, low priority' - retrying one time: no confirmation reply received for L-Data.req from 1.1.202 to 4/0/5, low priority hop count 6 repeat tpdu 00 81
2017-02-13 21:45:11.150 [WARN ] [tuwien.auto.calimero                ] - KNXnet/IP Tunneling 192.168.5.4:3671: response timeout waiting for confirmation
tuwien.auto.calimero.exception.KNXTimeoutException: no confirmation reply received for L-Data.req from 1.1.202 to 4/0/5, low priority hop count 6 repeat tpdu 00 81
	at tuwien.auto.calimero.knxnetip.ClientConnection.doExtraBlockingModes(ClientConnection.java:236)[208:org.openhab.binding.knx:1.9.0]
	at tuwien.auto.calimero.knxnetip.ConnectionBase.send(ConnectionBase.java:269)[208:org.openhab.binding.knx:1.9.0]
	at tuwien.auto.calimero.knxnetip.KNXnetIPTunnel.send(KNXnetIPTunnel.java:149)[208:org.openhab.binding.knx:1.9.0]
	at tuwien.auto.calimero.link.KNXNetworkLinkIP.onSend(KNXNetworkLinkIP.java:263)[208:org.openhab.binding.knx:1.9.0]
	at tuwien.auto.calimero.link.AbstractLink.send(AbstractLink.java:304)[208:org.openhab.binding.knx:1.9.0]
	at tuwien.auto.calimero.link.KNXNetworkLinkIP.sendRequestWait(KNXNetworkLinkIP.java:240)[208:org.openhab.binding.knx:1.9.0]
	at tuwien.auto.calimero.process.ProcessCommunicatorImpl.write(ProcessCommunicatorImpl.java:466)[208:org.openhab.binding.knx:1.9.0]
	at tuwien.auto.calimero.process.ProcessCommunicatorImpl.write(ProcessCommunicatorImpl.java:438)[208:org.openhab.binding.knx:1.9.0]
	at org.openhab.binding.knx.internal.bus.KNXBinding.writeToKNX(KNXBinding.java:149)[208:org.openhab.binding.knx:1.9.0]
	at org.openhab.binding.knx.internal.bus.KNXBinding.internalReceiveCommand(KNXBinding.java:112)[208:org.openhab.binding.knx:1.9.0]
	at org.openhab.core.binding.AbstractBinding.receiveCommand(AbstractBinding.java:97)[176:org.openhab.core.compat1x:2.0.0]
	at org.openhab.core.events.AbstractEventSubscriber.handleEvent(AbstractEventSubscriber.java:42)[176:org.openhab.core.compat1x:2.0.0]
	at org.apache.felix.eventadmin.impl.handler.EventHandlerProxy.sendEvent(EventHandlerProxy.java:415)[6:org.apache.karaf.services.eventadmin:4.0.8]
	at org.apache.felix.eventadmin.impl.tasks.HandlerTask.run(HandlerTask.java:90)[6:org.apache.karaf.services.eventadmin:4.0.8]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_65]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_65]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_65]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_65]
	at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]
2017-02-13 21:45:14.158 [WARN ] [tuwien.auto.calimero                ] - KNXnet/IP Tunneling 192.168.5.4:3671: response timeout waiting for confirmation
tuwien.auto.calimero.exception.KNXTimeoutException: no confirmation reply received for L-Data.req from 1.1.202 to 4/0/5, low priority hop count 6 repeat tpdu 00 81
	at tuwien.auto.calimero.knxnetip.ClientConnection.doExtraBlockingModes(ClientConnection.java:236)[208:org.openhab.binding.knx:1.9.0]
	at tuwien.auto.calimero.knxnetip.ConnectionBase.send(ConnectionBase.java:269)[208:org.openhab.binding.knx:1.9.0]
	at tuwien.auto.calimero.knxnetip.KNXnetIPTunnel.send(KNXnetIPTunnel.java:149)[208:org.openhab.binding.knx:1.9.0]
	at tuwien.auto.calimero.link.KNXNetworkLinkIP.onSend(KNXNetworkLinkIP.java:263)[208:org.openhab.binding.knx:1.9.0]
	at tuwien.auto.calimero.link.AbstractLink.send(AbstractLink.java:304)[208:org.openhab.binding.knx:1.9.0]
	at tuwien.auto.calimero.link.KNXNetworkLinkIP.sendRequestWait(KNXNetworkLinkIP.java:240)[208:org.openhab.binding.knx:1.9.0]
	at tuwien.auto.calimero.process.ProcessCommunicatorImpl.write(ProcessCommunicatorImpl.java:466)[208:org.openhab.binding.knx:1.9.0]
	at tuwien.auto.calimero.process.ProcessCommunicatorImpl.write(ProcessCommunicatorImpl.java:438)[208:org.openhab.binding.knx:1.9.0]
	at org.openhab.binding.knx.internal.bus.KNXBinding.writeToKNX(KNXBinding.java:158)[208:org.openhab.binding.knx:1.9.0]
	at org.openhab.binding.knx.internal.bus.KNXBinding.internalReceiveCommand(KNXBinding.java:112)[208:org.openhab.binding.knx:1.9.0]
	at org.openhab.core.binding.AbstractBinding.receiveCommand(AbstractBinding.java:97)[176:org.openhab.core.compat1x:2.0.0]
	at org.openhab.core.events.AbstractEventSubscriber.handleEvent(AbstractEventSubscriber.java:42)[176:org.openhab.core.compat1x:2.0.0]
	at org.apache.felix.eventadmin.impl.handler.EventHandlerProxy.sendEvent(EventHandlerProxy.java:415)[6:org.apache.karaf.services.eventadmin:4.0.8]
	at org.apache.felix.eventadmin.impl.tasks.HandlerTask.run(HandlerTask.java:90)[6:org.apache.karaf.services.eventadmin:4.0.8]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_65]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_65]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_65]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_65]
	at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]
2017-02-13 21:45:14.158 [ERROR] [.binding.knx.internal.bus.KNXBinding] - Value 'ON' could not be sent to the KNX bus using datapoint 'command DP 4/0/5 knx_licht_Schalter, DPT main 0 id 1.001, low priority' - giving up after second try: no confirmation reply received for L-Data.req from 1.1.202 to 4/0/5, low priority hop count 6 repeat tpdu 00 81
2017-02-13 21:52:15.060 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'nima.sitemap'
2017-02-13 21:52:15.092 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'nima.sitemap'

Events.log

2017-02-13 21:44:36.490 [ThingAddedEvent           ] - Thing 'ntp:ntp:local' has been added.
2017-02-13 21:44:43.706 [hingStatusInfoChangedEvent] - 'ntp:ntp:local' changed from UNINITIALIZED to INITIALIZING
2017-02-13 21:44:43.804 [hingStatusInfoChangedEvent] - 'ntp:ntp:local' changed from INITIALIZING to ONLINE
2017-02-13 21:44:44.971 [ItemStateChangedEvent     ] - wetter_Temperature changed from NULL to 1.99
2017-02-13 21:45:08.118 [ItemCommandEvent          ] - Item 'knx_licht_Schalter' received command ON
2017-02-13 21:45:08.138 [ItemStateChangedEvent     ] - knx_licht_Schalter changed from NULL to ON

ETS:Groupmonitor

etslog.png1256×93 12.3 KB

at the moment i don`t know openhab is the right one for me.
i get 44 lines of error but no Information about my Problem :rage:

15

nobody now something about this Problem? is the configuration ok? is the bous 771 not supported?

16

hmm i have problems with my Weinzierl baos 771
in this post mclane hase a Weinzierl 731 OH2 repeated writes to KNX interface and problems

DirkSander say`s he has/had problems with his “IP-BAOS” in this post: OH2 KNX 1.9 Binding - read from KNX results in a write

have someone no problems with a Weinzierl Gateway?

17

Now it Looks good with this config:

ip=192.168.5.4
busaddr=1.1.202
ignorelocalevents=true
type=TUNNEL
readRetries = 0

and this KNX Version (1.9.0-201611251544)

18

Hallo MikeFo,

I’m using also the PROServ IP Gatway and face the same issue. I read so many posts but I could not find a solution. It drives me crazy. Do you have found the problem or a workaround? If yes could you share them with me?

My test project was working fine in openhab 1 but I decided to go with OH2 for the final. I playing since three weeks only with the KNX binding and can’t find a solution but my project is 80% based on this.

Any help is highly appreciated.

Thank you very much in advance.

Marcel

1 Like
19

Hello Marcel,

This here was the solution for me, until version 2.x of the knx binding is available. I hope that will be helpful for you as well.

Michael

20

Hallo Michael,

Thnak you very very much. it works for me as well.

Marcel