The ready-made Zigbee Hub is convenient when the user needs a working network of sensors without setting up Linux, Docker, MQTT and coordinator firmware. This is especially noticeable for plants: the owner wants to see humidity, temperature, leakage and the state of the outlet, and not figure out why the container does not start after updating.
A DIY coordinator with Zigbee2MQTT gives more flexibility, but requires technical discipline. A ready-made hub removes some of the maintenance and may be better for a home, a small greenhouse, or a client who does not want to administer the infrastructure. The choice depends on who will be responsible for the system in a month, and not just on the price of the device.
When a ready-made hub is appropriate
The ready-made hub is suitable for scenarios where simple connection, clear support and minimal manual configuration are important. For example, a user has 10-20 Zigbee devices: temperature and humidity sensors, leaks, sockets, several relays. He needs to link them to GrowerHub, receive notifications and see history.
If the installation is for a mini-farm or client, a ready-made hub reduces the risk of dependence on a single enthusiast. The system is easier to transfer to another person: there is a clear interface, update rules and fewer homemade connections.
When is it better to DIY
The DIY approach is appropriate if you need non-standard devices, deep integration with Home Assistant, direct access to MQTT, custom scripts Node-RED or debugging exposes. A technical user will be able to quickly find the problem, look at the logs, change the configuration and connect a rare model.
But DIY requires responsibility: backups, updates, compatibility control, network key storage, availability checking and careful work with pairing. If no one does this, flexibility becomes a source of instability. The general role of Zigbee2MQTT is described in the article Zigbee2MQTT in simple words.
Requirements for plants
For GrowerHub, it is not the marketing functions of the hub that are important, but practical things: local operation of basic scenarios, support for the necessary sensors, freshness of data, clear availability events, load management taking into account safety and the ability to link the device to a plant zone.
If the hub hides too many details, it's harder to figure out why a sensor went missing or an outlet didn't switch. If the hub is too technical, the user may not be able to handle the support. Therefore, a good option lies between simplicity and diagnostics.
Connection with local automation
For automatic watering and accidents, the basic logic must work locally. The cloud can be convenient for remote access, but should not be the only point that decides to turn off the pump when there is a leak. An approach to such scenarios is described in the article local automation without cloud.
Conclusion
A ready-made Zigbee Hub is worth choosing when the system must be understandable and maintainable without constant manual configuration. DIY is better for those who want complete control and are ready to be responsible for the infrastructure. For GrowerHub, the right hub is one that reliably transmits plant data, shows communication problems and does not interfere with local security.