One-Flows: give a Moment a start rule

Establish where the rule runs

One-Flows in the sample home demonstrates how a Moment can start automatically. A rule describes When, Only if and Do this. The demo uses browser data and runs while this app is open and active. It does not create a persistent automation for your real home. Missed times are not replayed.

In the connected new interface of Core v0.37.0, One-Flows points to Core management. Configure real automations there using supported devices and your administrator permissions. The following steps describe the demo editor; do not assume its rules are already installed on Core.

Start with one tested Moment

First decide what should happen and test that Moment manually. For Evening calm, you could dim two sample lights. Check every action before linking a rule. If the Moment itself is unavailable, the rule cannot solve that problem.

Use a name explaining the trigger, such as Evening calm on weekdays. Begin without extra conditions and add them only after you understand the simple behaviour. This avoids several possible reasons for a start being missed at the same time.

Create a scheduled rule in the demo

1. Open One-Flows and choose Create rule. Give the rule a clear name.
2. Under When, choose At a time, enter a time and select at least one day. Check the timezone shown for this screen.
3. Under Do this, select the existing Moment you want to start. Read the displayed combination of actions again.
4. Leave Enable rule off initially and save. You can then review the settings at your own pace.
5. Check the rule, deliberately enable it and keep the app active around your chosen test time. Afterwards, check the history and sample devices.

Use conditions and state changes

Only if can contain a time window, selected days or a device value. Every condition must match at the same time. A time window whose end is earlier than its start continues into the next day, for example from 22:00 to 06:00.

For A device status changes, select an offered device value, comparison and threshold. The demo starts once when the state begins to match the comparison. It does not keep starting while the same value remains. This explains why a matching current value does not necessarily cause a new automatic run.

Read the check and history together

Check or Check now evaluates the rule against the current situation. It checks the conditions; it is not an instruction to execute the linked Moment manually. Read which step does not match: a paused rule, the time, a condition or the Moment’s availability.

Compare the check with the execution history. Skipped and Failed mean different things from Executed. Record the time and reason before changing settings. To test the actions directly, open the Moment itself and choose Start there.

Pause and troubleshoot methodically

Pause the rule before changing its purpose. For a missed run, check enabled status, timezone and days, conditions, device availability and the selected Moment in that order. In the demo, also check whether the app was active at that time.

A duplicated demo rule starts paused: give it a distinctive name and avoid two rules unintentionally doing the same thing. Deleting the rule leaves the Moment intact. Clearing browser data or using another browser can remove demo rules or display a different list. Discuss real Core problems with the administrator, providing the rule name and execution message.