openmixer — generated API reference
    Preparing search index...

    Interface ProbeUnavailable

    A probe that COULD NOT SCAN, and why.

    This is an absence of evidence, never evidence of absence. A probe gated off (no CAP_NET_RAW), never given a NIC, or unable to touch a link (it is carrying traffic, so active-probing it could disrupt a joined box) learned NOTHING about what is out there. Rendering that as an empty device list is the failure this type exists to prevent: on the live rig an established S-0808 reported as 0 device(s) -> [] purely because its link was too busy to probe — the reason was computed and then thrown away.

    A provider rebuilds its DiscoveryProvider.unavailable set on every pass, so an entry standing means "still blind here, right now", and a probe that regains its footing simply stops reporting one.

    interface ProbeUnavailable {
        at: string;
        protocol: "reac" | "dante" | "aes67";
        reason: string;
        reasonCode?: AnyCodedMessage;
        scope?: string;
    }
    Index
    at: string

    ISO-8601 timestamp this was determined.

    protocol: "reac" | "dante" | "aes67"

    Which protocol's probe could not scan.

    reason: string

    The English log/debug rendering of reasonCode, e.g. AF_PACKET needs root or CAP_NET_RAW. Kept for logs and as the honest fallback for a code a client predates.

    reasonCode?: AnyCodedMessage

    WHY, as a translatable CODE + its parameters — what a surface renders. The prober names the situation (discovery.reac.link-busy) and rides the untranslatable detail (a NIC, a packet count, a host error string) as parameters, so the client builds the sentence in the operator's own language.

    scope?: string

    The link/scope this blindness applies to (a NIC), when it is per-link rather than global.