¶ Introduction
Edge computing is a concept where the gateway processes the data itself, takes decisions, acts according to a user-defined logic, and transmits only the necessary data to a central datacenter.
This short step-by-step tutorial demonstrates how to setup your Kerlink gateway to quickly reach a full chain demo level.
¶ Prerequisites
This tutorial provides command line instructions as well as JetPorch playbooks.
Playbooks prove to be very usefull to easily deploy needed packages and configurations. Please refer to solution#create-a-playbook to get started with playbooks before going through the following guidelines.
All the following commands are meant to be run as root. You may switch to root user using
sudo su -or prefix all commands withsudoand enter your password.
¶ Setup
To replicate our demo setup, you will need:
- A LoRaWAN sensor (here a Kerlink Wal-e), which regularly transmits the t° and humidity levels, and features a test button
- A leader gateway (either an iFemto-cell or an iStation), which hosts the local LoRaWAN Network Server (LNS). It collects and decodes the data from the sensor, and also integrates a specific edge processing unit, which makes it possible to notify the end-user on its mobile phone
Demonstration workflow
Bonus: Denoted as followers, other gateways can be configured to forward LoRaWAN frames to the leader gateway. They must be able to reach the leader gateway through the network:
¶ Configure a Leader gateway
All the Edge logic is integrated in the leader gateway. We will thus install the Chirpstack LNS, as well as NodeRed which proves to be a usefull applicative to experiment with Edge logic. The gateway will also integrate a LoRaWAN forwarder connected to its local LNS.
We provide the step-by-step approach, and a more abstracted example which installs and configures the Chirpstack LNS in a single step. We recommend to first go through the different steps to understand how we demonstrate the integration in our example.
¶ Install and configure Chirpstack LNS
¶ Option 1 (recommended): Step-by-step deployment
¶ Add Chirpstack repository
We will use Chirpstack as the embedded LNS. Chirpstack is available from its own repository, and is directly installable in KerOS 6.
Please note that your gateway must have a data connection to get the online packages. If the gateway does not have a data connection, you will get the following error
Execute the following sample to add the Chirpstack repository in KerOS apt source.
cat > chirpstack_4.list << EOF
deb https://artifacts.chirpstack.io/packages/4.x/deb stable main
EOF
mv chirpstack_4.list /etc/apt/sources.list.d/
curl -s "https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x1ce2afd36dbcca00" | gpg --dearmor -o /etc/apt/trusted.gpg.d/chirpstack_4.gpg
cat > 50-chirpstack-mqtt-forwarder << EOF
Package: chirpstack-mqtt-forwarder
Pin: origin artifacts.chirpstack.io
Pin-Priority: -1
EOF
mv 50-chirpstack-mqtt-forwarder /etc/apt/preferences.d/
apt update
- name: Add chirpstack repository
groups:
- all
tasks:
- !external
use: copycontent
name: "Add chirpstack repository"
params:
dest: "/etc/apt/sources.list.d/chirpstack_4.list"
content: |
deb https://artifacts.chirpstack.io/packages/4.x/deb stable main
- !external
use: copycontent
name: "Exclude chirpstack-mqtt-forwarder"
params:
dest: "/etc/apt/preferences.d/50-chirpstack-mqtt-forwarder"
content: |
Package: chirpstack-mqtt-forwarder
Pin: origin artifacts.chirpstack.io
Pin-Priority: -1
- !shell
name: "Add chirpstack key"
cmd: curl -s "https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x1ce2afd36dbcca00" | gpg --dearmor > /etc/apt/trusted.gpg.d/chirpstack_4.gpg
- !shell
name: update repo
cmd: apt update
¶ Install Chirpstack LNS
Execute the following sample to install Chirpstack.
apt install chirpstack postgresql postgresql-client \
postgresql-contrib mosquitto mosquitto-clients redis zram
printf "\n[gateway]\n allow_unknown_gateways=true\n" | tee -a /etc/chirpstack/chirpstack.toml
- name: Install chirpstack
groups:
- all
defaults:
apt_packages:
- chirpstack
- postgresql
- postgresql-client
- postgresql-contrib
- mosquitto
- mosquitto-clients
- redis
- zram
tasks:
- !apt
name: Install packages
package: "{{ item }}"
with:
items: apt_packages
- !shell
name: Allow external gateway
cmd: printf "\n[gateway]\n allow_unknown_gateways=true\n" >> /etc/chirpstack/chirpstack.toml
¶ Setup postgresql database for Chirpstack LNS
Chirpstack LNS is using postgres as a database.
Execute the following sample to create a database, and configure it to accept Chirpstack connection.
su -l postgres -c "/usr/bin/initdb --pgdata='/var/lib/postgresql/data' --auth='trust'"
systemctl enable postgresql --now
su - postgres -c "psql -c \" create role chirpstack with login password 'chirpstack' \" "
su - postgres -c "psql -c \" create database chirpstack with owner chirpstack \" "
su - postgres -c "psql -d chirpstack -c \" create extension pg_trgm \" "
systemctl enable chirpstack --now
sleep 2
su - postgres -c "psql -d chirpstack -c \"insert into gateway (gateway_id, tenant_id, created_at, updated_at, last_seen_at, name, description, latitude, longitude, altitude, stats_interval_secs, tls_certificate, tags, properties) values (bytea '\x$EUI64', (select id from tenant limit 1), now(), now(), null, 'local gateway', 'self', 0.0, 0.0, 0.0, 30, null, '{}', '{}')\" "
- name: Setup postgresql for chirpstack
groups:
- all
tasks:
- !shell
name: Init database
cmd: su -l postgres -c "/usr/bin/initdb --pgdata='/var/lib/postgresql/data' --auth='trust'"
- !sd_service
name: Start posgres
service: postgresql
enabled: true
restart: true
- !external
use: copycontent
name: "Add chirpstack repository"
params:
dest: "/tmp/setup_postregsql.sh"
content: |
#!/bin/sh
su - postgres -c "psql -c \" create role chirpstack with login password 'chirpstack' \" "
su - postgres -c "psql -c \" create database chirpstack with owner chirpstack \" "
su - postgres -c "psql -d chirpstack -c \" create extension pg_trgm \" "
- !shell
name: Create database for chirpstack
cmd: sh /tmp/setup_postregsql.sh
- !sd_service
name: Start chirpstack
service: chirpstack
enabled: true
restart: true
- !shell
name: Add local gateway
cmd: sleep 2 && su - postgres -c "psql -d chirpstack -c \" insert into gateway (gateway_id, tenant_id, created_at, updated_at, last_seen_at, name, description, latitude, longitude, altitude, stats_interval_secs, tls_certificate, tags, properties) values (bytea '\x$EUI64', (select id from tenant limit 1), now(), now(), null, 'local gateway', 'self', 0.0, 0.0, 0.0, 30, null, '{}', '{}') \" "
¶ Configure firewall rules to access to the LNS management interface
Chirpstack LNS provides a web interface listening on port 8080. If we want to access it, we need to open this port to allow connection.
Security consideration:
This is for demonstration purpose. Do not use as this in a production environment.
Execute the following sample to configure the firewall.
cat > chirpstack.rules << EOF
*filter
-A INPUT -p tcp --dport http-alt -j ACCEPT
COMMIT
EOF
mv chirpstack.rules /etc/iptables/iptables.d/
systemctl restart iptables
- name: Allow http-alt connection
groups:
- all
tasks:
- !external
use: copycontent
name: "Open firewall for chirpstack"
params:
dest: "/etc/iptables/iptables.d/chirpstack.rules"
content: |
*filter
-A INPUT -p tcp --dport http-alt -j ACCEPT
COMMIT
- !sd_service
name: Reload firewall
service: iptables
enabled: true
restart: true
¶ Install the LoRaWAN forwarder
The leader gateway also integrates a LoRaWAN forwarder connected to its local LNS.
Execute the following sample to install and configure
chirpstack-mqtt-forwarder.
Make sure to adapt the MQTT topic to match your LoRaWAN region, cf. chirpstack-mqtt-forwarder configuration
apt update
apt install chirpstack-mqtt-forwarder
# Adapt LEADER_IP_ADDR to Hostname or IP of your leader gateway
# LEADER_IP_ADDR=myLeaderGW
# Adapt topic_prefix if needed (us915_0,as923,...)
cat > leader_config.toml << EOF
[mqtt]
topic_prefix = "eu868"
server = "tcp://${LEADER_IP_ADDR:=localhost}:1883"
EOF
conflex -t -o chirpstack-mqtt-forwarder.toml -T /usr/share/chirpstack-mqtt-forwarder/template.hb leader_config.toml
mv chirpstack-mqtt-forwarder.toml /etc/chirpstack-mqtt-forwarder/chirpstack-mqtt-forwarder.toml
systemctl enable chirpstack-mqtt-forwarder --now
mkdir -p /etc/mosquitto/conf.d/
echo "include_dir /etc/mosquitto/conf.d/" | tee -a /etc/mosquitto/mosquitto.conf
cat > local.conf << EOF
listener 1883 0.0.0.0
allow_anonymous true
EOF
mv local.conf /etc/mosquitto/conf.d/
systemctl enable mosquitto --now
- name: Setup a follower gateway
groups:
- all
defaults:
mqtt:
topic: "eu868"
server: "localhost:1883"
tasks:
- !shell
name: update repo
cmd: apt update
- !apt
name: Install chirpstack-mqtt-forwarder
package: chirpstack-mqtt-forwarder
- !template
name: Configure chirpstack-mqtt-forwarder
src: /usr/share/chirpstack-mqtt-forwarder/template.hb
dest: /etc/chirpstack-mqtt-forwarder/chirpstack-mqtt-forwarder.toml
- !sd_service
name: Restart chirpstack-mqtt-forwarder
service: chirpstack-mqtt-forwarder
enabled: true
restart: true
- name: Allow mqtt to listen on local interface
groups:
- all
tasks:
- !shell
name: allow include dir for mosquitto
cmd: mkdir -p /etc/mosquitto/conf.d/ && echo "include_dir /etc/mosquitto/conf.d/" >> /etc/mosquitto/mosquitto.conf
- !external
use: copycontent
name: add rule to listen on local interface
params:
dest: "/etc/mosquitto/conf.d/local.conf"
content: |
listener 1883 0.0.0.0
allow_anonymous true
- !sd_service
name: Reload mosquitto
service: mosquitto
enabled: true
restart: true
¶ Option 2: Deploy our example in a single step
Not recommended as first steps, up to this point the deployment can be launched thanks to a single playbook.
Single playbook sample
- name: Add chirpstack repository
groups:
- all
tasks:
- !external
use: copycontent
name: "Add chirpstack repository"
params:
dest: "/etc/apt/sources.list.d/chirpstack_4.list"
content: |
deb https://artifacts.chirpstack.io/packages/4.x/deb stable main
- !external
use: copycontent
name: "Exclude chirpstack-mqtt-forwarder"
params:
dest: "/etc/apt/preferences.d/50-chirpstack-mqtt-forwarder"
content: |
Package: chirpstack-mqtt-forwarder
Pin: origin artifacts.chirpstack.io
Pin-Priority: -1
- !shell
name: "Add chirpstack key"
cmd: curl -s "https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x1ce2afd36dbcca00" | gpg --dearmor > /etc/apt/trusted.gpg.d/chirpstack_4.gpg
- !shell
name: update repo
cmd: apt update
- name: Install chirpstack
groups:
- all
defaults:
apt_packages:
- chirpstack
- postgresql
- postgresql-client
- postgresql-contrib
- mosquitto
- mosquitto-clients
- redis
- zram
tasks:
- !apt
name: Install packages
package: "{{ item }}"
with:
items: apt_packages
- !shell
name: Allow external gateway
cmd: printf "\n[gateway]\n allow_unknown_gateways=true\n" >> /etc/chirpstack/chirpstack.toml
- name: Setup postgresql for chirpstack
groups:
- all
tasks:
- !shell
name: Init database
cmd: su -l postgres -c "/usr/bin/initdb --pgdata='/var/lib/postgresql/data' --auth='trust'"
- !sd_service
name: Start posgres
service: postgresql
enabled: true
restart: true
- !external
use: copycontent
name: "Add chirpstack repository"
params:
dest: "/tmp/setup_postregsql.sh"
content: |
#!/bin/sh
su - postgres -c "psql -c \" create role chirpstack with login password 'chirpstack' \" "
su - postgres -c "psql -c \" create database chirpstack with owner chirpstack \" "
su - postgres -c "psql -d chirpstack -c \" create extension pg_trgm \" "
- !shell
name: Create database for chirpstack
cmd: sh /tmp/setup_postregsql.sh
- !sd_service
name: Start chirpstack
service: chirpstack
enabled: true
restart: true
- !shell
name: Add local gateway
cmd: sleep 2 && su - postgres -c "psql -d chirpstack -c \" insert into gateway (gateway_id, tenant_id, created_at, updated_at, last_seen_at, name, description, latitude, longitude, altitude, stats_interval_secs, tls_certificate, tags, properties) values (bytea '\x$EUI64', (select id from tenant limit 1), now(), now(), null, 'local gateway', 'self', 0.0, 0.0, 0.0, 30, null, '{}', '{}') \" "
- name: Allow http-alt connection
groups:
- all
tasks:
- !external
use: copycontent
name: "Open firewall for chirpstack"
params:
dest: "/etc/iptables/iptables.d/chirpstack.rules"
content: |
*filter
-A INPUT -p tcp --dport http-alt -j ACCEPT
COMMIT
- !sd_service
name: Reload firewall
service: iptables
enabled: true
restart: true
- name: Setup a follower gateway
groups:
- all
defaults:
mqtt:
topic: "eu868"
server: "localhost:1883"
tasks:
- !shell
name: update repo
cmd: apt update
- !apt
name: Install chirpstack-mqtt-forwarder
package: chirpstack-mqtt-forwarder
- !template
name: Configure chirpstack-mqtt-forwarder
src: /usr/share/chirpstack-mqtt-forwarder/template.hb
dest: /etc/chirpstack-mqtt-forwarder/chirpstack-mqtt-forwarder.toml
- !sd_service
name: Restart chirpstack-mqtt-forwarder
service: chirpstack-mqtt-forwarder
enabled: true
restart: true
- name: Allow mqtt to listen on local interface
groups:
- all
tasks:
- !shell
name: allow include dir for mosquitto
cmd: mkdir -p /etc/mosquitto/conf.d/ && echo "include_dir /etc/mosquitto/conf.d/" >> /etc/mosquitto/mosquitto.conf
- !external
use: copycontent
name: add rule to listen on local interface
params:
dest: "/etc/mosquitto/conf.d/local.conf"
content: |
listener 1883 0.0.0.0
allow_anonymous true
- !sd_service
name: Reload mosquitto
service: mosquitto
enabled: true
restart: true
¶ Manage your LNS
¶ Access to the management interface
The interface is available from your gateway webui#hostname-url on the 8080 port.
Example:
- A Wirnet™ iFemtoCell has a board ID of 704BEc1234AB (and 7276FF00391234AB as EUI64)
- Chirpstack LNS interface URL is http://klk-wifc-1234AB.local:8080
Please refer to Chirpstack LNS documentation for more details.
At this stage, your gateway should now be visible in the 'Gateways" menu
¶ Create a Device Profile
¶ Add an Application
¶ Add your end-device in this application
Join your end-device !
¶ Deploy the Edge processing
In this demo, we use node-red to implement the specific logic of our edge solution.
Node-red requires additional ressources. Prior to installing the application, you need to enable swap memory, cf. faq#is-it-possible-to-enable-swap-memory
Execute the following sample to install node-red application
apt update
apt install node-red
systemctl enable node-red --now
- name: Deploy node-red service
groups:
- all
tasks:
- !apt
package: node-red
- !sd_service
name: Start node-red
service: node-red
enabled: true
restart: true
¶ Opening firewall for node-red
To connect to node-red web interface, we need to open the node-red port.
Security consideration:
This is for demonstration purpose. Do not use as this in a production environment.
cat > node-red.rules << EOF
*filter
-A INPUT -p tcp --dport 1880 -j ACCEPT
COMMIT
EOF
mv node-red.rules /etc/iptables/iptables.d/
systemctl restart iptables
- name: Allow node-red connection
groups:
- all
tasks:
- !external
use: copycontent
name: "Open firewall for node-red"
params:
dest: "/etc/iptables/iptables.d/node-red.rules"
content: |
*filter
-A INPUT -p tcp --dport 1880 -j ACCEPT
COMMIT
- !sd_service
name: Reload firewall
service: iptables
enabled: true
restart: true
¶ Deploy a demonstration flow into node-red
¶ Management interface
The interface is now available from your gateway webui#hostname-url on the 1880 port.
Example:
- A Wirnet™ iFemtoCell has a board ID of 704BEc1234AB (and 7276FF00391234AB as EUI64)
- NodeRed interface URL is http://klk-wifc-1234AB.local:1880/
¶ Demonstration flow
In the following demonstration flow, you will find an MQTT registration to get all uplink messages from our LoRaWAN test device, unpack the data, and trigger a ntfy notification when the device transmits a message following a push on its test button.
You will also find an example of a downlink message from the gateway to the device. A click on the left square next to the "on" and "off" boxes will respectively provision a downlink command in Chirpstack LNS to enable or disable the LED of our test device.
Import our example into node-red and get started:
- Copy the text of our example below
- Go to the Import menu of node-red and paste the text as JSON
- Deploy
Please refer to node-red documentation on how to import a node-red flow.
You will have to adapt the logic to your setup:
- According to your LoRaWAN device payload format
- With your Chirpstack Application ID in the downlink logic
Demo flow example - which connects to MQTT, receives messages from a device, and sends it to ntfy
[
{
"id": "193fbdbd9c664d13",
"type": "tab",
"label": "Flow 1",
"disabled": false,
"info": "",
"env": []
},
{
"id": "f381210bac9b8559",
"type": "subflow",
"name": "ntfy",
"info": "set msg.payload to content\nset msg.topic to topic",
"category": "",
"in": [
{
"x": 60,
"y": 80,
"wires": [
{
"id": "340242d93be4e1bd"
}
]
}
],
"out": [
{
"x": 580,
"y": 80,
"wires": [
{
"id": "937457591f52cf96",
"port": 0
}
]
}
],
"env": [],
"meta": {},
"color": "#DDAA99"
},
{
"id": "9b5169040f2e5f61",
"type": "mqtt-broker",
"name": "",
"broker": "127.0.0.1",
"port": "1883",
"clientid": "",
"autoConnect": true,
"usetls": false,
"protocolVersion": "4",
"keepalive": "60",
"cleansession": true,
"birthTopic": "",
"birthQos": "0",
"birthPayload": "",
"birthMsg": {},
"closeTopic": "",
"closeQos": "0",
"closePayload": "",
"closeMsg": {},
"willTopic": "",
"willQos": "0",
"willPayload": "",
"willMsg": {},
"userProps": "",
"sessionExpiry": ""
},
{
"id": "340242d93be4e1bd",
"type": "function",
"z": "f381210bac9b8559",
"name": "function 1",
"func": "msg.url = \"https://ntfy.sh/\" + msg.topic\nmsg.headers = {};\nmsg.headers['X-Title'] = 'Kerlink Demo';\nmsg.headers['Icon'] = 'https://www.kerlink.com/wp-content/themes/ci_kerlink/images/favicon.ico'\nmsg.headers['Tags'] = 'rotating_light'\nreturn msg;",
"outputs": 1,
"noerr": 0,
"initialize": "",
"finalize": "",
"libs": [],
"x": 200,
"y": 80,
"wires": [
[
"937457591f52cf96"
]
]
},
{
"id": "937457591f52cf96",
"type": "http request",
"z": "f381210bac9b8559",
"name": "",
"method": "POST",
"ret": "txt",
"paytoqs": "ignore",
"url": "",
"tls": "",
"persist": false,
"proxy": "",
"insecureHTTPParser": false,
"authType": "",
"senderr": false,
"headers": [],
"x": 390,
"y": 80,
"wires": [
[]
]
},
{
"id": "6bcf54eee5b8dcca",
"type": "mqtt in",
"z": "193fbdbd9c664d13",
"name": "wal-e message up",
"topic": "application/+/device/7076ff004d040032/event/up",
"qos": "2",
"datatype": "auto-detect",
"broker": "9b5169040f2e5f61",
"nl": false,
"rap": true,
"rh": 0,
"inputs": 0,
"x": 190,
"y": 240,
"wires": [
[
"27629ab6b4f065d7"
]
]
},
{
"id": "27629ab6b4f065d7",
"type": "function",
"z": "193fbdbd9c664d13",
"name": "wal-e data unpack",
"func": "const buf = Buffer.from(msg.payload.data, 'base64');\nvar newpayload = {}\nnewpayload.version = buf.readInt16LE(0)\nnewpayload.eventsrc = buf.readInt16LE(2)\nnewpayload.temp = (buf.readInt16LE(4)*0.1)\nnewpayload.hum = (buf.readInt16LE(6)*0.1)\nnewpayload.volt = (buf.readInt16LE(8)/1000.0)\nnewpayload.data = Buffer.from(msg.payload.data, 'base64').toString('hex');\nmsg.payload = newpayload\nreturn msg;",
"outputs": 1,
"noerr": 0,
"initialize": "",
"finalize": "",
"libs": [],
"x": 410,
"y": 240,
"wires": [
[
"bedb6d28236f99dd"
]
]
},
{
"id": "bedb6d28236f99dd",
"type": "switch",
"z": "193fbdbd9c664d13",
"name": "",
"property": "payload.eventsrc",
"propertyType": "msg",
"rules": [
{
"t": "eq",
"v": "0",
"vt": "str"
},
{
"t": "eq",
"v": "1",
"vt": "str"
},
{
"t": "eq",
"v": "2",
"vt": "str"
},
{
"t": "else"
}
],
"checkall": "false",
"repair": false,
"outputs": 4,
"x": 590,
"y": 240,
"wires": [
[],
[],
[
"d142ee8d2ab53e58"
],
[]
]
},
{
"id": "d142ee8d2ab53e58",
"type": "change",
"z": "193fbdbd9c664d13",
"name": "",
"rules": [
{
"t": "set",
"p": "payload",
"pt": "msg",
"to": "button alert",
"tot": "str"
},
{
"t": "set",
"p": "topic",
"pt": "msg",
"to": "kerlinkdemo",
"tot": "str"
}
],
"action": "",
"property": "",
"from": "",
"to": "",
"reg": false,
"x": 780,
"y": 300,
"wires": [
[
"e7dcbc0b61ccc662"
]
]
},
{
"id": "e7dcbc0b61ccc662",
"type": "subflow:f381210bac9b8559",
"z": "193fbdbd9c664d13",
"name": "ntfy",
"x": 950,
"y": 300,
"wires": [
[]
]
},
{
"id": "a8ef637d8c6bad1c",
"type": "inject",
"z": "193fbdbd9c664d13",
"name": "trigger manually",
"props": [
{
"p": "payload"
},
{
"p": "topic",
"vt": "str"
}
],
"repeat": "",
"crontab": "",
"once": false,
"onceDelay": 0.1,
"topic": "kerlinkdemo",
"payload": "nodered alert",
"payloadType": "str",
"x": 560,
"y": 300,
"wires": [
[
"d142ee8d2ab53e58"
]
]
},
{
"id": "94180ba5574c08a5",
"type": "mqtt out",
"z": "193fbdbd9c664d13",
"name": "wal-e message down",
"topic": "application/4b1cc342-885d-43de-98a7-eb91aae07d88/device/7076ff004d040032/command/down",
"qos": "",
"retain": "",
"respTopic": "",
"contentType": "",
"userProps": "",
"correl": "",
"expiry": "",
"broker": "9b5169040f2e5f61",
"x": 440,
"y": 420,
"wires": []
},
{
"id": "7e968cb850874d2b",
"type": "inject",
"z": "193fbdbd9c664d13",
"name": "on",
"props": [
{
"p": "payload"
},
{
"p": "topic",
"vt": "str"
}
],
"repeat": "",
"crontab": "",
"once": false,
"onceDelay": 0.1,
"topic": "",
"payload": "{\"devEui\":\"7076ff004d040032\",\"confirmed\":false,\"fPort\":1,\"data\":\"AQ==\"}",
"payloadType": "json",
"x": 250,
"y": 380,
"wires": [
[
"94180ba5574c08a5"
]
]
},
{
"id": "707146799641ee9c",
"type": "inject",
"z": "193fbdbd9c664d13",
"name": "off",
"props": [
{
"p": "payload"
},
{
"p": "topic",
"vt": "str"
}
],
"repeat": "",
"crontab": "",
"once": false,
"onceDelay": 0.1,
"topic": "",
"payload": "{\"devEui\":\"7076ff004d040032\",\"confirmed\":false,\"fPort\":1,\"data\":\"AA==\"}",
"payloadType": "json",
"x": 250,
"y": 460,
"wires": [
[
"94180ba5574c08a5"
]
]
}
]
¶ Install the notification application
ntfy (pronounced notify) is a simple HTTP-based pub-sub notification service. It allows you to send notifications to your phone or desktop via scripts from any computer, and/or using a REST API.
As a demonstration, we are here using it to send notification from the gateway directly to your end-user device.
In our example we use the
kerlinkdemotopic, but please feel free to adapt the topic to your needs.
¶ Extend your Small Private Network with Follower gateways
The "Follower" gateway is a gateway which is essentially forwarding collected LoRaWAN frames to a leader gateway hosting the LNS.
¶ Configure the Leader gateway's firewall rules to accept connections from Follower gateways
If you wish to connect another gateway as a follower, you need to open the MQTT port in the leader gateway.
Security consideration:
This is for demonstration purpose. Do not use as this in a production environment.
Execute the following sample in the leader gateway to configure the firewall.
cat > mosquitto.rules << EOF
*filter
-A INPUT -p tcp --dport 1883 -j ACCEPT
COMMIT
EOF
mv mosquitto.rules /etc/iptables/iptables.d/
systemctl restart iptables
- name: Allow mqtt conection
groups:
- all
tasks:
- !external
use: copycontent
name: "Open firewall for mosquitto"
params:
dest: "/etc/iptables/iptables.d/mosquitto.rules"
content: |
*filter
-A INPUT -p tcp --dport 1883 -j ACCEPT
COMMIT
- !sd_service
name: Reload firewall
service: iptables
enabled: true
restart: true
¶ Install and configure the LoRaWAN forwarder in Followers
Execute the sample from this section edge-computing#install-the-lorawan-forwarder in the Follower gateway.
apt update
apt install chirpstack-mqtt-forwarder
# Adapt LEADER_IP_ADDR to Hostname or IP of your leader gateway
# LEADER_IP_ADDR=myLeaderGW
# Adapt topic_prefix if needed (us915_0,as923,...)
cat > leader_config.toml << EOF
[mqtt]
topic_prefix = "eu868"
server = "tcp://${LEADER_IP_ADDR:=localhost}:1883"
EOF
conflex -t -o chirpstack-mqtt-forwarder.toml -T /usr/share/chirpstack-mqtt-forwarder/template.hb leader_config.toml
mv chirpstack-mqtt-forwarder.toml /etc/chirpstack-mqtt-forwarder/chirpstack-mqtt-forwarder.toml
systemctl enable chirpstack-mqtt-forwarder --now
- name: Setup a follower gateway
groups:
- all
defaults:
mqtt:
topic: "eu868"
server: "localhost:1883"
tasks:
- !shell
name: update repo
cmd: apt update
- !apt
name: Install chirpstack-mqtt-forwarder
package: chirpstack-mqtt-forwarder
- !template
name: Configure chirpstack-mqtt-forwarder
src: /usr/share/chirpstack-mqtt-forwarder/template.hb
dest: /etc/chirpstack-mqtt-forwarder/chirpstack-mqtt-forwarder.toml
- !sd_service
name: Restart chirpstack-mqtt-forwarder
service: chirpstack-mqtt-forwarder
enabled: true
restart: true
¶
Make sure to specify the leader "server": Replace "localhost" by your leader gateway address in our playbook sample, for example with "klk-wifc-XXXXXX:1883.