[{"data":1,"prerenderedAt":512},["ShallowReactive",2],{"post-esp32-lcd-i2c-not-working-fix-en":3,"related-posts-esp32-lcd-i2c-not-working-fix-en":465,"related-categories-esp32-lcd-i2c-not-working-fix-en":497},{"id":4,"title":5,"author":6,"authorImageUrl":7,"authorUrl":8,"body":9,"categorySlug":424,"categoryText":425,"dateModified":426,"datePublished":426,"description":427,"extension":428,"faqs":429,"image":448,"imageAlt":449,"language":450,"meta":451,"navigation":452,"path":453,"seo":454,"sitemap":455,"stem":456,"summary":457,"tags":458,"__hash__":464},"blog\u002Fblog\u002Fesp32-lcd-i2c-not-working-fix.md","ESP32 I2C LCD 16x2 Not Working: Address, 5 V, Contrast","Mauro Brambilla","\u002Fimages\u002Fauthors\u002Fbruma.jpg","\u002Fabout",{"type":10,"value":11,"toc":410},"minimark",[12,16,27,32,35,40,43,47,65,76,101,106,129,136,139,142,149,152,156,198,209,213,222,225,228,232,247,253,256,263,266,272,287,290,295,303,307,328,346,350,353,357,360,391,395,398],[13,14,15],"p",{},"An ESP32 I2C LCD 16x2 that stays blank is usually one of three things: the wrong I2C address (0x27 for a PCF8574 backpack, 0x3F for a PCF8574A), a contrast trimmer turned the wrong way, or the 5 V backpack's signal levels meeting a 3.3 V ESP32 pin. Scan the bus first, then adjust the trimmer.",[13,17,18,19,26],{},"The Gizmo Reolink Switch runs a 16x2 LCD with an I2C backpack on a XIAO ESP32-S3, so the pins, library versions and code below come from its ",[20,21,25],"a",{"href":22,"rel":23},"https:\u002F\u002Fgithub.com\u002Fopen-gizmo\u002Fgizmo-reolink-switch",[24],"nofollow","open-source firmware",", and the chip facts come from the Texas Instruments, Espressif and hd44780 library sources. I did not test faulty boards for this post, and I say so where it matters.",[28,29,31],"h2",{"id":30},"why-is-my-esp32-i2c-lcd-lit-but-blank","Why is my ESP32 I2C LCD lit but blank?",[13,33,34],{},"An I2C backpack is the small board soldered on the back of a 16x2 character LCD. It holds a PCF8574 chip, an I2C expander that turns the LCD's parallel pins into two wires (SDA and SCL), and a blue trimmer for the contrast. Lit but blank means the backlight has power, so the problem is one of the six causes below. Check them in this order, because each test takes under a minute.",[36,37],"blog-table",{":headers":38,":rows":39},"[\"Symptom\",\"Likely cause\",\"Test\"]","[[\"Backlight on, no characters\",\"Contrast trimmer at the wrong setting\",\"Turn the trimmer slowly, a quarter turn at a time\"],[\"Backlight on, top row of solid blocks\",\"LCD powered but not initialized\",\"Run the I2C scanner, then check the sketch and the contrast\"],[\"Scanner finds nothing\",\"SDA and SCL swapped, loose wire, no pull-ups\",\"Check the wiring against the pins below, then re-scan\"],[\"Scanner finds 0x3F, sketch uses 0x27\",\"Address mismatch\",\"Use the address the scanner printed\"],[\"Backlight off too\",\"No 5 V on the backpack\",\"Measure VCC and GND at the backpack pins\"],[\"Random characters or flicker\",\"Noise, long wires or full-screen clears\",\"Shorten the wires, rewrite rows instead of clearing\"]]",[13,41,42],{},"The row of blocks matters. It is commonly described as the sign of a powered LCD that never received its setup commands, but I could not find a datasheet line that says so, so treat it as a hint, not a rule. The scanner in the next section settles it.",[28,44,46],{"id":45},"_1-find-the-address-with-an-i2c-scanner","1. Find the address with an I2C scanner",[13,48,49,50,54,55,58,59,64],{},"An I2C address is the 7-bit number a device answers to on the bus. The scanner asks every address from 1 to 126 whether anyone is home. In the Arduino ",[51,52,53],"code",{},"Wire"," library, ",[51,56,57],{},"endTransmission()"," returns 0 when a device acknowledged. In the Arduino-ESP32 core's ",[20,60,63],{"href":61,"rel":62},"https:\u002F\u002Fgithub.com\u002Fespressif\u002Farduino-esp32\u002Fblob\u002Fmaster\u002Flibraries\u002FWire\u002Fsrc\u002FWire.cpp",[24],"Wire.cpp",", the ESP-IDF \"not found\" and \"fail\" results both map to return value 2, and a timeout maps to 5 (checked in the source as of November 2026).",[66,67,74],"pre",{"className":68,"code":70,"filename":71,"language":72,"meta":73},[69],"language-cpp","#include \u003CWire.h>\n\nvoid setup() {\n    Serial.begin(115200);\n    delay(2000); \u002F\u002F Give the USB serial monitor time to attach\n    Wire.begin(5, 6); \u002F\u002F XIAO ESP32-S3: SDA = D4 (GPIO5), SCL = D5 (GPIO6)\n    Wire.setClock(100000);\n}\n\nvoid loop() {\n    uint8_t found = 0;\n    for (uint8_t address = 1; address \u003C 127; address++) {\n        Wire.beginTransmission(address);\n        if (Wire.endTransmission() == 0) {\n            Serial.printf(\"Device at 0x%02X\\n\", address);\n            found++;\n        }\n    }\n    if (found == 0) Serial.println(\"No I2C device found: check wiring and power\");\n    delay(3000);\n}\n","i2c_scanner.ino","cpp","",[51,75,70],{"__ignoreMap":73},[13,77,78,79,82,83,86,87,90,91,82,94,90,97,100],{},"Open the serial monitor at 115200 baud. With the backpack connected you should see one line, usually ",[51,80,81],{},"Device at 0x27"," or ",[51,84,85],{},"Device at 0x3F",". Your address may differ, and that is the point of scanning. If the line is ",[51,88,89],{},"0x38"," to ",[51,92,93],{},"0x3E",[51,95,96],{},"0x20",[51,98,99],{},"0x26",", the backpack's address pads (A0, A1, A2) are set differently from the common default.",[102,103,105],"h3",{"id":104},"why-0x27-on-one-backpack-and-0x3f-on-another","Why 0x27 on one backpack and 0x3F on another?",[13,107,108,109,114,115,118,119,124,125,128],{},"The two addresses come from two chip variants. Texas Instruments' ",[20,110,113],{"href":111,"rel":112},"https:\u002F\u002Fwww.ti.com\u002Flit\u002Fds\u002Fsymlink\u002Fpcf8574.pdf",[24],"PCF8574 datasheet"," (revision of September 2024) defines the address as ",[51,116,117],{},"0100 A2 A1 A0",", which gives 0x20 to 0x27. The ",[20,120,123],{"href":121,"rel":122},"https:\u002F\u002Fwww.ti.com\u002Flit\u002Fds\u002Fsymlink\u002Fpcf8574a.pdf",[24],"PCF8574A datasheet"," defines ",[51,126,127],{},"0111 A2 A1 A0",", which gives 0x38 to 0x3F. With all three address pins high, the PCF8574 sits at 0x27 and the PCF8574A at 0x3F.",[13,130,131],{},[132,133],"img",{"alt":134,"src":135},"The PCF8574 backpack chip answers from 0x20 to 0x27 and the PCF8574A from 0x38 to 0x3F, with 0x27 and 0x3F as the all-address-pins-high values","\u002Fimages\u002Fblog\u002Fesp32-lcd-i2c-not-working-fix-addresses.webp",[13,137,138],{},"So a sketch that hardcodes 0x27 will find nothing on a PCF8574A board. Change the number to the one the scanner printed, or let the library find it, as the next section shows.",[13,140,141],{},"Once the scanner sees the backpack, a minimal sketch with the hd44780 library (the same one the Reolink Switch uses) proves the display works. It finds the address by itself:",[66,143,147],{"className":144,"code":145,"filename":146,"language":72,"meta":73},[69],"#include \u003CWire.h>\n#include \u003Chd44780.h>\n#include \u003Chd44780ioClass\u002Fhd44780_I2Cexp.h>\n\nhd44780_I2Cexp lcd; \u002F\u002F Autolocates the backpack and its pin mapping\n\nvoid setup() {\n    Wire.begin(5, 6); \u002F\u002F XIAO ESP32-S3: SDA = D4, SCL = D5\n    if (lcd.begin(16, 2) != 0) return; \u002F\u002F Non-zero: no display found\n    lcd.print(\"Hello, I2C\");\n}\n\nvoid loop() {}\n","lcd_hello.ino",[51,148,145],{"__ignoreMap":73},[13,150,151],{},"If the scanner finds the device but this sketch prints nothing, go to the contrast trimmer in step 2.",[102,153,155],{"id":154},"what-does-the-reolink-switch-do-about-the-address","What does the Reolink Switch do about the address?",[13,157,158,159,124,166,169,170,173,174,181,182,185,186,191,192,197],{},"This is a detail I only found by reading the code. ",[20,160,163],{"href":161,"rel":162},"https:\u002F\u002Fgithub.com\u002Fopen-gizmo\u002Fgizmo-reolink-switch\u002Fblob\u002Fmain\u002Fmicrocontroller\u002Fsrc\u002Fconfig\u002Fconfig.cpp",[24],[51,164,165],{},"config.cpp",[51,167,168],{},"DISPLAY_I2C_ADDRESS = 0x27",", and the README says the backpack is \"detected at ",[51,171,172],{},"0x27","\". But a search of the firmware finds the constant only in its definition and its declaration: nothing reads it. ",[20,175,178],{"href":176,"rel":177},"https:\u002F\u002Fgithub.com\u002Fopen-gizmo\u002Fgizmo-reolink-switch\u002Fblob\u002Fmain\u002Fmicrocontroller\u002Fsrc\u002Fdisplay\u002Fdisplay.cpp",[24],[51,179,180],{},"display.cpp"," creates a plain ",[51,183,184],{},"hd44780_I2Cexp display;",", and the header of the ",[20,187,190],{"href":188,"rel":189},"https:\u002F\u002Fgithub.com\u002FduinoWitchery\u002Fhd44780",[24],"hd44780 library"," lists that no-argument form as \"autolocate\u002Fautoconfigure everything\". The firmware pins version 1.3.2 in its ",[20,193,196],{"href":194,"rel":195},"https:\u002F\u002Fgithub.com\u002Fopen-gizmo\u002Fgizmo-reolink-switch\u002Fblob\u002Fmain\u002Fmicrocontroller\u002Fplatformio.ini",[24],"platformio.ini",".",[13,199,200,201,204,205,208],{},"In practice, a 0x3F backpack should work with this firmware without a code change, because the library probes for it. I have not tried a PCF8574A board with the switch, so that is a reading of the code, not a test. If the library finds no device, ",[51,202,203],{},"display.begin()"," returns a non-zero status, and the firmware's ",[51,206,207],{},"initDisplay()"," returns quietly with the display marked not ready. The LCD stays dark and the rest of the switch keeps running, which is why a missing screen can look like a dead board.",[28,210,212],{"id":211},"_2-turn-the-contrast-trimmer","2. Turn the contrast trimmer",[13,214,215,216,221],{},"The contrast trimmer is the small blue potentiometer on the backpack. It sets the voltage that decides how dark the characters appear, so a wrong setting gives a lit screen with nothing readable, or every cell filled in. The hd44780 library's own diagnostic sketch, ",[20,217,220],{"href":218,"rel":219},"https:\u002F\u002Fgithub.com\u002FduinoWitchery\u002Fhd44780\u002Fblob\u002Fmaster\u002Fexamples\u002FioClass\u002Fhd44780_I2Cexp\u002FI2CexpDiag\u002FI2CexpDiag.ino",[24],"I2CexpDiag",", prints this advice to the serial monitor: \"If all pixels are on, or no pixels are showing, but backlight is on, try adjusting contrast pot\".",[13,223,224],{},"Use a small screwdriver and turn it a quarter turn at a time, pausing to look. Do this while the sketch is running and the display has been initialized, otherwise you only learn about the contrast of an empty screen. If one end of the range shows a row of blocks and the other end shows nothing, text should appear somewhere in between.",[13,226,227],{},"I2CexpDiag is worth running if the scanner finds the device and the text still will not show. By its own description it scans the bus, tries to initialize each display, blinks the backlight and reports missing pull-ups. Its changelog also mentions a check for SDA and SCL shorted together.",[28,229,231],{"id":230},"_3-does-a-5-v-lcd-backpack-work-with-a-33-v-esp32","3. Does a 5 V LCD backpack work with a 3.3 V ESP32?",[13,233,234,235,240,241,246],{},"Often, but it is outside what the datasheets guarantee, and the reason is the pull-up resistors. I2C lines are open-drain: devices only pull them low, and a pull-up resistor lifts them to the high level. The ",[20,236,239],{"href":237,"rel":238},"https:\u002F\u002Fdocs.espressif.com\u002Fprojects\u002Farduino-esp32\u002Fen\u002Flatest\u002Fapi\u002Fi2c.html",[24],"Arduino-ESP32 I2C documentation"," says the lines \"require pull-up resistors\", and the ESP32-S3's internal weak pull-up is typically 45 kΩ (Table 5-4 of the ",[20,242,245],{"href":243,"rel":244},"https:\u002F\u002Fdocumentation.espressif.com\u002Fesp32-s3_datasheet_en.pdf",[24],"Espressif datasheet",", v2.2), which I read as too weak to rely on for I2C. So the pull-ups live on the backpack, and the question is what they connect to.",[13,248,249],{},[132,250],{"alt":251,"src":252},"A breadboard seen from above with a XIAO board, a level shifter and a 16x2 LCD with an I2C backpack, marked 3.3 V and 5 V on each side","\u002Fimages\u002Fblog\u002Fesp32-lcd-i2c-not-working-fix-illustration.webp",[13,254,255],{},"The hd44780 library's author warns about exactly this in the I2CexpDiag header, and notes that many backpacks carry 5 V pull-ups:",[257,258,260],"blog-quote",{"author":259},"hd44780 library, I2CexpDiag sketch header",[13,261,262],{},"WARNING: 3v only systems like ARM\u002FTeensy3\u002FESP8266 devices will need to take precautions on SDA and SCL connections if using 5V I2C devices.",[13,264,265],{},"Here are the numbers. The ESP32-S3's input high level may reach at most VDD + 0.3 V, about 3.6 V, in Table 5-4. If the backpack's pull-ups go to 5 V, SDA and SCL idle near 5 V, above that range. The PCF8574 on the other side needs a high of at least 0.7 × VCC (3.5 V at 5 V), according to its datasheet, and the ESP32-S3 guarantees only 2.64 V for its own high output. The 2.64 V output level only matters if a pin drives the line high itself, which open-drain I2C normally avoids.",[13,267,268],{},[132,269],{"alt":270,"src":271},"Bar chart of the I2C voltages: 5 V pull-ups, the 3.5 V PCF8574 high threshold at 5 V supply, and the 2.64 V ESP32-S3 output high, against the 3.6 V ESP32-S3 input maximum","\u002Fimages\u002Fblog\u002Fesp32-lcd-i2c-not-working-fix-voltage.webp",[13,273,274,275,280,281,286],{},"What the Reolink Switch does is documented in its ",[20,276,279],{"href":277,"rel":278},"https:\u002F\u002Fgithub.com\u002Fopen-gizmo\u002Fgizmo-reolink-switch#pinout",[24],"README",": the LCD is powered from the XIAO's 5V pad, and SDA and SCL go to D4 and D5 with nothing in between. The README gives no margin analysis, and I did not measure the voltage on the lines or look at which rail the pull-ups of the switch's module use, so I cannot say it is within spec. Seeed's ",[20,282,285],{"href":283,"rel":284},"https:\u002F\u002Fwiki.seeedstudio.com\u002Fxiao_esp32s3_getting_started\u002F",[24],"wiki"," describes the 5V pad as 5 V out from the USB port, so that is what the LCD runs from.",[13,288,289],{},"You have four ways out, from safest to riskiest:",[291,292],"blog-list",{":items":293,"variant":294},"[\"Put a bidirectional I2C level shifter between the ESP32 and the backpack. This is the option that stays inside every datasheet.\",\"Power the backpack from 3.3 V. The PCF8574 accepts 2.5 to 6 V, but many 16x2 LCDs are specified for 5 V, so check your module and expect a dim or blank screen if it is not.\",\"Move the backpack's pull-ups to 3.3 V. The library author calls this a cheat that needs a hardware modification, and a 3.3 V high is below the PCF8574's 3.5 V minimum at a 5 V supply.\",\"Leave it as it is, if it works, and accept that you are outside the guarantee.\"]","numbered",[13,296,297,298,302],{},"The same trade-off appears on the other OpenGizmo display: the 3.3 V logic section of ",[20,299,301],{"href":300},"\u002Fblog\u002Fmax7219-fc16-esp32-wiring-orientation","MAX7219 FC16 With ESP32"," walks through it with its own datasheet numbers.",[28,304,306],{"id":305},"_4-check-the-i2c-pins-on-the-xiao-esp32-s3","4. Check the I2C pins on the XIAO ESP32-S3",[13,308,309,310,315,316,319,320,323,324,327],{},"On a generic ESP32, the Arduino-ESP32 documentation lists SDA on GPIO21 and SCL on GPIO22, but it says the defaults vary by board. On the Seeed Studio XIAO ESP32-S3, the wiki gives SDA on D4 (GPIO5) and SCL on D5 (GPIO6), and the core's ",[20,311,314],{"href":312,"rel":313},"https:\u002F\u002Fgithub.com\u002Fespressif\u002Farduino-esp32\u002Fblob\u002Fmaster\u002Fvariants\u002FXIAO_ESP32S3\u002Fpins_arduino.h",[24],"board definition"," sets ",[51,317,318],{},"SDA"," to 5 and ",[51,321,322],{},"SCL"," to 6. So ",[51,325,326],{},"Wire.begin()"," with no arguments lands on D4 and D5, but a sketch that hardcodes GPIO21 and GPIO22 talks to the wrong pads.",[13,329,330,331,333,334,337,338,341,342,197],{},"The Reolink Switch avoids the question by passing both pins in ",[51,332,207],{},": ",[51,335,336],{},"Wire.begin(config::DISPLAY_SDA_PIN, config::DISPLAY_SCL_PIN)",", followed by ",[51,339,340],{},"Wire.setClock(100000)",", which is 100 kHz, the standard I2C speed. The whole pad map is in ",[20,343,345],{"href":344},"\u002Fblog\u002Fxiao-esp32s3-pinout-safe-pins","XIAO ESP32-S3 Pinout: Which Pins Are Safe to Use",[36,347],{":headers":348,":rows":349},"[\"Signal\",\"XIAO ESP32-S3 pad\",\"GPIO\",\"Backpack pin\"]","[[\"I2C data\",\"D4\",\"5\",\"SDA\"],[\"I2C clock\",\"D5\",\"6\",\"SCL\"],[\"Power\",\"5V\",\"-\",\"VCC\"],[\"Ground\",\"GND\",\"-\",\"GND\"]]",[13,351,352],{},"Double-check SDA and SCL are not swapped. A swapped pair is silent: the scanner prints your \"No I2C device found\" line, the same as a missing wire.",[28,354,356],{"id":355},"_5-why-does-the-lcd-text-corrupt-or-flicker","5. Why does the LCD text corrupt or flicker?",[13,358,359],{},"Garbled characters point at the bus or the supply, and flicker usually points at the software. They get separate fixes.",[361,362,363,374,380],"ul",{},[364,365,366,370,371,373],"li",{},[367,368,369],"strong",{},"Flicker:"," clearing the whole screen before every update makes the LCD blink. The Reolink Switch's ",[51,372,180],{}," comment says its rows are padded with spaces so old text is overwritten \"without a clear, which makes the LCD flicker\". Do the same: rewrite each row at full width.",[364,375,376,379],{},[367,377,378],{},"Corrupt characters:"," shorten the SDA and SCL wires, push the breadboard jumpers in properly, and keep the clock at 100 kHz. A slow bus is the cheapest thing to try first, because you change one number.",[364,381,382,385,386,390],{},[367,383,384],{},"Characters change when Wi-Fi starts:"," the supply may be dipping on transmit bursts. The ",[20,387,389],{"href":388},"\u002Fblog\u002Fesp32-brownout-detector-was-triggered","brownout detector guide"," covers how to find the weak link in the power path.",[28,392,394],{"id":393},"what-did-we-verify-and-what-is-still-open","What did we verify, and what is still open?",[13,396,397],{},"You now have a scan that finds the backpack, the two address ranges with their datasheet source, the trimmer check, and the 5 V question with its numbers. The pins, the pinned library version, the 100 kHz clock and the autolocating constructor come from the Reolink Switch firmware. The address ranges and the thresholds come from the TI and Espressif datasheets, as of November 2026.",[13,399,400,401,405,406,197],{},"Four limits remain. I did not test a PCF8574A board with the switch. I did not measure the voltage on SDA and SCL, and I do not know which rail the pull-ups of the switch's module use, since backpacks differ. The \"row of blocks\" reading is common advice, not a datasheet line. And the 5 V case is outside the guarantee, so a level shifter is the safe fix. For the full build around this screen, read ",[20,402,404],{"href":403},"\u002Fblog\u002Fcontrol-reolink-nvr-esp32","Control a Reolink NVR with an ESP32",", or see the ",[20,407,409],{"href":408},"\u002Fprojects\u002Fgizmo-reolink-switch","Gizmo Reolink Switch project page",{"title":73,"searchDepth":411,"depth":411,"links":412},2,[413,414,419,420,421,422,423],{"id":30,"depth":411,"text":31},{"id":45,"depth":411,"text":46,"children":415},[416,418],{"id":104,"depth":417,"text":105},3,{"id":154,"depth":417,"text":155},{"id":211,"depth":411,"text":212},{"id":230,"depth":411,"text":231},{"id":305,"depth":411,"text":306},{"id":355,"depth":411,"text":356},{"id":393,"depth":411,"text":394},"troubleshooting","Troubleshooting","2026-11-14T00:00:00Z","ESP32 I2C LCD 16x2 blank or showing blocks? Scan for the 0x27 or 0x3F address, turn the contrast trimmer, and check the 5 V backpack on 3.3 V pins.","md",[430,433,436,439,442,445],{"question":431,"answer":432},"Why is my I2C LCD lit but showing no text on an ESP32?","A lit but blank 16x2 LCD usually has working power but a wrong address, a contrast trimmer set too low or too high, or an initialization that failed. Run an I2C scanner to confirm the backpack answers, then turn the blue trimmer on the backpack slowly until the characters appear.",{"question":434,"answer":435},"Is the I2C LCD address 0x27 or 0x3F?","It depends on the chip on the backpack. A PCF8574 answers from 0x20 to 0x27, and a PCF8574A answers from 0x38 to 0x3F, according to Texas Instruments' datasheets. Common backpacks come set to 0x27 or 0x3F, but only a scan tells you which one you have.",{"question":437,"answer":438},"Can I connect a 5 V I2C LCD to a 3.3 V ESP32?","It is outside the datasheets' guarantees if the backpack's pull-up resistors go to 5 V, because the ESP32-S3's inputs accept at most VDD plus 0.3 V, about 3.6 V. Many projects run it anyway. The safe fixes are a bidirectional I2C level shifter or a backpack without 5 V pull-ups.",{"question":440,"answer":441},"Which pins are I2C on the XIAO ESP32-S3?","On the Seeed Studio XIAO ESP32-S3, SDA is D4 (GPIO5) and SCL is D5 (GPIO6). Generic ESP32 examples use GPIO21 and GPIO22 instead, so a copied sketch that hardcodes those GPIOs will not match your wiring. Passing the pins explicitly, Wire.begin(5, 6), removes the guesswork.",{"question":443,"answer":444},"Do I need a library to scan the I2C bus on an ESP32?","No. The Wire library that ships with the Arduino-ESP32 core is enough. A scanner calls Wire.beginTransmission() and Wire.endTransmission() for each address from 1 to 126, and an address that returns 0 means a device answered. The LCD library is only needed afterwards, to write text.",{"question":446,"answer":447},"Why does my 16x2 LCD flicker or show garbled characters?","Flicker usually comes from clearing the whole screen before every update, so rewrite each row padded with spaces instead. Garbled characters usually come from a loose breadboard wire, long SDA and SCL leads, or a supply that dips when Wi-Fi transmits. Shorten the wires and check the 5 V supply.","\u002Fimages\u002Fblog\u002Fesp32-lcd-i2c-not-working-fix.jpg","A woman with a grey bob turns the blue trimmer on an I2C backpack with a small screwdriver while a 16x2 LCD shows a row of solid blocks, next to an I2C label.","en",{},true,"\u002Fblog\u002Fesp32-lcd-i2c-not-working-fix",{"title":5,"description":427},{"loc":453},"blog\u002Fesp32-lcd-i2c-not-working-fix","A blank ESP32 I2C LCD is usually the address (0x27 for a PCF8574 backpack, 0x3F for a PCF8574A), the contrast trimmer, or 5 V signals on a 3.3 V pin. Scan the bus first, then adjust.",[459,460,461,462,425,463],"ESP32","Displays","XIAO ESP32-S3","Electronics","OpenGizmo","LvPbGEXzlYY3gIRhc8zegbxIEyxsw6xJOPJwhgv06C8",[466,474,481,490],{"title":467,"description":468,"image":469,"categoryText":470,"categorySlug":471,"tags":472,"path":300},"MAX7219 FC16 With ESP32: Wiring, 3.3 V Logic, Mirroring","Wire a 4-in-1 FC16 MAX7219 matrix to an ESP32 with five wires, check the 3.3 V logic question, and fix mirrored text with the right MD_MAX72XX hardware type.","\u002Fimages\u002Fblog\u002Fmax7219-fc16-esp32-wiring-orientation.jpg","Builds","builds",[473,459,460,461,462,463],"MAX7219",{"title":475,"description":476,"image":477,"categoryText":470,"categorySlug":471,"tags":478,"path":480},"ESP32 Crypto Ticker With MAX7219: Parts, Wiring, Setup","Build an ESP32 crypto ticker with a MAX7219 matrix: XIAO ESP32-S3 pinout, browser flashing, captive portal setup and a free CoinGecko key. Firmware on GitHub.","\u002Fimages\u002Fblog\u002Fhow-to-build-a-crypto-ticker-with-esp32-and-max7219.png",[459,461,473,460,463,479],"Wi-Fi","\u002Fblog\u002Fhow-to-build-a-crypto-ticker-with-esp32-and-max7219",{"title":482,"description":483,"image":484,"categoryText":485,"categorySlug":486,"tags":487,"path":489},"MAX7219 vs HUB75 LED Matrix for ESP32: Which to Pick","MAX7219 vs HUB75 LED matrix on an ESP32: pins, power, colors, libraries and cost compared, plus why the Gizmo Ticker uses a MAX7219 matrix.","\u002Fimages\u002Fblog\u002Fmax7219-vs-hub75-led-matrix-esp32.jpg","Comparisons","comparisons",[473,460,459,488,462,463],"Hardware","\u002Fblog\u002Fmax7219-vs-hub75-led-matrix-esp32",{"title":491,"description":492,"image":493,"categoryText":425,"categorySlug":424,"tags":494,"path":496},"ESP32 Captive Portal Not Working? Fix the Wi-Fi Popup","Why the ESP32 captive portal popup doesn't open on Android, iPhone or Windows: DNS, probe URLs, 302 redirects and the checks that fix it, with working code.","\u002Fimages\u002Fblog\u002Fesp32-captive-portal-not-working-fix.jpg",[459,479,425,495,463],"Firmware","\u002Fblog\u002Fesp32-captive-portal-not-working-fix",[498,502,508],{"name":485,"slug":486,"path":499,"count":500,"image":501},"\u002Fblog\u002Fcategories\u002Fcomparisons",8,"\u002Fimages\u002Fblog\u002Fesp32-ota-update-methods-compared.jpg",{"name":503,"slug":504,"path":505,"count":506,"image":507},"Guides","guides","\u002Fblog\u002Fcategories\u002Fguides",11,"\u002Fimages\u002Fblog\u002Fcoingecko-api-esp32-rate-limits.jpg",{"name":470,"slug":471,"path":509,"count":510,"image":511},"\u002Fblog\u002Fcategories\u002Fbuilds",6,"\u002Fimages\u002Fblog\u002F3d-printed-esp32-enclosure-design-guide.jpg",1795018236284]