The autoupdate is disabled so that commands given by the UI (MainUI, BasicUI, App) will not result in a predicted state. This is the desired behaviour.
But if the binding receives a command from the KNX bus (wall switch) the autoupdate=“false” is ignored resulting in the state becoming the predicted state.
Is this by desgin or is it possible to force the binding to ignore autoupdate on bus commands?
thanks for the quick response.
Here are the log lines:
Full down/up cycle from MainUI:
2022-01-17 15:25:29.630 [INFO ] [openhab.event.ItemCommandEvent ] - Item 'EG_Arbeitszimmer_Rollladen_links' received command DOWN
2022-01-17 15:25:34.769 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'EG_Arbeitszimmer_Rollladen_links' changed from 0 to 31
2022-01-17 15:25:46.570 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'EG_Arbeitszimmer_Rollladen_links' changed from 31 to 100
2022-01-17 15:25:49.964 [INFO ] [openhab.event.ItemCommandEvent ] - Item 'EG_Arbeitszimmer_Rollladen_links' received command UP
2022-01-17 15:25:55.096 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'EG_Arbeitszimmer_Rollladen_links' changed from 100 to 69
2022-01-17 15:26:06.899 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'EG_Arbeitszimmer_Rollladen_links' changed from 69 to 0
Full down/up cycle from wall switch:
2022-01-17 15:26:09.267 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'EG_Arbeitszimmer_Rollladen_links' changed from 0 to 100
2022-01-17 15:26:14.319 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'EG_Arbeitszimmer_Rollladen_links' changed from 100 to 31
2022-01-17 15:26:26.116 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'EG_Arbeitszimmer_Rollladen_links' changed from 31 to 100
2022-01-17 15:26:26.408 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'EG_Arbeitszimmer_Rollladen_links' changed from 100 to 0
2022-01-17 15:26:31.620 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'EG_Arbeitszimmer_Rollladen_links' changed from 0 to 69
2022-01-17 15:26:43.419 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'EG_Arbeitszimmer_Rollladen_links' changed from 69 to 0
I have a rollershutter locked by logic in KNX so an issued down command will be ignored. But if I send the down command from the wall switch the item state gets updated immediately to “100”. If I then read out the actual position from the acutator with ETS the GA responds with the correct “0”. And with this telegram the items gets updated to the correct value.
I neither have other links to this channel nor any corresponding *-control item as there are just a few (~20).
That is what I was thinking. But somehow it behaves like this
So I checked the KNX bus config and telegrams. As you can see in the screenshot there are no additional devices writing to the actual position GA 1/1/23.
2022-01-17 21:16:07.563 [DEBUG] [.internal.handler.DeviceThingHandler] - onGroupWrite Thing 'knx:device:interface:rollladen_eg' received a GroupValueWrite telegram from '1.1.28' for destination '1/1/20'
2022-01-17 21:16:07.574 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'EG_Arbeitszimmer_Rollladen_links' changed from 0 to 100
2022-01-17 21:16:15.950 [DEBUG] [.internal.handler.DeviceThingHandler] - onGroupWrite Thing 'knx:device:interface:rollladen_eg' received a GroupValueWrite telegram from '1.1.28' for destination '1/1/21'
2022-01-17 21:16:17.400 [DEBUG] [.internal.handler.DeviceThingHandler] - onGroupWrite Thing 'knx:device:interface:rollladen_eg' received a GroupValueWrite telegram from '1.1.28' for destination '1/1/20'
2022-01-17 21:16:17.411 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'EG_Arbeitszimmer_Rollladen_links' changed from 100 to 0
You can see that openhab is not longer listening to the position GA 1/1/23. But in response to the up/down commands the binding updates the state.
What am I getting wrong? Any suggestions?
Again Thanks in advance
Jo
Yes. It tells you right there in your DEBUG log received a GroupValueWrite telegram from '1.1.28' for destination '1/1/20'
openHAB is listening to messages for 1/1/20, because it’s there in your config
That’s right.
The circumvention is to have your wal switch talk to a GA that openHAB is not listening to.