Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simulate uplinks in the console #2234

Closed
kschiffer opened this issue Mar 25, 2020 · 4 comments · Fixed by #3266
Closed

Simulate uplinks in the console #2234

kschiffer opened this issue Mar 25, 2020 · 4 comments · Fixed by #3266
Assignees
Labels
c/application server This is related to the Application Server c/console This is related to the Console compat/api This could affect API compatibility in progress We're working on it ui/web This is related to a web interface

Comments

@kschiffer
Copy link
Member

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:
image

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 kschiffer added c/console This is related to the Console ui/web This is related to a web interface labels Mar 25, 2020
@kschiffer kschiffer added this to the Next Up milestone Mar 25, 2020
@kschiffer kschiffer self-assigned this Mar 25, 2020
@johanstokking johanstokking added c/application server This is related to the Application Server compat/api This could affect API compatibility labels Mar 25, 2020
@johanstokking
Copy link
Member

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.

@laurensslats
Copy link

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.

@kschiffer kschiffer removed their assignment Jun 19, 2020
@kschiffer
Copy link
Member Author

@adriansmares please reassign me once the AppAs support is done. Happy to pick this up directly thereafter.

@adriansmares adriansmares modified the milestones: Next Up, July 2020 Jul 14, 2020
@adriansmares adriansmares mentioned this issue Jul 15, 2020
5 tasks
@adriansmares
Copy link
Contributor

@adriansmares please reassign me once the AppAs support is done. Happy to pick this up directly thereafter.

The API has been added in #2919

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c/application server This is related to the Application Server c/console This is related to the Console compat/api This could affect API compatibility in progress We're working on it ui/web This is related to a web interface
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants