The problem first appeared in the vDC-Sonos. There were multiple reports for errors
on a scene invocation, or during a preset test, complaining that no speaker is
found in a given zone. The specificity of the vDC-Sonos is that when calling a scene,
the vDC collects all speakers from a zone to create a Sonos group and plays
the desired content afterward. The Sonos group configuration is volatile, thus
there is a need for such preliminary preparation for the scene. The problem was caused
by missing zoneId information stored in the vDC, when the device is re-added
and zoneId is used from the datamodel cache. The device receives it only when
it is moved to another room, that's why moving a device around became an effective
temporary solution to the problem.
The solution for the bug is to consistently provide the zone id to a device on its
acknowledgment process (announce device).
Fixes https://myesmart.atlassian.net/browse/DSD-10138
Closes DSD-10138