openHAB 2.3 connect but does not write to KNX bus

misam · September 14, 2018, 11:38am

I’ve done a clean setup of openhab 2.3, but despite of knx bridge result online write commands are not sended to the knx bus. KNX bus is connected and read values but doesn’t write commands even the event log reports the state change record. It’s really weird. I’ve already tried TUNNEL and ROUTER mode with and without parameters in different combinations.
Maybe it’s a problem similar to
https://community.openhab.org/t/send-value-to-knx/46676
https://community.openhab.org/t/no-sending-from-knx2-binding/45930/4
https://community.openhab.org/t/problems-with-knx/33373
None of the solutions previously proposed seems work to me.
Currently my setup it’s like that

knx.things

Bridge knx:ip:bridge [ 
    type="ROUTER",
    localSourceAddr="1.0.255"
]
{
    Thing device switch {
        Type switch        : scale_interrato                  "Switch"       [ ga="0/0/32+<0/1/32" ]
    }
}

knx.items

Switch scale_interrato              "Scale interrato"                 {channel="knx:device:bridge:switch:scale_interrato" }

I have separated the logs in different files. They report something like that

openhab.log

14-set-2018 12:13:10.382 [TRACE] [nhab.binding.knx.internal.client.AbstractKNXClient] - Received a Group Write telegram from '1.1.37' to '0/0/32'

events.log
initializing and status reading

2018-09-14 12:06:35.209 [hingStatusInfoChangedEvent] - 'knx:ip:bridge' changed from UNINITIALIZED to INITIALIZING
2018-09-14 12:06:35.227 [hingStatusInfoChangedEvent] - 'knx:ip:bridge' changed from INITIALIZING to UNKNOWN
2018-09-14 12:06:35.379 [hingStatusInfoChangedEvent] - 'knx:device:bridge:dimmer' changed from UNINITIALIZED to INITIALIZING
2018-09-14 12:06:35.410 [hingStatusInfoChangedEvent] - 'knx:device:bridge:dimmer' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE)
2018-09-14 12:06:35.469 [hingStatusInfoChangedEvent] - 'knx:device:bridge:switch' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_CONF$
2018-09-14 12:06:35.548 [hingStatusInfoChangedEvent] - 'knx:device:bridge:termostati' changed from UNINITIALIZED to INITIALIZING
2018-09-14 12:06:35.553 [hingStatusInfoChangedEvent] - 'knx:device:bridge:termostati' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE)
2018-09-14 12:06:35.561 [hingStatusInfoChangedEvent] - 'knx:device:bridge:contact' changed from UNINITIALIZED to INITIALIZING
2018-09-14 12:06:35.572 [hingStatusInfoChangedEvent] - 'knx:device:bridge:contact' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE)
2018-09-14 12:06:35.682 [hingStatusInfoChangedEvent] - 'knx:ip:bridge' changed from UNKNOWN to ONLINE
2018-09-14 12:06:35.697 [hingStatusInfoChangedEvent] - 'knx:device:bridge:dimmer' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
2018-09-14 12:06:35.699 [hingStatusInfoChangedEvent] - 'knx:device:bridge:termostati' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
2018-09-14 12:06:35.704 [hingStatusInfoChangedEvent] - 'knx:device:bridge:contact' changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE

commands

2018-09-14 12:06:52.506 [ome.event.ItemCommandEvent] - Item 'scale_interrato' received command ON
2018-09-14 12:06:52.518 [vent.ItemStateChangedEvent] - scale_interrato changed from NULL to ON
2018-09-14 12:06:53.360 [ome.event.ItemCommandEvent] - Item 'scale_interrato' received command OFF
2018-09-14 12:06:53.382 [vent.ItemStateChangedEvent] - scale_interrato changed from ON to OFF

example of successful read of another item

2018-09-14 12:13:02.536 [vent.ItemStateChangedEvent] - temperatura_soggiorno changed from 24.66 to 24.72

calimero.log

4-set-2018 12:13:10.382 [DEBUG] [calimero.link.224.0.23.12:3671                    ] - indication 1.1.37->0/0/32 L_Data.ind, low priority hop count 5, tpdu 00 81

I can’t find any log record that reports a write or send or whatever command to the KNX bus, or at least i can’t recognize it.
That’s very strange because once the KNX bus connection is up and running i’ll expect that both read and write works.

Udo_Hartmann · September 14, 2018, 11:47am

As you set two GA for the swtich, please add the DPT as a first test:

Bridge knx:ip:bridge [ 
    type="ROUTER",
    localIp="192.168.x.y",  // this parameter is not optional if using ROUTER mode!
    localSourceAddr="1.0.255" //maybe don't use this parameter at all for first atempts
]
{
    Thing device switch {
        Type switch        : scale_interrato                  "Switch"       [ ga="1.001:0/0/32+<0/1/32" ]
                                                                             //    ^^^^^^
    }
}

misam · September 14, 2018, 12:11pm

Great i’m not at home now and i cannot confirm if really the light switch on, BUT thanks to you now at least i see the send commands in the calimero log

14-set-2018 14:05:11.535 [DEBUG] [calimero.link.224.0.23.12:3671                    ] - send (wait for confirmation) 0.0.0->0/0/32 L_Data.ind, low priority hop count 6, tpdu 00 81
14-set-2018 14:05:11.538 [TRACE] [limero.knxnetip.KNXnet/IP Routing 224.0.23.12:3671] - add to multicast loopback frame buffer: 0.0.0->0/0/32 L_Data.ind, low priority hop count 6, tpdu 00 81
14-set-2018 14:05:11.541 [TRACE] [limero.knxnetip.KNXnet/IP Routing 224.0.23.12:3671] - sending cEMI frame seq 0, NonBlocking, attempt 1 (channel 0) 06 10 05 30 00 11 29 00 bc e0 00 00 00 20 01 00 81
14-set-2018 14:05:11.543 [TRACE] [limero.knxnetip.KNXnet/IP Routing 224.0.23.12:3671] - discard multicast loopback cEMI frame: 0.0.0->0/0/32 L_Data.ind, low priority hop count 6, tpdu 00 81
14-set-2018 14:05:11.543 [TRACE] [calimero.link.224.0.23.12:3671                    ] - send 0.0.0->0/0/32 succeeded
14-set-2018 14:05:11.546 [TRACE] [calimero.process.process 224.0.23.12:3671         ] - group write to 0/0/32 succeeded

this makes me think that now all will work. I’m gonna thank you again once checked at home

P.S. just to be sure, it is correct to setup a dimmer like this?

Type dimmer        : soggiorno      "Dimmer"            [ switch="1.001:0/6/1+<0/4/1", position="5.001:0/2/51", increaseDecrease="3.007:0/0/51+<0/1/51" ]

Udo_Hartmann · September 14, 2018, 1:22pm

Yes and no Yes, the definition should work, but the correct configuration would be more like this:

Assuming that

0/6/1 is ON/OFF command to the dimmer
0/2/51 is set absolute Brightness command to the dimmer
0/3/51 is absolute Brightness state from the dimmer
0/0/51 is INCREASE/DECREASE command to the dimmer

Type dimmer : soggiorno "Dimmer" [ switch="0/6/1", position="5.001:0/2/51+<0/3/51", increaseDecrease="0/0/51" ]

Please be aware that a dimmer state is always 0 to 100, never ON or OFF, so it makes no sense to set the dimmer state to ON/OFF (i.e. getting the state for switch parameter). Please also keep in mind, that Start/Stop dimming is not supported by openHAB, so if your wall switches send a Start and Stop command for increasing (or decreasing) the brightness until the stop command is sent, this will not work from openHAB side. You can simply omit the increaseDecrease parameter in such a case:

Type dimmer : soggiorno "Dimmer" [ switch="0/6/1", position="5.001:0/2/51+<0/3/51" ]

You will definitely need the absolute state of the dimmer (of course, you can omit this parameter, too, but… it makes no sense)

misam · September 17, 2018, 10:12am

Thank you Udo you made my day! Now my openhab works like a charm!!