I have recently installed Volumio on an RPI 2B (Raspberry Pi 2B) connected to my LAN via wired ethernet. My router is configured to apply a static DHCP lease so that the RPI always gets the same ip address (10.0.0.4) when connected. This all works very well.
I then installed Sound@Home on a Samsung S7 connected over wifi to the same LAN, and selected auto-configure. It immediately wrote a set of incorrect configuration settings to the RPI in the file /etc/dhcpcd.conf. It therefore configured the RPI as having a static ip address of its own (10.0.0.7 - not the static ip DHCP lease provided by the router (10.0.0.4). This caused an ip address conflict on my LAN with another device, and the RPI failed to connect.
I then manually reset the etc/dhcpcd.conf file on the RPI to back to the correct settings to allow for dynamic allocation of a static DHCP ip address (10.0.0.4) from the router’s DHCP server and rebooted the RPI. It all worked fine again.
Next, I selected manual configuration from the Sound@Home App, and entered 10.0.0.4 as the ip address of Volumio on the RPI. This too updated /etc/dhcpcd.conf on the RPI to the wrong ip address 10.0.0.7.
Not great - basically Sound@Home immediately breaks my Volumio installation and creates an ip address conflict with another networked device, as soon as I try to use it. Anyone suggest a solution?