-
**Is your feature improvement request related to a problem? Please describe.**
The custom operation is currently limited to SmartREST input and main device. Since we have workflow feature, mapper can…
-
Hi,
I use vcode for a multi module project [cumulocity-dynamic-mqtt-mapper](https://github.com/SoftwareAG/cumulocity-dynamic-mqtt-mapper/tree/develop), (branch develop).
The project structure is…
-
**Is your feature request related to a problem? Please describe.**
When connecting to a custom broker it always a problem to find a way how topic and measurements are defined.
Unfortunatly azure iot…
-
**Is your feature improvement request related to a problem? Please describe.**
The `tedge` CLI framework is used in `thin-edge` devices to create/update configs, create certificates, and connect to…
-
-
I would like to use this image with the following setup:
1. the device runs podman instead of docker
2. the `tedge-container-bundle` should use the podman client `podman-remote`
What is the recom…
-
Support registration of child devices via a local PKI service
**Overview**
* Integrate the PKI registration process with local child device registration
* Managed of the local intermediate CA c…
-
**Describe the bug**
The tedge-mapper-c8y process stops sending data to Cumulocity IoT when using the built-in bridge.
The device where the problem was seen includes a special MQTT subscriptio…
-
If a community block is already deployed as an extension. It should be removed or disabled form the list.
This is to prevent deploying a block twice.
-
**Describe the bug**
If the very first message sent by a child device is ill-formed, then:
- this child device is never registered
- and all its data are rejected by Cumulocity.
**To Reprodu…