Planning a Large Monnit Installation Sensor Counts Gateways and Site Survey Tips
A small Monnit setup is usually simple. One gateway, a handful of sensors, and a few alerts can cover a single cold room or plant area. A larger installation is different. Once you are planning 10, 20, 50 or more sensors across fridges, warehouses, corridors, plant rooms and outbuildings, the hard part is not sticking sensors to surfaces. The hard part is choosing the right hardware before anything ships.
Large installs fail when the design assumes every sensor can talk to one gateway, every wall behaves the same, or every temperature point needs the same probe. Good planning avoids weak radio links, missing power or network connections, messy software layouts, and gateways placed where they cannot do their job.
This guide walks through the main decisions to make before buying Monnit sensors and gateways.
Start with monitoring points, not sensor quantities
The first mistake is asking, “How many sensors do we need?” before defining what needs to be measured.
Start by listing monitoring points. A monitoring point is one place where you need a reading, alert, or trend. One fridge may need one air temperature sensor. A large walk-in chiller may need two or three points if temperatures vary between the door, rear wall, and evaporator area. A plant room may need temperature, humidity, water leak detection, and door status, all in the same space.
For each point, record:
The asset or area being monitored
The measurement needed
The likely sensor type
The mounting position
The expected distance to the gateway
Any walls, insulation, metal, machinery, or floor levels between the sensor and gateway
Whether the sensor needs a probe, cable, special range, or water-resistant housing
The alert contacts or teams that need to see it in software
A simple example for refrigeration:
Area | Monitoring need | Likely hardware plan |
10 upright fridges | Air temperature in each fridge | 10 temperature sensors, often with probes if the radio unit sits outside the fridge |
2 walk-in cold rooms | Front and rear temperature | 4 temperature points, likely probe-based |
Goods-in area | Ambient temperature | 1 room temperature sensor |
Freezer room door | Door open status | 1 open or closed sensor |
That example has 16 monitoring points before adding gateways. If the original estimate was “about 10 fridge sensors,” the order would already be short.
For warehouses and plant rooms, the count can grow just as quickly. A warehouse might need temperature and humidity in each zone, plus door contacts on roller shutters. A plant room might need pipe temperature, leak detection, humidity, and equipment run-time monitoring. Count the points first, then map those points to specific Monnit sensor models.
Match the sensor to the job, not just the reading
Two sensors may both measure temperature, but they may not suit the same installation.
A fridge or freezer usually needs careful placement. Putting the complete wireless sensor body inside a cold, metal-lined cabinet can weaken the radio signal and expose the device to harsher conditions than needed. In many cases, a sensor with an external probe lets the probe sit inside the chilled space while the radio body mounts outside or in a better signal position.
For a plant room, the issue may be heat, vibration, moisture, or access. A sensor placed too close to a boiler, pump or ventilation outlet may report the condition of that local hot spot, not the room. A water detection sensor needs to sit where water will actually collect, not just where it is easy to reach.
For a warehouse, height matters. A sensor mounted high in racking may show roof-level heat rather than the temperature around stored goods. If the warehouse has chilled zones, mezzanines, loading bays, or high-speed doors, each area may need separate monitoring.
When selecting Monnit sensors, check at least these details:
Measurement range
Probe type and cable length
Expected battery life under the intended reporting interval
Indoor or outdoor suitability
Mounting method
Sensor family compatibility with the chosen gateway
Distance and radio path to the gateway
Whether the reading represents the asset, room, product, pipe, or process you care about
The aim is not to buy the most sensors. The aim is to buy the right sensors once.
Plan gateway coverage before placing the order
Gateways are often treated as an afterthought. For a larger Monnit installation, they should be part of the first design sketch.
A gateway has two jobs. It receives wireless messages from sensors, then sends that data onward through its internet connection. Both sides matter. A well-placed gateway with poor internet access is a problem. A gateway with perfect Ethernet in the wrong part of the building is also a problem.
The right number of gateways depends on:
Building size and shape
Wall materials
Floor levels
Metal equipment, racking, fridges, tanks, ducting, and insulation
Sensor reporting frequency
Sensor count per gateway
Gateway model limits
Need for redundancy in critical areas
Available Ethernet, Wi-Fi, or cellular signal
Avoid designing to the absolute maximum sensor count listed for a gateway. Leave headroom for future sensors, replacement units, and changes to reporting behaviour. Also keep sensor groups sensible. If 20 fridge sensors sit in one retail area and another 20 plant-room sensors sit two floors away behind concrete and pipework, the clean design is usually not one gateway in the middle and hope.
A better starting point is to group gateways around physical zones:
Installation type | Example sensor plan | Gateway planning thought |
Small cold chain site | 10 fridge or freezer points | One well-placed gateway may work if RF paths are clean |
Medium warehouse | 20 to 40 sensors across racking, doors, and ambient zones | Plan at least one survey walk and expect more than one gateway if zones are separated |
Large plant area | 20 or more sensors around pumps, tanks, leaks, and rooms | Gateways may need to sit near clusters because metal and concrete can block signals |
Multi-building site | Sensors in separate buildings | Treat each building as its own RF area unless proven otherwise |
Gateway quantity is not only about range. It is about reliability, neat organisation, and future growth.
Treat buildings and obstructions as part of the design
Wireless range figures are valuable, but they do not describe every real building. Radio signals behave differently through open air, brick, blockwork, insulation, metal cladding, refrigeration panels, glass, timber, concrete, and machinery.
Large Monnit installations often face a mix of obstructions:
Metal fridge and freezer cabinets
Foil-backed insulation panels
Reinforced concrete walls and floors
Steel warehouse racking
Plant equipment and pipework
Fire doors
Lift shafts and stair cores
External walls between buildings
Moving stock, pallets, vehicles, or cages
Metal and dense building materials are common causes of weak signal paths. A gateway placed on the wrong side of a cold room panel may struggle to hear a sensor only a short distance away. By contrast, a sensor much farther away in a clear warehouse aisle may report cleanly.
Do not judge coverage by distance alone. Judge it by the path between the sensor and the gateway.
If possible, place gateways:
Higher rather than low behind equipment
Away from large metal surfaces
In or near the sensor cluster they serve
Where maintenance teams can still access them
Close to reliable power and connectivity
In a position that avoids unnecessary walls or floors between devices
A few metres of movement can make a large difference. In one fridge example, mounting the sensor body outside the chilled cabinet and running a probe inside can improve the radio path. In a plant room, moving the gateway from a utilities cupboard to a wall facing the equipment area may improve coverage without adding another gateway.
Use an RF or site survey when the layout is not simple
A site survey is the practical step between a drawing and a reliable purchase. It helps confirm gateway locations, sensor positions, and whether extra hardware is needed.
For small installations in open spaces, a desk plan may be enough. For larger sites, especially warehouses, cold stores, basements, plant rooms, and multi-building estates, a survey is the safer choice.
A useful survey checks:
Candidate gateway positions
Sensor positions at actual mounting height
Signal quality from each area
Building materials and obstructions
Available power and network points
Cellular signal if cellular gateways are being considered
Safe access for installation and battery changes
Environmental risks such as washdown, condensation, heat, or impact
The survey should test the difficult points, not only the easy ones. If 18 sensors are in clear view of the gateway and 2 are behind cold room panels, test the 2 difficult locations first. If those work, the easy points are less concerning. If they fail, the design can change before the purchase is finalised.
For a 20-sensor warehouse, the survey might show that all ambient sensors report well from one gateway, but the loading bay door sensors need a second gateway because shutters, vehicles, and racking create an inconsistent path. For a plant-room installation, the survey might show that sensors behind pumps and tanks need a gateway on the plant side of a wall, not in the corridor.
A good survey does not just answer “Will it work?” It answers “Where should we put the hardware so it keeps working?”
Choose gateway connectivity for the site, not convenience
Monnit gateways commonly need a way to send data to the monitoring platform. The best connectivity choice depends on the site and its IT rules.
Ethernet is often preferred where a reliable network point is available. It can be stable and simple, but only if the gateway can be placed where the sensors can reach it. Do not put the gateway in a comms cabinet far from the sensors just because Ethernet is there.
Wi-Fi can help where cabling is difficult, but it depends on the site’s wireless policy, coverage, passwords, and reliability. Some industrial sites separate operational networks from guest or corporate networks, so confirm access before buying.
Cellular gateways can be useful where no local network is available, where IT approval is slow, or where a temporary installation is needed. They still depend on mobile signal at the gateway location. A mobile phone signal check can help, but a proper test with the intended gateway location is better.
Before choosing gateway connectivity, ask:
Is Ethernet available near the correct RF location?
Can the gateway use the local network under site IT rules?
Is Wi-Fi permitted for monitoring equipment?
Is cellular signal strong enough in the gateway location?
Is there a backup plan if local internet fails?
Who owns power, network access, and ongoing support?
For critical monitoring, do not let network convenience override sensor coverage. If the perfect RF location has no Ethernet, it may be better to add a network point, use approved Wi-Fi, or test a cellular option than to move the gateway into a poor radio position.
Build software organisation into the hardware plan
Software organisation sounds like an admin task, but it affects hardware decisions. A large sensor estate can become hard to manage if every device has a vague name such as “Temperature Sensor 1” or “Door 3.”
Plan the structure before installing. This helps installers label sensors correctly and helps users understand alerts later.
Use naming that matches the physical site. For example:
`Kitchen Fridge 01 Air Temp`
`Kitchen Fridge 01 Door`
`Warehouse Zone A Humidity`
`Plant Room Leak Tray 02`
`Freezer Room Rear Probe`
`Loading Bay Roller Door 04`
Group devices by building, floor, zone, department, or asset type. The right method depends on who responds to alerts. A facilities team may prefer plant areas and rooms. A food safety team may prefer fridge and freezer groups. A warehouse team may prefer zones and loading bays.
Also plan:
Alert thresholds for each sensor type
Escalation contacts
Reporting intervals
Who receives low battery notices
Who can edit settings
Naming labels on the physical devices
Spare sensor naming and storage
Future expansion space in the naming system
If you buy 20 fridge sensors, label them before installation and match each label to the software record. This avoids the common problem of alarms arriving from a device no one can physically identify.
Software planning also supports gateway selection. If one gateway serves all sensors in Building A and another serves Building B, that structure can make troubleshooting easier. When readings stop or signal levels change, the physical and software layout tell the same story.
Plan for growth and maintenance from day one
A large monitoring system rarely stays the same. More fridges arrive. A warehouse changes racking. A plant room gains equipment. Compliance requirements change. A temporary sensor becomes permanent.
Build in practical headroom.
For sensors, order the right quantity for the current plan, plus any known near-term additions. For gateways, leave capacity and coverage margin where growth is likely. For mounting, avoid positions that require high-risk access every time a battery needs changing.
Maintenance planning should include:
Safe access to every sensor
Clear records of sensor location
Battery change process
Spare sensors and probes
Gateway power supply access
Network contact for connectivity issues
Review dates for alert thresholds
A change log for moved or replaced sensors
Think about physical damage too. Warehouse sensors near forklift routes may need safer mounting positions. Plant-room sensors near hot surfaces or wet areas may need different housings or mounting methods. Door sensors on busy roller shutters need careful placement so they do not get knocked out of alignment.
A larger installation is successful when it can be maintained by normal site staff, not only by the person who designed it.
A practical pre-purchase checklist
Before confirming the order, work through this list.
Sensor count
Have all monitoring points been listed?
Does each point have a chosen Monnit sensor type?
Are probe lengths and measurement ranges correct?
Are fridge, freezer, warehouse, and plant-room conditions matched to the hardware?
Are spare or future sensors needed?
Sensor location
Is each sensor location marked on a drawing or schedule?
Has the reading location been separated from the radio body location where needed?
Are sensors away from false hot spots, cold spots, impact areas, and water risks?
Can batteries be changed safely?
Gateway count and placement
Are gateways placed for RF coverage, not only for network access?
Has each building or difficult zone been considered separately?
Is there capacity for future sensors?
Are gateway model limits checked against the planned sensor count?
Is redundancy needed for critical areas?
RF and site conditions
Has a site survey been carried out for larger or complex layouts?
Have the worst locations been tested?
Are metal, concrete, insulation, racking, and machinery accounted for?
Are multi-floor or multi-building paths proven rather than assumed?
Connectivity and software
Is Ethernet, Wi-Fi, or cellular confirmed at the gateway location?
Are IT approvals complete where needed?
Is the software naming structure agreed?
Are alert thresholds and users planned?
Are physical labels matched to software names?
Taking the time to plan these details reduces repeat visits, rushed changes, and incorrect hardware purchases.
The best large installations are designed before they are installed
Planning a Large Monnit Installation Sensor Counts Gateways and Site Survey Tips comes down to one core idea: design around the real site, not an ideal drawing.
Count monitoring points before counting sensors. Match each sensor to the asset and environment. Place gateways where they can hear the sensors and connect reliably. Use a site survey when walls, metal, distance, or multiple buildings create uncertainty. Build the software structure before the first alert arrives.
A 10-sensor fridge project can often stay simple. A 20-sensor warehouse or plant-room project needs more care. Larger sites need clear zones, tested gateway positions, and a hardware list based on evidence. That planning work is far cheaper than discovering after installation that the wrong sensors were ordered or the gateway cannot reach the most important location.
Comments