-
-
**Describe the bug**
The Cumulocity IoT install software operation Operation was stuck in EXECUTING status due to a dns lookup error.
```
Oct 05 12:21:29 pippin tedge-mapper[462]: 2023-10-05T…
-
-
**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…
-
**Describe the bug**
tedge-agent does not publish the `{topic_id}/cmd/firmware_update` retained message when a `firmware_update.toml` workflow is defined.
This results in the Cumulocity IoT De…
-
**Is your feature request related to a problem? Please describe.**
Add support for the Cumulocity IoT [device profiles](https://cumulocity.com/docs/device-integration/fragment-library/#device-pro…
-
**Is your feature improvement request related to a problem? Please describe.**
If for some reason a workflow definition is rejected by __tedge-agent__, the workflow is rejected on start and an erro…
-
Hi,
I have set up four servers bigCouch to form a cluster. And I select another server to be client (eg, YCSB), which will send large scale request to the bigCouch cluster. The thread number on the c…
-
**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…
-
**Describe the bug**
When a large payload > 1 MiB is published to the Cumulocity mapper, it gets stuck in a disconnect-reconnect loop at the MQTT client level. This happens because maximum message …