Thanks, that's what I figured. Is there any way to speed up the specific example I gave? Some way to forcibly make the AP adopt the change immediately, even if it means abruptly ending all current sessions? ... View more

Does Meraki have any sort of documentation that shows which APs currently have the hardware/certs to support which Wi-Fi channels (agnostic of region - I understand that will result in a subset of the hardware capabilities based on where I put the AP). ... View more

Ok, I think I understand a bit better now. I pick the "primary" 20MHz channel, and then if I've selected to transmit at 40 or 80MHz channel widths, then the equivalent 40MHz or 80MHz band that contains that primary channel will be used if one exists for the given regulatory domain. The client still identifies the primary channel number as its 20MHz channel, but should report its center frequency based on the center frequency of the full width.   But here's a follow-up question. I'm looking at one of my APs that is in Germany, under a CE regulatory domain. On the RF profile configuration page for autoChannel, I see the following options: But then on the Radio Settings page, if I want to manually choose a channel, it looks like this:   Why is 144 listed as an available channel in the first selection, but not the second? I'm guessing that the first screen is a superset, and the second screen is specific to this MR33, and it doesn't support this channel because it is older and because Channel 144 was only added somewhat more recently? Can you confirm if that is correct, and if newer APs can operate on channel 144, and if so, which APs have that capability?   My initial reason for this line of questioning was that I expected to able to set this AP to channel 132, and the Channel Width to 80MHz. Instead, it only establishes a 40MHz-wide connection when I configure that way. I assume this is happening because the Meraki access point is saying that Channel 144 is not permitted for use, and thus the 80MHz channel there is not available.   Also, why are channels 149-161 not being allowed in an EU deployment? My understanding (admittedly may be wrong) is that is for short Range devices and would be allowed as long as the transmit power is less than some limit. Even if this particular AP doesn't support that range, why would they not show as permitted options for this RF profile in the first screenshot? They do show up as available on my APs in an American deployment. If this is also a limitation of this particular AP, can you tell me what newer models may support this range in Germany?   Thanks! ... View more

No - it doesn't work there either. I get the same reply about only 20 or 40 being allowed when I use the dashboard UI. ... View more

I also tried using postman to emulate what worked for you. I get the same result there:   Body: { "fiveGhzSettings": { "channel": 36, "channelWidth": 80, "targetPower": 30 } }   Reply: {"errors":["Invalid channel width for fiveGhzSettings: channel width must be in 20, 40"]} ... View more

Thanks for the quick reply. I was including the rfProfilefield in the body. I have removed it, but it still doesn't work for me. Throws the same error: dashboard.wireless.updateDeviceWirelessRadioSettings(meraki_ap_serial, fiveGhzSettings={'channel': 36, 'channelWidth': 80, 'targetPower': 30})   and the result: Meraki API error: wireless, updateDeviceWirelessRadioSettings - 400 Bad Request, {'errors': ['Invalid channel width for fiveGhzSettings: channel width must be in 20, 40']}   ... View more