Rollershutter Stop does not trigger KNX telegram

Hi.

I got here a very strange behavior and after days of testing I am stuck.

Working with OH2.1 and KNX Binding 1.9.

I want to integrate Rollershutters with Blinds. UP/DOWN is working well but the Stop Button does nothing (X in the middle)

I got an item:

Rollershutter Raff "Raff [%d %%]" (EG) { knx="3/1/11, 3/2/11, 5.001:3/5/11" }

Activating UP:

19:00:00.398 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'Raff' received command UP
19:00:00.403 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Wrote value 'UP' to datapoint 'command DP 3/1/11 Raff, DPT main 0 id 1.008, low priority

Activating DOWN:

19:00:19.830 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'Raff' received command DOWN
19:00:19.834 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Wrote value 'DOWN' to datapoint 'command DP 3/1/11 Raff, DPT main 0 id 1.008, low priority'

Activating Stop (X):

19:00:03.070 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'Raff' received command STOP

Nothing more, not in the log, not in Busmonitor. As if the ItemCommandEvent would not trigger anything.

GA’s are not used twice or otherwise in any kind.

I also found a possible workaround but the situation is still very confusing:

Another item + rule

Switch RaffStop {knx="3/2/11"}
rule "raff"
    when
        Item Raff received command STOP
    then
        sendCommand(RaffStop, OFF)
    end

Please, is someone able to enlighten me this issue?

Thanks in advance.

Regards

Rob

Strange…
Have you tried to remove the DPT from the status GA to see if this helps?
or add 1:007 to the stop/step GA

You could enable TRACE on both related bundles to see if you find more useful info:

log:set TRACE org.openhab.binding.knx
log:set TRACE tuwien.auto.calimero

I am running OH 2.2.0 Snapshot 978 with org.openhab.binding.knx 1.11.0.201707030109 (not big diff from your setup) and it works fine.
The telegram (ETS view) is:

Hi.

Thx for your reply.

I played already a lot with various DPT’s without success. The MDT actor uses 1.009 for the stop/step.

I have enabled the suggested logs.

Activating Stop (X):

2017-07-04 20:45:07.361 [ItemCommandEvent          ] - Item 'Raff' received command STOP
2017-07-04 20:45:07.362 [TRACE] [.binding.knx.internal.bus.KNXBinding] - 1. internalReceiveCommand from openHAB (item='Raff', command='STOP', operatingEnvironmentIsFelix = 'true'

No telegram in ETS.

It stucks in a very high level of the binding compared to other sucessful command. Not even a trace from calimero.

A good command like DOWN looks like this:

2017-07-04 20:50:48.398 [TRACE] [.binding.knx.internal.bus.KNXBinding] - 1. internalReceiveCommand from openHAB (item='Raff', command='DOWN', operatingEnvironmentIsFelix = 'true'
2017-07-04 20:50:48.398 [TRACE] [.binding.knx.internal.bus.KNXBinding] - 2. internalReceiveUpdate from openHAB (item='Raff', state='DOWN')
2017-07-04 20:50:48.399 [TRACE] [g.knx.internal.dpt.KNXCoreTypeMapper] - toTypeClass looking for dptId = 1.008
2017-07-04 20:50:48.399 [TRACE] [g.knx.internal.dpt.KNXCoreTypeMapper] - toTypeClass looking for dptId = 1.009
2017-07-04 20:50:48.399 [TRACE] [g.knx.internal.dpt.KNXCoreTypeMapper] - toTypeClass looking for dptId = 5.001
2017-07-04 20:50:48.399 [INFO ] [tuwien.auto.calimero                ] - calimero.link.IP:3671: send message to 3/1/11, wait for confirmation
2017-07-04 20:50:48.399 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.IP:3671: cEMI L-Data.req from 0.0.2 to 3/1/11, low priority hop count 6 repeat tpdu 00 81
2017-07-04 20:50:48.400 [DEBUG] [tuwien.auto.calimero                ] - KNXnet/IP Tunneling IP:3671: sending cEMI frame seq 100, wait for cEMI.con, attempt 1 (channel 9) 06 10 04 20 00 15 04 09 64 00 11 00 bc e0 00 02 19 0b 01 00 81
2017-07-04 20:50:48.401 [DEBUG] [tuwien.auto.calimero                ] - KNXnet/IP Tunneling IP:3671: received cEMI L-Data.con with req 208
2017-07-04 20:50:48.402 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.IP:3671: confirmation of 3/1/11
2017-07-04 20:50:48.402 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Wrote value 'DOWN' to datapoint 'command DP 3/1/11 Raff, DPT main 0 id 1.008, low priority'
2017-07-04 20:50:48.402 [DEBUG] [tuwien.auto.calimero                ] - calimero.link.IP:3671: send to 3/1/11 succeeded
2017-07-04 20:50:48.403 [DEBUG] [tuwien.auto.calimero                ] - process IP:3671: group write to 3/1/11 succeeded

Regards

Rob

Hi!

I still have no idea why this isn’t working for me, but I got another strange behavior which may contribute to the overall picture.

I created anoter item in order to control the blinds.

Rollershutter	Raff_EG_KU_Blind "Küche Lamelle [%d %%]"		(EG_Kitchen, HOME_Rollershutter) 	{knx="3/2/20, 3/2/20, 3/4/20"}

3/2/20 GA for Step/Move and 3/4/20 for Absolute Blind Position.

Works like a charm.

Now I want to add the Status GA for the Absolute Blind Position to read the percentage (3/6/20)

Rollershutter	Raff_EG_KU_Blind "Küche Lamelle [%d %%]"		(EG_Kitchen, HOME_Rollershutter) 	{knx="3/2/20, 3/2/20, 3/4/20+3/6/20"}

Again - command broken and does nothing anymore.

No exeption, no error , no nothing.

Maybe someone got an idea.

Thanks.

Regards

Rob