Skip to content
Get started

EZSP Proxy Tap

IMPORTANT

This component is EXPERIMENTAL. The API (both Python configuration and C++ interfaces) may change at any time without following the normal breaking changes policy. Use at your own risk. Once the API is considered stable, this warning will be removed.

The ezsp_proxy_tap component acknowledges frames from a Silicon Labs EZSP Zigbee network coprocessor (NCP) attached to a Serial Proxy. The NCP resets if it gets no acknowledgement in time, so a slow or unstable network between the device and the API client can otherwise reset it.

The component requires a Serial Proxy.

# Example configuration entry
ezsp_proxy_tap:
  serial_proxy_id: zigbee_serial

Configuration Variables

Section titled “Configuration Variables”
  • id (Optional, ID): Manually specify the ID to use for code generation.
  • serial_proxy_id (Required, ID): The ID of the Serial Proxy the NCP is attached to.

How It Works

Section titled “How It Works”

The component acknowledges frames only while the API client has the port in PROTOCOL mode. The client must then not send its own acknowledgements. While a client holds the port in RAW mode the component sends nothing.

The API client must support PROTOCOL mode, for example serialx. With other clients the port stays in RAW mode and the component has no effect.

The component follows the NCP’s frame numbers from its next reset. If the NCP is already running, the component follows them from the first frame it receives.

See Also

Section titled “See Also”