OzarkEdge
Part of the Furniture
Which is what we're talking about here.
Well maybe, if I knew what I was talking about!
I'm less concerned about the specific actor/label than I am about the action/result. As I 'see' it for my purposes, acsd is making decisions on behalf of Auto settings, and DFS could very well be a condition to that decision process... which could mean acsd is in play even when setting a fixed channel and fixed bandwidth, like for 160MHz... if it has to move off DFS (radar detected), then it has to move off DFS, even when the setting is not "Auto".
It seems to work fine for some people like @bbunge but inconsistently for myself. However, the more I looked into how acds2 makes decisions the more complicated I realised it was.
Indeed, complicated! And I didn't even realize acsd/Auto was in disrepair.
Channel 153 was probably chosen by ACSD because he's set both the channel and the bandwidth to auto. ACSD selects the channel/bandwidth combination based on what it thinks is "best". The router may have started up on a different (perhaps DFS) channel and then switched at a later time (we don't have that information).
Since your initial explanation of 20/40/80/160, I added the suffix (auto) to mean 'auto' [max] bandwidth, not fixed like 160MHz.
Given ch Auto and 'auto' bw that includes 160MHz, I'd expect the router to boot to a control channel in one of the 160MHz ranges, and stay there unless some Auto/DFS detection dictates a change. WiFi and radar are minimal around here so maybe I can make some observations to prove/disprove some presumptions.
OE