Trigger video capture operation locally on a tedge enabled raspi 5 via MQTT

[benjamin.ruoff]

Hi @Vachaspati_Diwevedi2 thank you for your answer but where should I get this operation ID from?

According to Reuben’s explanation here:

How to get the specific ID of an Operation via SmartRest

If you’re using thin-edge.io (>= 1.4.x), then you don’t have to worry about any of this. By default thin-edge.io subscribes to the devicecontrol/notifications topic which is the Cumulocity operations in JSON format. On a device, you can checkout the MQTT message being received and sent to the server by just subscribing to the local MQTT broker. The exert below shows the configuration snapshot operation being received by thin-edge.io, the mapper converts the message to a thin-edge.io message, th…

the device does not need to provide or know any operation ID when triggering an operation locally. thin-edge handles the entire operation lifecycle internally.

As far as I understand it, since I want to trigger the operation locally via MQTT on thin-edge, without using the Cumulocity REST API, I should not need to provide an operation ID at all — that part should be fully managed by thin-edge + Cumulocity.

But after checking the c8y_VideoCapture.template and reading Reubens post, it also seems that the operation is expected to be triggered by publishing to

/devicecontrol/notifications

which I still need to try out.

Could you confirm that this interpretation is correct and maybe share a minimal working example of the exact MQTT payload required for c8y_VideoCapture?