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

OMA LwM2M Registry API returns XML documentation page instead of JSON metadata for object definitions #785

Open
moise-iot opened this issue Oct 30, 2024 · 3 comments

Comments

@moise-iot
Copy link

moise-iot commented Oct 30, 2024

Registration Information

When querying the OMA LwM2M Registry API to retrieve the definition of an object, the response retrieve is the documentation xml page instead of the expected JSON file containing metadata information the Object. This issue occurs across the majority of API calls, even though the documentation specifies JSON as the expected response format

Step to reproduce

  1. Use the API endpoint (e.g., http://www.openmobilealliance.org/api/lwm2m/v1/Object?ObjectID=3) to retrieve an object's definition.

  2. Observe that the response returns an XML path rather than JSON.

image

Expected Behavior:

The API should return the object's metadata in JSON format, as outlined in the OMA documentation.

Actual Behavior:

The API responds with an XML documentation page.

Concept Description
Number of Object(s) or Reusable Resource(s) to register 3
Name of SDO, Company or individual IoTerop
Object Name (as defined in the .xml file) Device
Short Object description, to be used in the public registry (max 134 characteres) This LwM2M Object provides a range of device related information which can be queried by the LwM2M Server, and a device reboot and factory reset function
@jpradocueva
Copy link
Member

@moise-iot thanks for raising this issue. We are working in some redirects and this one went wrong. We will address it soon.

@moise-iot
Copy link
Author

thank you

@jpradocueva
Copy link
Member

@moise-iot, this problem was resolved last night. It should be working ok. Otherwise, please email me at [email protected]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants