CONTENTS

• Description
• Requirement
• Configuration
  • 1. Login The Thing Stack and Add Gateway
    • Step1. Login The Thing Stack
    • Step2. Add Gateway
    • Step3. Create API Key
  • 2. Connect Gateway to The Thing Stack via LNS
    • Step1. Prepare the CA File (*. trust)
    • Step2. Prepare the Client Key file (*.key)
    • Step3. Configure the Gateway
  • 3. Connect Gateway to The Thing Stack via CUPS
    • Step1. Prepare the CA File (*. trust)
    • Step2. Configure CUPS to Send the LNS API Key
    • Step3. Prepare the Client Key file (*.key)
    • Step4. Configure the Gateway

Description

The Things Network, a leading provider of LoRaWAN networks and services, is upgrading its stack to v3 (The Thing Stack v3). As a leading LoRaWAN end-devices and gateways provider, Linovision IoT’s gateway can be easily connected to The Thing Stack, no matter it’s via ‘Semtech Packet forwarder’ or the Basic Station. 

Basics Station contains two sub protocols for connecting Gateways to Network Servers, LoRaWAN Network Server (LNS) and Configuration and Update Server (CUPS). This document will guide you how to connect toThe Thing Stack via CUPS or LNS, you can select one of both to complete the configurations.

If you prefer using Semtech Packet forwarder, please click here.

Requirement

• The Thing Stack Sandbox Account
• Linovision LoRaWAN Gateway

Configuration

1. Login The Thing Stack and Add Gateway

Step1. Login The Thing Stack

Select the cluster according to your gateway location and login The Thing Stack using the credentials/the things ID.

This is the login page, choose Login with The Things ID

Input the credentials and click Submit

When done, you will see this console page successfully.

Step2. Add Gateway

1. Login the web interface of the gateway to check frequency plan. In this example, the frequency plan is EU868.

You will need to take a note of the Gateway ID and Gateway EUI, which is needed when Register a device in The Thing Stack.

The default Gateway ID in Linovision gateway is the same as Gateway EUI. You can change the Gateway ID to yours. In this example, Gateway ID= g65, Gateway EUI= 24E124FFFEF1272B. Note that the gateway ID must have less than 36 characters and only use lowercase letters, numbers and dashes(-). 

2. Click Register a Gateway in The Thing Stack page and input the gateway information.

• Gateway EUI: this can be found on the status page of gateway web GUI. You can also click Continue without EUI to leave blank
• Gateway ID: the same the ID you configured in gateway web GUI. In this example is iot-g65
  Gateway name: user-defined
• Frequency plan: the same as the gateway setting, in this example is EU868
• Require authenticated connection: enabled

Note:

1) The Gateway ID cannot be reuse if you delete it in The Thing Stack

2) It is suggested to check the boxes of Generate API key and download the key files directly. 

 When done, the gateway is created well.

Step3. Create API Key

Note: if you already generate API key when adding a new gateway, please skip this Step.

If you need gateway to connect to LNS, please create a LNS API key; if you need gateway to connect to CUPS, please create a LNS API key and a CUPS API key.

1. Create a LNS API Key

Click API Keys > Add API Key

Input any name you like, tick Grant Individual rights and select the rights as below, then click Create API Key.

There will be a window pop-up to let you know copy the API Key.

 In this example, the LNS API key is: NNSXS.KDSXSAHLASC6REZDI3RV3ZTU27FDTNQVSRT7TYQ.MD7XXFD5D7ZOJW7XT2G3IV3QSVCTMVKJLKB2RF7HPPQOJPRUH6LQ

2. Create a CUPS API Key

Note: if you need to connect gateway to The Thing Stack via LNS protocol, skip this step.

Click API Keys > Add API Key, input any name you like, tick Grant Individual rights and select the rights as below, then click Create API Key and copy the key.

In this example, the CUPS key is:

NNSXS.O75NDWBFXFP2PVPGJU7NL5GBAUFNUWPLCUT57XA.BBMHEII2FJT433QJX37CNOQBBJ74465BJC5BZSF6JPT4OLB4XXAQ

Note: The Key is unique for the application created for each device.

2. Connect Gateway to The Thing Stack via LNS

Step1. Prepare the CA File (*. trust)

This is the CA certificate which secures your domain. Which contains links to common root SSL certificates used in The Things Stack, issued by trusted certificate authorities (CAs), in Linovision Gateway, we can just download the ISRG Root X1 Trust file to deploy, you will get a CA file named isrgrootx1.pem, we should rename it to *.trust.

 Besides, you can find more CA files here.

Step2. Prepare the Client Key file (*.key)

Note: if you already generate API key when adding a new gateway, please skip this Step.

Execute the following command to generate the LNS.key file, replace <your-lns-api-key> with the LNS API key you copied before.

On Linux or macOS use the following commands:

export LNS_KEY="your-lns-api-key"
echo "Authorization: Bearer $LNS_KEY" | perl -p -e 's/\r\n|\n|\r/\r\n/g' > lns.key

On Windows Command Prompt use the following commands:

set LNS_KEY=your-lns-api-key
echo Authorization: Bearer %LNS_KEY% > lns.key

In this example, here are the details in Command Prompt:

Then you will find the lns.key file under the corresponding path.

Here are the files used to upload in Linovision Gateway.

Step3. Configure the Gateway

1. Make sure that your gateway can connect to Internet successfully.

2. Go to Packet Forwarder > General, disable Embedded NS and create a new Destination. 

3. Click + to create a new destination

Select the type as Basic Station,  enable this option and input the information of Connecting to an LNS, and then click Save&Apply.

• URI: the format is wss://<server-address>:8887, you can click here to fill in the information to get the correct URI.
• CA File: import .trust format file
• Client Key File: import lns.key format file

Click Import for both CA file and Client Key, then click Save.

4. Check the gateway status in The Thing Stack side. It’s online successfully.

In the above screenshots, we can see the packets from the gateway.

3. Connect Gateway to The Thing Stack via CUPS

Step1. Prepare the CA File (*. trust)

This is the CA certificate which secures your domain. Which contains links to common root SSL certificates used in The Things Stack, issued by trusted certificate authorities (CAs), in Linovision Gateway, we can just download the ISRG Root X1 Trust file to deploy, you will get a CA file named isrgrootx1.pem, we should rename it to *.trust.

 Besides, you can find more CA files here.

Step2. Configure CUPS to Send the LNS API Key

Note: if you already generate API key when adding a new gateway, please skip this Step.

Click General settings, paste the content of LNS Key (start with "NNSXS....") you generated in the previous step here.

Step3. Prepare the Client Key file (*.key)

Note: if you already generate API key when adding a new gateway, please skip this Step.

Execute the following command to generate the CUPS.key file, replace <your-cups-api-key> with the CUPS API key you copied before.

On Linux or macOS use the following commands:

CUPS_KEY="your-cups-api-key"
echo "Authorization: Bearer $CUPS_KEY" | perl -p -e 's/\r\n|\n|\r/\r\n/g'  > cups.key

On Windows Command Prompt use the following commands:

set CUPS_KEY=your-cups-api-key
echo Authorization: Bearer %CUPS_KEY% > cups.key

In this example, here are the details in Command Prompt:

Then you will find the lns.key file under the corresponding path.

Here are the files used to upload in Linovision Gateway.

Step4. Configure the Gateway

1. Make sure that your gateway can connect to Internet successfully.

2. Go to Packet Forwarder > General, disable Embedded NS and create a new Destination. 

3. Click + to create a new destination

Select the type as Basic Station,  enable this option and input the information of Connecting to an CUPS, and then click Save&Apply.

• URI: the format is https://<server address>:443, you can click here to fill in the information to get the correct URI.
• CA File: import .trust format file
• Client Key File: import Cups.key format file

4. Check the gateway status in The Thing Stack side. It’s online successfully.

In the above screenshots, we can see the packets from the gateway.

Introduction

Linovision gateway is able to decode the data of LoRaWAN sensors and map the sensor data into BACnet objects used by BMS system or BACnet devices, which can quickly and easily integrate LoRaWAN devices to Building Management System.

Requirement

• Linovision Gateway: IOT-G65/G67 with firmware version 60.0.0.41 and later
• Any LoRaWAN sensor
• BACnet Client tool: take Yabe as example

Configuration

1. Go to Network Server > Payload Codec to check if there is decoder of your LoRaWAN node, if not please add and custom the decoder referring to article How to Use Payload Codec on Linovision Gateway.

2. Connect LoRaWAN node to Linovision gateway referring to article How to Connect LoRaWAN Nodes to Linovision Gateway. Note that ensure the correct payload codec is selected when adding this device.

   

3. Go to Network Server > Packets to check if there is uplink packet and click Details to check if the decoder works. If works, the JSON item will show the decoded result.

4. Select the Application you use and add a BACnet/IP transmission.

5. Go to Protocol Integration > BACnet Server > Server to enable BACnet server and configure the settings. Note that the Device ID should be changed to an unique value to avoid conflict with other BACnet server devices, or the BACnet client may not find this device.

6. Go to Protocol Integration > BACnet Server > BACnet Object page, click Add to add an object.

• Device Name: select the device added on Network Server > Device page
• LoRa Object: select or customize a sensor variable decoded on JSON item of Network Server > Packets page
• Object Name: customize an unique object name
• Object Type: select Analog Input or Binary Input for non-editable sensor data

Example 1: temperature data

• COV: when the change of analog type object value exceeds the COV Increment, the gateway will send notification to BACnet client actively. This should ensure the BACnet client supports COV feature.

Example 2: button status

• Active/Inactive Text: display the real status when button is pressed or unpressed
• Polarity: Define the binary status as Normal or Reverse.

Note: for LInovision buttons (IOT-S500BT and IOT-S500SP), it's suggested to add msgid value (update a random value if the press is triggered) to an object and know if the button is pressed by the change of this value.

7. After adding, you can check if object values are updated regularly.

8. Open Yabe BACnet client tool, click Add device to scan the devices, then you can find the BACnet server device according to the Device ID and check the object list.

9. Click the object to check all the properties of this object.

---END---

 Q1: Is there API for Linovision gateway to get historical data?

Answer: There is no API to get historical data. If you have any requirements about it please contact Linovision about it.  

Q2: What kind of the material does the IOT-G67’s outer shell made of

Answer: Polycarbonate+ die-casting aluminum.

Q3: Is it possible to connect multiple IOT-G65 to the network server of one IOT-G65?  How many can I connect?

Answer: Yes, you can connect up to 4 units of devices.

Q4: I want to ask if the gateway could perform end device localization based on TDoA (Time Difference of Arrival)? 

Answer: Currently cannot. Linovision gateways support the gateway GNSS positioning now.

Q5: What are the main factors that will affect the number of the IOT-CX controller that gateway manage?

Answer: The number of IOT-CX controller that connect to gateway would be affected by factors like reporting interval, distance in between, payload length, Lora frequency band and spread factor.

Q6: What is the maximum length of the PoE cable supported for the IOT-G67 gateway ? 

Answer: The length is up to 80-100 meters.

Q7: What is the difference between LoRaWAN 1.0.2 and 1.0.3? If I am using class B, which version shall I use? And can version 1.1 compatible with 1.0.3?

Answer: LoRaWAN1.0.3 supports unicast & multicast class B devices. Class A and class C sections are unchanged compared to LoRaWAN1.0.2 with the exception of a new MAC command "DeviceTimeRequest" used to synchronize the real time clock of a device. For devices operating in class A or class C, there is no need to upgrade to LoRaWAN 1.0.3. Click here for more information about LoRaWAN 1.0.3.

Q8: What are the new features for the  LoRaWAN V1.1 compared with  LoRaWAN  v1.0.2?

Answer: LoRaWAN V1.1 protocol is optimized for battery-powered end-devices and adds support for handover roaming, Class B and security enhancements. Click here for more information about LoRaWAN 1.1.

Q9: How many super capacitors in your IOT-G67? How many Farad for each one?

Answer: IOT-G67 has 5 capacitors inside, and each one is 25 Farad.

Q10: Can the IOT-G65 and IOT-G67 support external 4G antenna?

Answer: IOT-G65 can be customized to connect external antenna, while the IOT-G67 cannot. Please contact Linovision sales if you need external antenna customization.

Q11: Why the time stamp of message that received on Network Server is different from the set time of Linovision LoRaWAN Gateway?

Answer: In standard LoRaWAN protocol, the upload time is defined on UTC time zone. So the time displayed on Chirpstack server is different due to different time zone.

Q12: Can the LoRaWAN sensor data collected by the Linovision LoRaWAN gateway be sent to cloud/websites other than the Linovision IoT Cloud?

Answer: Yes. Linovision gateway supports data transmission via MQTT/HTTP/HTTPS. You can refer to articles below:

How to Connect LoRaWAN Gateway to MQTT Broker

How to Connect Linovision LoRaWAN Gateway to HTTP(s) Server

Q13: Does the Node-RED of Linovision LoRaWAN gateway start up on boot or it needs to be started manually?

Answer: It starts up when it's enabled on Web GUI.

Q14: Is it possible to send a payload to the Linovision LoRaWAN gateway to send an instruction to a LoRaWAN Controller using HTTP like we do posting a message to a specific topic in MQTT?

Answer: No. When the gateway is connected to HTTP/HTTPS server, it only supports uplink. If you want to send downlink, one way is to use the Node-Red feature on the gateway. In that case, the gateway works as HTTP server and it requires a public IP (Cellular or WAN) to allow connection from HTTP client.

Q15: Are the IOT-G67 gateway able to use nanosecond timestamp for geolocation? 

Answer: Not supported now. Linovision have plans to upgrade chip which is suitable for geolocation. Please contact Linovision if you have any applications requiring for it.

Q16: Do you have any recommendations regarding lightning protection?

1. If we mount the gateway on relatively low height (4-5 m, on top of fiber optic PoP), and we connect the gateway body (by original metal mount) with the lightning protection of the PoP, do we need the surge protection on the antennas and LAN cable?

2. Do you have to offer some directional antennas, in cases where we want to cover only a part of space, for example 90 degrees? This would improve our reception in cases where the gateway is mounted outside of a city.

Answer:

1. The height is not the most important. The critical thing is whether there is other devices/buildings higher than your gateway. Antenna needs lightning surge protectors separately. If your network cable has passed any surge protection system, there is not need to add extra protection.

2. Not by default. If necessary, please share your directional antenna requirements to Linovision in details.

Q17: The gateway disappears from TTN quite often, how to check the issue? 

Answer: Regarding the disconnection between the gateway and TTN, you can check the following points:

1. Whether the network of the gateway is normal: Fail to Access the Network of Linovision Gateway.

2. If you use Semtech type packet forwarder, you can change to TTN type which is more stable: Linovision Gateway -The Things Stack(TTN) Integration via Basic Station

Q18: Can you inform about the difference in range between IOT-G65-L04EU-868M without external antennas and IOT-G65-L04EU-868M -EA with external antenna in an Indoor application?

Answer: The gain of external antenna is 2dB, while the gain of internal is about 1dB.

 If the gateway just need to cover the end devices in the building (2 floors nearby), the internal antenna version is enough, the signal quality (Average SNR) is 2dB less than the external antenna). The distance (max) can reach 1 km in building/park/city.

If the gateway needs to cover wider area, the external antenna version is recommended, the signal quality (Average SNR) is 6dB more than the internal antenna version.

The distance (max) can reach 2 km in buildings/parks/cities.

Q19: What is the maximum number of channels we can configure in LoRaWAN gateway to receive or send data from Nodes(Channels)?

Answer: The max number of channels that can send and receive is 8. One channel of the gateway can deal with a data packet one second, so if the interval is 1 min, it can deal 480 data packet (nodes); if your sensor interval is 1 hour, it's sure that the gateway can work with 100 devices.

Q20: What's the meaning of the packet with different colors under "Network Server->Packet" tab?

Answer: Blue and white means normal transmission and grey means the message is in queue and waiting for sending. This always happens in sending downlinks to Class A type device.

Q21: Can we connect & configure 2 sensors to the same Application in Linovision gateway? If yes, how to separate every sensor data?

Answer: If the sensor modules are the same, you can use the same application including the same decoder and the MQTT destination. You can configure decoder to add device EUI of every sensor to distinguish every sensor. For more details please refer to How to Use Payload Codec on Linovision Gateway.

Q22: Is it possible to select all international frequencies (for all LoRaWAN frequencies) in one chip with IOT-G67?

Answer: It's unable to select all LoRaWAN frequencies in only one hardware.

Q23: Does Linovision IOT-G6x gateway support Node Red? If so, do I need to expand the eMMC for it?

Answer: Linovision IOT-G6x gateway has supported Node Red with firmware version 60.0.0.35 or above. There is not need to expand the eMMC.

Q24: How to use the Node-Red of Gateway? 

Answer: Please refer to LoRaWAN Gateway User Guide about Node-RED introduction and application examples.

Q25: Can the gateway connect to the Ginjer platform?

Answer: Yes, this platform has integrated with TTN, gateway can connect Ginjer platform via TTN.

Q26: Will all the traffic go over the VPN tunnel if connect the gateway to Loriot and enable the VPN?

Answer: No, because VPN tunnels and Loriot traffic destination are different.

Q27: Why can't I see the cellular settings on the gateway Web GUI?

Answer: You can go to "Status->Overview->System information" webpage to check whether the product model contains "L0XX". If not included, it means this model doesn't support cellular. Otherwise please submit a ticket to support@linovision.com about it.

Q28: Is there a way to send data over http(s) to the gateway that will be forwarded to the lorawan-sensor? 

Answer: For the HTTP API to send the downlink message to the sensor, it's not supported in our gateway. It's suggested to use MQTT integration which supports both uplinks and downlinks.

Q29: Why can't I connect the gateway to the Internet through WLAN?

Answer: Please check the settings of WAN Failover, which supports Cellular and WAN interface there by default. You need to select WLAN as the primary interface to make the gateway access the network.

Q30: What is the DC power input connector type of IOT-G67?

Answer: The connector type for power input is M12 Connector. For detailed definitions, please refer to the chapter2.5 of IOT-G67 Quick Guide.

Q31: Can IOT-G6x gateway connect to SCADA system? 

Answer: Yes, if your SCADA supports MQTT protocol and can work as MQTT broker, you can connect Linovision gateway to SCADA system and transfer data to it. SCADA system can also poll Modbus data from IOT-C50x according to How to Achieve Modbus RTU to/over TCP between Linovision Gateways and Controllers. By the way, Linovision IOT-G6x gateway has integrated the Node-Red for flexible integration.

Q32: Can I connect gateway to Linovision IOT-G6x gateway build-in NS? How many gateways can I connect it at most? Can I use third-party gateway to connect?

Answer: One Linovision LoRaWAN gateway can connect to 4 Linovision IOT-G6x gateways at most, which is a feature of Linovision IOT-G6x gateways only.

Q33: Does the Linovision IOT-G65 support dual interfaces to connect network?

Answer: Yes, Linovision IOT-G65 supports main interface and back up interface to connect to network.

Q34: Can IOT-G6x gateway connect to multiple MQTT/HTTP servers?

Answer: Yes, Linovision IOT-G6x gateway supports to connect to 1 MQTT server and 1 HTTP/HTTPs server.

Water damage is often an unseen threat under floorboards, ceilings, and around pipelines causing serious damage over time such as mold, equipment failure, and facility damage if not prevented in time. Water leak detection sensors monitor the presence of water in the specified area and alert you whenever they sense a leak. Among various types of water leak detection sensors, the cable type sensor and spot type sensor are the most widely used types.

Now let’s see what are the differences between them and how to choose in your applications.

When we're detecting water leaks, what are we detecting exactly? We're talking about both point detection and linear detection. It can be either point and spot detection or when using specialized cables linear detection for large areas.

The spot type sensor or point detection sensor, which is designed to sense water at a single point and confined areas. There are two probes on the sensor and both of them must touch the water simultaneously to detect a water leak and trigger an alarm. You can deploy the sensor to those places where a leak easily happened, for instance, the drip pans, floor drains, or where water tends to converge. The spot sensors are suitable for monitoring limited areas given their small and precise range.

The zone type sensor or cable/linear detection sensor is designed to detect a leak in expansive and open areas. These water-sensitive cables can be put on the floor, wrapped around pipes, or attached to a wall for detecting leakage of clean or polluted water or other conductive liquid anywhere on the total length of the cable. It’s always difficult to predetermine the leak points in a large space like under raised floors, so the cable sensors are the ideal choice in that case.

Theoretically, all leak detection cables are based on two sensing wires with reliability and durability. With a standard length of 3 meters, the cable is light, easy to install but robust enough to keep its shape, and both ends of the cable are equipped with terminals for length expansion. The sleek design of the cable allows it to dry and can be put into use again even after having been soaked in liquid and can still maintain its high sensitivity to react quickly without false alarms. 

These basically systems are designed to continuously monitor for any amount of water and then produce an alarm if the water is indeed detected. It's in a way very similar to the concept of detecting the presence of smoke or heat in a fire detection system.

Solution

As a matter of fact, the Linovision water leak detection sensor is an early warning solution based on LoRaWAN® technology, which can be quickly deployed in multiple zones for effective monitoring. With the feature of Custom Image on the Linovision IoT Cloud platform, you can now plot the leak sensors on your floor plans, building maps and the software will automatically change the color of the bubble and send you alerts on mobile push when a water leakage occurs. 

variety of leak sensor options available, it is important to evaluate the exact situation of monitoring required. You may probably need to take some factors into consideration including the area/zone being monitored, the environment of implementation, the simplicity of operation, the scalability of the device, and the total cost of your project.

Background

The icing of airport runways is a major safety hazard that affects the safety of aviation flights. In the history of civil aviation, there were several runway excursions due to the icing of the runway. As a result, airports use a variety of methods to deice the runway. And the common method performed in aviation is deicing with chemical fluids by lowering the freezing point. Thus, to meet the demand for the unfrozen runway in the winter season, a sufficient supply of deicing fluid should be guaranteed. In this case, Linovision LoRaWAN® Ultrasonic Level Sensor can be deployed inside the storage tank to monitor the fluid level for the safe level of runway deicing fluid.

Challenges

• Timely report of shortage of runway deicing fluid

• Chemical deicing fluid deals damage to the sensor

• Requirement for long-term maintenance-free solution

Solution

Normally, the chemicals used to deice runways can pose a hazard to submersible level monitoring sensors. Equipped with IP67 and industrial-grade enclosure, Linovision IOT500-UDL Ultrasonic Distance/Level Sensor provides highly accurate and contact-free distance measurement in harsh environments. When mounted at the inner top of the deicing fluid tank, IOT500-UDL emits a high-frequency acoustic pulse from its transducer. The pulse travels through the air gap, reflects against the deicing fluid surface and returns to the transducer. IOT500-UDL measures the pulse time of flight and converts this into the level height of deicing fluid. What’s more, the built-in 19000 mAh high-capacity battery makes IOT500-UDL suitable for 10-years maintenance-free applications.

Once fluid level reaches the threshold, LoRaWAN® based IOT500-UDL will immediately report the level height to Linovision IoT Cloud or third-party cloud platforms, notifying admins of the shortage of deicing fluid. By implementing the Linovision deicing fluid level monitoring solution, the airport can keep the runway unfrozen without the accidental shortage of deicing fluid.

In recent years, the office and the way we work have undergone a massive transformation. How do you make sure your office ticks all the boxes to accomplish your business goals? Smart office solution might be the answer you are looking for. A smart office is a workplace where modern technology is leveraged to help employees work smarter, better, and faster. Overview of office is fed with various data, collected by different types of sensors and gateways. This way, people can see which workplaces are available, where their colleagues are, which meeting rooms appear to be empty or how is the indoor air quality. To kick off and level up your office into a smart one, a mini gateway could be a suitable choice.

Challenges 

•Unnecessary Cost Consumption

For deploying smart office solution in every necessary space of a whole office building, full functional gateway could be helpful yet a little luxury considering cost.

For existent smart office solution, physical obstacles in buildings would inevitably form some blind spots, causing difficulties in receiving data to some extent.

Solution

IOT-G63 Mini LoRaWAN® Gateway is great to start smart office journey and level up user experience. The word “Mini” doesn’t mean that IOT-G63 makes any compromise in terms of functions as a qualified gateway. With built-in network server, the IOT-G63 supports Semtech’s latest packet forwarder, and is compatible with multiple network server platforms like TTN, ChirpStack and Link WAN, which offers a wide range of options for data processing. In addition, the Listen Before Talk function would bridge the gap between reliability and efficiency. When LBT is enabled, the device continuously monitors channels so as to transmit only when a channel is not in use.

Benefits

• Affordable & Available Gateway

IOT-G63 Mini LoRaWAN® Gateway is another masterpiece from Linovision gateway family with mini size. Coupled with an elegant and aesthetic appearance, UG63 is in perfect accord with the office surroundings.

• Massive Connectivity

Adopting Semtech SX1302 LoRa chip, IOT-G63 supports connection with more than 2000 LoRaWAN® nodes.

• Blind Spot Coverage

Besides the general features of a LoRaWAN® gateway, the Gateway Fleet makes IOT-G63 is particularly suited to provide network coverage for indoor blind spots.

• Actionable Utilization Insights

By streamlining the employee-to-facility management channel, smart office solutions can radically reduce the time and effort to menial tasks, unnecessary obstacles and activities that drain time and energy from the workforce.

Since December 2019, the COVID-19 pandemic has spread globally at a rapid speed. Until now, it is still a tremendous threatening factor for public safety and society, with hundreds of thousands of people being confirmed the contagious diagnosis on a global basis every day. These patients need to be isolated in isolation wards respectively. Under this circumstance, Milesight smart button allows these patients to alert a nursing staff remotely of their need for help.

• Ease workloads of nursing staff

Nurses used to go from ward to ward to find out whether patients need help. As the number of confirmed patients goes through the roof, they can no longer allocate so much energy and time to do this repetitive work.

• Improve patient safety by alerts whenever they need help

Confirmed patients are stuck in isolation wards, regardless of their symptoms are serious or subtle, whereas nurses cannot squeeze a little time to keep an eye on them.

• Reduce costs of purchasing new devices

As COVID-19 ravages all around the world, more isolation wards need to be established. In contrast, those isolation wards where confirmed patients all recover need to be tear down or rescheduled. Hence, most of the original devices suitable for addressing COVID-19 will be subjected to abandonment.

Linovision IOT-S500BT is a LoRaWAN^®-based smart button for wireless controls, triggers and alarms. It supports multiple press actions, all of which can be defined by the user to control devices or trigger scenes. It is remarkable that Linovision also provides a red button that is primarily used to send SOS alarms, while a white one is used for general scenarios. Compact and battery-powered, IOT-S500BT is easy to install. Besides, it can be carried everywhere with a lanyard.

Topology 

Solution

In hospitals or specific isolation places, every isolation ward is equipped with one smart button, that is, every isolated patient can get help if required. With easy configuration, if the alert of smart button is triggered by pressing it, which means patients need help, the signal can be transmitted by Linovision LoRaWAN^® gateways to a cloud platform such as Linovision IoT Cloud. Accordingly, nursing staff can find out who and where the patients needs help and provide care required in a much more efficient way.

Benefits

• Avoid repetitive work

With the increasing number of confirmed patients, Milesight smart button allows nursing staff to avoid repetitive patrol of usually going from ward to ward, so they can put left time and energy to more patients.

• Swift response , no matter where and when

Anything can happen in an isolation ward. Milesight smart button ensures that the nurses receive alerts of help from patients in time, or saving their lives.

• Reusable devices

Linovision smart buttons are movable and can be re-deployed in other isolation wards, which save much cost.

Background

The revolution of the rapidly urbanizing society involves the rapid increase of grocery stores which play an increasingly crucial role in people's lives. At the same time, the management of grocery stores brings various problems to the owners of grocery stores, such as loss of burglary damage and the high cost of unifying video surveillance. As a smart solution, the Linovision solution adopts a more convenient and cost-effective management method to prevent burglary and enhance grocery store security, which can receive alarms anytime and anywhere in a timely manner.

Challenges

- High cost of unifying video surveillance becomes a hindrance to the security system.

- Installation and maintenance are time-consuming and labor-intensive.

Solution

This solution leverages Linovision IOT-S500DCS Magnetic Contact Switch and Linovision IOT-S500L PIR & Light Sensor to implement all-round monitoring of entrances and exits, windows and warehouses to prevent potential intruders.

IOT-S500DCS Magnetic Contact Switch protects doors and windows, serving as a trigger for alarm systems when unauthorized intrusion is detected. By adopting magnetic sensor technology to function, the switch consists of two parts: a sensor and a magnet. When doors or windows open, the magnet detaches from the sensor, triggering the alert of unauthorized opening.

IOT-S500L PIR & Light Sensor uses the PIR motion detection technology to detect human presence accurately. Human presence in a non-operating time indicates the intrusion. The switch and sensor take advantage of battery power supply and wireless communication technology – LoRaWAN^®, facilitating the quick and easy deployment without wiring of power supply and Ethernet.

When an unscheduled opening or human presence occurs, the sensors will send out an alert to the Linovision IoT Cloud via a LoRaWAN^® gateway, enabling admins to view alerts remotely and receive instant notification