From 5f2c8fdcec28e9516fb91d7f8de166ca52e87e74 Mon Sep 17 00:00:00 2001
From: Your Name <you@example.com>
Date: Sun, 9 Aug 2026 18:11:51 +0000
Subject: [PATCH] feat: event-trigger run logs live value on no-change

Diagnosis aid: when a rule evaluates but doesn't fire, run now prints
'OK: <cmd> = <value> (no change)' so a rule that silently never crosses
its threshold (e.g. wrong sensor in the check command) is visible
instead of just 'evaluated N rule(s)'.
---
 bin/pos-system-event-trigger | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/bin/pos-system-event-trigger b/bin/pos-system-event-trigger
index b7d5095..bde8470 100755
--- a/bin/pos-system-event-trigger
+++ b/bin/pos-system-event-trigger
@@ -94,6 +94,8 @@ run_rules() {
             fi
         elif [ "$DRY_RUN" -eq 1 ]; then
             log "(dry-run) OK: $RULE_CMD = $VALUE_DISPLAY (no change)"
+        else
+            log "OK: $RULE_CMD = $VALUE_DISPLAY (no change)"
         fi
     done
     if [ "$skipped" -gt 0 ]; then