Scene Cycler

Logic Node for Gira X1 — v4.5.1 — by w00rks UAB

Scene Cycler replaces complex multi-node scene logic with a single configurable node. It handles scene cycling via button press, direct scene activation via timed triggers, auto-off on timer expiry, LED status mapping, and per-scene active status tracking. Supports lighting scenes, climate modes, and any multi-state KNX actuator control.

Parameters

Name	Type	Default	Description
Number of Scenes	Integer (1–8)	4	How many scene slots the node manages. Controls the number of Dynamic Scene/LED inputs and Scene Active outputs.
Off Scene Value	Integer (0–255)	5	The 8-bit value sent to the actuator when the node is in the "off" state. Must differ from all scene values.
Enable On/Off Gate	Boolean	True	When enabled, the On/Off input controls the node: it can block cycling (when false) and turn the scene off. When disabled, the On/Off input is ignored entirely.
Browse & Confirm	Boolean	False	Enables browse-then-confirm mode. See Browse & Confirm Mode below.
Activation Delay	Integer (0–30)	0	Seconds to wait before activating a cycled scene. 0 = immediate. See Activation Delay below.
Number of Cycling Scenes	Integer (0–8)	0	How many of the first N scenes participate in button cycling. 0 = all scenes cycle (default). Scenes beyond this number are direct-only. See Direct-Only Scenes below.
Scene Value 1–N	Integer (0–255)	1, 2, 3…	The 8-bit value sent to the actuator for each scene slot.
LED Value 1–N	Integer (0–255)	0	The 8-bit LED bitmask sent to the button LED for each scene slot.
LED Blink Value 1–N	Integer (0–255)	0	Native blink telegram value per scene. When non-zero and Activation Delay is active, this value is sent to the LED output once, letting the Tastsensor flash natively instead of the node toggling the LED manually. 0 = use manual blink (default, backward compatible). See Activation Delay below.
Scene Overlay 1–N	Boolean	False	Per-scene overlay control. When enabled, the Direct Scene input never interrupts active use. While the room is off, it arms the scene (LED preview, lights stay off). While the room is on, it passively tracks (no visible change). When the user turns off, the overlay re-arms automatically. See Scene Overlay below.

Inputs

Name	Type	Default	Description
Cycle Trigger	Boolean (1-bit)	False	Connect to a button. Each rising edge advances to the next scene in sequence, wrapping around after the last cycling scene. When Number of Cycling Scenes is set, only the first N scenes are cycled.
On/Off	Boolean (1-bit)	True	Gate input. When the gate is enabled (Enable On/Off Gate = True): falling edge turns off, rising edge re-enables cycling (or confirms scene in Browse & Confirm mode). Defaults to True so cycling works immediately without a connection.
Direct Scene 1–N	Boolean (1-bit)	False	Connect to timers or triggers. A rising edge immediately activates the corresponding scene. A falling edge triggers auto-off (only if the scene was previously activated via this input).
Scene Readback	Integer (8-bit)	0	Bus sync input. Connect the same data point as Scene Output (as a DatapointEvent) to restore state after X1 restart. When "Keep value" is enabled on the data point, the runtime sends the last scene value on startup, allowing the node to sync LED, Is On, and Scene Active outputs. Does not write back to Scene Output (no feedback loop). See After Reboot below.

Outputs

Name	Type	Description
Scene Output	Integer (8-bit)	The active scene value. Connect to the actuator's scene input group address.
LED Status	Integer (8-bit)	The LED bitmask for the current scene. Connect to the button's LED status group address.
Is On	Boolean (1-bit)	True when any scene is active (current scene ≠ Off Scene Value). Useful for general on/off status display.
Scene Active 1–N	Boolean (1-bit)	Per-scene active indicator. True for the currently active scene, false for all others. Useful for status displays, visualization panels, or triggering other logic.

Scene Active outputs must not feed back into Direct Scene inputs If Scene Active N is wired to the same data point as Direct Scene N, a feedback loop occurs and the light will blink uncontrollably. Always use separate data points for input triggers and output status indicators.

Execution Priority

When multiple inputs change in the same execution cycle, the node processes them in strict priority order. The first matching priority handles the event and exits.

Direct Scene rising edge — Activates the scene immediately, or arms it if Scene Overlay is enabled. Always takes precedence over all other inputs.
Cycle Trigger rising edge — Advances to the next scene (or activates an armed overlay scene). Subject to gate check in standard mode (blocked when On/Off = false and gate is enabled). In Browse & Confirm mode, cycling always works (browsing bypasses the gate).
On/Off rising edge (Browse & Confirm only) — Confirms and activates the browsed or armed scene.
Direct Scene falling edge — Auto-off when a timer expires. Scene Overlay scenes don’t auto-off — lights stay as they are.
On/Off falling edge — Turns off (sets scene to Off Scene Value). Re-arms any active Scene Overlay.
Scene Readback — Bus sync from the scene data point. Restores internal state (LED, Is On, Scene Active) without writing Scene Output. Used for restart recovery.

Gate-blocked fallthrough When Cycle Trigger fires but is blocked by the gate (On/Off = false), the node does not stop. It falls through to check lower priorities, allowing the On/Off falling edge (Priority 5) to process in the same cycle.

Browse & Confirm Mode

When Browse & Confirm is enabled, the Cycle Trigger becomes a browse control:

While off (no active scene)

Cycle Trigger advances the selected scene (internal preview), but does not activate it.
LED Status updates to show the previewed scene's bitmask.
Scene Output is not written — the actuator stays off.
Pressing On/Off (rising edge) confirms and activates the selected scene.

While on (scene active)

Cycle Trigger switches to the next scene immediately (live switching), with Activation Delay applied if configured.

Scene memory

When turned off via On/Off, the selected scene is preserved.
Pressing On/Off again restores the last selected scene.
This allows quick on/off toggling without losing the scene selection.

Example: Office lighting with browse & confirm

Lights are off. User presses the scene button 3 times → LED previews Scene 3.
User presses On/Off → Scene 3 activates, lights turn on.
User presses On/Off again → Lights turn off.
User presses On/Off again → Scene 3 restores immediately.

Activation Delay

When Activation Delay is set to a value greater than 0, scene changes triggered by the Cycle Trigger are delayed by the specified number of seconds.

During the delay, the LED Status indicates a pending change. There are two modes:
- Manual blink (default): When LED Blink Value is 0, the node toggles the LED on/off every 500ms.
- Hardware blink: When LED Blink Value is non-zero, the node sends that value once to LED Status, and the Tastsensor flashes natively. This produces smoother blinking with less bus traffic.
Scene Output is not updated until the delay expires.
When the delay expires, the steady LED Value replaces the blink feedback.
If the user cycles again before the delay expires, the timer resets — only the final selection activates.
Turn-off actions (On/Off falling edge, Direct Scene falling edge) are always immediate and cancel any pending delay.
Direct Scene rising edges are always immediate and cancel any pending delay.

When is this useful? Climate and AC control, where rapid mode switching can damage compressors. The delay allows the user to browse through modes without each intermediate selection being sent to the actuator.

Interaction with Browse & Confirm

Browsing while off: no delay (LED preview only, no actuator change).
Confirmation via On/Off: always immediate (no delay).
Live switching while on: Activation Delay applies.

Direct-Only Scenes

When Number of Cycling Scenes is set to a value greater than 0, only the first N scenes participate in button cycling. Scenes at positions beyond N are "direct-only" — they can only be activated via their corresponding Direct Scene input (e.g. from a timer) and are never reached by the Cycle Trigger.

Setting Number of Cycling Scenes to 0 (default) means all scenes cycle — fully backward compatible.
Direct-only scenes still have LED values, Scene Active outputs, and auto-off behavior.
If the current scene is a direct-only scene (e.g. activated by a timer) and the user presses the cycle button, cycling restarts from Scene 1.

Example: Office with 4 cycling scenes + 1 night scene

Parameter	Value
Number of Scenes	5
Number of Cycling Scenes	4
Scene Values	1 (Welcome), 2 (Cozy), 3 (Clean), 4 (Work), 5 (Night)
Off Scene Value	6

The button cycles through scenes 1–4 only. Scene 5 (Night) is activated by a timer via Direct Scene 5, and auto-off turns the lights off when the timer expires. The next button press after night mode ends restarts from Scene 1.

Scene Overlay

When Scene Overlay is enabled for a scene, the corresponding Direct Scene input acts as a transparent overlay — it never interrupts active use:

Room State	Direct Scene Rising Edge	What Happens
Off	Arms the scene	LED preview shown, lights stay off. The next button press activates the armed scene instead of cycling.
On	Passively tracks	No visible change — user keeps their current scene undisturbed.

Turn-off re-arm

When the user turns off while an overlay is passively tracked (Direct Scene still high), the overlay automatically re-arms. The next button press activates the overlay scene.

When the overlay expires

When the Direct Scene input falls (timer expired):

Scene was only armed (lights off): arm is cleared and LED resets. Room stays off.
Scene was activated (lights on): lights stay on — no auto-off. The overlay is simply removed: the next button press cycles normally.

Example: Night mode overlay

8:00 PM — Lights on (cleaning scene). Night timer fires → passively tracked. Lights stay on cleaning.
11:00 PM — User turns off. Overlay re-arms (LED shows night indicator).
11:30 PM — User presses button → Night scene activates (dim lights).
12:00 AM — User turns off. Night still armed (timer still active).
12:15 AM — User presses button → Night scene activates again.
6:00 AM — Night timer expires. Arm cleared, LED reset.
6:30 AM — User presses button → Normal cycling → Scene 1 (bright lights).

Per-scene control Each scene has its own Scene Overlay setting. This lets you have some Direct Scene inputs that always activate immediately (e.g. motion sensors) and others that overlay without interrupting (e.g. night timers).

Use Cases

Lighting scenes (4 scenes + off)

Parameter	Value
Number of Scenes	4
Off Scene Value	5
Scene Values	1 (Welcome), 2 (Cozy), 3 (Clean), 4 (Work)
Enable On/Off Gate	True
Browse & Confirm	True
Activation Delay	3

User browses scenes with the cycle button, previews via LED, confirms with On/Off. 3-second delay on live switching prevents accidental changes.

Climate control (3 modes + off)

Parameter	Value
Number of Scenes	3
Off Scene Value	4
Scene Values	1 (Cold), 2 (Heat), 3 (Fan)
Enable On/Off Gate	False
Activation Delay	5

No On/Off gate needed. Cycle button steps through modes. 5-second delay protects the compressor from rapid switching.

GPA Wiring Tips

Scene Output — Wire directly to the actuator's KNX group address. Enable "Keep value" in the data point manager if you want the scene to persist across reboots.
On/Off input — Enable "Keep value" on its group address so the gate state survives reboots.
Direct Scene inputs — Connect to timer trigger data points. Do not enable "Keep value" (timers restart fresh after reboot).
Scene Active outputs — Use separate data points from the Direct Scene inputs. Never wire a Scene Active output back to the corresponding Direct Scene input on the same data point.
LED Status — Wire to the button's LED status group address.

After Reboot

On startup, the node initializes to the Off Scene Value internally. To fully restore state after an X1 reboot, connect the Scene Readback input:

Enable "Keep value" on the Scene Output data point in GPA.
Create a DatapointEvent node for the same data point.
Wire it to the Scene Readback input.

On restart, the runtime sends the kept scene value to Scene Readback. The node syncs its internal state and updates LED Status, Is On, and all Scene Active outputs — without writing back to Scene Output (no feedback loop).

Without Scene Readback If Scene Readback is not connected, the node starts at "off" internally. The actuator still restores from "keep value", but LED Status, Is On, and Scene Active outputs may be incorrect until the first user interaction.