-
Notifications
You must be signed in to change notification settings - Fork 118
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
add lwM2M gateway design #879
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rhoninl added some comments
68f4f78
to
5622b6d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rhoninl added some comments, please take a look
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #879 /- ##
==========================================
Coverage 37.60% 37.93% 0.33%
==========================================
Files 46 46
Lines 2976 2976
==========================================
Hits 1119 1129 10
Misses 1737 1730 -7
Partials 120 117 -3 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rhoninl added some comments, please take a look
1. Start the LwM2M client and obtain all device information from deviceShifu. | ||
2. Register the device with the server and update the device information. | ||
3. Handle requests from the server. | ||
4. If the server enables the Observe feature, notify the server when data changes or a timeout occurs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
which timeout? do you mean there is an interval can be configured?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The interval is configured by the LwM2M server, but it resets whenever the data changes. i think interval is not good for this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
What this PR does / why we need it:
for deviceshifu only support http protocol and telemetryservice is hard to support lwM2M which protocol have pull and push at the same time
Will this PR make the community happier?
yes
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #How is this PR tested
documentation no need test
Special notes for your reviewer:
Release note: