Switch in *.item file does not switch KNX actuator

  • Platform information: Raspberry pi 3 model b Rev 1.2
  • OS: Rasbian GNU/Linux 9
  • openHAB version: 2.5.2.1

Since couple of weeks i am unable to turn on/off lights or rollershutters. I am able to switch the buttons in my openhab app but the actuator do not recognize the command anymore…The KNX config file is looking good… IP Adresses of my Raspberry or my KNX IP interface (MDT IP Interface) hasn’t changed. And “Tunnel” is activated as well.i doublechecked the KNX adresses within ETS5 and everything is correct…

Any idea how i can troubleshoot on this?

Thanks in advance,
Stef

Did you try a restart or openHAB?

thanks for your reply.

yes i tried many times… i am running out of ideas and hope someone can give me a hint :slightly_smiling_face:

Well, then raise the log level for knx to DEBUG. Maybe the log will show some details.

is that the right one?

2020-03-05 20:47:08.303 [ome.event.ItemCommandEvent] - Item ‘Licht_OG_Ankleidezimmer’ received command OFF

2020-03-05 20:47:08.320 [vent.ItemStateChangedEvent] - Licht_OG_Ankleidezimmer changed from ON to OFF

==> /var/log/openhab2/openhab.log <==

2020-03-05 20:47:52.282 [WARN ] [ueemulation.internal.upnp.UpnpServer] - Could not send UPNP response: Cannot assign requested address (sendto failed)

No, you have to raise the log level. Use the karaf console:

[23:44:27] openhabian@openhab2:~$ openhab-cli console

Logging in as openhab
Password:

                          __  _____    ____
  ____  ____  ___  ____  / / / /   |  / __ )
 / __ \/ __ \/ _ \/ __ \/ /_/ / /| | / __  |
/ /_/ / /_/ /  __/ / / / __  / ___ |/ /_/ /
\____/ .___/\___/_/ /_/_/ /_/_/  |_/_____/
    /_/                        2.5.2
                               Release Build

Hit '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown openHAB.

openhab> log:set DEBUG org.openhab.binding.knx      
openhab> log:list
Logger                                             │ Level
───────────────────────────────────────────────────┼──────
ROOT                                               │ WARN
javax.jmdns                                        │ ERROR
javax.mail                                         │ ERROR
org.apache.karaf.jaas.modules.audit                │ INFO
org.apache.karaf.kar.internal.KarServiceImpl       │ ERROR
org.apache.karaf.shell.ssh.SshUtils                │ ERROR
org.apache.karaf.shell.support                     │ OFF
org.eclipse.lsp4j                                  │ OFF
org.eclipse.smarthome                              │ INFO
org.jupnp                                          │ ERROR
org.openhab.binding.knx                            │ DEBUG
org.openhab                                        │ INFO
org.openhab.ui.paper                               │ WARN
org.openhab.ui.paper.internal                      │ INFO
org.ops4j.pax.url.mvn.internal.AetherBasedResolver │ ERROR
org.ops4j.pax.web.pax-web-runtime                  │ OFF
smarthome.event                                    │ INFO
smarthome.event.InboxUpdatedEvent                  │ ERROR
smarthome.event.ItemAddedEvent                     │ ERROR
smarthome.event.ItemRemovedEvent                   │ ERROR
smarthome.event.ItemStateEvent                     │ ERROR
smarthome.event.ThingAddedEvent                    │ ERROR
smarthome.event.ThingRemovedEvent                  │ ERROR
smarthome.event.ThingStatusInfoEvent               │ ERROR
openhab> logout
[23:45:20] openhabian@openhab2:~$

So the first step is to login to karaf. The second step is to set the log level to DEBUG. The third step is to check, if the setting is correct (not essential :wink: ) and the last step is to logout from karaf.
To get all information from begin, restart openHAB. Check only openhab.log. (var/log/openhab2/openhab.log) because frontail will give you much to much information in addition.

In addition to what @Udo_Hartmann was saying, you could also check ETS5’s bus protocol if there are any GA-commands on the bus.

In addition to restarting OH try cleaning the cache.

sudo systemctl stop openhab2

sudo openhab-cli clean-cache

sudo systemclt start openhab2

Hi Udo_Hartmann,
i enabled the debugging on knx and got the following result:

at org.eclipse.osgi.container.Module.start(Module.java:444) ~[org.eclipse.osgi-3.12.100.jar:?]
at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) ~[org.eclipse.osgi-3.12.100.jar:?]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [bundleFile:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [bundleFile:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1221) [bundleFile:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:515) [bundleFile:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [bundleFile:3.6.4]
at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [bundleFile:3.6.4]

2020-03-06 18:57:36.767 [WARN ] [ueemulation.internal.upnp.UpnpServer] - Could not send UPNP response: Cannot assign requested address (sendto failed)
2020-03-06 18:59:48.207 [WARN ] [ueemulation.internal.upnp.UpnpServer] - Could not send UPNP response: Cannot assign requested address (sendto failed)
2020-03-06 19:01:48.209 [WARN ] [ueemulation.internal.upnp.UpnpServer] - Could not send UPNP response: Cannot assign requested address (sendto failed)

could be that the hue emulation causes this issue??

Thank you anyway for your advise!!

Thanks for the hint, tried it out without success.

do you mean to start “Busmonitor” ? i have started it and check if i get a response - if a get a response i will double check the KNX adresses - hopefully there was no change. i can’t imagine that this will be changed automatically… (i hope so) :slight_smile:

Thank you so much for your help as well :slight_smile:

No, this is nothing about knx.

Did you restart openHAB?

yes
sudo reboot

it seems when i push the light button, nothing happens… absolut nothing…

i have an image (backup) of an very old openhab 2 version … do you think it make sens to try it out with antoher SD card and check if it is working?

No, the point of restarting openHAB is, to get a complete debug from knx binding, so where is the debug of knx?

i doublechecked the debug configuration:

ROOT │ WARN
javax.jmdns │ ERROR
javax.mail │ ERROR
org.apache.karaf.jaas.modules.audit │ INFO
org.apache.karaf.kar.internal.KarServiceImpl │ ERROR
org.apache.karaf.shell.ssh.SshUtils │ ERROR
org.apache.karaf.shell.support │ OFF
org.eclipse.lsp4j │ OFF
org.eclipse.smarthome │ INFO
org.jupnp │ ERROR
org.openhab │ INFO
org.openhab.binding.knx │ DEBUG
org.openhab.ui.paper │ WARN
org.openhab.ui.paper.internal │ INFO
org.ops4j.pax.url.mvn.internal.AetherBasedResolver │ ERROR
org.ops4j.pax.web.pax-web-runtime │ OFF
smarthome.event │ INFO
smarthome.event.InboxUpdatedEvent │ ERROR
smarthome.event.ItemAddedEvent │ ERROR
smarthome.event.ItemRemovedEvent │ ERROR
smarthome.event.ItemStateEvent │ ERROR
smarthome.event.ThingAddedEvent │ ERROR
smarthome.event.ThingRemovedEvent │ ERROR

and from the point of reboot, there is nothing in the logfile regarding knx … did i miss somthig to add?

Then I doubt that knx binding is installed.

1 Like

sorry to bother you …

should i uninstall it reinstall it?

Sure.

as soon the knx binding is installed i should find “knx.cfg” in the services folder - right?
or is it now located in another folder?

btw.: thank you very much for your help

I guess i found the problem!!!

i had to enable “Include Legacy 1.x Bindings”

than i was able to install “knx binding 1.x” where i can use my knx.cfg file …

Udo thank you so much for the hint with the binding - that was the correct hint to find the solution!! :slight_smile:

THANK you so much!!