Expand description
§zigbee-deconz
dresden elektronik’s deCONZ serial protocol, which ConBee, ConBee II, ConBee III, RaspBee and RaspBee II coordinator firmware speaks.
frame: SLIP framing, the frame header and checksum.message: requests and responses, typed in both directions.client(featureclient): an async client.
Written from dresden elektronik’s public serial protocol documentation; no code was copied from any other implementation.
Part of zigbee-bridge, maintained by Pulzar. See the user guide, the library guide and the API documentation.
License: MIT.
Re-exports§
pub use frame::Decoder;pub use frame::Frame;pub use frame::FrameError;pub use message::Address;pub use message::ApsConfirm;pub use message::ApsIndication;pub use message::ApsRequest;pub use message::DecodeError;pub use message::Request;pub use message::Response;
Modules§
- client
- An async deCONZ client: one request at a time, and every device state the firmware reports as an event (it says there when a received frame or a delivery confirm is waiting to be read).
- frame
- deCONZ frames on the wire: SLIP-framed (RFC 1055), each frame a command id, sequence number, status, total length, payload, and a 16-bit checksum (the two’s complement of the byte sum).
- ids
- Command ids, parameters, states and statuses.
- message
- Typed requests and responses, both directions, so the client, the simulator and the fuzz targets share one definition of each layout.