[SOLVED] Off state return


i need your help for a strange problem. i use openhab 2.2.0. my installation with windows was ok but i would like make a new with debian. with sitemap no problem for action a light but i have no state return.

have you got an idea ?

in items
Switch Lumiere_cellier "Lumiere cellier" { knx="0/1/1+0/3/1" }```

in items
Switch Lumiere_cellier "Lumiere cellier" { knx="0/1/1+0/3/1" }

in sitemap
sitemap maison label="Maison" {
    Frame label=" " {

		Switch item=Lumiere_cellier label="lumière cellier" icon="light"

> Blockquote

> Blockquote
in knx.cfg

# KNX gateway IP address 
# (optional, if serialPort or connection type 'ROUTER' is specified)

# Local KNX Binding bus address.
# Use it, when two or more openHAB Instances are connected to the same KNX bus.
# (optional, defaults to 0.0.0)

# Ignore local KNX Events, prevents internal events coming from
# 'openHAB event bus' a second time to be sent back to the 'openHAB event bus'.
# Note: To send back events second time is a Bug, but for backward compatibility, the behavior is not changed.
# For new installations, its recommend to set "ignorelocalevents=true"
# (optional, defaults to false)

# KNX IP connection type. Could be either TUNNEL or ROUTER (optional, defaults to TUNNEL)
# Note: If you cannot get the ROUTER mode working (even if it claims it is connected), 
# use TUNNEL mode instead with setting both the ip of the KNX gateway and the localIp.

# KNX gateway port (optional, defaults to 3671)
# Note: If you use eibd, setting to 6720

# Local endpoint to specify the multicast interface, no port is used (optional)

# Serial port of FT1.2 KNX interface (ignored, if ip is specified)
# Valid values are e.g. COM1 for Windows and /dev/ttyS0 or /dev/ttyUSB0 for Linux

# Pause in milliseconds between two read requests on the KNX bus during
# initialization (optional, defaults to 50)

# Timeout in milliseconds to wait for a response from the KNX bus (optional, 
# defaults to 10000)

# Number of read retries while initialization items from the KNX bus (optional,
# defaults to 3)

# Seconds between connect retries when KNX link has been lost
# 0 means never retry, it will only reconnect on next write or read request
# Note: without periodic retries all events will be lost up to the next read/write
#       request
# (optional, default is 0)

### Auto refresh feature
# Number of entries permissible in the item refresher queue. 
# (optional, defaults to 10000)

# Number of parallel threads for refreshing items. (optional, defaults to 5)

# Seconds to wait for an orderly shutdown of the auto refresher's 
# ScheduledExecutorService. (optional, defaults to 5)

What do you mean?

I will take a wild guess… I think that he means: While he can generate commands that reach as KNX telegrams the actuators, he is not able to receive KNX telegrams from the KNX Bus to update the state of his Items… :stuck_out_tongue:

@bruce : Which KNX/IP interface are you using?
Did this work ok on your previous (windows) OH2 installation?
Are you running OH2.3 on the new debian machine?

yes dim you’re right (sorry for my english).

but i found the problem, i need restart openhab after add a switch in sitemap, i’m not sur that is normal buts it’s ok.

thank you