# Inbox Rules for automatic approval?

**URL:** <https://community.openhab.org/t/inbox-rules-for-automatic-approval/170581>\
**Category:** Other\
**Created:** [October 3, 2026, 4:02am UTC](https://community.openhab.org/t/inbox-rules-for-automatic-approval/170581 "2026-10-03T04:02:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jimtng](https://community.openhab.org/user_avatar/community.openhab.org/jimtng/32/98543_2.png) [@jimtng](https://community.openhab.org/u/jimtng)\
**Post date:** [October 3, 2026, 4:02am UTC](https://community.openhab.org/t/inbox-rules-for-automatic-approval/170581/1 "2026-10-03T04:02:09Z")

</div>

Would it be useful to have a set of rules to automatically approve inbox items, turning them into Things? I’ve built this add-on but haven’t submitted it yet - unsure whether it’s something that’s needed.

Once the Things are created, one can create the corresponding items automatically using Yaml Composer’s dynamic Things feature.

 ![image](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/8/4/84d95bcb595f732f102f27bd9cd42a426f4f2e7e.png)

* * *

# Inbox Rules

Inbox Rules implements openHAB’s inbox auto-approval predicate using configurable string rules.  
Matching discovery results are approved by the core inbox processor; supported actions are then applied to the new Thing through the Thing registry.

## Configuration

Configure the add-on through Main UI under **Settings → Add-on Settings → Inbox Rules** , or set `rules` in ConfigAdmin. Each entry is one rule:

Set `rulesEnabled` to `false` to disable all rules; it defaults to `true`.

```sh
criteriaKey=value; actionKey=value

```

Rules are evaluated in order; the first matching rule approves the result.  
A rule without action keys only approves it.  
Lines beginning with `#` or `//` are comments.  
Invalid rules are ignored.

### Criteria

- `thingUid`, `bridgeUid`, and `label` match the corresponding discovery result values.
- `representationProperty` matches the value stored at the result’s representation property.
- `propertyMatch` and `configMatch` accept comma-separated `key=value` or `key:value` comparisons against discovery properties.
- Criteria support `*` (zero or more characters) and `?` (one character).

### Actions

- `setLabel` changes the approved Thing’s label.
- `setLocation` sets its location.
- `setProperties` and `setConfig` accept comma-separated assignments, such as `setProperties=room=Kitchen,source=${properties.id}`.

Action values support `${label}`, `${thingUID}`, `${bridgeUID}`, and `${properties.name}` interpolation.  
Unknown interpolation variables become empty strings.  
Actions are applied once when the approved Thing is added to the registry.

**Example:**

```plaintext
# Approve a discovered device and enrich it
thingUid=zwave:device:*; label=Front Door Sensor; setLabel=${label}; setLocation=Ground Floor; setProperties=room=Entry,serial=${properties.serialNumber}

```

* * *

---

<div class="post-metadata">

**Author:** ![BrettLHolmes](https://community.openhab.org/user_avatar/community.openhab.org/brettlholmes/32/105286_2.png) [@BrettLHolmes](https://community.openhab.org/u/BrettLHolmes)\
**Post date:** [October 12, 2026, 1:48am UTC](https://community.openhab.org/t/inbox-rules-for-automatic-approval/170581/2 "2026-10-12T01:48:24Z")

</div>

Hi @jimtng

actually yes, i have a need to setup a system from scratch and the binding discovers i am using discovers the things and places the. In the inbox. This would be a great advantage in this process.

I was concentrating on the yaml composer side and not given a lot of thought to this part.