.png)
How Many Monnit Sensors Can One Gateway Support
A Monnit gateway is often the smallest line item in a wireless sensor quote, but it decides how well the whole system works. Add too few gateways and the network can become patchy. Add too many and the project costs more than it should.
For most Monnit wireless deployments, a single gateway is commonly planned to support up to 100 sensors, assuming the gateway model, sensor type, reporting rate, and site conditions all fit that design. That number is a useful starting point, not the only thing that matters.
The better pre-purchase question is this: how many sensors can one gateway support reliably in your building, yard, cellar, cool room, shed, or plant room?
The short answer is usually up to 100 sensors per gateway
Monnit’s wireless sensor networks are built around gateways that collect data from nearby sensors and send it to Monnit’s cloud platform or monitoring system. In many setups, the practical planning figure is up to 100 wireless sensors per gateway.
That does not mean every project should load one gateway with 100 sensors.
A gateway serving 20 sensors in a concrete pump room may work harder than a gateway serving 80 sensors in an open warehouse. A network with sensors reporting every 10 minutes behaves differently from one where most sensors report only a few times per day. Battery status, signal strength, interference, antenna position, and gateway connection type all affect the result.
Think of the 100-sensor figure as a capacity ceiling under suitable conditions. For a new purchase, it is usually smarter to design for the site, then check the sensor total.
A simple rule helps:
If the sensors are in good radio range, report at normal intervals, and are not all clustered in radio-hostile spaces, one gateway may be enough for up to 100 sensors.
If any part of that sentence feels doubtful, plan the network before you place the order.
How the Monnit network architecture works
A Monnit wireless system has three main parts:
Wireless sensors
One or more gateways
The monitoring platform, often iMonnit or a connected system
The sensors measure conditions such as temperature, humidity, door activity, water detection, pressure, voltage, dry contact states, movement, and other site conditions. Each sensor sends readings wirelessly to a gateway.
The gateway acts as the bridge. It listens for sensor messages, confirms what it receives, and passes that data through an internet or network connection. Depending on the gateway model, that backhaul may use Ethernet, cellular, Wi-Fi, or another supported connection.
Most buyers picture the gateway as a router for sensors. That is close, but one detail matters: wireless sensors generally do not form a mesh where every sensor passes messages along for other sensors. In a typical Monnit setup, each sensor needs a usable radio path back to a gateway.
That means a sensor count on paper is not enough. A gateway can only support sensors it can hear well enough, often enough, in the conditions where the equipment will be installed.
The gateway is a collector, not just a counter
When people ask, “How many Monnit sensors can one gateway support?”, they are often asking about a number. The better way to view the gateway is as a collector with limits across several areas:
Factor | Why it affects capacity |
Sensor count | Each sensor needs to be registered, heard, and managed by the gateway. |
Reporting interval | Frequent readings create more radio traffic and more data to forward. |
Radio signal quality | Weak signals can mean missed messages or repeat transmissions. |
Physical layout | Walls, racking, doors, tanks, insulation, and distance affect coverage. |
Gateway backhaul | A stable internet or cellular path keeps data moving after the gateway receives it. |
Alarm behaviour | Sensors that report often during events can increase bursts of traffic. |
A low-traffic network with strong signals can sit near the upper end of capacity. A high-traffic network in a difficult building may need extra gateways well before the sensor count reaches 100.
Sensor density changes the real capacity
Sensor density means how many sensors sit within the same radio area and how often they communicate. A site can have the same number of sensors but behave very differently.
Picture two installations.
The first has 70 temperature sensors spread across a light industrial warehouse. They report every 30 or 60 minutes. The gateway has a clear mounting position, high on a wall, away from metal cabinets and electrical noise. That network may be easy to support with one gateway.
The second has 45 sensors in a cold storage facility. Some sit inside cool rooms, some behind insulated panel doors, some near compressors, and some on mobile stock areas. Several sensors may report more often because temperature changes matter. Even with fewer sensors, this site may benefit from two gateways.
The sensor count went down, but the network difficulty went up.
Reporting interval is a major design choice
Every wireless message takes airtime. The shorter the reporting interval, the busier the network becomes.
A sensor that reports once every hour creates far less traffic than a sensor that reports every minute. Alarm conditions can also change behaviour. For example, a temperature sensor may report on a normal schedule most of the day, then send extra messages when a threshold is crossed.
Before deciding that one gateway is enough, list the sensors by reporting pattern:
Low-traffic sensors Examples include storage room temperature, door activity on rarely used doors, and periodic humidity readings.
Medium-traffic sensors Examples include cool room temperature, equipment runtime, and open-close monitoring on active access points.
High-traffic sensors Examples include process measurements, frequent status checks, or sensors set to report at short intervals.
A gateway that supports 100 low-traffic sensors may not be the right design for 100 high-traffic sensors. In a busy system, extra gateways can reduce congestion and improve the chance that readings arrive on time.
Not all sensors behave the same way
Two sensors may both count as “one sensor” in a gateway limit, but they may not create the same workload.
A basic temperature sensor that sends routine readings is different from a device watching a fast-changing input. A sensor placed at the edge of coverage may also consume more network attention if messages need retries or arrive with weak signal strength.
Battery-powered wireless sensors also benefit from good signal quality. When a sensor struggles to reach the gateway, it may use more energy trying to communicate. Better gateway placement can improve both data reliability and battery life.
Radio coverage often sets the real limit first
Radio coverage is the part buyers often underestimate. A gateway may technically support a large number of sensors, but only inside a usable coverage area.
Wireless range depends on the radio band, gateway antenna, sensor antenna, building materials, mounting height, interference, and site shape. Open air is easier than a plant room. A timber-framed building is usually easier than a structure filled with concrete, steel, foil insulation, cool room panels, liquid tanks, or earth banks.
In Australian sites, common problem areas include:
Cold rooms and freezer rooms with insulated metal panels
Warehouses with tall pallet racking
Plant rooms with pumps, motors, and switchboards
Basements and underground storage areas
Farms with sheds spread over a wide area
Food production areas with washdown zones
Water treatment sites with tanks and pipework
Multi-level buildings with concrete floors
A gateway should sit where it can hear the sensors, not merely where power and Ethernet happen to be convenient.
Gateway placement matters more than people expect
Small changes in placement can have a large effect. Mounting a gateway higher on a wall can improve coverage. Moving it away from a metal cabinet can reduce signal loss. Placing it near the centre of a sensor group often performs better than placing it at one end of the site.
Good gateway placement usually follows these principles:
Mount the gateway in a clear, elevated position where possible.
Avoid enclosing it in metal cabinets unless the antenna is designed for that.
Keep it away from large motors, switchboards, and dense metal structures.
Place it near the centre of the sensor area, not at the edge.
Check signal strength after installation, not just during planning.
Use additional gateways for separated buildings or difficult rooms.
The best pre-purchase plan includes a rough site map. Mark the gateway position, sensor locations, heavy walls, cool rooms, large equipment, and any external sheds. This simple drawing often shows whether one gateway is likely to make sense.
When one gateway is enough
One gateway is often enough when the site has a compact layout, moderate reporting intervals, and good radio paths.
Suitable examples may include:
A small warehouse with sensors spread through one open area
A café, restaurant, or shop with a few fridges and storage areas
A medical or laboratory storage area with sensors in nearby rooms
A single plant room with clear gateway placement
A small farm shed or pump house with sensors close to the gateway
A facility with fewer than 100 sensors and strong signal readings after testing
In these cases, the decision is usually easy. The gateway has enough stated capacity, the sensors are nearby, and the building does not block signals heavily.
One gateway can also make management simpler. There is only one backhaul connection to maintain, one physical device to power, and one coverage zone to check. If the network is small and stable, there may be little value in adding hardware.
When to add another gateway
Additional gateways should be considered when coverage, traffic, or operational risk makes one gateway a weak point.
The strongest signs include weak signal readings, missed sensor messages, long distances, heavy walls, or separated buildings. Another gateway can also help when a site grows over time. Starting with one gateway may be fine for 25 sensors, but adding another 50 later may change the design.
Consider extra gateways in these situations.
The sensors sit in separate physical zones
A single gateway may not suit a site split across multiple buildings, floors, wings, yards, or cool room banks. Distance is only part of the issue. Each boundary, wall, door, and panel can reduce signal quality.
If sensors form two natural clusters, one gateway per cluster often works better than forcing all sensors back to a central point.
Several sensors are near the edge of coverage
A sensor that works during a quick test may still be unreliable over weeks of normal operation. Doors open and close. Stock levels change. Vehicles move. Pallet racking fills. Weather changes affect some outdoor links.
If multiple sensors show weak or inconsistent signal, adding a gateway closer to them is often better than hoping the network will settle.
The reporting intervals are short
High-frequency reporting increases radio traffic. If many sensors need frequent readings, extra gateways can spread the load. This matters more for process monitoring, rapid alarm detection, or sites with many active status sensors.
The site cannot tolerate missing readings
Some sites need higher confidence because the readings protect stock, compliance records, equipment, or safety processes. For example, cold chain monitoring may need stronger coverage than a basic comfort temperature check.
If the cost of a missed alert is high, extra gateway coverage can be a sensible design choice even when the sensor count is under the stated limit.
The network will grow
If the first stage has 60 sensors and the second stage may add another 50, plan for expansion early. It may be easier to install gateways in the right places from the start than to redesign the network later.
A practical buying decision is not only “Will it work today?” It is also “Will it still work after the next batch of sensors?”
A simple way to estimate gateway needs before buying
A full site survey is best for complex facilities, but a basic estimate can catch many issues early.
Use this planning flow:
Count the sensors
Start with the total number of Monnit wireless sensors expected in the first stage. If the number is close to 100, allow room for growth rather than filling the gateway to its limit.
Group sensors by location
Put sensors into physical zones, such as warehouse, cool rooms, loading dock, plant room, office kitchenette, external shed, or pump station.
Mark difficult barriers
Note concrete walls, metal cladding, insulated panels, basements, tanks, machinery, and long distances.
Choose likely gateway positions
Pick locations with power, network access, and good radio position. The best spot is not always beside the modem.
Review reporting intervals
Identify sensors that need short intervals or frequent alarms. These can justify a lower sensor count per gateway.
Leave capacity for growth
If future sensors are likely, do not design the first gateway at its maximum.
Check after installation
Use signal and message history to confirm the design. Move the gateway or add another if weak spots appear.
This process helps avoid two common mistakes: buying one gateway because the sensor count is under 100, or buying multiple gateways when a better placement would have solved the issue.
A practical rule for pre-purchase planning
For a straightforward site, one Monnit gateway can often support a large sensor network, up to the commonly used 100-sensor planning figure. For a harder site, plan around radio zones rather than a single number.
A good rule is:
Use one gateway for a compact site with good coverage and moderate reporting.
Use two or more gateways for separated areas, difficult building materials, short reporting intervals, or high-value monitoring.
Leave spare capacity if the system may expand.
Confirm the design with real signal readings once the sensors are installed.
The gateway is not just a device that “allows” a certain number of sensors. It is the centre of a radio coverage area. If the sensors can reach it clearly and the traffic level is reasonable, one gateway may be all you need. If the site is large, dense, metallic, cold, underground, or likely to grow, extra gateways are often the cleanest way to build a reliable Monnit network.
