/**
 * @license
 * Copyright 2022-2026 Matter.js Authors
 * SPDX-License-Identifier: Apache-2.0
 */

/*** THIS FILE IS GENERATED, DO NOT EDIT ***/

import type { ClusterType, ClusterTyping } from "../cluster/ClusterType.js";
import type { ClusterId } from "../datatype/ClusterId.js";
import type { ClusterModel } from "@matter/model";
import type { NodeId } from "../datatype/NodeId.js";
import type { GroupId } from "../datatype/GroupId.js";
import type { EndpointNumber } from "../datatype/EndpointNumber.js";
import type { FabricIndex } from "../datatype/FabricIndex.js";

/**
 * Definitions for the Binding cluster.
 *
 * > [!NOTE]
 *
 * > NOTE: This scope of this document is the Binding cluster as part of the Cluster Library. The Binding cluster is
 *   meant to replace the support from the Zigbee Device Object (ZDO) for supporting the binding table.
 *
 * A binding represents a persistent relationship between an endpoint and one or more other local or remote endpoints. A
 * binding does not require that the relationship exists. It is up to the node application to set up the relationship.
 *
 * A binding is used to inform a client endpoint of one or more targets for a potential interaction. For example: a
 * light switch that controls one or more light bulbs, needs to be told the nodes and endpoints of the bulbs, or told a
 * group in which the bulbs are members. For example: A client that needs to subscribe to an occupancy sensor, needs to
 * know the node and endpoint of the sensor.
 *
 * In such cases, a binding is used to direct a local endpoint to a target. The existence of the Binding cluster on the
 * client endpoint, allows the creation of one or more binding entries (bindings) in the Binding cluster.
 *
 * Each binding indicates another endpoint or cluster on another endpoint. Multiple bindings are allowed, depending on
 * the interaction.
 *
 * A binding is either a unicast binding, where the target is a single endpoint on a single node, or a groupcast
 * binding, where the target is a group, which may indicate multiple endpoints on multiple nodes. The binding may also
 * target a single cluster on the target endpoint(s).
 *
 * When a client cluster requires a target for an interaction, the Binding cluster shall exist on the same endpoint.
 *
 * Once a binding entry is created on the Binding cluster, the client endpoint may initiate interactions to the binding
 * target.
 *
 * @see {@link MatterSpecification.v151.Core} § 9.6
 */
export declare namespace Binding {
    /**
     * The Matter protocol cluster identifier.
     */
    export const id: ClusterId & 0x001e;

    /**
     * Textual cluster identifier.
     */
    export const name: "Binding";

    /**
     * The cluster revision assigned by {@link MatterSpecification.v151.Cluster}.
     */
    export const revision: 1;

    /**
     * Canonical metadata for the Binding cluster.
     *
     * This is the exhaustive runtime metadata source that matter.js considers canonical.
     */
    export const schema: ClusterModel;

    /**
     * {@link Binding} always supports these elements.
     */
    export interface BaseAttributes {
        /**
         * Each entry shall represent a binding.
         *
         * @see {@link MatterSpecification.v151.Core} § 9.6.6.1
         */
        binding: Target[];
    }

    /**
     * Attributes that may appear in {@link Binding}.
     */
    export interface Attributes {
        /**
         * Each entry shall represent a binding.
         *
         * @see {@link MatterSpecification.v151.Core} § 9.6.6.1
         */
        binding: Target[];
    }

    export type Components = [{ flags: {}, attributes: BaseAttributes }];

    /**
     * @see {@link MatterSpecification.v151.Core} § 9.6.5.1
     */
    export class Target {
        constructor(values?: Partial<Target>);

        /**
         * This field is the remote target node ID. If the Endpoint field is present, this field shall be present.
         *
         * @see {@link MatterSpecification.v151.Core} § 9.6.5.1.1
         */
        node?: NodeId;

        /**
         * This field is the target group ID that represents remote endpoints. If the Endpoint field is present, this
         * field shall NOT be present.
         *
         * @see {@link MatterSpecification.v151.Core} § 9.6.5.1.2
         */
        group?: GroupId;

        /**
         * This field is the remote endpoint that the local endpoint is bound to. If the Group field is present, this
         * field shall NOT be present.
         *
         * @see {@link MatterSpecification.v151.Core} § 9.6.5.1.3
         */
        endpoint?: EndpointNumber;

        /**
         * This field is the cluster ID (client & server) on the local and target endpoint(s). If this field is present,
         * the client cluster shall also exist on this endpoint (with this Binding cluster). If this field is present,
         * the target shall be this cluster on the target endpoint(s).
         *
         * @see {@link MatterSpecification.v151.Core} § 9.6.5.1.4
         */
        cluster?: ClusterId;

        fabricIndex: FabricIndex;
    }

    /**
     * Attribute metadata objects keyed by name.
     */
    export const attributes: ClusterType.AttributeObjects<Attributes>;

    /**
     * @deprecated Use {@link Binding}.
     */
    export const Cluster: typeof Binding;

    /**
     * @deprecated Use {@link Binding}.
     */
    export const Complete: typeof Binding;

    export const Typing: Binding;
}

/**
 * @deprecated Use {@link Binding}.
 */
export declare const BindingCluster: typeof Binding;

export interface Binding extends ClusterTyping {
    Attributes: Binding.Attributes;
    Components: Binding.Components;
}