-
**Summary:**
Apart from isolated unit tests should contain flow tests, where various common/expected flows are tested. For example in NS context that could be an example:
1. Create a device via…
-
**Summary:**
The device registries will prompt an error on `PUT` operations when the payload does not at least contain a `join_eui` or `dev_eui`, even though the route contains the device id.
**Ste…
-
Think I have to explain what I mean with the title...
As far as I recall it is best practice to join a network as few as possible maybe just once when the device is provisioned.
That is why certain …
-
**Summary:**
The CLI is getting commands for simulating LoRaWAN traffic, but currently only joins and (un)confirmed data messages are supported. We should add support for rejoins as well.
…
-
#### Summary
Simulate uplink and schedule downlink based on examples declared in the device repository.
#### Why do we need this?
To make it really easy to test integrations.
#### …
-
#### Summary
Alerting gateways UP or DOWN in TTN V3 (connected versus disconnected)
Feature: sent an email when status af gateways change (name and current status (from UP tot DOWN of from DOWN …
-
I am trying to get lorawan support working. I have setup a local chirpstack instance, with `chirpstack-network-server` `chirpstack-application-server` and `chirpstack-gateway-bridge` running. I can se…
-
#### Summary
Class B-related options should be available and configurable on gateways
References #19 https://github.com/TheThingsNetwork/lorawan-stack/pull/1747
#### Why do we need thi…
-
**Summary:**
- We should have release notes for new versions
- These release notes cannot be linked to the public repository GitHub releases, as some functionality is in this private repository
- …
-
This will involve wireless communication so there can be several ways to do this. We need to consider how we will preserve signal integrity when transmitting and if it's worth it to build a new PCB ju…