Device registration and custom form

Hello,

I am pretty new to the platform, but after 2 days of searching the documentation and the forum, I don’t find an answer. My goal is to develop a server-side agent (according to the cumulocity terminology) to register special devices through the device registration pannel and custom forms.

I developed a microservice that reads from a MoM topic, containing information about a device I want to register. The microservice creates a registration for the device (/devicecontrol/newDeviceRequests), make a request to create credentials (/devicecontrol/deviceCredentials, that results in a 404 not found, but allows the registration status to change to PENDING_ACCEPTANCE). Then are my two problems :

  • When I click on “accept” in the device registration pannel of the UI, the device does not appear in the devices list, it is just marked as “ACCEPTED” in the registration view.
  • When I have to accept a device, I would like to create a custom form. I understand I need to do an extensibleDeviceRegistration application, but I find the documentation not very verbose on this subject.

What am I missing to add the registered device to my device list, and what steps should I follow to extend my registration form ?

Best regards

Hi @paul.de-la-porte-des,

Regarding the general single device registration: clicking on accept for the device registration, will not create the device.

The lifecycle is described quite well over here: REST - Cumulocity documentation

Once you press accept, the next time the device requests it’s device credentials via: /devicecontrol/deviceCredentials it would receive a set of credentials as part of the response.

With the newly received credentials the device would then be able to create a device representation of itself on its own.

The documentation for the extensible device registration is available here: Registering devices - Cumulocity documentation
Where exactly are you struggeling with?

Regards,

Tristan

Hello, thank you for your fast response. I’m struggling with the form itself. My metadata endpoint is called on device registration, it return basically the same payload as the example from the doc, and then instead of the form I get a loading toast saying “Saving the definition of the current registration form…” (translated from french, not literaly this). I don’t understand where the issue comes from