Lorawan-stack: Simulate uplinks in the console
Summary
We should provide functionality to simulate uplinks for end devices in the console.
Why do we need this?
- Helps users debugging their apps/end devices
- Close v2/v3 feature gap
What is already there? What do you see now?
Nothing of that sort. See also #2232
What is missing? What do you want to see?
UI to simulate uplinks on end device level, see v2:
Environment
v3.7.0
How do you propose to implement this?
Details to follow.
Can you do this yourself and submit a Pull Request?
Yes but anyone feel free to pick up.
kschiffer
All 4 comments
This needs AppAs support for a dry uplink.
@adriansmares in V2 this is quite hacky; afaik we generate some random metadata. What's most important is that we run the user specified frm_payload through the decoders and it becomes available like any other data uplink message. The purpose is to test decoders and integrations primarily.
johanstokking
on 25 Mar 2020
This is a much requested feature. Let's try focussing on this issue by the end of June / early July.
_The Docs-team is now starting with documentation creation on writing payload formatters._
laurensslats
on 11 Jun 2020
@adriansmares please reassign me once the AppAs support is done. Happy to pick this up directly thereafter.
kschiffer
on 19 Jun 2020
@adriansmares please reassign me once the
AppAssupport is done. Happy to pick this up directly thereafter.
The API has been added in #2919
adriansmares
on 17 Jul 2020
Related issues
johanstokking
·
8Comments
adriansmares
·
8Comments
htdvisser
·
9Comments
adamsondelacruz
·
7Comments
johanstokking
·
3Comments
Most helpful comment
This needs
AppAssupport for a dry uplink.@adriansmares in V2 this is quite hacky; afaik we generate some random metadata. What's most important is that we run the user specified
frm_payloadthrough the decoders and it becomes available like any other data uplink message. The purpose is to test decoders and integrations primarily.