From 9ffbc6e94d7dfae0178e6a5dbb5c4a8ca3c8737b Mon Sep 17 00:00:00 2001 From: Torsten Paul Date: Sun, 24 Sep 2023 06:23:01 +0200 Subject: [PATCH] Fix typo in tm1637.rst (#3203) --- components/display/tm1637.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/components/display/tm1637.rst b/components/display/tm1637.rst index 502508671..9da0d458c 100644 --- a/components/display/tm1637.rst +++ b/components/display/tm1637.rst @@ -86,7 +86,7 @@ The TM1637 has a similar API to the fully fledged :ref:`display-engine`, but it' 7-segment displays don't have a concept of individual pixels. In the lambda you're passed a variable called ``it`` as with all other displays. In this case however, ``it`` is a TM1637 instance (see API Reference). -The most basic operation with the TM1637 is wiring a simple number to the screen as in the configuration example +The most basic operation with the TM1637 is writing a simple number to the screen as in the configuration example at the top of this page. But even though you're passing in a string (here ``"0123"``), ESPHome converts it into a representation that the TM1637 can understand: The exact pixels that should be turned on. And of course, not all characters can be represented. You can see a full list of characters :ref:`at the MAX7219 docs `.