cap_router_mgr

What problem does it solve?

It helps you inspect and change how the device routes incoming events to actions, without manually editing rule files, reducing configuration mistakes and speeding up iteration.

Core Features & Use Cases

• Rule CRUD via capabilities: List, fetch, add, update, and delete router rules through cap_router_mgr capability calls.
• Controlled reload semantics: Reload router rules only when you explicitly need disk reload behavior.
• Strict rule_json correctness: Enforces that rule_json is a JSON string with required fields like id, match, and actions, and that match.event_type is correctly placed.
• Common automation patterns: Apply rules that trigger on events such as startup triggers and message text commands (including prefix-style command matching), then run agent/scripts, send messages, emit events, or drop messages.

Quick Start

Ask the assistant to list router rules, then create or update a single rule id using a complete rule_json string, and finally verify it by calling get_router_rule.