Rule triggers for seemingly no reason

[SnoutBug]

Expected Behavior

Rule triggers when any conditions are met

Current Behavior

Rule triggers seemingly w/o reason.

Possible Solution

None - let me know what logs you'd need for debugging

Steps to Reproduce (for Bugs)

1. Set up a rule to listen to any item that can update to ON
2. listen on update state = ON
3. notice that rule will activate sometimes - mostly at night
4. Check history of that entity channel, it shows no state change

Context

I set up a notification for movements:

Which triggered at 5 am for "wohnzimmer", however no corresponding movement (bewegung) was monitored (erkannt).

This is the corresponding rule of "wohnzimmer" which posts the notification.

I am thinking that this is a bug, as every other state change on that channel is monitored correctly as well as any other entity, but the rule triggered regardless.

Your Environment

OpenHAB 5.0.3 on a Raspi inside a docker container.

[rkoshak]

Please click on the code tab for your rule and post the text you find there. Use code fences

```
code goes here
```

I have several rules that trigger on updates to ON and am not seeing this behavior. Something else must be going on and we need to investigate.

What would make it a whole lot easier is if you updated to OH 5.1.0 M4 or later. The source of events have been added to the events so we could see exactly where these events are coming from. If you do that, I'll have you add an inline script action using JS with the following code:

console.info('Rule triggered by " +event.eventSource);

[SnoutBug]

Sure I can try updating to milestone.

In the meantime, this is the code for the rule:

configuration: {}
triggers:
  - id: "1"
    configuration:
      itemName: Presence_Sensor_Arbeitszimmer_Bewegung
      state: ON
    type: core.ItemStateUpdateTrigger
  - id: "2"
    configuration:
      itemName: Presence_Sensor_Flur_Bewegung
      state: ON
    type: core.ItemStateUpdateTrigger
  - id: "3"
    configuration:
      itemName: Presence_Sensor_Kueche_Bewegung
      state: ON
    type: core.ItemStateUpdateTrigger
  - id: "4"
    configuration:
      itemName: Presence_Sensor_Wohnzimmer_Bewegung
      state: ON
    type: core.ItemStateUpdateTrigger
conditions:
  - inputs: {}
    id: "5"
    configuration:
      itemName: Zu_Hause
      operator: =
      state: OFF
    type: core.ItemStateCondition
  - inputs: {}
    id: "7"
    configuration:
      itemName: Schalter_Bewegungsalarm
      operator: =
      state: ON
    type: core.ItemStateCondition
actions:
  - inputs: {}
    id: "6"
    configuration:
    # omitted blockly for readability
      type: application/javascript
      script: >
        rules.runRule('ntfy', {'Topic': 'home_alert', 'Title': 'Bewegung
        erkannt', 'Priority': 'urgent', 'Tags': '', 'Payload':
        ['```','\r\n','Flur          ',items.getItem('Presence_Sensor_Flur_Bewegung').state,'\r\n','Wohnzimmer    ',items.getItem('Presence_Sensor_Wohnzimmer_Bewegung').state,'\r\n','Arbeitszimmer
        ',items.getItem('Presence_Sensor_Arbeitszimmer_Bewegung').state,'\r\n','Küche         ',items.getItem('Presence_Sensor_Kueche_Bewegung').state,'\r\n','```'].join(''),
        'Markdown': 'yes'});
    type: script.ScriptAction
  - inputs: {}
    id: "8"
    configuration:
      type: application/javascript
      script: |
        console.info('REGEL BENACHRICHTIGUNG');
        console.info(ctx.ruleUID);
        console.info((event !== undefined));
        console.info(event.type);
        console.info(event.itemState?.toString());
        console.info(event.oldItemState?.toString());
        console.info(event.itemName);
        console.info(event.itemCommand?.toString());
        console.info(event.channel);
        console.info(event.event);
    type: script.ScriptAction

For now this printed the following which seems pretty unuseful:

20:03:09.082[INFO] [org.openhab.automation.script.ui.c982e949a8] - REGEL BENACHRICHTIGUNG
20:03:09.082[INFO] [org.openhab.automation.script.ui.c982e949a8] - c982e949a8
20:03:09.083[INFO] [org.openhab.automation.script.ui.c982e949a8] - true
20:03:09.084[INFO] [org.openhab.automation.script.ui.c982e949a8] - ItemStateUpdatedEvent
20:03:09.084[INFO] [org.openhab.automation.script.ui.c982e949a8] - ON
20:03:09.085[INFO] [org.openhab.automation.script.ui.c982e949a8] - undefined
20:03:09.086[INFO] [org.openhab.automation.script.ui.c982e949a8] - Presence_Sensor_Wohnzimmer_Bewegung
20:03:09.087[INFO] [org.openhab.automation.script.ui.c982e949a8] - undefined
20:03:09.088[INFO] [org.openhab.automation.script.ui.c982e949a8] - undefined
20:03:09.089[INFO] [org.openhab.automation.script.ui.c982e949a8] - undefined

[rkoshak]

Sure I can try updating to milestone.

5.1 was rel;eased today.

[SnoutBug]

@rkoshak

I upgraded and those are the logs:

13:09:41.827[INFO] [org.openhab.automation.jsscripting.rule.c982e949a8] - REGEL BENACHRICHTIGUNG
13:09:41.828[INFO] [org.openhab.automation.jsscripting.rule.c982e949a8] - c982e949a8
13:09:41.828[INFO] [org.openhab.automation.jsscripting.rule.c982e949a8] - true
13:09:41.829[WARN] [org.openhab.automation.jsscripting.rule.c982e949a8] - event.itemState is deprecated, use event.receivedState for update triggers or event.newState for change triggers instead.
13:09:41.830[INFO] [org.openhab.automation.jsscripting.rule.c982e949a8] - ON
13:09:41.831[INFO] [org.openhab.automation.jsscripting.rule.c982e949a8] - undefined
13:09:41.832[INFO] [org.openhab.automation.jsscripting.rule.c982e949a8] - Presence_Sensor_Wohnzimmer_Bewegung
13:09:41.833[INFO] [org.openhab.automation.jsscripting.rule.c982e949a8] - undefined
13:09:41.833[INFO] [org.openhab.automation.jsscripting.rule.c982e949a8] - undefined
13:09:41.834[INFO] [org.openhab.automation.jsscripting.rule.c982e949a8] - undefined
13:09:41.835[WARN] [org.openhab.automation.jsscripting.rule.c982e949a8] - event.type is deprecated, use event.eventName instead. If you use Blockly, simply resave the script.
13:09:41.836[INFO] [org.openhab.automation.jsscripting.rule.c982e949a8] - ItemStateUpdatedEvent
13:09:41.839[INFO] [org.openhab.automation.jsscripting.rule.c982e949a8] - Rule triggered by null

When I trigger the rule manually, it says Rule triggered by manual

[rkoshak]

And what does event.log say about Presence_Sensor_Wohnzimmer_Bewegung? The rule triggered because this Item was updated. Hopefully it changed, and you'll have an entry in events.log telling you what caused that Item to update.

If it just updated to the same state, you'll need to change the level of openhab.event.ItemStateUpdatedEvent to INFO and wait for the rule to be triggered unexpectedly again. When that happens, the entry for that Item's update will tell you what caused the update and therefore what caused the rule to run.

Note, it should be the rare case that a rule is triggered by an Item update. Almost always you want to trigger on an Item changed because if the Item didn't change there is usually nothing to do. And an Item can be updated under a number of circumstances where you don't want a rule to run including: binding deciding to refresh it's Channels once a day or periodically to make sure devices are responding, restoreOnStartup, etc.