I have a project where I need to control 48 Xenons in a mesh network. Each Xenon is supposed to receive a command via mesh subscribe, operate some field equipment, and report its progress (or lack thereof) via mesh publish.
Xenons are installed outdoors, in a flat field, in a row with 5.5m between each unit. I initially planned to have Argon gateway in the middle, with end units being 130m away from the gateway (but still 5.5m from the nearest Xenon):
X <- 5.5m -> X <- 5.5m -> X … X <- 5.5m -> A <- 5.5m -> X <- 5.5m -> X … X <- 5.5m -> X
I started with 6 Xenons, spaced out nearly the full length of the field, and it worked OK.
Now I added 18 more (full 24 set on one side), and it appears that not all Xenons are connecting to the mesh, or at least not all at the same time. Oddly, sometimes ones further away connect, and closer ones do not. Seems to be function of time rather than distance (?!?).
Secondly, I can see that even when most Xenons are connected to the mesh (they do their jobs as commanded and report back), I can only see Argon and a handful of Xenons connected to the cloud at any one time in my Web IDE. This means I can OTA flash Argon, but not Xenons, and this is a problem (this is a remote, unattended site).
I’m suspecting that Argon can’t cope with this many Xenons attempting to use it as a gateway.
Optionally, too much traffic on mesh?
I’m also not sure if there is a way to boost Xenon mesh antennas, and if this would even make a difference.
Can I add more Argons (gateways) to the same mesh? (And if so, how? Last time I tried app said one Argon per mesh.)
If not, should I split my field of 48 Xenons into 4 (or more) separate mesh networks? Will there be issues with 4 mesh networks operating in close(ish) proximity?
I’m trying to avoid having multiple independent Argons getting separate instructions from the outside world and publishing to separate mesh networks (opens up a whole new set of modbus related problems…)