[IDEA] Zigbee Router mode/role support with Ziggurat?

[Hedda]

Could it be a good idea to run in Zigbee Router mode/role support with Ziggurat?

Use case example is if have multiple/many network-attached (ESPHome-based) OpenThread RCP devices connected to and controlled by Home Assistant then an idea would be have the option to manually or automatically assign them differenet roles:

• Zigbee Coordinator via Ziggurat.
• Zigbee Router via Ziggurat.
• OpenThread Border Router.
• OpenThread Router.

Then you do not have an extra idling device OpenThread RCP device if it as it could be used as a Zigbee Router via Ziggurat but then it could still be "converted" into a Zigbee Coordinator via Ziggurat via an option if and when the Zigbee Coordinator fails, (and though it would not be ideal to remove a working Zigbee Router in that process it might still be a prefered choice over not having a Zigbee Coordinator).

Then later could also open the possibility to allow manual or automatic fail-over for high-availability if you could set up one of those OpenThread RCP devices as either "general hot-spare" or specifically set a specific OpenThread RCP device as a backup Zigbee Coordiator that is online but not used unless the first goes down.

[puddly]

I don't think we'll be implementing this any time soon, it's way too complex. You can just flash the standalone device with our EmberZNet router firmware. Standalone router mode is a massive project and not something that would benefit users when compared to existing solutions. It would require running Ziggurat on an ESP32 in RCP mode, implementing the ZCL, standalone functionality, key exchange from the client side, the joining state machine, and so on.