Empty Cache
Data Orchestrator MQTT v1 strives to save bandwidth upon reconnections, to make sure even frequent reconnections don't affect bandwidth consumption. As such, upon connecting and if MQTT advertises a session present, both sides assume that data flow is ordered and consistent. However, there might be cases where this guarantee isn't respected by the device for a number of reasons (e.g.: new device, factory reset, cache lost...). In this case, a device might declare that it has no confidence about its status and its known properties, and can request to resynchronise entirely with Data Orchestrator.
In Data Orchestrator jargon this message is called empty cache and it is performed by publishing "1" on the device /control/emptyCache topic.
After an empty cache message properties might be purged and Data Orchestrator might publish all the server owned properties again.