I know that this question has already been asked in another topic [KNX Dimmer not working as expected] but the suggested solutions do not work, at least for me.
I have a few dimmable lights for which I defined a slider and a switch.
Things (this is only an example as all the dimmers are defined the same way) :
Both slider and switch are working but the problem is that when I use the switch to open the light, the slider goes systematically to 100% and then back to the former dimming position.
I tried setting the dimmer item “autoupdate to false” but did not see any change in the behaviour of the slider when I put the light on.
Would you have any other idea ?
Thanks a lot (in advance) and have a nice week-end.
Here are the lines corresponding to the concerned light when I swith it on.
2020-09-18 12:21:23.854 [ome.event.ItemCommandEvent] - Item 'Bureau_Plaf_Lamp' received command ON
2020-09-18 12:21:23.924 [TRACE] [.internal.handler.DeviceThingHandler] - Handling command 'ON' for channel 'knx:device:bridge:generic:C_Bureau_Plaf_Lamp'
2020-09-18 12:21:24.303 [TRACE] [.internal.handler.DeviceThingHandler] - onGroupWrite Thing 'knx:device:bridge:generic' processes a GroupValueWrite telegram for destination '2/0/1' for channel 'knx:device:bridge:generic:C_Bureau_Plaf_Lamp'
2020-09-18 12:21:24.312 [vent.ItemStateChangedEvent] - Bureau_Plaf_Lamp changed from 0 to 100
2020-09-18 12:21:24.314 [GroupItemStateChangedEvent] - gLights2eme changed from OFF to ON through Bureau_Plaf_Lamp
2020-09-18 12:21:24.548 [TRACE] [.internal.handler.DeviceThingHandler] - onGroupWrite Thing 'knx:device:bridge:generic' processes a GroupValueWrite telegram for destination '1/2/5' for channel 'knx:device:bridge:generic:C_Bureau_Plaf_Lamp'
2020-09-18 12:21:24.560 [vent.ItemStateChangedEvent] - Bureau_Plaf_Lamp changed from 100 to 18
Wonder where that has come from.
It does not appear to be from autoupdate (as you would expect when you’ve disabled that), because -
There’s no “predicted” log message (unless you’ve filtered that out)
Timing - autoupdate is generally much quicker than 500mS
So it looks like it’s coming from the binding. I don’t know anything about KNX configuring, but it seems the bus or the device is reflecting the command back. (then later giving a real status update)
Thanks for your answer; no, I did not filter anything; nevertheless, here is a more complete log (openhab.log and events.log).
2020-09-18 15:07:04.224 [TRACE] [.internal.handler.DeviceThingHandler] - Handling command 'ON' for channel 'knx:device:bridge:generic:C_Bureau_Plaf_Lamp'
2020-09-18 15:07:04.228 [TRACE] [.knx.internal.channel.KNXChannelType] - getCommandSpec testing Keys '[increaseDecrease, position, switch]' for command 'ON'
2020-09-18 15:07:04.230 [TRACE] [.knx.internal.channel.KNXChannelType] - getCommandSpec key 'switch' uses expectedTypeClass 'class org.eclipse.smarthome.core.library.types.OnOffType' witch isInstance for command 'ON' and dpt '1.001'
2020-09-18 15:07:04.231 [TRACE] [nx.internal.client.AbstractKNXClient] - writeToKNX groupAddress '1/0/1', commandSpec 'org.openhab.binding.knx.internal.channel.WriteSpecImpl@b60a4d'
2020-09-18 15:07:04.233 [TRACE] [nx.internal.client.AbstractKNXClient] - sendToKNX mappedValue: 'on' groupAddress: '1/0/1'
2020-09-18 15:07:04.253 [DEBUG] [nx.internal.client.AbstractKNXClient] - Wrote value 'ON' to datapoint 'command DP 1/0/1 'knx:ip:bridge', DPT id 1.001, low priority' (0. attempt).
2020-09-18 15:07:04.621 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from '1.1.31' to '2/0/1' with value '[1]'
2020-09-18 15:07:04.623 [DEBUG] [.internal.handler.DeviceThingHandler] - onGroupWrite Thing 'knx:device:bridge:generic' received a GroupValueWrite telegram from '1.1.31' for destination '2/0/1'
2020-09-18 15:07:04.629 [TRACE] [.internal.handler.DeviceThingHandler] - onGroupWrite Thing 'knx:device:bridge:generic' processes a GroupValueWrite telegram for destination '2/0/1' for channel 'knx:device:bridge:generic:C_Bureau_Plaf_Lamp'
2020-09-18 15:07:04.631 [TRACE] [g.knx.internal.dpt.KNXCoreTypeMapper] - toType datapoint DPT = 1.001
2020-09-18 15:07:05.826 [TRACE] [nx.internal.client.AbstractKNXClient] - Received a Group Write telegram from '1.1.31' to '1/2/5' with value '[122]'
2020-09-18 15:07:05.830 [DEBUG] [.internal.handler.DeviceThingHandler] - onGroupWrite Thing 'knx:device:bridge:generic' received a GroupValueWrite telegram from '1.1.31' for destination '1/2/5'
2020-09-18 15:07:05.841 [TRACE] [.internal.handler.DeviceThingHandler] - onGroupWrite Thing 'knx:device:bridge:generic' processes a GroupValueWrite telegram for destination '1/2/5' for channel 'knx:device:bridge:generic:C_Bureau_Plaf_Lamp'
2020-09-18 15:07:05.845 [TRACE] [g.knx.internal.dpt.KNXCoreTypeMapper] - toType datapoint DPT = 5.001
2020-09-18 15:07:04.165 [ome.event.ItemCommandEvent] - Item 'Bureau_Plaf_Lamp' received command ON
2020-09-18 15:07:04.672 [vent.ItemStateChangedEvent] - Bureau_Plaf_Lamp changed from 0 to 100
2020-09-18 15:07:04.749 [GroupItemStateChangedEvent] - gLights2eme changed from OFF to ON through Bureau_Plaf_Lamp
2020-09-18 15:07:05.860 [vent.ItemStateChangedEvent] - Bureau_Plaf_Lamp changed from 100 to 48
There it is. You get an ON message to 2/0/1, openHAB does the only thing it can with ON and interprets as 100%.
Later a % message comes to 1/2/5.
You probably do not want to listen to 2/0/1.
