-
**Describe the bug**
Cumulocity IoT operations which are created whilst the Cumulocity IoT MQTT bridge is disconnected do not get processed by the tedge-mapper-c8y when the network outage has pas…
-
**Is your feature improvement request related to a problem? Please describe.**
I would like to use a serial-number as my technical device-id, but use a different/more meaningful name for the Device i…
-
**Is your refactoring request related to a problem? Please describe.**
The `c8y_api::smartrest::topic` has various mechanisms to generate SmartREST topics for the main device, immediate child devic…
-
**Describe the bug**
Requests to thin-edge.io Cumulocity IoT proxy (localhost:8001) returns sporadically with a 502 Bad Gateway status code.
The `tedge-mapper-c8y` which is providing the local…
-
**Describe the bug**
During the testing of "flaky" integration tests (tests that sometimes pass and sometimes fail with the same code base), evidence appeared where a Cumulocity Shell operation (`5…
-
Besides presenting the talk2m pool definition, we want to see as well the c8y group assignment of each device. Each group should reference the managed object and link to the URL.
-
**Is your feature request related to a problem? Please describe.**
Thin-Edge can not connect to a Cumulocity instance if the HTTPS and MQTTS ports exposed by it are different from the default ones …
-
**Is your feature improvement request related to a problem? Please describe.**
The `c8y_http_proxy::actor.rs::upload_file()` API currently reads the file contents into memory before passing it into…
-
I'd like to propose an enhancement that uses the C8y's "Device Profile" function to manage containers with a docker-compose (or similar orchestrator of multiple containers/services). In other words,…
-
In #2716, support was added to the mapper for a built-in Cumulocity bridge, to replace the mosquitto-based bridge.
Here is a list of follow up tasks that need completing before the feature is fully c…