---

What this feels like in the field

• You're on-site. The client wants their lighting scenes working before you leave. The rule you wrote in ElkRP isn't triggering and you can't figure out why.
• Tech support's hold time is 45 minutes. You need the answer now, not tomorrow.
• You know there's a correct way to structure the WHENEVER conditions, FLAGS, and output logic — but the manual is 200 pages and the index is useless.
• You're billing by the hour, but the last two hours haven't been productive — they've been spent troubleshooting syntax you've never used before.

AntlerBridge answers the question you're stuck on in about 30 seconds. From your phone. While you're still on the ladder.

---

Why use AntlerBridge for logic troubleshooting?

---

What you can ask AntlerBridge

You don't need to know the right chapter or page number. Just describe the real-world problem in front of you.

• "How do I write a WHENEVER rule for a time-based lighting scene that activates after sunset?"
• "My two rules are both controlling Output 3 — how do I resolve the conflict?"
• "What's the correct syntax for a Zone Follower using AND conditions?"
• "How do I set up M1XSP serial commands for UPB lighting control?"
• "Show me how to program a FLAG-based workaround for a two-channel device."
• "How do I convert an OmniPro II macro into M1-native WHENEVER/AND/THEN logic?"
• "What's the maximum number of rules the M1 Gold supports and how should I structure them?"

---

Answer format you can trust

Every response from AntlerBridge is structured for field use — not academic reading.

---