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

Bug: The property ClassType of a lorawan device is not mapped to a twin device #1274

Closed
hocinehacherouf opened this issue Sep 21, 2022 · 0 comments · Fixed by #1286
Closed
Assignees
Labels
bug Something isn't working
Milestone

Comments

@hocinehacherouf
Copy link
Contributor

hocinehacherouf commented Sep 21, 2022

Remarks:

  • The property ClassType is only refereced on frontend layer.
  • The backend doesnt implement any mapping of the property ClassType between lorawan device and twin device.
@hocinehacherouf hocinehacherouf added the bug Something isn't working label Sep 21, 2022
@hocinehacherouf hocinehacherouf changed the title Bug: The property ClassType of a lorawan device is not mapped to a device twin Bug: The property ClassType of a lorawan device is not mapped to a twin device Sep 21, 2022
@kbeaugrand kbeaugrand added this to the S40 milestone Sep 22, 2022
@kbeaugrand kbeaugrand self-assigned this Sep 22, 2022
@kbeaugrand kbeaugrand moved this to 📝 Todo in IoT Hub Portal Sep 22, 2022
@hocinehacherouf hocinehacherouf moved this from 📝 Todo to 🚧 In Progress in IoT Hub Portal Sep 26, 2022
@hocinehacherouf hocinehacherouf moved this from 🚧 In Progress to 💬 Ready for Review in IoT Hub Portal Sep 26, 2022
kbeaugrand pushed a commit that referenced this issue Sep 27, 2022
* Add missing mapping on ClassType between lorawan and twin #1274

* Remove unused mapping on property ClassType
@kbeaugrand kbeaugrand moved this from 💬 Ready for Review to 🚀 Ready in IoT Hub Portal Sep 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: 🚀 Ready
Development

Successfully merging a pull request may close this issue.

2 participants