Description

When working as embedded network server, Linovision LoRaWAN gateways support both sending data packets to third party MQTT/HTTP/HTTPS server or receiving the downlink commands to transfer to LoRaWAN end devices.

Requirement

• Linovision LoRaWAN Gateway: IOT-G56, IOT-G63 V1, IOT-G65, IOT-G67, IOT-G8x (Firmware version 80.0.0.64 or later)
• MQTT Server/Broker
• MQTT Client tool: take MQTT Explorer as example

Configuration

Step1. Connect gateway to MQTT broker.

Refer article How to Connect LoRaWAN Gateway to MQTT Broker？to connect gateway to MQTT broker and ensure the broker and MQTT client can receive uplinks from devices.

Step2. Send Downlink Command from Gateway

Set the gateway to send downlink commands to device directly to check if the device can receive the downlink commands and take actions.

Device EUI: the device EUI to send downlink commands

Type: downlink command type. For Linovision devices, please select hex type.

Payload: downlink command content (get from device manufacturer). For Linovision devices, please refer to downlink command contents on corresponding user guides

Port: application port of device. It is 85 by default for Linovision devices.

Confirmed: after enabled, the device will send confirmed packet back to gateway if it receives the command. If not receive, the gateway will resend the downlink command 3 times at most.

Note: for class A type devices, the gateway will add the command to queue and send it when the class A device send uplinks.

Step3. Publish Topic on MQTT Explorer to send downlink data to device. 

Set a Downlink Data topic. If you need to send MQTT downlink to specific device, please add “$deveui” on the topic.

Example: /linovision/downlink/$deveui

Publish Topic Format :

/linovision/downlink/[devEUI]

Example :

From the gateway, we can get the device EUI about the device we want to control:

So we can publish a topic on the MQTT Explorer like below:

Topic: /linovision/downlink/24e124126a148401

Format: json

Content: 

send as below format and replace the data content as downlink command

{"confirmed": true, "fport": 85, "data": "CQEA/w=="}

JavaScript

After click Publish, we can go to Network Server > Packets to check. If the gateway have subscribe corresponding downlink topic data successfully, there will be at least one grayed message packet record.

Linovision Device Command Examples

The MQTT downlink command format is fixed as below:

{
"confirmed": true,       //Set as true or false
"fport": 85,            //application port of device
"data": "BwAA/w=="    //base64 format downlink command
}

----END---

Description

When working as embedded network server, Linovision LoRaWAN gateways support sending data packets to third party MQTT/HTTP/HTTPS server. We can create a new application on gateway, which can define the method of decoding the data sent from LoRaWAN end-device and choosing MQTT data transport protocol to send data to MQTT server.

Requirement

•  LoRaWAN Gateway: IOT-G8x (Firmware version 80.0.0.64 or later), IOT-G65, IOT-G67, IOT-G56, IOT-G63 V1
• MQTT Server/Broker
• MQTT client tool: take MQTT Explorer as example

Configuration

Step1. Enable the gateway built-in network server.

Go to Packet Forwarder > General to enable the localhost server address.

Enable the Network server on Network Server > General page.

Step2. Add an Application

Go to Network Server>Applications to add a new application, click save.

Name: user-defined, arbitrary value

Description: user-defined, arbitrary value

Step3. Connect gateway to MQTT broker.

Go to Network Server > Applications to add a “data transmission” for the application. One application can add only one MQTT integration.

Fill in the MQTT broker information and create topic to store different data type, click save.

Broker Address: IP address/domain of MQTT broker

Broker Port: communication port of MQTT broker

Client ID: user-defined, a unique ID identity of the client to the server.

User Credentials and TLS should be enabled and configured as required.

Note: if MQTT broker is HiveMQ, please do enable TLS and set the option as CA signed server certificate.

After MQTT configuration complete, you can check connection status here:

Step4. Add LoRaWAN nodes to the gateway.

Go to Network Server>Profiles to add a new profile, then click save. You can also use pre-defined profiles.

Name: user-defined, arbitrary value

Max TXPower: default value

Other parameters can be checked from LoRaWAN nodes user guide or you can keep all settings by default.

Go to Network Server>Device to add a new device, click Save&Apply.

Device Name: user-defined, arbitrary value

Description: user-defined, arbitrary value

Device-Profile: choose one of corresponding profiles added before.

Application: choose one of corresponding applications added before.

Other parameters can be confirmed with the LoRaWAN node manufacturers.

When the status shows as below, that’s mean above steps are done correctly.

Step5. Add uplink data topic.

Customize the uplink data to publish to MQTT broker and save the settings. If you add “$deveui” on your topic, you can replace it as real device EUI when subscribing topics. 

Example: /linovision/uplink/$deveui

Step6. Subscribe topic from MQTT client to get uplinks.

MQTT explorer is a comprehensive MQTT client and it can be replaced to other kinds of MQTT client tools(MQTT.fx, MQTT Box, etc.)

Open the MQTT Explorer, and fill in related MQTT server information in the popup window.

Name: user-defined

Protocol: mqtt://

Host: MQTT broker address

Port: broker port

User name/Password: if there is user credentials, please fill in it. If not, keep them blank.

Click ADVANCED,copy the Uplink data topic on the gateway, and paste it on the MQTT explorer, click +ADD.

Keep MQTT client ID by default,then click BACK and click CONNECT.

After while, the data will be forwarded to MQTT broker and the MQTT Exploerer can receive the data from MQTT server.

The uplink format is fixed as json and the content is as below.

{
  "applicationID": 1,                   // application ID
  "applicationName": "cloud",           // application name
  "deviceName": "24e1641092176759",     // device name
  "devEUI": "24e1641092176759",         // device EUI
  "time": "2020-0327T12:39:05.547336Z", // uplink receive time
  "rxInfo": [                           // lorawan gateway information related to lora
    {
      "mac": "24e124fffef021be",        // ID of the receiving gateway
      "rssi": -57,                      // signal strength (dBm)
      "loRaSNR": 10,                    // signal to noise ratio
      "name": "local_gateway",          // name of the receiving gateway
      "latitude": 0,                    // latitude of the receiving gateway
      "longitude": 0,                   // longitude of the receiving gateway
      "altitude": 0                     // altitude of the receiving gateway
    }
  ],
  "txInfo": {                           // lorawan node tx info
    "frequency": 868300000,             // frequency used for transmission
    "dataRate": {
      "modulation": "LORA",             // LORA module
      "bandwidth": 125,                 // bandwidth used for transmission
      "spreadFactor": 7                 // spreadFactor used for transmission
    },
    "adr": false,                       // device ADR status
    "codeRate": "4/5"                   // code rate
  },
  "fCnt": 0,                            // frame counter
  "fPort": 85,                          // application port
  "data": "AWcAAAJoAA=="                // base64 encoded payload (decrypted)
}

FAQ

Q1.How to send decoded or customize uplink content to MQTT broker?

A1:  Yes, this needs to use Payload Codec feature on the gateway. Reference articles:

IOT-G56/G65/G67: How to Use Payload Codec on Linovision Gateway

IOT-G63 V1/G8x: How to Use Payload Codec on Linovision Gateway (Old)

Q2.What’s the troubleshooting when the status of MQTT server connection is “Disconnected”.

A2: 

1) Go to Maintenance > Tools >Ping , check if the gateway can ping to the broker address successfully.

2) Check if your MQTT client tool can connect to MQTT broker well, then follow the settings of MQTT client tool to configure the gateway.
3) Check if the gateway MQTT client ID is conflict with other MQTT clients.
4) Check if CPU load is too high, and if there is little available RAM and eMMC.
5) Change the log severity to Debug and replicate the disconnection problem, then download all log files and send them to support@linovision.com.

Q3.Why the connection status shows “connected” but MQTT client does not receive any data?
A3:
1)Ensure the devices has been added to gateway and go to Network Server > Packets to check if there are uplink packets from devices regularly.
2) Ensure the devices has been added to the correct Application.
3) Ensure the gateway firmware is upgraded to latest version. 
4) Change the log severity to Debug and replicate the disconnection problem, then download all log files and send them to support@linovision.com.

To enhance comprehension of the PoE network system, it is essential to become acquainted with the PoE devices, as the initially published IEEE802.3af standard categorized Power over Ethernet (PoE) technology into two primary types of power devices: power sourcing equipment (PSE), which supplies power over the Ethernet cable, and powered devices (PD), which receive the power. Presented below is an introduction to power sourcing equipment and a selection of frequently asked questions.

• PoE PSE (Power Sourcing Equipment): PoE PSE denotes the equipment supplying power to PoE PDs. It can take the form of a PoE switch or a PoE injector. The PoE PSE injects power into the Ethernet cable, alongside data signals, enabling connected PoE PDs to receive both power and data through a single cable. It serves as the power source for PoE devices.

• PoE PD (Powered Device): PoE PD refers to the device that draws power from the PoE network infrastructure. It encompasses various device types, such as IP phones, wireless access points, IP cameras, and network switches. The PoE PD consumes power from the PoE PSE, allowing it to operate without the need for a separate power source. Typically, it features an Ethernet input for data communication and a power input to receive power from the PoE PSE.

IOT-S300WS7 is an ultimate all-in-one RS485 Modbus weather monitoring system for various and continuous atmospheric conditions including air temperature, relative humidity, barometric pressure, light intensity, rainfall(optical), wind speed, and wind direction (ultrasonic). It boasts high resolution and accuracy with rugged and aesthetic housing.

1. Highly Integrated Design: Solar PoE Switch streamlines the installation and maintenance. Users only need to deal with one device instead of separately configuring and managing the solar controller and PoE switch, this integrated design allows for smoother energy flow within the system by optimizing the collaboration between components. From the cost perspective, purchasing a single unit is often a lower cost than buying two separate devices. Additionally, you will save on labor costs associated with installation and maintenance.

2. Compact Size: The integrated design can decrease the number of devices and overall physical size, saving space. It can eliminate the need for separate cables, power supplies, making installation and maintenance much easier. This is particularly crucial in setups with limited space.

3. Simplified Deployment and reduced system complexity: the integrated device reduces the complexity of configuring multiple components. Simplifying the device's installation process. It can decrease the technical complexity, especially for users with limited technical expertise.

1. Complexity of installation: Users would need to individually install solar power controllers and PoE switches, which could consume more time and require additional technical expertise. The configuration process may involve coordinating between different devices. Installing and managing two separate devices is more complex than installing a single integrated device.

2. Space Occupancy: Independently deployed devices typically require more space, as they cannot be integrated into a relatively compact design. This can be a challenge in applications with space constraints.

3. Technical Challenges: Configuring two separate devices may pose higher demands on technical personnel. Ensuring effective collaboration between the two systems may require additional technical expertise. Separate systems may require distinct maintenance and monitoring efforts for solar power and PoE networks. This can introduce additional complexity in troubleshooting issues and monitoring overall system performance.

4. Lack of Integrated User Experience: Users might need to deal with independently sourced devices from different vendors, potentially involving different user interfaces and some incompatible issues.