Skip to main content

Lorawan

  • Requirements to connect a LoRaWAN device to the Box/HUB
    In order to connect your Lorawan device to our Box/HUB you'll need to have in mind these informations:
     
    1. If your Lorawan device is not in our compatibility checker, it means we don't have the associated codec.
    •   You will have access to the Raw payload of your device, but it won't be decoded by our services
    •   Feel free to ask us to add the codec you need (the sooner the best)
    2. You will have to get some information (see below), these parameters will be sent to you by the manufacturer/supplier and they are mandatory for the process.
     
    3. The lorawan network works with what is called a JOIN process, during this process the sensor will send a JOIN request and the BOX/HUB will accept it.
                --> You will need to configure the Box/Hub BEFORE doing the JOIN process, otherwise the sensor will send the JOIN but nothing will happen.
     
    Here is the information you will need to set up your loRaWAN device in our Box/Hub:
     
     
    • DevEUI / AppEUI / Application Key are the parameters given by your supplier.
    • CodecID : will be the codec associated with your device.

    In Advanced tab you will be able to configure the Class type of your device. Class A is set by default

    mceclip0.png

     

    See more
  • LoRaWAN frequency plans supported

    Asia - AS_923_1

    Asia - AS_923_2
    All SF5 to SF12
     
    Uplink:
    923.20 MHz
    923.40 MHz
     -
    923.60 MHz
    923.80 MHz
    924.00 MHz
    924.20 MHz
    924.40 MHz
    924.60 MHz

    Downlink:
    923.2 MHz
    All SF5 to SF12
     
    Uplink:
    921.40 MHz
    921.60 MHz
     -
    921.80 MHz
    922.00 MHz
    922.20 MHz
    922.40 MHz
    922.60 MHz
    922.80 MHz

    Downlink:
    921.4 MHz

    Asia - AS_923_3

    Australia - AU_915_928
    All SF5 to SF12
     
    Uplink:
    916.60 MHz
    916.80 MHz
     -
    917.00 MHz
    917.20 MHz
    917.40 MHz
    917.60 MHz
    917.80 MHz
    918.00 MHz

    Downlink:
    916.6 MHz

     
    All SF5 to SF12
     
    Uplink :
    916.8 MHz
    917.0 MHz
    917.2 MHz
    917.4 MHz
    917.6 MHz
    917.8 MHz
    918.0 MHz
    918.2 MHz

    Downlink:
    923.3 MHz

    Europe - EU_433

    Europe - EU_863_870
    All SF5 to SF12
     
    Uplink :
    433.175 MHz
    433.375 MHz
    433.575 MHz
     
    Downlink :
    434.665 MHz
    All SF5 to SF12
     
    Uplink:
    868.10 MHz
    868.30 MHz
    868.50 MHz
    -
    867.10 MHz
    867.30 MHz
    867.50 MHz
    867.70 MHz
    867.90 MHz
     
    Downlink:
    869.525 MHz

    India - IN_865_870

    US - US_902_928
    All SF5 to SF12
     
    Uplink:
    865.0625 MHz
    865.4025 MHz
    865.985 MHz

    Downlink:
    866.550 MHz
    All SF5 to SF12
     
    Uplink (sub-band 2):
    903.90 MHz
    904.10 MHz
    904.30 MHz
    904.50 MHz
    904.70 MHz
    904.90 MHz
    905.10 MHz
    905.30 MHz
     
    Downlink:
    923.3 MHz
    See more
  • LoRaWAN codec requirements
    Wattsense can add for free any LoRaWAN sensor provided that they meet the requirements below:
    1. The sensor sends the entire payload of data in one go. Wattsense does not handle fragmented packets sent in several transmissions.
    2. The sensor can be used by anyone. It is not tied to a specific environment.
    3. Wattsense does not require a complex user interface to configure or interpret the sensor's data
    4. The codec is not customized. Which it means it can be used for other users
    5. The manufacturer is capable to provide the following should you ask or when asked by Wattsense:
      • Exact reference of the sensor
      • Technical documentation describing the structure of the payload
      • (optional) Javascript library of the codec. This will reduce considerably the development time
      • (optional) A contact from a reseller
    See more
  • Checklist to debug your Lorawan Network
    Here is the important checklist to follow if you have trouble to connect Lorawan equipment:
     

    • Verify AppEUI, DevEUI, and AppKey

    The same AppEUI, DevEUI and AppKey stored in the end device should be provisioned onto the console.
    In case of mistaken values, the activation of the device stays inoperative.

    mceclip3.png

    • Repeat JOIN process

    When an End Device communicates with the network server to perform the activation process, this process is called Join Procedure.
    It may happen that something went wrong during the join-request message or join-accept message transmission to activate the end device.
    If you see X in "Last Value" fields of your device in the console, recommence the join procedure.
    Join process is specific to each Lorawan end device supplier. This information is available in technical documentation.
     

    • Appropriate Class Type

    All Lorawan end-devices support Class A, although Class C could be included on your device.
    If your device use a different class than Class A, you may verify the class configured in your device, in Advanced Tab:
    mceclip2.png
     

    • Check Codec used to communicate

    Codec is use to decode the payload from the sensor. You may have the incorrect codec to decode the uplinks/downlinks from your device.
    Please corroborate the codecID selected on the console with the Codec of your end-device.
    mceclip4.png

    • Verify Frequency 

    Lorawan uses a proprietary spread spectrum modulation, so the frequency must match with your device. The correct frequency allows to transmit the data correctly in the network:
    mceclip5.png
     
    In case that you continue having problems to configured your Lorawan end-device, contact us: Wattsense Support
     
     
    See more