# Multiroom group permanently breaks after short Wi-Fi disconnect – client cannot be re-added until Volumio service restart **URL:** \ **Category:** Help\ **Tags:** bug\ **Created:** [August 14, 2026, 5:34pm UTC](https://community.volumio.com/t/multiroom-group-permanently-breaks-after-short-wi-fi-disconnect-client-cannot-be-re-added-until-volumio-service-restart/77223 "2026-08-14T17:34:51Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![misha](https://community.volumio.com/letter_avatar_proxy/v4/letter/m/c6cbf5/32.png) [@misha](https://community.volumio.com/u/misha)\ **Post date:** [August 14, 2026, 5:34pm UTC](https://community.volumio.com/t/multiroom-group-permanently-breaks-after-short-wi-fi-disconnect-client-cannot-be-re-added-until-volumio-service-restart/77223/1 "2026-08-14T17:34:51Z")
I have two Volumio devices, `volumio-livingroom` (192.168.210.26) and `volumio-kitchen` (192.168.210.27), running as a Multiroom group. After running normally for some time, the group disappears. The second device is still visible in the Multiroom UI and the “Add” button can be pressed, but it does not join the group. Rebooting the devices fixes the problem. I have now found that rebooting is not necessary: running `sudo systemctl restart volumio` on the affected client (`volumio-kitchen`) is sufficient. Afterwards the client can immediately be added to the group again. **Likely trigger identified in logs** I was able to find the exact moment when the working group was lost. At 20:27:55 the Kitchen device had a short Wi-Fi disconnect: `wlan0: CTRL-EVENT-DISCONNECTED` `dhcpcd: wlan0: carrier lost` `avahi-daemon: Leaving mDNS multicast group` `Discovery: A device disappeared from network` The Wi-Fi connection recovered a few seconds later. Volumio then successfully rediscovered and reconnected to Livingroom: `20:28:08 Discovery: Found device Volumio livingroom` `20:28:08 Discovery: Connecting to remote: 192.168.210.26` `20:28:08 Discovery: Connected to remote: 192.168.210.26` However, immediately afterwards Volumio removes Kitchen from Multiroom: `20:28:09 MRS: Removing this device as multiroomSync client` `20:28:09 MRS: Setting this device as single` `20:28:09 Setting Multiroom Single` `20:28:09 MRS: disable multiroom output` and finally: `20:28:11 MRS: STOPPING SNAPCLIENT` `systemctl stop volumioSnapclient` `snapclient: Received SIGTERM signal` **Additional observation** When trying to manually add Kitchen to the group afterwards, Snapclient actually connects successfully to the server: `Connected to 192.168.210.26` but Volumio immediately issues: `MRS: STOPPING SNAPCLIENT` and executes: `systemctl stop volumioSnapclient` Therefore this does not appear to be a Snapcast connectivity problem. The client can reach the Snapserver, but the Volumio Multiroom state appears to remain inconsistent after the temporary network interruption. Restarting only the `volumio` service on Kitchen clears this state and Multiroom works again. **Network** FRITZ!Box 5590 Fiber with two additional FRITZ!Mesh repeaters. Temporary Wi-Fi interruptions/channel changes can occur. The important issue appears to be that Multiroom does not recover correctly after connectivity has been restored. **Expected behavior** After a temporary network interruption, the Multiroom group should either automatically recover, or it should at least be possible to manually add the client to the group again without restarting Volumio. **Actual behavior** The client remains visible, but cannot be added until the Volumio service is restarted. **Logs** Kitchen: [http://logs.volumio.org/volumio/6Bq88O0.html](http://logs.volumio.org/volumio/6Bq88O0.html) Livingroom: [http://logs.volumio.org/volumio/0GNvLVR.html](http://logs.volumio.org/volumio/0GNvLVR.html) **Environment** Kitchen device/model: Raspberry Pi 4 Model B Rev 1.5 (WLAN) Livingroom device/model: Raspberry Pi 2 Model B Rev 1.1 (Ethernet) Volumio version Kitchen: 3.912 Volumio version Livingroom: 3.912 ---
**Author:** ![tfro71](https://community.volumio.com/letter_avatar_proxy/v4/letter/t/d07c76/32.png) [@tfro71](https://community.volumio.com/u/tfro71)\ **Post date:** [September 9, 2026, 8:43pm UTC](https://community.volumio.com/t/multiroom-group-permanently-breaks-after-short-wi-fi-disconnect-client-cannot-be-re-added-until-volumio-service-restart/77223/2 "2026-09-09T20:43:27Z")
same issue here. One player sees the other but the other does not see the its buddy. This is directly after being able to play the same mysic on both players. Both are wired. Only rebooting one (but you never know which one) solves it shortly ---
**Author:** ![tfro71](https://community.volumio.com/letter_avatar_proxy/v4/letter/t/d07c76/32.png) [@tfro71](https://community.volumio.com/u/tfro71)\ **Post date:** [September 9, 2026, 8:46pm UTC](https://community.volumio.com/t/multiroom-group-permanently-breaks-after-short-wi-fi-disconnect-client-cannot-be-re-added-until-volumio-service-restart/77223/3 "2026-09-09T20:46:16Z")
any clue where to find the logs in the ui? ---
**Author:** ![pwstereo](https://community.volumio.com/user_avatar/community.volumio.com/pwstereo/32/1054_2.png) [@pwstereo](https://community.volumio.com/u/pwstereo)\ **Post date:** [September 9, 2026, 9:43pm UTC](https://community.volumio.com/t/multiroom-group-permanently-breaks-after-short-wi-fi-disconnect-client-cannot-be-re-added-until-volumio-service-restart/77223/4 "2026-09-09T21:43:44Z")
[http://volumio.local/dev/](http://volumio.local/dev/) replace volumio.local with your actual device name or IP address.