From 29220f47b7ad4687b052b78fe8811667324a8c35 Mon Sep 17 00:00:00 2001 From: Medad Newman Date: Mon, 2 May 2022 21:37:12 +0100 Subject: [PATCH] remove I --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index c1b5a5e..cccf06d 100644 --- a/README.md +++ b/README.md @@ -35,7 +35,7 @@ Steps to deploy the application: # Usage with Helium Network -The key difference between using The Things Network and the Helium Network MQTT intergration is The Things Network hosts their packet broker, while the helium network does not. Therefore, we have to setup our own packet broker, and get Helium to and TTNhabbridge to connect to it. I have here a few steps on how to do it. +The key difference between using The Things Network and the Helium Network MQTT intergration is The Things Network hosts their packet broker, while the helium network does not. Therefore, we have to setup our own packet broker, and get Helium to and TTNhabbridge to connect to it. Here a few steps on how to do it. 1. Setup a MQTT packet broker on machine with port 1883 open to the internet. Docker is the simplest way to do it. Run the following command, changing the `` and `` password fields to something secret : ``` @@ -64,7 +64,8 @@ docker run \ thethingsnetwork: url: "tcp://eu1.cloud.thethings.network" user: "icss-lora-tracker@ttn" - pass: "NNSXS.JDUJCMUYUNDVPIOZ53TN6GBTT2P74NBH5FZXYXQ.OCWSRRQ4E46M5OMNATY35GJ6lkaBH6MOWZ5QFP32DMLP823S6M2A" + pass: "NNSXS.JDUJCMUYUNDVP + OZ53TN6GBTT2P74NBH5FZXYXQ.OCWSRRQ4E46M5OMNATY35GJ6lkaBH6MOWZ5QFP32DMLP823S6M2A" topic: "v3/+/devices/+/up" helium: url: "tcp://beta.medadnewman.co.uk:1887"