@NJC A snapshot of the channel spread in my condo:

My 2.4, which is where the majority of my devices are running (iot devices) is running on channel 7 which as you can see is the most congested. I'm having problems with iot devices dropping out and having to be reset to reconnect them.That's not an issue I was having with my previous router which I had on channel 4 which is relatively uncrowded.

The 5GHz is running on channel 40 and 153 which again are congested but not as much. Being able to move the channels would be extremely desirable

@TP-Link There are about 20 devices scattered around the house: Google minis, Wemo switches, Wyze cameras, Chromecast devices, HP network printer. The primary issue is with the Google minis. About once a day 1 or 2 of the minis (the specific mini varies), declares that it is unconnected. A reboot of the mini is required to get the connection back.

The fact that it happens once a day, usually overnight, leads me to wonder whether it is related to lease renewal. Unfortunately there is no setting for specifying the lease time. As an experiment I have reserved IP addresses for all the IoT devices.

The issue with using the guest network is that it would isolate communication between my devices, at least I presume that Guest is isolated from the mesh network. If Chromecast is on guest and my laptop is on the mesh, I can't cast. If Chromecast is on the mesh and the Google Minis are on guest, then I can't control Chromecast from the minis. It really is not viable to isolate IoT to Guest.

There are other mesh devices that support creating multiple SSIDs on the same network. In those devices I can have a 2.4 and 5 mesh with SSID "main", a second 2.4 wth SSID "IoT". Both "main" and "IoT" would be on the same network and cross communication possible. There would then be "Guest" which is an isolated network. This would be a desirable feature for Deco that would likely address the issues with "low cost" IoT devices that run 2.4 only.