Delay when setting items in OpenHAB

[vzorglub (Vincent Regaud)]

This is because the sendCommand doesn’t change the state of the item straight away, it needs to be processed through the event bus and persistence first. As a result, when you are retreiving the item state, it hasn’t changed yet. One way to deal with that is to wait a little bit for the event bus to catch up.

Notice the use of the code fences:

How to use code fences

We all have to type this content over and over and over. Here is a posting we can all point to when the topic comes up. Why use code fences? Because rules, sitemap, logs, and configs are all but unreadable when code fences are not used. When to use code fences? Whenever one is posting any sort of code, config, log, and any text where line wrapping, indentation, and using an equal spaced font makes the text more legible. How to use code fences? Use 3 backticks (```)... Or use <code>... …

rule “Dim lights”
when
    Time cron “0 45 19 ? * *”
then
    I_ART_Flurlampe_vorne.sendCommand(15)
    I_ART_Flurlampe_hinten.sendCommand(15)
    if (I_ART_Anwesenheit.state == ON) {
        Tread::sleep(100) // 100ms
        I_FL_Deckenlampe_vorn_Dimmer.sendCommand(I_ART_Flurlampe_vorne.state)
        I_FL_Deckenlampe_hinten_Dimmer.sendCommand(I_ART_Flurlampe_hinten.state)
    }
end