TM1637 Documentation
- Dominant language
- No language data
- Stars
- 313
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
### The problem
In the [documentation for the TMS1637](https://esphome.io/components/display/tm1637.html) is the section on connecting multiple displays.
"Connect multiple displays
To connect multiple TM1636 displays you need as many control lines as you have displays. This is achived by sharing control-lines for clk and dio between displays."...
1. It reads *TMS1636* here but should be TMS1637.
2. I can find no reference for the wiring shown in the diagrams for connecting multiple displays in this manner. If this is possible, there should be a corresponding configuration shown (yaml). All other references use a shared CLK and individual DIO lines for each display.
### Which version of ESPHome has the issue?
2023.5.5
### What type of installation are you using?
Home Assistant Add-on
### Which version of Home Assistant has the issue?
_No response_
### What platform are you using?
ESP32
### Board
_No response_
### Component causing the issue
_No response_
### Example YAML snippet
```yaml
display:
- platform: tm1637
id: right_display
clk_pin: GPIO14
dio_pin: GPIO27
length: 4
lambda: |-
it.printf(0, "%4.1d", id(step_count));
- platform: tm1637
id: left_display
clk_pin: GPIO14
dio_pin: GPIO12
lambda: |-
it.printf(0, "%4.1d", id(step_count));
```
### Anything in the logs that might be useful for us?
_No response_
### Additional information
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the “Connect multiple displays” section in the linked tm1637.html documentation and compare its diagrams with the provided YAML example using shared CLK and separate DIO pins. Done means correcting the TM1636/TM1637 naming and either documenting the diagrammed wiring with valid YAML or removing the unsupported wiring reference.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- yaml
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100