Changing profile of device in core-metadata does not trigger callback in custom device service based on device-sdk-c.

[GabrielMonS]

🐞 Bug Report

Affected Services [REQUIRED]

The issue is located in: Metadata/Device service sdk

Is this a regression?

Yes, the previous version in which this bug was not present was: **N/A**

Description and Minimal Reproduction [REQUIRED]

After adding a new device to my service using the edgex core UI, if I edit the device and change the profile it should use, core-metadata seems to record the change (it returns a success code and if I go to edit it again, the profile assigned has changed) but my device service does not perform a device_update(). In fact, no logs appear when I do this, as if it was ignoring the event or not listening to it.

🔥 Exception or Error

🌍 Your Environment

Deployment Environment: Ubuntu 22.04 on a AMD64 system.

**EdgeX Version [REQUIRED]: Core version: 3.1.1 ; SDK version: 4.0.0-dev1 **

Anything else relevant? Changing a property in protocols does trigger a call on the device_update() function. If I change the profile(which does not trigger any call) and then change the protocols, when the device_update() is called, it uses the new profile specified.