Looking for zones file

Volumio Information

Volumio Version: 3.0.10
Hardware: rpi4
DAC: dragonfly

searching for the file containing the ip of the zones
hope that some one knows what file it is …

best regards,


From your other message, I am assuming this is regarding the multi room zones?
If so there is no file with IP addresses, but Volumio multiroom uses mdns to broadcast available devices. When you clone a device onto a new device, the cloned image will have the same device ID, hence it won’t show up.

To fix your issue you need to remove the preset device ID from the cloned backup:

  • The straightforward way
    Cloned Volumio Image - no multiroom
  • The more involved way
    Delete the uuid key in the config.json from the system_controller/system folder. I am away from a Volumio device, but you should be able to figure things out from here? :slight_smile:

tnx ash i will look into it :slight_smile:

where could i find all user data ?
factory reset doesn’t wipe the data…

the config doesn’t contain uuid :

  "playerName": {
    "value": "Volumio",
    "type": "string"
  "startupSound": {
    "value": true,
    "type": "boolean"
  "kernelSettingValue": {
    "value": 1,
    "type": "number"
  "kernelSettingLabel": {
    "value": "Default",
    "type": "string"
  "device": {
    "value": "",
    "type": "string"
  "show_wizard": {
    "value": true,
    "type": "boolean"

Should be in /data/configuration/

What is the path of this file? It looks like the default one from /volumio/app/plugins/?

You should be looking for the one in /data/configuration/system_controller/system/config.json

If that doesn’t contain a uuid then share a log from a fresh reboot and we have a look why it isn’t getting created…

1 Like

found it and yess it’s there … gonna clean the uuid by clearing the value
after reboot it not recreated just empty with a different ip

What do you mean by ip? There should be nothing related to an (network) IP address in this file…

Maybe elaborate a bit about what exactly you are trying to achieve? It might some time…

i was checking it with the rest api… there was a change but it works :slight_smile:

to get it good working i had to clear both of the pi’s uuid’s