Gateway Analyzer
Gateway Analyzer is an optional uplink-only layer.
Two cases
Driver already emits canonical data
Native observation → Driver → AirNgin logical record
Analyzer is bypassed.
Driver emits native/manufacturer data
Native observation
→ Driver
→ GatewayAnalyzer
→ validated AirNgin logical records
What Analyzer must not do
Analyzer cannot:
- generate downlink commands
- write to the native bus
- publish/subscribe MQTT directly
- make arbitrary HTTP requests
- read Gateway credentials
- change association or DeviceSerial
- reboot/reset the Gateway
Output
Logical output may contain state, telemetry, or event records. The runtime validates those records and decides which publisher/state pipeline receives them.
Offline and last-known-good
A valid synchronized rule remains cached and usable offline. A new candidate becomes active only after parse/validation/preparation and an atomic activation step. A malformed candidate never replaces last-known-good.
Resource policy
Every target firmware integration must define a bounded GatewayAnalyzerExecutionPolicy covering execution time, input, output, record count, state, queue, and concurrency. Numeric values are selected for the actual MCU/RAM/workload and Analyzer content cannot raise its own limits.