Replies: 2 comments 1 reply
-
Personally I'm hoping someone will add Fault Tolerance / High-Availability to enable support for multiple radio adapters for redundency, see: and |
Beta Was this translation helpful? Give feedback.
0 replies
-
and how can everything written above relate to the XZG firmware? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
FYI, Zigbee2MQTT + ZHA projects are independently working on "Zigbee-on-Host" architecture projects, depend on OT RCP firmware.
Nerivec already merged initial Zigbee-on-Host v0.1.0 into zigbee-herdman v3.4.0 so it can soon be tested Zigbee2MQTT dev (edge):
puddly is at the same sime working on a experimental "ziggurat" project which is a open-source Zigbee stack implemented in Rust that in similarly in concept allow you to run the Zigbee stack on the host computer and depend on sending raw frames to an OpenThread RCP radio using the Spinel serial protocol.
Zigbee on Host for Zigbee2MQTT (based on zigbee-herdsman)
Open Source ZigBee stack designed to run on a host and communicate with a radio co-processor (RCP).
Current implementation aims for compatibility with OpenThread RCP firmware. That base provides compatibility with any chip manufacturer that supports it (Silabs, TI, etc.) with the only requirements being proper implementation of the STREAM_RAW mechanism of the Spinel protocol (which allows to send raw 802.15.4 frames, including... ZigBee!) and hardware MAC ACKing (much faster).
This library can also serve as a base for pentesting ZigBee networks thanks to the ability to easily craft various payloads at any layer of the specification and send them through the raw stream using any network parameters.
More info in his readme file:
ziggurat Zigbee stack and zigpy-spinel radio adapter library for ZHA (based on zigpy)
An experimental open source Zigbee stack implemented in Rust.
This project aims to replace the functionality provided by existing radio adapters running Zigbee firmware and move all processing to the host, eliminating practically all limitations imposed by microcontroller-based Zigbee stacks.
Existing Zigbee applications (i.e. ZHA, Z2M, and OpenHAB) would implement a new radio type and communicate with the Ziggurat server over TCP, a UNIX socket, or possibly a virtual serial port, using a high-level wire protocol similar to that of existing Zigbee stacks.
Ziggurat communicates with a 802.15.4 radio hardware over the OpenThread Spinel serial protocol. We currently use OpenThread RCP firmware to just send & receive packets and automatically send 802.15.4 ACKs. The stack handles all encryption, decryption, and processing, treating the radio hardware as just an 802.15.4 frontend. We aim to use with OpenThread RCP firmware for the foreseeable future, as it provides a uniform and hardware-agnostic 802.15.4 frontend that theoretically runs on chips from every major vendor and eliminates the need to use multiple firmwares when switching between Zigbee and Thread applications.
More info in these readme files:
and
Beta Was this translation helpful? Give feedback.
All reactions