Correct @PhilipDAth the ports are disabled by the schedule you set in the port schedule. @Adam I'm sure you probably saw that you can enable/disable the port itself and/or enable/disable the PoE separately, and wanted to know if the schedule could control the PoE without disabling the entire port.
I'm curious, what use case do you have where you might want to disable the PoE on a port, but still leave that port active to pass data and not provide power? If they're PoE ports, both PD and non-PD devices either will or will not negotiate, so it's automatic. I'm curious if there's a case where you might have a PD plugged in, but force the PSE to NOT provide power.
You always have Meraki's virtual stacking at your disposal which can make PoE management very easy. For example, say I have a large school district with a district-wide wireless network across many schools with a thousand APs, all my switches and/or switch ports are properly tagged (like "HS" for high school on the switches, and "wifi" for switch ports with APs plugged in), and I want to reboot only the 100 access points just in the high school. I'd simply go to switch > switch ports and type "switch:HS and tag:wifi" and it'll immediately pull up those 100 ports, and I can click edit and bounce the PoE on all 100 ports instantly. Or say for example I've got an issue with a specific model of AP, but my AP switch ports are only tagged with "wifi" and the tags don't reflect the actual AP model, and I want to reboot every MR42 across the entire district, regardless of which school they're in. A simple lldp:MR42 search would do that. Anyway, I could go on and on all day about virtual stacking examples, really cool and powerful feature/tool.
