KNX Rollershutter - unexpected deterministic behavior

Norman_Trapp · March 11, 2022, 4:02pm

Platform information:
- Hardware: RP3b+
- OS: _openhabian (latest stable) Linux/5.10.63-v8+ (aarch64)
- Java Runtime Environment: 11.0.12 (Zulu11.50+19-CA)
- openHAB version: 3.2.0

I have configured several shutters. In KNX they are connected to 3 different actuators.
2 actuators control the shutters, 1 actuator controls the blinds.
I have configured the shutters and blinds in OH3.
One is working properly. Up/down and stop work correctly. One moves up with the down command and down with the up command.
All others move up or down. However, they do not stop even though the stop command is sent from OH3.
I currently cannot find the error. Everything is configured identically. Both in OH3 and in the ETS.
Does anyone have any idea how I can approach the problem?

2022-03-11 16:36:17.172 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'SchalterRolloKueche_RolloKueche' changed from 100 to 0
2022-03-11 16:36:39.297 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'SchalterRolloKueche_RolloKueche' changed from NULL to 0
2022-03-11 16:36:39.298 [INFO ] [openhab.event.ItemUpdatedEvent      ] - Item 'SchalterRolloKueche_RolloKueche' has been updated.
2022-03-11 16:37:24.645 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'SchalterRolloKueche_RolloKueche' received command DOWN
2022-03-11 16:37:24.648 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'SchalterRolloKueche_RolloKueche' predicted to become DOWN
2022-03-11 16:37:24.656 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'SchalterRolloKueche_RolloKueche' changed from 0 to 100
2022-03-11 16:37:29.068 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'SchalterRolloKueche_RolloKueche' received command STOP
2022-03-11 16:37:30.058 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'SchalterRolloKueche_RolloKueche' received command STOP
2022-03-11 16:37:30.513 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'SchalterRolloKueche_RolloKueche' received command STOP
2022-03-11 16:37:30.759 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'SchalterRolloKueche_RolloKueche' received command STOP
2022-03-11 16:37:30.939 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'SchalterRolloKueche_RolloKueche' received command STOP
2022-03-11 16:37:31.131 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'SchalterRolloKueche_RolloKueche' received command STOP
2022-03-11 16:37:31.299 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'SchalterRolloKueche_RolloKueche' received command STOP
2022-03-11 16:37:32.246 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'SchalterRolloKueche_RolloKueche' received command UP
2022-03-11 16:37:32.248 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'SchalterRolloKueche_RolloKueche' predicted to become UP
2022-03-11 16:37:32.252 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'SchalterRolloKueche_RolloKueche' changed from 100 to 0
2022-03-11 16:37:56.778 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'SchalterRolloKueche_RolloKueche' received command STOP
2022-03-11 16:37:59.668 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'SchalterRolloKueche_RolloKueche' received command DOWN
2022-03-11 16:37:59.671 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'SchalterRolloKueche_RolloKueche' predicted to become DOWN
2022-03-11 16:37:59.675 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'SchalterRolloKueche_RolloKueche' changed from 0 to 100
2022-03-11 16:38:02.434 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'SchalterRolloKueche_RolloKueche' received command STOP
2022-03-11 16:38:03.569 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'SchalterRolloKueche_RolloKueche' received command UP
2022-03-11 16:38:03.572 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'SchalterRolloKueche_RolloKueche' predicted to become UP
2022-03-11 16:38:03.579 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'SchalterRolloKueche_RolloKueche' changed from 100 to 0

stamate_viorel · March 11, 2022, 6:09pm

Without showing your configuration items things and maybe Knx ets screenshot you probably won’t get to much help just with the logs…

Norman_Trapp · March 12, 2022, 10:33am

Here the Thing configuration:

UID: knx:device:a3cf9e2b89:df9f8e3041
label: Schalter Rollo Küche
thingTypeUID: knx:device
configuration:
  pingInterval: 300
  readInterval: 0
  fetch: true
bridgeUID: knx:ip:a3cf9e2b89
location: Küche
channels:
  - id: Schalter_Rollo_Kueche
    channelTypeUID: knx:rollershutter-control
    label: Rollo Küche
    description: ""
    configuration:
      upDown: 2/1/2
      stopMove: 2/1/0

Here the item configuration in OH3:

Here the ETS configuration:

stamate_viorel · March 12, 2022, 7:02pm

From the look at your thing i cannot determine if you choose router or tunnel and the Knx topology in ets but nevertheless if you have multiple lines in your Knx then make sure the group adresses you want to read or write are passing trough your filter tables toward the tunnel or router on that specific line. Hope it makes sense what I mean. Also I highly recomand not to use up down if your Knx module can provide and absolute control and value this way you can really have some feedback and finer control

Norman_Trapp · March 13, 2022, 11:36am

I’m running in tunneling mode. I’ve only one Line in KNX 1.1
The KNX configuration on each rollershutter is exactly the same, also the OH configuration.
The strange thing ist that some rollershutter doesn’t recognize the Stop command.
Unfortunable I can only use one connection to the KNX Bus, cause my IP Gateway doens’t support more than one tunnel. So I not able to debug the communication on both sides simultaneously.
The KNX configuration is running fine since years, so i don’t want to change it, if there ist no need to.

stamate_viorel · March 13, 2022, 2:23pm

Well let’s start by checking the flags on all the stop groups devices making a comparison between working group adress and not working. Also i saw you left fetch true on the thing and put the read to 0 i would change fetch to false and read to something reasonable like 300. After you did all this and still doesn’t work let’s do a test with ets in monitor group and try to stop from withing ets. If that doesn’t work then use a cable and connect directly to your Knx tunnel device and check again if yes then you have network problem. Another thing i can think of is that because you let openhab predict it’s state of the item so i will add an autoupdate false metadata to the item.
Let me know