本文整理了Java中com.zsmartsystems.zigbee.transport.ZigBeeTransportReceive类的一些代码示例，展示了ZigBeeTransportReceive类的具体用法。这些代码示例主要来源于Github/Stackoverflow/Maven等平台，是从一些精选项目中提取出来的代码，具有较强的参考意义，能在一定程度帮忙到你。ZigBeeTransportReceive类的具体详情如下：
包路径：com.zsmartsystems.zigbee.transport.ZigBeeTransportReceive
类名称：ZigBeeTransportReceive

ZigBeeTransportReceive介绍

[英]Defines the interface for data passed from the transport layer (ie dongle) to the ZigBee stack framework.

ZigBee transport interface implemented by different hardware drivers. This could support for example serial interfaces for dongles, or IP connections to remote interfaces.

The ZCL interface allows the stack to specify the NWK (Network) header, the APS (Application Support Sublayer) and the payload. The headers are provided separately to allow the framework to specify the configuration in some detail, while allowing the transport implementation (eg dongle) to format the data as per its needs. The payload is serialised by the framework using the ZigBeeSerializer and ZigBeeDeserializer interfaces, thus allowing the format to be set for different hardware implementations.

The ZDO interface exchanges only command classes. This is different to the ZCL interface since different sticks tend to implement ZDO functionality as individual commands rather than allowing a binary ZDO packet to be sent and received.
[中]定义从传输层（即加密狗）传递到ZigBee堆栈框架的数据接口。
ZigBee传输接口由不同的硬件驱动程序实现。例如，它可以支持加密狗的串行接口，或远程接口的IP连接。
ZCL接口允许堆栈指定NWK（网络）头、APS（应用程序支持子层）和有效负载。标题是单独提供的，以允许框架详细指定配置，同时允许传输实现（例如加密狗）根据需要格式化数据。该框架使用ZigBeeSerializer和ZigBeeDeserializer接口对有效负载进行序列化，从而允许为不同的硬件实现设置格式。
ZDO接口只交换命令类。这与ZCL接口不同，因为不同的条倾向于将ZDO功能作为单独的命令来实现，而不是允许发送和接收二进制ZDO数据包。

代码示例

代码示例来源：origin: zsmartsystems/com.zsmartsystems.zigbee

@Override
public void shutdown() {
  if (conbeeHandler == null) {
    return;
  }
  conbeeHandler.setClosing();
  zigbeeNetworkReceive.setNetworkState(ZigBeeTransportState.OFFLINE);
  serialPort.close();
  conbeeHandler.close();
  logger.debug("ConBee dongle shutdown.");
}

代码示例来源：origin: zsmartsystems/com.zsmartsystems.zigbee

zigbeeNetworkReceive.receiveCommand(apsFrame);
return;
switch (deviceState.getNetworkState()) {
  case NET_CONNECTED:
    zigbeeNetworkReceive.setNetworkState(ZigBeeTransportState.ONLINE);
    break;
  case NET_JOINING:
  case NET_LEAVING:
  case NET_OFFLINE:
    zigbeeNetworkReceive.setNetworkState(ZigBeeTransportState.OFFLINE);
    break;
  default:

代码示例来源：origin: zsmartsystems/com.zsmartsystems.zigbee

@Override
public boolean notify(final AF_INCOMING_MSG clusterMessage) {
  ZigBeeApsFrame apsFrame = new ZigBeeApsFrame();
  apsFrame.setCluster(clusterMessage.getClusterId());
  apsFrame.setDestinationEndpoint(clusterMessage.getDstEndpoint());
  apsFrame.setSourceEndpoint(clusterMessage.getSrcEndpoint());
  apsFrame.setProfile(getEndpointProfile(clusterMessage.getDstEndpoint()));
  // nwkHeader.setDestinationAddress(clusterMessage.geta);
  apsFrame.setSourceAddress(clusterMessage.getSrcAddr());
  apsFrame.setApsCounter(clusterMessage.getTransId());
  apsFrame.setPayload(clusterMessage.getData());
  zigbeeNetworkReceive.receiveCommand(apsFrame);
  return true;
}

代码示例来源：origin: zsmartsystems/com.zsmartsystems.zigbee

zigbeeNetworkReceive.receiveCommand(apsFrame);
return;

代码示例来源：origin: zsmartsystems/com.zsmartsystems.zigbee

logger.debug("ConBee transport initialize");
zigbeeNetworkReceive.setNetworkState(ZigBeeTransportState.UNINITIALISED);