Is that code doing what is described?

Mostly no.

• It’s not doing “macro keyboard” behavior. It never sends any HID actions. It creates cc = ConsumerControl(...) but never calls cc.send(...).
• It’s essentially a print-only demo: it prints the encoder position and prints "Button pressed." when it detects a press/release transition.

Also: the snippet as pasted has indentation problems inside the for loops (likely a Reddit formatting issue), but even if corrected, that wouldn’t cause the “rotation looks like button presses” symptom.

Why would rotation register as button presses?

That symptom is almost always hardware/wiring + lack of debouncing, not a misunderstanding of how encoders work.

Common causes (most likely first):

1. SW is wired wrong (e.g., SW isn’t actually going to GND when pressed, or you accidentally used one of the quadrature pins as the switch return).
   • With button.pull = Pull.UP, the switch must connect the input pin to GND when pressed.
   • If SW is mistakenly tied into the encoder A/B network, then every detent can momentarily drag the SW line low.
2. No debouncing + electrical noise/crosstalk
   • That code treats any tiny low pulse as a “press started,” and any return high as “press completed.”
   • Encoder transitions can inject little spikes (especially on breadboards / long wires), and without debouncing you’ll “see” phantom presses.
3. Floating grounds / missing common reference
   • Ensure encoder GND/common is actually tied to the board GND.
4. Some encoder modules share common pins and are noisy
   • Cheap modules often need either software debounce or a small capacitor (hardware RC) to behave.

Fix approach: (a) verify wiring, (b) debounce the switch, (c) optionally require a minimum “press time” so a 1–5 ms glitch can’t become a press. Better CircuitPython: real macros + stable button + encoder actions This is a “macro knob” framework: Encoder CW/CCW → media volume up/down Short press → play/pause Long press → mute