-
Notifications
You must be signed in to change notification settings - Fork 311
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
New gateway registration flow (Console) #3947
Comments
Let's start with this indeed. Do you need a list of fields that are advanced, with their default values? That would eliminate already some fields that are always shown now. |
Other things in scope:
|
Should we triage this then? @NicolasMrad |
Here's the scaffold I would suggest for this: Let me know if you have any questions. You can also refer to my comment on end device onboarding. Many notes are relevant for this as well. Again, here's the full wireframe: Note that there are two onboarding flows, based on whether the gateway is claimable or not ( |
References also TheThingsNetwork/lorawan-devices#124. If there's anything needed that is generic for a particular gateway and model, we might want to load that from the device repository too. |
The new gateway onboarding foundation (as laid out here: #3947 (comment)) was just merged and is now available in OS and Enterprise. I'm leaving this issue open since there are still some missing bits:
@mjamescompton is currently working on updating the documentation accordingly. |
The two remaining items here depend on https://github.com/TheThingsIndustries/lorawan-stack/issues/2018. I'm removing the milestone on this until we resolve the blocker. |
I would even suggest to close this and track the rest of the progress in #2018 and a new issue once this is resolved. |
Summary
Congruently to #3522, we also want to revisit the gateway registration flow, which is currently too verbose and has many options that are usually not relevant during registration. Additionally, we can use templates of the device repository once we add support for gateways.
Why do we need this?
Gateway onboarding is currently not smooth.
What is already there? What do you see now?
Gateway registration using the gateway registration form.
What is missing? What do you want to see?
How do you propose to implement this?
This issue is currently still a bit of a stub. I will follow up timely with wireframes to make this issue actionable. Implementation will likely happen in two stages:
How do you propose to test this?
While doing so, we should also extend the gateway end-to-end tests accordingly.
Can you do this yourself and submit a Pull Request?
I'll follow up with the wireframes and then we can decide who picks up the implementation.
The text was updated successfully, but these errors were encountered: