Thank You for the explanation.
↧
Replacing gateway
↧
Commercial Analog output LoRaWAN Controller (0-10V dc) AS923
I’ve seen a LED lighting controller with 0-10V DC output
but its a 240VAC powered which is not desirable in HVAC ducts as supply is 12VDC
↧
↧
Getting "Drop uplink message" with "Join server not found" in V3
Hi, I’m having the same issue. I’m trying to deploy a private TTN enviroment with the stack v3.8.4 and I managed to configure the gateway. Now I’m trying to join a device.
I have a Multitech Conduit AEP as gateway, configured with packet forwarding as says the guide.
In the other side I have an Adeunis pulse sensor with OTAA verification, I registered to an App following the console guide.
Right now I’m stuck because I don’t know what to check to resolve this join fail of the device.
This is the activity of the device (image attatched):
Thanks,
↧
Getting "Drop uplink message" with "Join server not found" in V3
The stack is running in a local environment. This is the Ip of the pc so gateway can see my machine.
This is the gateway view after receiving the device uplink:
This is the rellevant information about device configuration:
↧
Getting "Drop uplink message" with "Join server not found" in V3
Hey @MarcRomero, Are you running in docker? I had the issue and unticked “External Join Server” but if you are using an external join server than i’m not sure but would make sure the correct ports are open. think its 8001 from memory.
↧
↧
Getting "Drop uplink message" with "Join server not found" in V3
Hi @dbrosy, Yes I’m runing it in docker, I dont think I’m using an “External Join Server”. The machine with stack and gateway are runing on a local network.
This are the servers (all are at 192.168.124.9:1885):
Sorry If I’m not specifig but I’ve just started to test the stack v3 and I dont know all its funcionalitys.
↧
LoRaWAN Academy - AWS stack error
Hi @johan,
I’ve just tried to setup an new environment and am getting this error for v2.15.4 running Go 1.14.3. It looks like this deprecated in favour of v2.15.5 running Go 1.14.4.
“No Solution Stack named ‘64bit Amazon Linux 2018.03 v2.15.4 running Go 1.14.3’ found”
Can you advise when the CF stack will be updated please?
TIA!
Matt…
↧
ADR and gateway distance
As for the data rate for OTAA, Semtech writes in Joining and Rejoining:
In addition to random frequency selection, randomly selecting available DataRates (DRs) for the region that you want is also important.
Note: It is important to vary the DR. If you always choose a low DR, join requests will take much more time on air. Join requests will also have a much higher chance of interfering with other join attempts as well as with regular message traffic from other devices. Conversely, if you always use a high DR and the device trying to join the network is far away from the LoRaWAN gateway or sitting in an RF-obstructed or null region, the gateway may not receive a device’s join request. Given these realities, randomly vary the DR and frequency to defend against low signals while balancing against on-air time for join requests.
And as for ADR acknowledgements:
The same strategy is indeed explained in Semtech’s Understanding ADR:
If no answer is received from the network server by the time the acknowledgement delay period has expired, the data rate will automatically be reduced by one step, as illustrated in Figure 8.
Figure 8After this one-step data rate reduction, the end device continues sending messages to the server (at this new, lower, data rate) requesting an ADR acknowledgement. Once an acknowledgement is received, the end device uses the new, server-determined, data rate until it receives an instruction to change it again via the normal ADR mechanism. However, if no answer is forthcoming, the end device continues to ratchet down the data rate, step by step, until it gets a response or, assuming the device and network are in Europe, until it reaches SF12 (Figure 9).
Note: The highest spreading factor that can be used with LoRaWAN varies by region, for instance in the USA, the highest SF is SF10.
Figure 9
Just like in the LoRaWAN specifications: not a word about the transmission power.
↧
Getting "Drop uplink message" with "Join server not found" in V3
This is mine.
not sure why all your Components are showing the same port as acording toconfig they should have different ports
post your config file as i suspect there is some issues with it. you will need to redact it
↧
↧
Getting "Drop uplink message" with "Join server not found" in V3
This is the config out of runing “sudo docker-compose run --rm stack config”:
config.txt (21.1 KB)
I supose data comes from docker-compose.yml:
version: '3.7'
services:
# If using CockroachDB:
cockroach:
image: cockroachdb/cockroach
command: start --http-port 26256 --insecure
restart: unless-stopped
volumes:
- ./data/cockroach:/cockroach/cockroach-data
ports:
- "127.0.0.1:26257:26257" # Cockroach
- "127.0.0.1:26256:26256" # WebUI
redis:
image: redis
command: redis-server --appendonly yes
restart: unless-stopped
volumes:
- ./data/redis:/data
ports:
- "127.0.0.1:6379:6379"
stack:
image: thethingsnetwork/lorawan-stack:latest
entrypoint: ttn-lw-stack -c /config/ttn-lw-stack.yml
command: start
restart: unless-stopped
depends_on:
- redis
# If using CockroachDB:
- cockroach
# If using PostgreSQL:
# - postgres
volumes:
- ./blob:/srv/ttn-lorawan/public/blob
- ./config/stack:/config:ro
# If using Let's Encrypt:
- ./acme:/var/lib/acme
environment:
TTN_LW_BLOB_LOCAL_DIRECTORY: /srv/ttn-lorawan/public/blob
TTN_LW_REDIS_ADDRESS: redis:6379
TTN_LW_IS_DATABASE_URI: postgres://root@cockroach:26257/ttn_lorawan?sslmode=disable
ports:
# If deploying on a public server:
# - "80:1885"
# - "443:8885"
- "1881:1881"
- "8881:8881"
- "1882:1882"
- "8882:8882"
- "1883:1883"
- "8883:8883"
- "1884:1884"
- "8884:8884"
- "1885:1885"
- "8885:8885"
- "1887:1887"
- "8887:8887"
- "1700:1700/udp"
# If using (self) signed certificates:
#secrets:
# - cert.pem
# - key.pem
# If using (self) signed certificates:
#secrets:
# cert.pem:
# file: ./cert.pem
# key.pem:
# file: ./key.pem
And from ttn-lw-stack.yml:
log:
level: "debug"
# Redis configuration
redis:
address: 'redis:6379'
# Identity Server configuration
is:
# If using CockroachDB
database-uri: 'postgres://root@cockroach:26257/ttn_lorawan?sslmode=disable'
# Email configuration for "thethings.example.com"
email:
sender-name: 'The Things Stack'
sender-address: 'noreply@192.168.124.9:1885'
network:
name: 'The Things Stack'
console-url: 'http://192.168.124.9:1885/console'
identity-server-url: 'http://192.168.124.9:1885/oauth'
# Web UI configuration for "thethings.example.com":
oauth:
ui:
canonical-url: 'http://192.168.124.9:1885/oauth'
is:
base-url: 'http://192.168.124.9:1885/api/v3'
# HTTP server configuration
http:
cookie:
# generate 32 bytes (openssl rand -hex 32)
block-key: '423aa334b3c6ef6ffbc802fdcd9cdd6a1eff1258ee03576630f04738b37f4373'
# generate 64 bytes (openssl rand -hex 64)
hash-key: '949f699b8c18b40a06a001d4e0c5710cbe726f587bc5e192bc850fd25d23e27405d92095366b7026db8da524ccad259ebd253e7638eb8f28fcee002b84db4fc9'
metrics:
password: 'metrics' # choose a password
pprof:
password: 'pprof' # choose a password
# If using (self) signed certificates:
# tls:
# source: file
# root-ca: ./cert.pem
# certificate: ./cert.pem
# key: ./key.pem
# Let's encrypt for "thethings.example.com"
tls:
source: 'acme'
acme:
dir: '/var/lib/acme'
email: 'you@thethings.example.com'
hosts: ['thttp://192.168.124.9:1885']
default-host: 'http://192.168.124.9:1885'
# If Gateway Server enabled, defaults for "thethings.example.com":
gs:
mqtt:
public-address: '192.168.124.9:1882'
public-tls-address: '192.168.124.9:8882'
mqtt-v2:
public-address: '192.168.124.9:1881'
public-tls-address: '192.168.124.9:8881'
# If Gateway Configuration Server enabled, defaults for "thethings.example.com":
gcs:
basic-station:
default:
lns-uri: 'wss://192.168.124.9:8887'
the-things-gateway:
default:
mqtt-server: 'mqtts://192.168.124.9:8881'
# Web UI configuration for "thethings.example.com":
console:
ui:
canonical-url: 'http://192.168.124.9:1885/console'
is:
base-url: 'http://192.168.124.9:1885/api/v3'
gs:
base-url: 'http://192.168.124.9:1885/api/v3'
ns:
base-url: 'http://192.168.124.9:1885/api/v3'
as:
base-url: 'http://192.168.124.9:1885/api/v3'
js:
base-url: 'http://192.168.124.9:1885/api/v3'
qrg:
base-url: 'http://192.168.124.9:1885/api/v3'
edtc:
base-url: 'http://192.168.124.9:1885/api/v3'
oauth:
authorize-url: 'http://192.168.124.9:1885/oauth/authorize'
#logout-url: 'http://192.168.124.9:1885/oauth/logout'
token-url: 'http://192.168.124.9:1885/oauth/token'
client-id: 'console'
client-secret: 'console' # choose or generate a secret
I hope this helps, I defined the urls as 192.168.124.9:1885 because gateway couldn’t see the localhost url.
↧
Dragino Lps8 position
Hello dear forum,
I recently bought a Dragino Lps8 gateway.
So my problem, if I now want to use TTN-Mapper (on the iPhone), TTN-Mapper only shows me one data point to no gateway. I entered the coordinates of Google Maps in the gateway.
Where can I now set that my gateway also sends its coordinates?
Lg Tom
↧
Dragino Lps8 position
Please note we’re an English forum, so please edit your message to rewrite in English for future readers.
That said: this is a known issue for MQTT-enabled gateways since May 11th. So, I guess yours uses MQTT as well?
↧
Calculating the time between two packets (TTN + Node-RED)
I’m using a RN2483 which fires a packet with current time in milliseconds as the payload. Upon arrival the ‘delay’ is calculated and displayed, it keeps track of cur/min/max/avg and lost ‘packets’ pretty similar to a ping. In below data you can see it can take up to 25 seconds before it arrives, but on average it takes 531 milliseconds.
2020-07-07 12:25:34.330418 mac tx uncnf 100 7a32cf2873010000
2020-07-07 12:25:34.827556 *********/devices/******/up - received 3413, lost 7, on 2 gateways 'eui-1dee192e3d82b8e4' 'ttn-1424ar-001', rtt cur/min/avg/max 460/359/531/25727
2020-07-07 12:25:36.483470 transmission successful
2020-07-07 12:25:36.484862 up=4067, down=9, mac_tx=2154↧
↧
Sensor node for liquid level measurement
Hello,
I’m looking for a LoRa sensor (TTN) for liquid level measurement. I have to constantly check the water level in the pump and send a message when the level reaches a minimum and maximum value. This is especially important for my project because I try to implement a network of sensors wherever possible (e.g. I am currently using Laird nodes for temperature measurement). In other words, as a designer I build proof-of-concept. Can you recommend any devices at an average price? Nodes operated by Cayenne will be welcome. 
↧
Data backup on Gateway in case of network outage?
@ descartes Hi the time stamp in the RAK store and forward backup, is a time delta in micro secs between last packet sent and current. So you have to do a bit work on on your backend to re-hydrate correct time stamp after an backhall outage.
The issue for many of us who use cellular backhall as default, is to get over the flowing. But brings it’s own issues.
// Corp
IT: Gateway can’t be on corp lan/wan must be hidden (often in a ceiling void)
Cyber security: Gateway can Never be on lan/wan or only after 3 months of sec evaluation
// Medium sized enterprise:
You will have to talk to Dave, he’s real busy always got a lot on…
// Small biz
Ow my niece does the IT after school on Thursdays
However, even why you have a wired backhall I’ve encountered the following issues…
- Gateway stolen
- Power turned off at weekends
- Hairy arsed electricians pulling out power cables to gateways as it was needed for something else
↧
Data backup on Gateway in case of network outage?
Had a client that would call to say the server was down around 5pm each day - turned out the cleaner was removing the note about not unplugging it …
So for all those situations where the gateway goes awol for what ever reason, my scheme of keeping data points on the device (subject to power & cost issues), seems like a plan.
↧
ADR and gateway distance
Some join sequences seem to hit the same SF several times before moving on - a quick run through from to 7 to 0 would seem more efficient, possibly trying a couple of times at the 7, 8 & 9, travelling hopeful, before using up air time & battery banging away at SF12 in vain.
Then perhaps backoff for many multiples of the configured send interval rather than fruitlessly trying just a few moments later.
↧
↧
Data backup on Gateway in case of network outage?
I’d say it’s not worth the trouble of duplicated administration, required for decryption. And above all: LoRaWAN being radio in a license-free spectrum, maybe one should not rely on the data to start with?
↧
LoRaWAN - Actuator Control Remotely
Hello, I am new to working with LoRaWAN. I have several questions about it. I have a LoRa CubeCell HTCC AB-01 module (Heltec) and a UG87 gateway (Ursalink). I am working with them to develop a remote control project for an actuator. The module can be programmed in Arduino IDE. I have run the tests using the examples provided by Arduino: LoRaSender, LoRaReceiver, Ping-Pong and LoRaWAN, and they have all worked in the module correctly. I would like to know some things:
-
How does the LoRaWAN sample code work? What exactly does it do? What does it consist of?
-
How to send the information that the module sends and that TTN receives to a local server to be able to work with it (manipulate, classify, filter, etc.)?
-
How to modify the code that is loaded to the module so that it can remotely control an actuator?
Any information you can offer me will be very helpful. Thank you.
↧
Data backup on Gateway in case of network outage?
Probably not. I suspect this is a confusion based on the free-running microsecond counter of the gateway concentrator chip, which is what the server uses to time downlink replies. It does not measure the time “since” a previous packet as that would break in the case of backhaul packet loss, it is merely a local counter stamp. And it’s the same thing a gateway normally sends when backhaul is live.
It does indeed take some doing to convert it into an actual time - you have to have a sample of both at at point in the same run of the same packet forwarder program, and enough sense of the time to know how many times it has rolled over. Uplink frame counts may make as much sense.
But this is also why someone who really wants a packet backup on the gateway should probably write their own. Including an RTC time is quite simple (and yes, if you’re going to this trouble you want a battery backed RTC and not a situation where you only have time after you can connect to an NTP server).
If you’re really stuck, put an RTC in a node and have it announce the time (doesn’t have to be right, just and monotonic) and use that as a time standard to measure other nodes’ packets by.
↧