CropWatch Knowledge Base
EN English

Adding a sensor

New sensors are added from the location they belong to. A guided screen in three steps reads the sensor's QR code or DevEUI, checks it, registers it on the LoRaWAN network and assigns one licence. This guide covers every step and every message on the way, and what to do when a new sensor does not connect.

On this page

Before you start

Have these to hand before you begin. Nothing is saved until you press Register device on the last step, so you can stop at any point and start again later.

  • The sensor and its label: the label on the sensor or on its box carries the DevEUI, a 16-character code that identifies the sensor, and usually a QR code that contains it.
  • Its join keys, for some sensors: a sensor that CropWatch has not prepared for your account also needs a JoinEUI (16 characters) and an AppKey (32 characters). They are on the label or on an info card in the box. The screen tells you whether they are needed.
  • A free licence: every sensor uses one licence from your own account. The top of the screen shows “Licenses available” with the number you have free.
  • Manager access or higher on the location: see Who can add sensors.
  • A gateway in range: readings travel from the sensor to CropWatch through a gateway. Check that one is powered on and online, close enough to where the sensor will go. Setting one up is covered in Installing an indoor gateway.

The sensor is registered in the location's network region, shown under the page title, for example “Network region Asia-Pacific (AS923)”. The region cannot be changed in the app. If it does not match the country your location is in, contact support before you add sensors there.

Who can add sensors

Adding a sensor goes by your level on the location. The location's owner, Admins and Managers can add sensors; Users and Viewers cannot. What each level allows is set out in The six levels, and raising someone's level in Changing someone's level.

The Add Device button appears for everyone who can open the location, whatever their level. Someone below Manager can open the screen, but as soon as they enter a DevEUI a red box says “You can't add devices to this location” and “Adding devices needs Manager access or higher. Ask the location owner to change your access.” Continue stays grey.

Two things follow from who adds the sensor:

  • You become its owner: the person who adds a sensor owns it.
  • The licence is yours: it comes from the account of the person adding the sensor, not from the location's owner. A Manager adding sensors to someone else's location needs free licences of their own.

Opening Add a device

The Add a device screen for Greenhouse 1: the title with the network region Asia-Pacific (AS923), “Licenses available: 3” at the top right, the bar with the three steps, the Identify your device form, and the two side panels.

The Add a device screen, opened from Greenhouse 1.

The Add a device screen, opened from Greenhouse 1.
  1. Open Locations in the menu and choose the location the sensor will belong to.
  2. Press Add Device in the row of buttons at the top of the location page, after Refresh.
  3. The Add a device screen opens. Under its title you see the location's name and network region, and beside it a count such as “Licenses available: 3”.

Below that, a bar shows the three steps: Identify device, Name and place, and Review and register. Each step's number turns into a tick once it is done. Two panels beside the form (below it on a phone) explain “What happens when you register” and “Where to find the DevEUI”.

Back at the top of the screen, or Cancel on the first step, takes you back to the location without saving anything. The location page itself is described in The location page.

Step 1: identifying the sensor

Step 1 after the check: the DevEUI DE5A00000000A001 is entered, the Device model box shows the CropWatch air temperature and humidity sensor with “Recognized from the DevEUI”, and a green tick says the network keys are on file.

Once the DevEUI is complete, the check runs and the model and keys appear.

Once the DevEUI is complete, the check runs and the model and keys appear.

The first step, headed “Identify your device”, needs the sensor's DevEUI. There are two ways to give it:

  • Scan QR code: the large button on the left opens your camera and reads the code on the sensor or its box. On a phone this is the quickest way, and it also fills in the join keys when the code carries them.
  • The DevEUI box: type or paste the code printed on the label.

Either way, the moment the box holds 16 valid characters, CropWatch checks the sensor by itself; there is no button to press. The Device model box, and the key boxes if they are needed, appear only after that check.

Scanning the QR code

  1. Press Scan QR code. A window titled “Scan the device QR code” opens. The first time, your browser asks whether CropWatch may use the camera: allow it.
  2. Hold the phone so the QR code sits inside the square on the screen. On a phone the back camera is used. The line under the picture reads “Point the camera at the QR code on the device or its box.”
  3. When the code is read, the window closes by itself and the DevEUI box is filled in. The check starts straight away.

The scanner reads CropWatch labels and the QR codes most LoRaWAN sensor makers print. It takes the DevEUI from the code, and also the JoinEUI and AppKey when the code contains them. A CropWatch label names the sensor's model as well, and the scanner chooses that model for you.

Some makers' codes hold more than one 16-character number. After scanning, compare the DevEUI box with the DevEUI printed on the label. If they differ, correct the box by hand.

Two more buttons sit at the bottom of the window:

  • Use a photo: reads one still picture instead of the live view. On a phone it opens the camera; on a computer it lets you choose a picture file. A still photo is sharper, so try it when the live view will not pick up a small or worn code.
  • Type the DevEUI instead: closes the window so you can type the code.

When the camera will not scan

The Scan the device QR code window with the message “No camera is available here. Type the DevEUI instead.” and the buttons Use a photo and Type the DevEUI instead.

When no camera can be used, the window says so and offers the other two ways.

When no camera can be used, the window says so and offers the other two ways.

When something goes wrong, the window says what, in place of the picture or under it:

  • “Camera access was blocked. Allow camera access in your browser settings, or type the DevEUI instead.”: the camera has been refused for CropWatch. Open your browser's settings for the CropWatch site, allow the camera, then close the window and press Scan QR code again. Each time the window opens, it tries the camera afresh.
  • “No camera is available here. Type the DevEUI instead.”: the browser found no camera it could use. This also happens when another app is using the camera. Close that app and try again, use a photo, or type the DevEUI.
  • “No QR code found in that photo. Take it closer, with the code sharp and filling most of the picture.”: the photo was read but held no code. Take another one, closer, in focus and in good light.
  • “That QR code doesn't contain a DevEUI. It reads: …”: a code was read, but it is not the sensor's code. It is often a link to the maker's website or a product number, and the window shows what it says. Look for a second code on the sensor, the box or the info card, or type the DevEUI.

When the live view is blocked, Use a photo is the quickest way round it: it asks your phone's camera for a single picture instead of showing the camera inside the page.

Typing the DevEUI

A DevEUI is 16 characters long and uses only the numbers 0 to 9 and the letters A to F. On most labels it sits next to “DevEUI”, “EUI” or “Device EUI”.

  • Spacing does not matter: spaces, colons and dashes are ignored, so 00 13 7A 10 00 04 41 DF, 00:13:7A:10:00:04:41:DF and 00137A10000441DF are the same sensor.
  • Capitals do not matter: small letters are read as capitals.
  • Pasting works: copy the code from an email or a spreadsheet and paste it into the box.

The box tells you what is wrong as you type:

  • A character is not accepted: the box names it, for example “"O" isn't valid”. The usual cause is the letter O typed for the number 0, or the letter I or l for the number 1.
  • “17 of 16 characters. Check the label again.”: there are too many characters. This shows as soon as you type the extra one.
  • Too few characters: nothing is shown and no check runs; the box is waiting for the 16th character. A DevEUI is eight pairs, so count the pairs against the label.

What the check tells you

Step 1 with a DevEUI typed in small letters with spaces, and a red box: “This device is registered to another account”, with a Contact support button. Continue is grey.

A DevEUI held by another account stops the setup at step 1.

A DevEUI held by another account stops the setup at step 1.

While CropWatch checks the sensor, “Checking this device…” shows with a spinner. Then one of these appears:

  • A Device model box: the sensor can be added. Confirm the model, enter the keys if asked, and press Continue.
  • “You've already added this device”: a sensor with this DevEUI is already in CropWatch and you can see it. The message gives its name and location. Press Open followed by its name to go to it, and change its name or location in its settings instead of adding it again. A sensor someone else added and shared with you shows this message too.
  • “This device is registered to another account”: another CropWatch account has this DevEUI, or CropWatch supplied the sensor to a different customer. Check the DevEUI first. If it is right, ask the previous owner to remove the sensor from their account, or press Contact support and give your order number.
  • “You can't add devices to this location”: your level on this location is below Manager. Ask the location's owner or an Admin to raise it.
  • “We couldn't check this DevEUI. Check your connection and try again.”: the check did not reach CropWatch. Check your phone's signal or Wi-Fi and press Try again.
  • “We couldn't check this DevEUI because of a problem on our side. …”: the fault is at CropWatch. Wait a moment and press Try again, or contact support with the reference number shown.
  • “Too many attempts in a short time. Wait a while, then try again.”: your account has reached its hourly limit of checks. Wait up to an hour.

Every Contact support button opens a new email to CropWatch support with “Device setup”, any reference number and the DevEUI already in the subject line.

Choosing the device model

Once the check passes, a “Device model” box appears. The model decides how CropWatch registers the sensor on the network and how it reads the sensor's data, so it must match the sensor in your hand.

The app often picks the model for you. The line under the box says where the choice came from:

  • “Read from the CropWatch label.”: the QR code on a CropWatch label named the model.
  • “Recognized from the DevEUI. Change it if this isn't your model.”: if CropWatch supplied the sensor, this is the model on record. Otherwise it is a guess based on other sensors whose DevEUI starts the same way, so check it.
  • “The label says device type …, which this app doesn't know yet. Choose the model.”: the CropWatch label names a model code the app does not recognise yet. Choose the model yourself.
  • No line: choose the model yourself.

Models that suit this sensor are listed first. Models that cannot be registered in this location's network region are greyed out and cannot be chosen. Two messages can appear under the box:

  • “Choose the device model.”: you pressed Continue without choosing one.
  • “This model can't be set up in this location's network region yet. Contact support to have it added.”: the model has no network settings for this region yet, so it cannot be registered here until support adds them.

Choose carefully. A sensor's settings page has no model box, so a wrong model can only be corrected by support. If you are not sure which model you have, ask support before you register.

Network keys

Step 1 for a sensor whose keys CropWatch does not hold: the model was recognised from the DevEUI, and empty JoinEUI (AppEUI) and AppKey boxes ask for the join keys.

When CropWatch does not hold the keys, two boxes ask for them.

When CropWatch does not hold the keys, two boxes ask for them.

Under the model, the screen tells you whether the sensor's join keys are needed. These are the codes the sensor uses to join the network.

  • “Network keys are on file.”: followed by “CropWatch provisioned this device, so you don't need to enter any keys.” There is nothing to type.
  • Two boxes, “JoinEUI (AppEUI)” and “AppKey”: CropWatch does not hold this sensor's keys. Copy them from the label or from the info card in the box. The JoinEUI is 16 characters and the AppKey 32; spaces, colons and dashes are ignored, as in the DevEUI box. Scanning a QR code that carries the keys fills both boxes. As the line under the AppKey says, it is “Sent securely to the network server and never shown again.”

Watch for this warning:

  • “The label doesn't show the AppKey.”: some CropWatch labels print the AppKey as a row of X's to keep it private, and CropWatch does not have the key on record for this sensor yet. Without the real AppKey the sensor cannot join the network. Type the AppKey from the info card in the box, or press Contact support and CropWatch will add the key for you.

If the network will not accept the keys after you press Register device, the screen brings you back to this step with the key boxes open and a red message:

  • “That AppKey doesn't match this device's network registration. …”: the sensor is already registered on the network with a different AppKey. Check every character; the AppKey is the longest code on the label.
  • “This device is already registered on the network. Enter its JoinEUI and AppKey to confirm it's yours.”: type both keys. Once the AppKey matches, CropWatch takes over the existing registration.
  • “Check the JoinEUI and AppKey and try again.”: the keys were missing or not in the right form.

Correct the keys, press Continue through the next two steps (your name, position and licence are still filled in), and press Register device again.

Step 2: name and place

Step 2, Name and place it: the device name “GH1 Climate, east end”, the group Climate picked from the suggestions Climate, Irrigation and Soil, today's date as Installed on, the position panel with the location's coordinates, and “Uses 1 of your 3 available licenses.” with Change.

Step 2 with a name, a suggested group and today's install date.

Step 2 with a name, a suggested group and today's install date.

The second step, headed “Name and place it”, sets what the sensor is called and where it sits. Only the name is required.

  • Device name: what your team sees on the dashboard and in alerts. Pick something you would recognise standing in the field, such as “Greenhouse 2, north end”. Up to 120 characters. Pressing Continue with the box empty shows “Give the device a name.” You can rename the sensor later; see Device Name.
  • Group (optional): a free label. Groups already used at this location appear under the box as buttons, up to eight of them; press one to use it, so the spelling matches the other sensors. What groups do is explained in Group.
  • Installed on (optional): the day the sensor went in. Days after today cannot be chosen. The date appears on the review step; the app does not display it anywhere after setup.

Below these, a panel shows where the sensor will appear on the map:

  • “Position: same as location”: followed by the location's coordinates. The sensor gets no position of its own. Leave it like this if the sensor is at the location.
  • “This location has no coordinates yet. You can set the device's own position.”: the location itself has no map position yet.
  • Set precise position: opens Latitude and Longitude boxes, filled with the location's coordinates to start with. Type the sensor's own position in decimal degrees, such as 35.6812 and 139.7671; a comma works as the decimal mark too. A sensor with its own position gets its own pin on the location's map, which is shown only when the location itself has a position.
  • Use the location's position: closes the boxes and goes back to the location's position.

“Enter a latitude between -90 and 90, for example 35.6812.”, or the same message for longitude, means the number is out of range or not a plain decimal. Degrees, minutes and seconds (35°40′52″) are not accepted; convert them to decimal first. Back at the bottom returns to step 1 with everything you typed kept.

Choosing the licence

The bottom of step 2 shows the licence the sensor will use:

  • “Uses 1 of your 3 available licenses.”: CropWatch has picked your first free licence. There is nothing to do.
  • Change: appears when you have more than one free licence. It opens a “License” list of your free licences by number, such as “License #4”. Which one you pick makes no difference to the sensor; use it if you keep track of licences by number.
  • “All your licenses are in use”: with “Each device needs one license. Add licenses in Billing, then come back to finish.” Continue stays grey. Press Add licenses to open the Billing & Subscriptions page. If your account is invoiced directly by CropWatch, that page says so; ask CropWatch to add licences.

Pressing Add licenses leaves the setup screen, and what you typed is not kept. Buying licences first and adding the sensor afterwards saves typing everything twice.

Step 3: review and register

Step 3, Review and register: Device, Model, DevEUI, Network keys “On file (provisioned by CropWatch)”, Location Greenhouse 1 with the group, Installed on and License, with Edit links and the Register device button.

Everything that will be saved, on one screen.

Everything that will be saved, on one screen.

The last step, “Review and register”, lists what will be saved: Device, Model, DevEUI, Network keys, Location (followed by the group and any precise position), Installed on if you set a date, and License.

Network keys reads either “On file (provisioned by CropWatch)” or “JoinEUI and AppKey entered”. Edit beside Device, Model or Location takes you back to the step where that is set.

Compare the DevEUI with the label one last time, then press Register device.

While it registers

“Registering GH1 Climate, east end” with a list: the DevEUI check is ticked, Registering on the network has a spinner, and Added to Greenhouse 1 and Assigned a license are still waiting.

The list while CropWatch registers the sensor.

The list while CropWatch registers the sensor.

The heading changes to “Registering” followed by the sensor's name, with “This usually takes a few seconds. Please keep this page open.” A list shows the work:

  1. Checked the DevEUI is available: ticked at once; this was done in step 1.
  2. Registering on the network: CropWatch registers the sensor on The Things Industries, the LoRaWAN network server CropWatch uses, in the location's network region. That registration is what lets the network accept the sensor when it tries to join, and pass its readings on to CropWatch. How readings travel is explained in What is LoRaWAN?.
  3. Added to (location name): the sensor is saved in the location.
  4. Assigned a license: one of your free licences is given to the sensor.

The list fills in once the work is finished. The side panel says “If any step fails, nothing is saved and your license isn't used.”, and that holds: if registering on the network or assigning the licence fails, CropWatch removes what it had started and your licence stays free.

When the sensor is set up

A large tick and “GH1 Climate, east end is set up”, the instruction to power the device on, four ticked lines including “Registered on The Things Industries, Asia-Pacific (AS923)”, and the buttons Add another device and Open device.

The sensor is registered, saved and has its licence.

The sensor is registered, saved and has its licence.

A large tick and “(name) is set up” mean everything worked. The list now says what happened on the network:

  • “Registered on The Things Industries, Asia-Pacific (AS923)”: a new registration was made, in your location's network region (Asia-Pacific in this example).
  • “Linked the existing network registration”: the sensor was already on the network, and CropWatch took over that registration after confirming the sensor is yours.
  • “Already registered on the network”, “Already in (location name)” and “License already assigned”: this sensor had already been set up under the same name at the same location, for example when the connection dropped after an earlier press of Register device. Nothing was added twice and no second licence was used.

Under the list: “Power the device on now. Most devices join the network and send their first reading within 5 minutes.” Then:

  1. Switch the sensor on or fit its battery, as described in Sensor installation and maintenance.
  2. Press Open device to go to the new sensor's page, or Add another device to start again for the next sensor. Add another device keeps the group and install date you used and picks your next free licence. The licence count at the top drops by one.
  3. Until its first reading arrives, the sensor is listed as “Never reported” on the location page.

Messages after Register device

The review step with a red box above the summary: “We couldn't reach the network server”, its explanation, the buttons Try again and Contact support, and “Reference CW-4F7A2C”.

A message after Register device, with the reference to quote to support.

A message after Register device, with the reference to quote to support.

If the work stops, you stay on the review step and a box above the summary says why. Most boxes end with a short reference such as “Reference CW-1A2B3C”: quote it to support. Key problems take you back to step 1 instead (see Network keys).

What each message means and what to press
MessageWhat it meansWhat to do
“This device is registered to another account”Another CropWatch account has this DevEUI, or CropWatch supplied the sensor to a different customer.Press Check the DevEUI and compare it with the label. If it is right, press Contact support.
“You've already added this device”You already have this sensor, under another name or at another location.Press Open followed by its name, and change it in its settings instead.
“This device is already being set up”Another window, or another person, started registering this sensor moments ago.Press Open location and look for the sensor there in a minute.
“That license is no longer available”The licence you chose was used for another sensor in the meantime, perhaps in another window.Press Change to reload your free licences and pick one, or Add licenses.
“This model isn't available here yet”The model has no network settings for this location's region.Press Choose another model if you picked the wrong one; otherwise press Contact support.
“This device is registered as a different model”The sensor is already on the network as another model.Press Choose another model and pick the one that matches the sensor, or press Contact support.
“This device is registered on another network”The DevEUI is registered elsewhere on the network, outside CropWatch. The seller or previous owner may need to release it.Press Contact support.
“We couldn't confirm this device automatically”The sensor is already on CropWatch's network, but its keys cannot be checked automatically.Press Contact support and quote the reference. Support adds the sensor for you.
“We couldn't reach the network server”The Things Industries did not answer. Nothing was saved and no licence was used.Wait a minute and press Try again. Everything you entered is kept.
“Please wait a moment”Your account has reached its hourly limit of registrations.Wait up to an hour, then press Register device again.
“You can't add devices to this location”Your level on the location is below Manager.Ask the location's owner or an Admin to raise it.
“Setup couldn't be completed”Something went wrong on CropWatch's side. Nothing was saved and no licence was used.Press Try again, or press Contact support and quote the reference.

When the first reading does not arrive

Most sensors send a first reading within 5 minutes of being switched on. If yours stays “Never reported”, work down this list:

  1. Power: check the battery is fitted the right way round and the sensor is on. Taking the battery out and putting it back makes the sensor try to join the network again.
  2. Gateway: check that a gateway near the sensor is powered on and online (the Gateways pages are described in Gateways in the app). Move the sensor close to the gateway for a while. If it reports there, its spot is too far away or blocked; see RSSI and SNR for reading signal strength.
  3. Model: a wrong model registers the sensor with the wrong network settings, and only support can change it. If you were unsure of the model, contact support.
  4. Keys: if you typed the JoinEUI and AppKey, one wrong character stops the sensor from joining, and the app cannot tell when you register. Contact support with the DevEUI.

If there is still no reading 5 hours after installation, contact CropWatch support with the DevEUI and where the sensor is installed, as Connecting to the network explains. The quick checks in Quick checks before contacting support go into more detail.

Quick answers

  • I cannot find Add Device: it is on a location's page, not on the dashboard. Open Locations in the menu, choose the location, and look along the buttons at the top.
  • Continue on the first step stays grey: the check has not finished, or it found a problem. Read the box under the DevEUI. With fewer than 16 characters, no check runs.
  • Continue on the second step stays grey: you have no free licences. See Choosing the licence.
  • It says all my licences are in use, but I have free ones: only licences on your own account are offered, so another person's free licences never appear. If your own are free, reload the page: when CropWatch cannot reach the billing service, the screen shows no free licences rather than letting a sensor through unpaid.
  • “You've already added this device” for a sensor I never added: someone added it and shared it with you, so it is already in CropWatch. Press Open followed by its name to find it.
  • “This device is registered to another account”: the sensor is still on its previous owner's account, or CropWatch supplied it to another customer. Ask the previous owner to remove it, or contact support with your order number.
  • The camera opens but never reads the code: hold the code inside the square, steady, closer and in good light. If it still will not read, press Use a photo.
  • “Please wait a moment” or “Too many attempts in a short time”: each account can check 150 DevEUIs and register 60 sensors an hour. Wait up to an hour.
  • I chose the wrong model: the sensor's settings have no model box. Contact support with the DevEUI.
  • I gave it the wrong name or group: change both on the sensor's settings page; see Sensor settings.
  • I added it to the wrong location: move it from the sensor's settings, but read Location, and what moving a sensor really does first: moving changes who can see it.
  • Adding several sensors in a row: after each one, press Add another device. The group and install date carry over to the next sensor.
  • I closed the page while it was registering: open the location. If the sensor is listed, it finished. If not, add it again. Using the same name and location is safe either way: if the earlier setup did finish, CropWatch says so and uses no second licence, and if it is still running you see “This device is already being set up”.