How to Add Devices in iMonnit Step by Step Guide
Adding a device in iMonnit is usually quick, but a small typo in the Device ID, a lowercase Security Code, or an offline gateway can stop the process cold. The good news is that iMonnit gives you a clear path: add the device, choose a setup, then confirm that it is communicating correctly.
This guide walks through the full process for adding sensors and gateways to an iMonnit account, including what to check before you start, how to scan or enter device details, and how to validate that the device is working.
Before you add a device
If this is your first time using iMonnit, create a new account before adding hardware. If you already have an account, log in and make sure you can access the main menu.
You will also need the device itself. For most sensors and gateways, iMonnit uses two pieces of information from the device label:
Device ID
This is the unique number assigned to the device. It is often shown as `ID` on the label.
Security Code
This is the code used to confirm that the device belongs to you. It is often shown as `SC` on the label. The Security Code uses letters and must be entered in uppercase. It does not use numbers.
QR code
Many devices include a QR code that can be scanned with a smartphone camera in the iMonnit mobile app.
You can usually find the Device ID and Security Code on the side or bottom label of the sensor or gateway. If a device has a barcode label, check that area first.
Before moving ahead, place the device somewhere well lit so the label is easy to read or scan. If the QR code is scratched, too small to scan, or your phone camera is not available, you can type the Device ID and Security Code manually.
Step 1. Add the device in iMonnit
To begin, log in to iMonnit and open the main menu. For a sensor, choose Sensors, then look for the Add Sensor button.
The exact screen may look a little different depending on whether you are using the web portal or the mobile app, but the flow is the same. You need to tell iMonnit which device you are adding, then confirm ownership with the Security Code.
Scan the QR code when possible
The fastest option is to scan the QR code on the device label.
In the mobile app, use your smartphone camera to scan the QR code on a gateway or sensor. When the scan works, iMonnit can add the device directly to your account without requiring you to type the ID or Security Code by hand.
This is the best option when you are adding several devices because it reduces typing errors. It also helps avoid common mistakes like confusing similar characters or entering a lowercase letter in the Security Code field.
Enter the Device ID and Security Code manually
If scanning is not available, add the device manually. Find the device label and enter the Device ID exactly as shown.
Next, enter the Security Code. Use uppercase letters only. If the label shows letters, type those letters in uppercase. Do not add spaces unless the iMonnit field specifically formats them for you.
Before selecting Add Device, review both fields carefully. A single wrong character can prevent the device from being added.
A quick manual check helps:
Confirm that the Device ID comes from the correct device label.
Confirm that the Security Code is typed in uppercase.
Make sure the Security Code contains letters, not numbers.
Check that you did not accidentally scan or type a nearby device label.
When everything looks correct, select Add Device.
Add the gateway if your setup needs one
Many Monnit wireless sensors communicate through a gateway. If your sensor needs a gateway, make sure the gateway has been added to the account and is powered before you expect the sensor to report data.
For a gateway, the same basic rule applies. Use the QR code if available, or enter the Device ID and Security Code manually from the gateway label. After it is added, connect it to power and to the internet using the correct connection type for that gateway, such as Ethernet or cellular if supported by the model.
A sensor can be added to the account even if the gateway is not fully communicating yet, but validation will not pass until the gateway is online and able to send data to iMonnit.
Step 2. Choose the setup for your use case
After the device is added, iMonnit will ask how you want to use it. Many sensors include preset use cases to help you get started quickly.
For example, a temperature sensor may offer common setups based on what you want to monitor. You might use a preset for general room temperature, cold storage, equipment areas, or another common condition. The exact list depends on the sensor type.
Choose the use case that best matches the job. If none of the presets fit, create custom settings.
Two settings you may see during setup are Heartbeat Interval and Aware State.
Heartbeat Interval controls routine check-ins
The Heartbeat Interval tells the sensor how often to check in when nothing unusual is happening. A shorter interval means the sensor reports more often. A longer interval means fewer routine messages.
Use a shorter interval when you need closer tracking. Use a longer interval when you do not need updates as often and want to reduce routine transmissions.
The right setting depends on what the sensor is monitoring. A temperature sensor in a sensitive storage area may need more frequent reporting than a sensor used only to confirm general conditions.
Aware State controls event-based behavior
Aware State settings help define when the sensor should react to a condition. For instance, a temperature sensor might enter an aware state when the reading moves outside the range you set.
This matters because the aware state is often tied to alerts and more active reporting. If the threshold is too narrow, the sensor may report too often. If it is too wide, you may miss changes that matter.
Choose settings that match the real condition you care about, not just the default values. If you are unsure, start with a preset use case, save it, then adjust after reviewing the first readings.
Save the setup
When the setup matches your use case, select Save.
Do not skip this step. Adding the device and saving the setup are separate parts of the process. If you leave the screen before saving, the device may be added but not configured the way you intended.
After saving, give the device a clear name if iMonnit allows you to edit it during setup. A name like “Walk-in Cooler Temperature” or “Mechanical Room Door Sensor” is much easier to manage later than a generic sensor name.
Good names are especially helpful if you plan to add more devices in the future.
Step 3. Validate communication
The validation checklist helps confirm that the sensor can communicate with the gateway and that the signal is strong enough for normal use.
This step matters because adding a sensor to your account does not always mean it is already reporting successfully. Validation checks the connection path from the sensor to the gateway and from the gateway to iMonnit.
Confirm the gateway is online
Start with the gateway. A wireless sensor needs a gateway to pass readings to iMonnit.
Check that the gateway is:
Added to the correct iMonnit account.
Connected to power.
Connected to the internet.
Fitted with the required antenna or antennas when applicable.
Connected by Ethernet if your gateway model uses an Ethernet cable.
If the gateway is not online, the sensor may not validate even if the sensor itself is working. In that case, fix the gateway connection first.
Look for signs that the gateway has power and network access. Depending on the gateway model, indicator lights may show power, connection, or activity. If the gateway uses Ethernet, confirm that the cable is seated firmly and connected to an active network port.
Confirm the gateway has communicated with iMonnit
Once the gateway is powered and connected, iMonnit needs to receive communication from it. The validation checklist may show whether the gateway has properly communicated with the platform.
If it has not, wait a few moments and refresh the status. New devices sometimes need a short time to check in.
If the status still does not update, check the basics:
The gateway is registered to the same account where you added the sensor.
The gateway has a working internet connection.
The antenna is attached correctly if the gateway requires one.
The gateway is not blocked by network rules that prevent outbound communication.
For Ethernet gateways, try a known-good cable or port if the gateway does not appear online. For gateways that use another connection type, make sure the service or signal needed for that model is available.
Confirm the sensor can reach the gateway
After the gateway checks in, confirm that the sensor is communicating. A sensor may fail validation if it is too far from the gateway, blocked by dense materials, or not powered correctly.
Place the sensor near the gateway during setup if you are troubleshooting. This removes distance and building materials from the test. Once it validates, move it to the intended location and check the signal again.
Common signal problems include:
Too much distance between the sensor and gateway.
Metal enclosures, concrete walls, or large equipment between devices.
A gateway placed too low or hidden behind other objects.
A sensor installed before it has completed its first check-in.
A battery tab or protective strip left in place if the device uses one.
If the sensor does not report right away, trigger the condition it measures if that is safe and practical. For example, a door sensor may report after the door opens or closes. A temperature sensor may need time before the first reading appears.
Check signal strength before final placement
A sensor that reports once is not always in the best location. Before final installation, check the signal strength in iMonnit.
A strong signal gives the device a better chance of communicating reliably over time. A weak signal may work during setup but fail later when conditions change.
If the signal is weak, try one change at a time:
Move the gateway higher.
Reduce the distance between the sensor and gateway.
Avoid placing the sensor inside metal cabinets unless the model is designed for it.
Keep the gateway antenna clear of obstructions.
Test the sensor in its final position before mounting it permanently.
Small placement changes can make a large difference. Moving a gateway a few feet or rotating an antenna may improve communication enough to pass validation.
Troubleshooting common add device issues
Most add device issues come from one of four areas: account access, label entry, gateway connection, or signal strength.
The Device ID or Security Code is not accepted
Recheck the label and enter the information again. Make sure you are using the Device ID from the device you are adding, not from another sensor in the same box.
For the Security Code, use uppercase letters. If a character is hard to read, compare it with the barcode label and any printed device paperwork that came with the unit.
If scanning the QR code fails, clean the label gently, improve the lighting, and hold the phone steady. If it still does not scan, use manual entry.
The sensor is added but no data appears
Check whether the gateway is online. If the gateway has not communicated with iMonnit, the sensor readings cannot reach the account.
Next, check the sensor’s power. If it uses batteries, confirm they are installed correctly and that any protective tab has been removed. If it is externally powered, confirm the power source is active.
Then wait for the next Heartbeat Interval or trigger a reading if the sensor type supports that behavior.
The gateway is online but the sensor signal is weak
Move the sensor closer to the gateway and test again. If the signal improves, the issue is likely placement.
Keep the final installation path in mind. A clear test beside the gateway does not guarantee the sensor will work through multiple walls, metal racks, or equipment. Test from the final location before you mount the device permanently.
The wrong use case was selected
You can usually adjust sensor settings after adding the device. Open the sensor settings, choose a better preset or create custom settings, then save your changes.
After changing settings, review the Heartbeat Interval and Aware State values. Make sure they still match how you want the sensor to behave.
What a successful setup looks like
A successful iMonnit device setup has three clear signs:
The device appears in the correct account.
The setup or use case has been saved.
The validation checklist shows that the gateway and sensor are communicating properly.
Once those pieces are in place, monitor the first few readings to make sure the values make sense. For a temperature sensor, compare the reading to the expected room or equipment temperature. For a contact sensor, open and close the monitored door or panel and confirm that the state changes.
Adding one device also gives you a repeatable process for the next one. Log in, add the device, scan or enter the ID and Security Code, choose the use case, save the setup, then validate communication. Work through those steps carefully, and your iMonnit system will be ready to monitor the conditions that matter.
Comments