Hello @Jeff Marcum ,
welcome to this moderated Azure community forum.
You are referencing tags, device twins and data.
It must be clear the Azure IoT Hub support MQTT as a communication protocol but only supports a limited set of MQTT topics with specific message formats so IoT Hub device-to-cloud and cloud-to-device communication takes place:
- You can send telemetry message to the IoT Hub
- You can receive desired properties (part of the device twin)
- You can send reposted properties (part of the device twin) (this is an 'expensive' call and normally used as a reply on desired properties to tell the desired state is received)
- Additionally, direct methods can be handled when the device is live connected
A device also supports tags.
These must be seen as context to a device registration (on the cloud side) so incoming messages can be enriched with these tags. These tags can also be used in a more special IoT Edge solution with layered deployments.
The device cannot reach out to the tags.
You are talking about tags but I think these are reported properties?
These reported properties are normally not deleted because it represents the current state. If a device has certain reported properties and new desired properties are supplied, You can check if the device has picked up the changes already.
Also, the Azure portal experience for the device twin is not automatically refreshed.
You need to close and open the page again to refresh it.
It's better to route device twin changes to eg. a storage account so you have a better view on the historical changes of all device twins.
If you really want to delete tags or desire properties, you need to set then to 'null' (check the information on the device twin page in the portal).
If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. All community members with similar issues will benefit by doing so. Your contribution is highly appreciated.