

🔧 Turn up your DIY game with precision and style!
The Cylewet CYT1100 pack includes five 360° rotary encoder code switches with built-in push buttons and 5-pin layouts, designed for smooth, accurate input control in Arduino and microcontroller projects. Each encoder features a 20mm shaft and comes with knob caps, offering durable, easy-to-mount components ideal for prototyping, control panels, and audio gear.
| ASIN | B07DM2YMT4 |
| Item model number | CYT1100 |
| Manufacturer | Cylewet |
| Package Dimensions | 8.4 x 5 x 2 cm; 50 g |
C**N
These rotary encoders are excellent for prototyping and DIY electronics. The 360° rotation feels smooth, and the detents are nicely defined, which makes them accurate for adjusting values in menus or controlling parameters. The built-in push button is a great bonus, allowing you to add extra functionality (like selecting options) without needing a separate switch. The 5-pin layout is standard and works seamlessly with Arduino, ESP32, and other microcontrollers. I was able to wire one up quickly, and the output signals were clean and consistent. The included knob caps fit snugly and give a nice finished look to projects. Having 5 in a pack is perfect—I can use them in multiple builds, and it’s great value compared to buying singles. They’re sturdy, easy to mount, and have held up well under repeated use. Highly recommended if you’re building control panels, audio gear, or any project that needs precise input with a push-button option
R**S
This encoder thing is pretty neat. I've been using it in some ESPHOME projects lately, and it works well enough. It's got that push button right on top which is nice - no need to add a separate one (that'd be silly). The knob spins smoothly, but sometimes when i turn it really fast the encoder struggles to keep up. I guess even with 360 degrees of rotation, there's a limit to how much information it can handle at once. Oh well, not a big deal in my case since i usually don't need super precise control anyway (unless you're building a rocket or something). The build quality seems decent for the price - no complaints here. I like that it comes with 5 encoders in one pack, so you have some spares if one breaks or you just need more in your project. It's also nice to see all those pins laid out clearly on the encoder, makes it easy to solder them onto a breadboard (i mean, who uses anything else?). Overall, this is a solid choice for anyone looking to add some rotary control to their projects. Just remember to take care when wiring it up - one wrong connection and you're in trouble. But hey, that's part of the fun right?
D**T
What makes these rotary encoders stand out among a sea of equivalent products are the metal knobs!! They're beautifully machined, and the knurling in the grip area feels great. When you look at them, you want to touch them and spin them around and around. And of course, the rotary encoders work as you'd expect. For my particular geek project, I was using an ESP32 with ESPHome/HomeAssistant to read the rotary encoder and the momentary switch pushbutton that's built into the rotary encoder shaft. And I was using three of the five encoders that come in this kit to manually specify the set R, G and B values for an LED strip (WS2812). Pressing the rotary encoder triggers a script MP3 player (the DF Robot Mini) to play the Futurama theme song. This requires the use of 3 GPIO pins on the ESP32, two to read the clockwise/anticlockwise motion, and one for the momentary switch. And of course, you have to connect the rotary encoder to ground. While this is a pretty trivial ESPHome/HomeAssistant configuration, I'll include the YAML anyway just in case someone finds it useful. Of course, if you're programming directly in Arduino or using one of the other automation platforms, these encoders will work just fine. For the Rotary Encoder motion: # Rotary encoder to set the Red channel value sensor: - platform: rotary_encoder name: "red_led_encoder" id: "red_led_encoder" publish_initial_value: true restore_mode: RESTORE_DEFAULT_ZERO resolution: 4 min_value: 0 max_value: 50 on_clockwise: - lambda: |- turn_on_todays_lights.execute(); # forces a refresh of the WS2812 with the new encoder value on_anticlockwise: - lambda: |- turn_on_todays_lights.execute(); pin_a: number: GPIO14 mode: input: True pullup: True pin_b: number: GPIO12 mode: input: True pullup: True # 1Momentary switch press plays the futurama theme song - platform: gpio pin: number: GPIO25 mode: INPUT_PULLUP inverted: true name: "futurama-theme-momentary-switch" device_class: running filters: delayed_on_off: 50 ms on_press: then: - logger.log: "Button Pressed: Playing Futurama theme." - script.execute: play_futurama_theme on_release
Q**E
These things look nice, they feel nice ... and they seem to perform well. However, figuring out how they work, in the complete absence of any documentation is a bit of a pain. There are three pins on one side, two pins on the other side. There are also two larger pins on the other sides, for mounting or alignment purposes. The two pin side is very straightforward, and represent the two pins of a normally-open switch. The three pin side is also straightforward, in that the center pin is the ground, and the other two represent what I will call encoder1 and encoder2. When you rotate the spindle, you will find that there are a total of 20 detents (bumps) during a rotation of 360 degrees. Each movement of the spindle from one detent to the next results in the encoder1 and encoder2 pins going through multiple transitions, not a single one (as you might expect). Assuming that you have tied the encoder pins to (say) 5V with a resistor, a rotation between detents, will produce a set of encoder transitions. For example: 11 10 00 01 11 (clockwise) or 11 01 00 10 11 (anti-clockwise). Thus, in the first state change from 11, you can tell whether the rotation is clockwise or anti-clockwise. So, a practical use of this, in either the Arduino, the Raspberry Pi, or some other platform, will require polling the two encoder pins, and monitoring the state transitions. When you see a full set of transitions from 11 back to 11, you can determine whether to increment or decrement the counter you are associating with the control. The polling speed is determined by how fast you expect the user to twirl the dial! I use 1 millisecond polling on my Raspberry Pi, and I cannot twirl the dial fast enough to lose any transitions. You can use slower polling, if necessary. In my case my Pi has little else to do, so why not a fast poll? I hope this helps others quickly get up-to-speed in using these devices.
G**I
Rather resilient (even when removing the little metal bumps that give it the clicks).
Trustpilot
2 weeks ago
4 days ago