-
Notifications
You must be signed in to change notification settings - Fork 12
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
Story: As a deployer, I want to provide a default list of IoT device models #217
Labels
enhancement
New feature or request
Milestone
Comments
What are common and should be provided by the template (not-modifiable by user):
For LoRa:
|
As a preconized solution :
|
This was referenced Feb 10, 2022
kbeaugrand
added
documentation
Improvements or additions to documentation
and removed
refinement
labels
Feb 10, 2022
9 tasks
kbeaugrand
moved this from :pencil: Todo
to :construction: In Progress
in IoT Hub Portal
Feb 14, 2022
kbeaugrand
moved this from :construction: In Progress
to :speech_balloon: Ready for Review
in IoT Hub Portal
Feb 14, 2022
Hi @Metal-Mighty and @adcoly, I provided a new version on our preview environment. You can find in our documentation the related APIs that are provided: Could you verify if that fit the needs we discussed ? Regards, |
kbeaugrand
added
enhancement
New feature or request
and removed
documentation
Improvements or additions to documentation
labels
Feb 14, 2022
kbeaugrand
moved this from :speech_balloon: Ready for Review
to :rocket: Ready
in IoT Hub Portal
Feb 18, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
While deploying the solution, the deploy should provide some templates to the users that are validated.
He also need to update them if needed (when a device change, new commands available, ...).
End users may not be able to modify default templates after the installation.
However, in case of LoRa devices they should be able to add commands that are not present in the default template.
Acceptance criteria
The text was updated successfully, but these errors were encountered: