Hi,
I am trying to use a push button wired to a HM IO-Module. The channel of the module is also directly connected to an actuator switching some light.
My Item is
Switch IO_Bad_OG_ost_4 "I/O Bad OG Ost #1 shortpress" <homematic> (Aktoren_Technik) { channel="homematic:HG-HMW-IO-4-FM:e3224ce8:LEQ0773177:1#PRESS_SHORT"}
On pressing the button, I get following messages in the log:
13:32:38.984 [INFO ] [marthome.event.ItemStateChangedEvent] - IO_Bad_OG_ost_4 changed from OFF to ON
13:32:39.013 [INFO ] [marthome.event.ItemStateChangedEvent] - A6_Licht_Bad_OG_Decke changed from OFF to ON
13:32:40.998 [INFO ] [marthome.event.ItemStateChangedEvent] - IO_Bad_OG_ost_4 changed from ON to OFF
The button press generates an ON Message, and after 2 seconds, an OFF message (via the IO-Module) . The linked actuator just switches (toggles) the light ON or OFF. The additional OFF message seems to get ignored (which is part of the homematic direct link, I suppose).
When I change the Item defenition to a Contact Type Item, I donât get any message, the binding seems to enforce the âSwitchâ type Item.
Anyway, I want to get rid of the direct connection between the button and the switch/lamp, and create some rule to switch a proxy Item on/off instead, but that turns out to be kind of complicated. If I push the button 2 times quickly (within the 2 seconds range between the ON and OFF message in the log), I get:
14:15:57.802 [INFO ] [marthome.event.ItemStateChangedEvent] - IO_Bad_OG_ost_4 changed from OFF to ON
14:15:57.829 [INFO ] [marthome.event.ItemStateChangedEvent] - A6_Licht_Bad_OG_Decke changed from OFF to ON
14:15:58.330 [INFO ] [marthome.event.ItemStateChangedEvent] - A6_Licht_Bad_OG_Decke changed from ON to OFF
14:16:00.318 [INFO ] [marthome.event.ItemStateChangedEvent] - IO_Bad_OG_ost_4 changed from ON to OFF
The second push does not even show up in the log, but the light is switched off correctly.
Does anybody have an idea whatâs going on here? How can I correctly interpret this kind of device/behaviour?
Regards,
Thomas
(N.B. The thread Homematic: Repeated PRESS_SHORT events? seems to direct to the same issue, but with no solutionâŚ)