No, not ‘perfect.’ All fouled up.
This optimization is a black box set on ‘improving’ whatever condition it is allowed to operate on.
My network didn’t need ‘optimizing,’ It had been stable and serving me well for many months. But… could it be better? Maybe, but actually, no.
And since the logic it uses is opaque to the user, and the user has no option to manually set channels used (like to the ones that were working before optimizing - and there is no option to revert) customer is stuck with a network scrambled in performance, which subsequent scans inform him is ‘perfect.’
Ultimately, I power cycled the modem, the mesh router and one remote node, all the cams, bulbs and plugs, hoping the core router logic would return me to where I was before ‘optimizing.’
Then I ‘trained’ the system by letting the timed ‘sequence’ feature of tinyCam cycle between cams for a few hours, then cam groups for a few hours, and I was pretty much back where I started: ‘stable & well-served.’
UPDATE (10 days later)
The optimization feature is now usable. When performance degrades, optimizing improves cam connectivity at least minimally.