You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
thin-edge.io should allow services to register support for operations via the /cmd/<command_name> topic, and such supported operations should be sent to the cloud.
Currently, if a service register a topic, the mapper will log the following error:
Nov 05 21:32:11 57e667c78707 tedge-mapper[337]: 2024-11-05T21:32:11.607598388Z ERROR c8y_mapper_ext::converter: Mapping error: Unexpected error: log_upload operation for services are currently unsupported
Below shows an example of what would be expected. The example shows a service registering support for the log_upload operation.
thin-edge.io should make no distinction between a service's or child devices when it comes to registering of commands (from the user's perspective).
Whilst the Cumulocity IoT device management UI does not currently allow users to send operations to devices, this is a purely UI limitation, and users are free to create their custom UI plugins to allow sending operations to services (as a service is just a managed object after all). See the additional context section for proof that the operations are sent to the correct thin-edge.io service entity.
Describe alternatives you've considered
Additional context
To verify that an operation created for a service does get sent to the device (with the proper external id of the service), a c8y_LogfileRequest operation was created and below is the received MQTT messages on the device. It shows that the tedge-mapper-c8y does also correctly map the incoming operation to the proper thin-edge.io topic id related to the service.
Is your feature request related to a problem? Please describe.
thin-edge.io should allow services to register support for operations via the
/cmd/<command_name>
topic, and such supported operations should be sent to the cloud.Currently, if a service register a topic, the mapper will log the following error:
Below shows an example of what would be expected. The example shows a service registering support for the log_upload operation.
tedge mqtt pub -r -q 1 te/device/main/service/nginx@nginx/cmd/log_upload '{"types":"container"}'
Describe the solution you'd like
thin-edge.io should make no distinction between a service's or child devices when it comes to registering of commands (from the user's perspective).
Whilst the Cumulocity IoT device management UI does not currently allow users to send operations to devices, this is a purely UI limitation, and users are free to create their custom UI plugins to allow sending operations to services (as a service is just a managed object after all). See the additional context section for proof that the operations are sent to the correct thin-edge.io service entity.
Describe alternatives you've considered
Additional context
To verify that an operation created for a service does get sent to the device (with the proper external id of the service), a
c8y_LogfileRequest
operation was created and below is the received MQTT messages on the device. It shows that the tedge-mapper-c8y does also correctly map the incoming operation to the proper thin-edge.io topic id related to the service.The text was updated successfully, but these errors were encountered: