Thinedge.io send no supportet opperation to Cumulocity

Forum
,
1

I have a problem where I can’t sporadically perform operations from the Cumulocity, e.g., software updates, log files, configuration snapshots, etc. When I connect after a disconnect using “tedge connect c8y” , I get the following logos. I use thinedge.io 1.6.9

^Croot@imx6ull-iwg26i:~# tedge mqtt sub ‘c8y/s/us’ -q 0
[c8y/s/us] 102,864004045897441:device:main:service:tedge-mapper-c8y,service,tedge-mapper-c8y,down
2025-12-18T09:26:12.216325826Z ERROR MQTT: Connection error: Mqtt state: Mqtt serialization/deserialization error: IO: Connection reset by peer (os error 104)
^Croot@imx6ull-iwg26i:~# tedge mqtt sub ‘c8y/s/us’ -q 0
2025-12-18T09:26:34.947899321Z ERROR MQTT: Connection error: Mqtt state: Connection closed by peer abruptly
[c8y/s/us] 117,60
[c8y/s/us] 114,c8y_DeviceProfile,c8y_DownloadConfigFile,c8y_LogfileRequest,c8y_RemoteAccessConnect,c8y_Restart,c8y_SoftwareUpdate,c8y_UploadConfigFile,ecu_mqtt
[c8y/s/us] 500
[c8y/s/us] 102,864004045897441:device:main:service:tedge-mapper-c8y,service,tedge-mapper-c8y,up
[c8y/s/us] 102,864004045897441:device:main:service:tedge-mapper-c8y,service,tedge-mapper-c8y,up

^Croot@imx6ull-iwg26i:~# tedge mqtt sub ‘c8y/s/us’ -q 0
[c8y/s/us] 102,864004045897441:device:main:service:tedge-mapper-c8y,service,tedge-mapper-c8y,down
2025-12-18T09:26:12.216325826Z ERROR MQTT: Connection error: Mqtt state: Mqtt serialization/deserialization error: IO: Connection reset by peer (os error 104)
^Croot@imx6ull-iwg26i:~# tedge mqtt sub ‘c8y/s/us’ -q 0
2025-12-18T09:26:34.947899321Z ERROR MQTT: Connection error: Mqtt state: Connection closed by peer abruptly
[c8y/s/us] 117,60
[c8y/s/us] 114,c8y_DeviceProfile,c8y_DownloadConfigFile,c8y_LogfileRequest,c8y_RemoteAccessConnect,c8y_Restart,c8y_SoftwareUpdate,c8y_UploadConfigFile,ecu_mqtt
[c8y/s/us] 500
[c8y/s/us] 102,864004045897441:device:main:service:tedge-mapper-c8y,service,tedge-mapper-c8y,up
[c8y/s/us] 102,864004045897441:device:main:service:tedge-mapper-c8y,service,tedge-mapper-c8y,up

2

The error messages you observed are due to a mosquitto restart and should cause no trouble. When the connection to the MQTT broker is lost, thin-edge tries to reconnect in the background.

Also among all the messages sent by the mapper over the topic c8y/s/us you can observe the following:

114,c8y_DeviceProfile,c8y_DownloadConfigFile,c8y_LogfileRequest,c8y_RemoteAccessConnect,c8y_Restart,c8y_SoftwareUpdate,c8y_UploadConfigFile,ecu_mqtt

These are the operations supported by the device. So, from a device perspective, things seem to be okay.

What is more precisely your issue? Are the operations not available from the tenant? Not responding? Returning errors?

Also when debugging the connection to Cumulocity from a device, it’s better to follow all the Cumulocity related messages with:

tedge mqtt sub 'c8y/#'