Concepts

Bridge Pipeline

The bridge processes MQTT and forwards selected data to Zabbix trapper items:

1. receive MQTT message
2. parse/validate message type (alive, adv1, adv4, adv8)
3. resolve device from LLD cache
4. apply delay throttling
5. enqueue/send to Zabbix

LLD Ownership

LLD endpoints are served by the SafeCall HTTP server:

• GET /lld/gateways
• GET /lld/beacons

Bridge mode consumes these endpoints to map incoming MQTT MACs to Zabbix hostnames.

Data Mapping

Bridge sends item keys:

• gateways: wtgateway.temperature, wtgateway.load, wtgateway.last_seen
• beacons: wtbeacon.battery, wtbeacon.temperature, wtbeacon.humidity, wtbeacon.pressed, wtbeacon.last_seen

Discovery Model In Zabbix

Zabbix LLD discovery rules poll SafeCall endpoints via HTTP Agent. Host prototypes attach discovered hosts to templates and trigger definitions.

Observability Layers

• zabbix doctor: checks SafeCall-side dependencies and network paths
• bridge debug mode: runtime counters, drop reasons, cache state, send outcomes
• zabbix verify: API-level read-only checks that required Zabbix objects exist