AsyncAPI channel · Picarro · Picarro Edge — SAM FOUP Signal Streams

picarro.sam.controller.Controller/watch

Server stream of picarro.sam.controller.Signal. This is a "mapping signal": each message carries mapping_action (MAP_ADDITION | MAP_UPDATE | MAP_REMOVAL) and mapping_key (the analyzer identity, e.g. "Picarro_8008-AMSADS3008"). analyzer_health is cached server-side and re-emitted to new watchers.

Open source AsyncAPI → All Picarro channels Picarro provider profile
Provider: Picarro AsyncAPI: v3.0.0 Spec: Picarro Edge — SAM FOUP Signal Streams Operations: 1 Messages: 3

Channel address

picarro.sam.controller.Controller/watch

Operations

receive
receiveControllerSignals
CLI equivalent: controller-api-tool monitor analyzer_health analyzer_driver

Messages

raw
Raw message received over PicarroMQ from SAM core. mapping_key is the PicarroMQ topic; mapping_action is fixed as MAP_UPDATE. Not cached server-side. Debugging use.
Content-Type:
analyzer_driver_started
mapping_action fixed as MAP_ADDITION; mapping_key is the analyzer identity (e.g. "Picarro_9038-NUV1083"). Implicitly invalidates existing analyzer_health mappings. Not cached server-side.
Content-Type:
analyzer_health
mapping_action indicates added/updated/removed; mapping_key is the analyzer identity. Cached server-side and re-emitted on subsequent watch() calls.
Content-Type:

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.