For the use case invoked in this subthread (an individual monitoring device on each plant), I don’t think it’s the best.
We’re currently working with Nordic nRF52xx/53xx/54xx modules, which have dual ARM cores and built-in 2.4GHz radio, so, support for protocols like Bluetooth Mesh, Zibgee, Thread.
That means you can have a single module that can handle mesh comms with neighboring devices, as well as sensor reading, machine learning and output control. You wouldn’t need a separate comms module to communicate back to a base station or a high post and antenna for long-range comms. So it offers big savings on the device production side and the installation time/cost side.
When I've done similar projects in the past, we did the edge compute on a more expensive box that could be more conveniently accessed by users. It was also the system collected and summarized data into reports, so having the data locally helped.
So you’d centralize the more intensive processing on a unit with more power, and have smaller node devices on the plants doing simpler tasks - just reading from sensors and uploading data, and/or receiving commands to switch things on/off. They’d be solar powered too but the batteries and solar panels can be smaller.
These are all the trade offs you’re constantly working with in this game.