Hello @Odysee
As mentioned in the community forum, running two meshbots at the same time with multiple actions could crash the Z-Wave service. This suggests that there is a limit to how many operations an Ezlo controller can handle at once without encountering problems.
To mitigate this, delays were introduced between actions in a Meshbot, and new Execution Policies were implemented to define the sequence in which actions are executed. The policies include:
- Execute actions in parallel: All actions are started at the same time.
- Execute actions sequentially: Each action is executed once the previous action is finalized.
For your specific case, where you’re considering running checks every few seconds and creating 50 of them, it’s advisable to approach this with caution. Running too many checks in a short interval could potentially overload the controller, leading to instability or failure. Instead, consider the following:
- Space out the checks to run less frequently if possible.
- Use the Execution Policies to sequence actions and prevent overloading the controller.
- Consider the complexity and number of actions each Meshbot performs.
- Monitor the performance and responsiveness of your system as you add more Meshbots.
It’s also worth noting that we are continuously working on improving the performance and capabilities of our controllers, as indicated by the ongoing development and updates mentioned in the Beta - Ezlo Linux 2.0.32.2097.3 [production-146] for Ezlo Plus, Ezlo Secure controllers forum thread.
Ultimately, while there isn’t a one-size-fits-all answer to how much your controller can handle, it’s best to start with a conservative approach and gradually increase the number of Meshbots while keeping an eye on the system’s performance.