OH3 rule: timer issue

[djmg_uli (Full name)]

Hi there,

I am running OH3.1 on a synology docker and i do have troubles with rules and timers.
As blockly does not support timers (yet?) i tried to just copy&paste my code from OH2.5 to OH3 but it did not work out. The code is as follows:

triggers:
  - id: "1"
    configuration:
      itemName: LupusAlarmsensoren_LupusAlarmsensorGaragentor
      state: "{WEB_MSG_DC_OPEN}"
      previousState: "{WEB_MSG_DC_CLOSE}"
    type: core.ItemStateChangeTrigger
conditions: []
actions:
  - inputs: {}
    id: "2"
    configuration:
      type: application/vnd.openhab.dsl.rule
      script: |-
        var Timer Garagenlichttimer = null
          
        LichtGarageInnen_Betrieb.sendCommand(ON)
        LichtGarageFront_Betrieb.sendCommand(ON)	
        LichtGarageSeite_Betrieb.sendCommand(ON)	
        HeizungGaragerechts_Betrieb.sendCommand(OFF)
        HeizungGaragelinks_Betrieb.sendCommand(OFF)

        Garagenlichttimer = createTimer(now.plusSeconds(240)) [|
          Garagenlichttimer = null
          LichtGarageInnen_Betrieb.sendCommand(OFF)
          LichtGarageFront_Betrieb.sendCommand(OFF)
          LichtGarageSeite_Betrieb.sendCommand(OFF)
        ]
    type: script.ScriptAction

In the event monitor stream i could see that the trigger was touched, the rules started but it did not work at all (nothing happened inside the rule). Can you help me?

[djmg_uli (Full name)]

anyone?

[rossko57]

Do your “before” commands get issued, you’ve not said?

I think the timer code will fail at the first line when it executes, there are no global variables in GUI entered DSL rules, so Garagenlichttimer will not exist at that time.
There should be complaints in your openhab.log.

[djmg_uli (Full name)]

I am not sure what you meant with “before” … please see attached screenshot on how i jump into that rule.
Do you have an idea how to solve that issue with the variable?
(or any other solution)

[rossko57]

@djmg_uli

I am not sure what you meant with “before”

Your script does a bunch of commands, then sets up a timer to do a bunch more commands later.
Is the ‘sooner’ or ‘later’ part going wrong?

@djmg_uli

Do you have an idea how to solve that issue with the variable?

Don’t use the (global) variable, you’re not doing anything useful with it. You can create ‘anonymous’ timers without a preceding variable = createTimer(...), just createTimer(...)

[djmg_uli (Full name)]

Works great, thanks for helping me out!

[djmg_uli (Full name)]

One more question:
This was the syntax for the DSL type of rule.
How would you do the timer in ECMA/Javascript form?

[Wolfgang_S]

@djmg_uli

How would you do the timer in ECMA/Javascript form?

Create timer in openHAB3 rule with ECMA

Platform information: Hardware: i686 / 1 GB / 130 GB OS: Debian 10.7 Java Runtime Environment: openjdk 11.0.9.1 openHAB version: openHAB 3.0.0 Issue: I’d like to create a rule with a timer that fires some fixed time after an item was updated. I’ve tried doing it by generating a rule with the openHAB3 GUI and adding ECMA script for the timer, with the syntax/example from these docs. I suspect the example isn’t appropriate ECMA syntax - so what would be the correct way of doing this? R…

[djmg_uli (Full name)]

I tried this in my rule (in application/javascript editor), but it did not work out:
(first of all turn on the lights, wait 1 minute and switch it off again)

if (itemRegistry.getItem('UmgebungslichtGarten_Beleuchtungsstaerke').getState() > '200') {
  events.sendCommand('LichtGarageSeite_Betrieb', 'ON');
}

var timer = ScriptExecution.createTimer(ZonedDateTime.now().plusMinutes(1), function(){
  events.sendCommand('LichtGarageSeite_Betrieb', 'OFF');
});

[rossko57]

@djmg_uli

did not work out:

Try to give people more information than “not working”.

[djmg_uli (Full name)]

Sorry, of course i should:
The rule starts accordingly and powers on the Light but after the timer should have finished, they dont power off.
Therefore i thought the timer part was/is not working