Hi, Currently I have two items: Switch KNX_GV_Garage_Poort_4_0_0 "Garage Poort" <garagedoor> (gGV_Garage) { knx="4/0/0" } Number Tex_Zone_Z066 "Garagepoort [MAP(tex_contacts.map):%s]" <garagepoort> (gGV_Garage, gDeur, gAlarmcontact) When I send an “ON” to the first item, my garagedoor…

Ok, I’ve found a solution. :slight_smile: I’ve changed my item to: Switch Virtual_GV_Garage_Poort "Garage Poort [MAP(garagepoort.map):%s]" <garagepoortswitch> (gGV_Garage) {autoupdate="false"} The autoupdate=“false” avoids the garagedoor being ‘closed’ as soon as the close-button is pr…

postUpdate instead of sendCommand: [image] Control of led and switch at the same time Beginners The best approach is the proxy item as Markus points out. However, to answer your specific question: sendCommand will cause the bindings/channels linked to an Ite…

Sorry, I should have posted my rule right away. This is what I have: rule "Sync Garagepoort items" when Item Tex_Zone_Z066 received update then if (Tex_Zone_Z066.state == 0) { // Garagedoor is closed postUpdate(KNX_GV_Garage_Poort_4_0_0, OFF) } else if (Tex_Zone_Z066.state == 1) { …

Does anyone have an idea what could be wrong?

The KNX binding behaviour appears to be atypical, in that using postUpdate on an Item does not cause commands to be sent out by most other bindings. I don’t know how KNX works, so I wouldn’t necessarily call that a binding deficiency. [image] Dries: I would like the first item (KNX_GV_Garage_P…

Does your KNX object (ets device object) have a read flag?, or Does the KNX switch actuator have a status switch object (passive or active) associated to the switch? If yes, for the first question, then you should not need to postupdate the item linked to that GA. Maybe a “<” should be added in f…

Hi both, Thanks for your input. @george.erhan : unfortunately, the KNX item does not have a read flag, nor does it have a status switch object. I used an additional virtual item. My .items: Switch KNX_GV_Garage_Poort_4_0_0 "Garage Poort" <garagedoor> (gGV_Garage) { knx="4/0/0" } Num…

Hi, Use a timer or the expire binding for this kind of situation! Measure the time the door needs to close and open, and send the command only when the time needed to close/open has elapsed. I think it will work very nice. Best regards, George

Hi @george.erhan , I’m not really sure if I get your remark. If I switch item “Virtual_GV_Garage_Poort” to “OFF/closed” via BasicUI, the .state of that same item is updated immediately. It doesn’t pass via a rule. I can use a timer to update the .state of another item, indeed. But not the same item…

Hi, The rule you have written can never work in the setup you described. Using a timer, or the expire binding allows you to set the sendCommand, or postUpdate to the KNX item at a different time than the virtual item. Handling the state virtual item manually (through UI, or REST API), should be t…

Hi George, Still not sure if I understand you correctly. You mention the use of a timer. Are you suggesting something like this? (opening the garagedoor takes approx. 22 seconds) // *************************** // Keep the garagepoort-items in sync. // *************************** rule "Sync Gara…

Merge two items in one

Setup, Configuration and Use Scripts & Rules

sihui (SiHui) June 1, 2017, 4:34pm 2

postUpdate instead of sendCommand: