logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

How to flash LN882H with open source Tasmota/Esphome style firmware - backup procedure included

p.kaczmarek2 66195 297

TL;DR

  • LN882H modules can be flashed over UART with open-source Tasmota/Esphome-style firmware to free cloud-controlled devices and integrate them with Home Assistant.
  • Wire module TX, RX, GND, 3V3, and BOOT/GPIOA9 to ground, and keep GPIOA9 low throughout the entire flashing process.
  • Backup uses `python LN882H_Flash_Dumper.py COMx flashdump`, and the firmware flash command is `LN882H_CMD_Tool.exe COMx download flash 921000 0x0 flashimage.bin`.
  • After flashing, power-cycle the module, disconnect BOOT from ground, and open 192.168.4.1 to configure it like other OpenBeken/Tasmota-style devices.
  • A reliable external 3.3V supply is recommended because powering directly from the USB-to-UART adapter’s 3.3V pin may fail.
Generated by the language model.
ADVERTISEMENT
Report a violation of the law
Cool? Ranking DIY | New topic
Notify about new articles
📢 Listen (AI):
  • #271 21320690
    XJ_
    Level 12  
    Posts: 141
    Help: 13
    Rate: 39
    >>21320676
    sure, add loop is also solution
  • ADVERTISEMENT
  • #272 21321492
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14622
    Help: 655
    Rate: 12637
    I didn't have time yet to check the recent posts, but I think it would be good to try to include such issues in the self tests, like I just did for UART buffer write:
    https://github.com/openshwprojects/OpenBK7231...mmit/a2f3b020686633c643ab8790875e00173bb9d354
    This allowed me to verify and check the great UART fix that @XJ_ submitted here:
    https://github.com/openshwprojects/OpenBK7231...mmit/e99ff0c1517af7c95e7c94c9211a5be1afe593c4
    Again, I didn't have yet time to investigate fully, but in general, I would try to slowly move towards having all features self-tested, just like I've did with UART, just to be sure that there are no strange errors like that...

    I will try to check this particular issue later, if my time allows it.

    PS: I did the same for startScript command: https://github.com/openshwprojects/OpenBK7231...mmit/9cd823cbdae04d10285777f62115504cfe7f0bd1
    Helpful post? Buy me a coffee.
  • #273 21321519
    max4elektroda
    Level 24  
    Posts: 756
    Help: 48
    Rate: 187
    p.kaczmarek2 wrote:
    , but I think it would be good to try to include such issues in the self tests,

    While I think that generally speaking self tests are a good idea, it will not help for platform specific bugs like the one I found here (if we don't talk about windows code bugs): the testing code will never reach code in this sections.
    And, how can I name it without sounding like I don't appreciate your valuable work?
    I just think this tests sometimes have a limited use case: if a test is written after a bug was corrected, it can only help if the code in question is changed incorrectly in the future.
    But usually this is exactly what you do before changing the code: test it. And if you fail because one special case was not in your scope, you will also have no test for this case and can only update the testing code after the bug was found and only prevent doing the same or similar error again.
    So it really depends on the type of code, if a test makes sense, and it will not help here.
  • ADVERTISEMENT
  • #274 21321538
    io2345
    Level 9  
    Posts: 268
    Help: 1
    Rate: 7
    >>20905518 This method is still the preferred way for the LN882H in 11/2024, right?
  • #275 21321552
    max4elektroda
    Level 24  
    Posts: 756
    Help: 48
    Rate: 187
    io2345 wrote:
    This method

    That depends on which step you refer in detail: the post shows all steps needed very detailed. Depending on your device and skills you might e.g. be able to flash a module without desoldering it. But up to now there's no known way to initial flash the device without UART connection if that's your question.
  • #276 21321561
    divadiow
    Level 38  
    Posts: 5065
    Help: 438
    Rate: 893
    >>21321538

    a couple of things to note:
    - the LN882H_Flash_Dumper.py in the first post will create a 4mb file with a duplicate of the flash content. It'll take twice as long doing it. Updated script attached to read 2mb only. (maybe @p.kaczmarek2 wouldn't mind changing file in first post)
    ref: https://www.elektroda.com/rtvforum/topic4083817.html#21284784 - https://www.elektroda.com/rtvforum/topic4008545-90.html#20912035
    - there a Windows GUI flash option (no flash backup function) https://www.elektroda.com/rtvforum/topic4045532.html
    Attachments:
    • LN882H_Flash_Dumper.zip (1.16 KB) You must be logged in to download this attachment.
  • #277 21321611
    XJ_
    Level 12  
    Posts: 141
    Help: 13
    Rate: 39
    max4elektroda wrote:
    I just think this tests sometimes have a limited use case: if a test is written after a bug was corrected, it can only help if the code in question is changed incorrectly in the future.

    I agree, it is necessary to consider where it makes sense. For example, for a code fix for RS232 or Flash, I would definitely leave the test, because new platforms are often added and new modules using them may have a different approach, e.g. from multiple threads at a time...
  • #278 21321650
    max4elektroda
    Level 24  
    Posts: 756
    Help: 48
    Rate: 187
    I agree on this crucial parts.
    And it's also very usefull for "complex" code which relys on other code, so a change "somwhere else" can break a funktion.
    For the flashing code it depends - the common code could and should be tested if possible.
    You won't be able to do this on specific code like here: The ota flashing part is platform specific and distinguished by "#if defined <platform>" - invisible for the tests running on windows code.

    So for this it comes down to writing some own testing routine for that code, freeing it from all the hardware related stuff.

    And integrating this sort of tests into OBK tests would be strictly speaking not totally impossible - but almost: To make sure you test the actual code you would need to make a process to extract the code from the actual driver - change it to make it run on other platforms and remove the hardware part (e.g. with sed/grep/awk...) - very hard work. And if changes to the code are done, you will probably also need to change the "extraction code" accordingly. So, I think it's o.k. to call it impossible.
  • #279 21321789
    io2345
    Level 9  
    Posts: 268
    Help: 1
    Rate: 7
    >>21321552 Thank you for answering. I already did flash a device some time ago (this one: https://www.elektroda.com/rtvforum/topic4036567.html). But now I can't reach it on the network any longer, although the device can be switched on/off using the hardware button. So I thought about reflashing it to see if it helps and was wondering, if the procedure is still the same.
  • #280 21321797
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14622
    Help: 655
    Rate: 12637
    Have you tried entering safe (AP) mode by doing quick 5 power off and on cycles?
    Helpful post? Buy me a coffee.
  • #281 21321837
    io2345
    Level 9  
    Posts: 268
    Help: 1
    Rate: 7
    >>21321797 Never heard of that before. I will try. Device will restart as Access Point? Connect has to be done to 192.168.4.1 (as far as I remember), right?

    Hinzugefügt nach 1 [Stunden] 20 [Minuten]:

    It helped, I could connect to AP and after a reboot to the device. Might be worth mentioning, that I have two more identical devices running on FW 1.17.590 and 1.17.611. The device with the problem was OTA updated to 1.17.739 about a month ago. Maybe this version had a little problem. Will update now to the latest version.
  • #282 21332078
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14622
    Help: 655
    Rate: 12637
    max4elektroda wrote:
    I think I finally found it - see https://github.com/openshwprojects/OpenBK7231T_App/pull/1441

    I think I can merge it, but has anyone, @divadiow , someone else tested it as well just to be sure? If not, I must try to find my LN882H dev board...
    https://www.elektroda.com/rtvforum/topic4062695.html
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • Helpful post
    #283 21332121
    divadiow
    Level 38  
    Posts: 5065
    Help: 438
    Rate: 893
    I've just UART flashed to 1441_merge_6d6a6086fa18 without issue then OTA in Firefox 132.0.2 to OpenLN882H_1.17.789_OTA.bin no problem.
  • ADVERTISEMENT
  • #284 21332221
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14622
    Help: 655
    Rate: 12637
    Thank you for testing, merged.
    Helpful post? Buy me a coffee.
  • #285 21332298
    max4elektroda
    Level 24  
    Posts: 756
    Help: 48
    Rate: 187
    Thanks to both of you!
  • #287 21336923
    max4elektroda
    Level 24  
    Posts: 756
    Help: 48
    Rate: 187
    Ah, they also found one of the bugs in OTA I recently discovered (after days of trying to isolate the problems with OTA and firefox):
    divadiow wrote:
    Code: text Expand Select all Copy to clipboard
    3. Fix the problem that the address may be calculated incorrectly during OTA file download and writing to flash

    Code snippet showing a fix changing the condition in an if statement.

    But they still don't see that data got from HTTP in rare cases could fill internal 4k buffer twice, which caused the main crashes during OTA.
  • #288 21336927
    XJ_
    Level 12  
    Posts: 141
    Help: 13
    Rate: 39
    max4elektroda wrote:
    But they still don't see that data got from HTTP in rare cases could fill internal 4k buffer twice, which caused the main crashes during OTA.

    👍
  • #289 21344542
    notzed
    Level 2  
    Posts: 2
    divadiow wrote:
    indeed, but why isn't it controllable? are RX/TX GPIOs always fixed high? The datasheet says FULLMUX, like other controllable GPIOs...


    I know it's late but after a day of frustration I found this out why today. The gpio input/output mode functions aren't clearing the alternative function bit so setting the port to input or output still leaves it operating as uart1 tx. I think this is a bug because it would mean you couldn't change from pwm to digital either. It's unclear why both uart0 and uart1 are both initialised and used for output (log + stdio?).

    Issue, a fix but no pr sorry: https://github.com/openshwprojects/OpenBK7231T_App/issues/1461

    Also for what it's worth the cozylife mini smart switch (at least) has an onboard 5V buck converter (BP2525) that can run on almost any ac/dc voltage (tested >=12v, >=9v probably works) which makes it a lot easier & safer to play with in-situ, not to mention useful for non-mains applications like irrigation.
  • #290 21344566
    poldim1
    Level 2  
    Posts: 3
    Rate: 1
    anyone know if there is a way to flash this from a mac/linux? I no longer have any PC's in the house...
  • #292 21360652
    jhatter55
    Level 3  
    Posts: 4
    Is it possible to enable the Wemo support for the LN882 like some of the other devices have? I can execute this command "backlog startDriver SSDP; startDriver Wemo" and it says OK but Alexa does not discover it. MQTT works fine. I use this feature with some BL602 devices I have and it works correctly. Great work supporting these other chips that aren't esp8266 and ESP32.
  • #293 21360764
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14622
    Help: 655
    Rate: 12637
    I think you can use online builds system to try compiling LN882H with WEMO driver:
    https://www.elektroda.com/rtvforum/topic4033833.html
    Wait a second, I've just checked and it seems it's already enabled in the main tree:
    A code snippet configuring drivers for the LN882H platform.
    This means that you need to do some debugging.
    WEMO driver reqisters following handlers:
    Code: C / C++
    Log in, to see the code

    They are not present when driver is not run:
    Screenshot of a webpage at URL 192.168.0.163/setup.xml displaying Not found message.
    but once you start a driver, you can visit them easily:
    Code: text Expand Select all Copy to clipboard
    
http://192.168.0.163/setup.xml

    Screenshot showing an XML file with Belkin device data on a web page.
    So, my first question is - is the setup.xml working on your device?
    Helpful post? Buy me a coffee.
  • #294 21368504
    notzed
    Level 2  
    Posts: 2
    The code is a bit hard to navigate at first, but i'm getting familiar with it.

    I found the logs setup on UART0 (A8/A9) initialised sdk/OpenLN882H/components/utils/debug/log.c.
    And some 'AT console' on UART1 (A2/A3 marked TX/RX) at sdk/OpenLN882H/components/ln_at/ln_at.c, but it doesn't seem to do anything particularly useful.

    >>21345439
    max4elektroda wrote:
    But I don't know what happenes to all the logs if UART is not present...


    Configuring the pins as gpio properly seems to work as expected, the uart is running but doesn't go anywhere and the REST logs still work.

    Also for what it's worth after breaking off 2 boot pads I realised you don't need to solder anything on BOOT - it just needs to be grounded when for a short time when the power is applied which can be done with a piece of wire or test probe by hand. For the cozylife switch signal ground is available on S1, so you only need to solder to the 2 TX/RX pins and it all works in-place. I've been using 12V DC to power them via the mains input so you don't need a separate 3v3 power connection either.

    Added after 9 [minutes]:

    poldim1 wrote:
    anyone know if there is a way to flash this from a mac/linux? I no longer have any PC's in the house...


    I tried wine but the tool just hangs, I tried windows 10 in qemu but couldn't figure out the serial port config. In VirtualBox with a windows 10 install I could get the flash tool to work sometimes but it wasn't very reliable and I didn't want to install python so I didn't try reading or writing a whole flash. Its possible it could be made to work. I have a 'live usb' stick with a windows 10 install I created - first installed on qemu and then copied it to the flash stick. It's slow and tedious and updates take forever (disabling network helps) but it's enough to run the gui flash tool and it's been reliable.
  • #295 21371400
    jhatter55
    Level 3  
    Posts: 4
    >>21360764 Sorry for just getting back to this. Yes Setup.xml works on the device and it looks like yours minus the different device name and ip address but Alexa does not discover it like it did for the BL602 device.
    Screenshot of an XML file showing Belkin device data.
  • #296 21375129
    max4elektroda
    Level 24  
    Posts: 756
    Help: 48
    Rate: 187
    notzed wrote:
    I found the logs setup on UART0 (A8/A9) initialised sdk/OpenLN882H/components/utils/debug/log.c.
    And some 'AT console' on UART1 (A2/A3 marked TX/RX) at sdk/OpenLN882H/components/ln_at/ln_at.c, but it doesn't seem to do anything particularly useful.

    There are several code fragments "initializing" UARTs, the question is, which ones are included.
    Just for reference: One UART is B8/B9 (not "A"), and in the documents it's sometimes referred as UART0 and sometimes as UART1
    E.g. here they are called "UART_RX1/UART_TX1" ...
    https://developer.tuya.com/en/docs/iot/WL2H-U-Module-Datasheet?id=Kbohlj8eg19u5
    And in the code (e.g. in "./project/OpenBeken/bsp/serial_hw.c") B8/B9 is UART0 and A2/A3 UART1 ...

    To match it to the pins on the module:

    The two pins labeled RX/TX beneath GND on modules LN-02 and WL-2S are A2/A3 (UART0 on the Tuya page, UART1 in code)
    The two pins labeled RX1/TX1 on the back of WL-2S and labelled B8/B9 on the pins on the other side of VCC/GND on LN-02

    LN882H module with visible electronic components on a yellow background.LN882H module with visible pads and pin labels.Close-up of PCB with LN882H module and markings.

    Added after 1 [minutes]:

    notzed wrote:
    Configuring the pins as gpio properly seems to work as expected, the uart is running but doesn't go anywhere and the REST logs still work.

    Could you please explain a bit more detailed, what you did to configure this pins "properly"?
  • #298 21376302
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14622
    Help: 655
    Rate: 12637
    I've recently released a youtube guide for the same process:
    [Youtube] LN882H module pinout and setup for flashing - step by step video guide
    But this now means we have two LN882H flashing topics, so....

    I am closing this topic for now, please continue dicussion in YT guide topic.
    Helpful post? Buy me a coffee.
Cool? Ranking DIY | New topic
Notify about new articles
📢 Listen (AI):
Report a violation of the law

Topic summary

✨ The discussion focuses on flashing LN882H modules with open-source firmware similar to Tasmota/Esphome, enabling cloud-free operation and integration with Home Assistant. Flashing requires a USB to UART converter with reliable 3.3V power supply, connecting module TX to UART RX, RX to TX, GND to GND, and 3.3V to 3.3V. Users report challenges including access to the BOOT pin, interference from board components on RX/TX lines, and the necessity of short wiring to ensure stable flashing. Various USB to UART converters (CH340, FT232RL, PL2303, CP2101) have differing success rates; CH340 and CP2101 are recommended over some FTDI and PL2303 adapters. Correct baud rate (115200) and running the flashing tool from non-system drives (e.g., D:) improve success. The LN882H_CMD_Tool is used for flashing and dumping firmware; flashing requires power cycling and keeping BOOT grounded during operations. Users successfully dumped firmware but often encountered "Fail. Error downloading file" during flashing, resolved by adjusting baud rate, shortening cables, and using compatible USB-UART adapters.

Power-saving features are under active development; enabling PowerSave mode reduces power consumption and device temperature but may cause WiFi connection issues in some firmware versions. PowerSave commands can be set via startup commands or command tool, with better effect when applied directly via command tool. Temperature monitoring shows LN882H devices run hot (up to 74°C) without load, improved by PowerSave mode. Integration with energy metering (BL0937) is affected by PowerSave due to interrupt handling. Static IP assignment is currently unimplemented in firmware. DHT sensor support is partially implemented; drivers require manual start commands, and pin mapping must be correct. NTP client requires manual driver start and supports server IP configuration via commands. Safe mode can be triggered by power cycling to reset device settings. Firmware and tools are evolving with ongoing commits addressing power management, filesystem (LittleFS), and device stability.

Overall, flashing LN882H modules demands careful hardware setup, compatible USB-UART adapters, correct flashing parameters, and power cycling. Firmware features like power saving, sensor support, and network configuration are improving but still have limitations. Community contributions and testing continue to enhance LN882H open-source firmware usability and integration.
Generated by the language model.
Today's popular

FAQ

TL;DR: Need to flash LN882H and keep a recovery path? Use 5 wires and keep BOOT low; as one expert put it, "BOOT is like IO0". First dump the original flash, then write the regular firmware binary over UART, usually at 115200 baud if higher speeds fail. This FAQ is for OpenBeken/OpenLN882H users who need a practical flash, backup, OTA, and recovery workflow. [#20923772]

Dlaczego to ma znaczenie: LN882H can run cloud-free firmware, but success depends more on wiring discipline, baud rate, and power cycling than on the chip itself.

Opcja Typowe użycie Co działało w praktyce Główne ryzyko
LN882H_CMD_Tool.exe Flashowanie UART w Windows Często ruszało po zmianie na 115200 Błąd Fail. Error downloading file.
LN882H_Flash_Dumper.py Backup flash i OTP Tworzy dump przed zmianą firmware Długi odczyt, wymaga poprawnego BOOT
OTA z Web App Aktualizacja już działającego OBK Chrome/Chromium działały stabilniej niż Firefox Firefox mógł wywołać crash OTA
BK7231GUIFlashTool Nowsze narzędzie GUI Wspierane dla LN882H od aktualizacji 2026 Nadal wymaga tego samego okablowania

Najważniejszy wniosek: Najczęstsza przyczyna nieudanego flashowania LN882H nie była w module, tylko w procedurze: BOOT musi pozostać niski, po każdej próbie trzeba odłączyć i podłączyć zasilanie, a zejście do 115200 baud często rozwiązywało zapis. [#20958664]

Quick Facts

  • LN882H flashuje się przez UART podobnie do ESP8266: potrzebne są połączenia TX, RX, GND, 3.3V i BOOT/GPIOA9, a GPIOA9 musi pozostać w stanie niskim przez cały proces. [#20905518]
  • W praktyce zapis przy 2,000,000 baud często kończył się błędem, a kilka osób potwierdziło sukces dopiero po przejściu na 115200 baud. [#20958664]
  • PowerSave na LN882H potrafił mocno obniżyć temperaturę: w jednym teście spadek wyniósł z 64.0°C do 36.0°C po PowerSave 2, kosztem większych opóźnień sieciowych. [#21055421]
  • LittleFS jest systemem plików flash, który przechowuje pliki i skrypty, z odpornością na restart oraz małym narzutem pamięci. Na LN882H dodanie LittleFS zwiększało rozmiar binarki o około 42 KB. [#21069454]
  • OTA na LN882H bywało niestabilne w Firefox; po naprawce przetestowano poprawny update z buildu 1441_merge_6d6a6086fa18 do OpenLN882H_1.17.789_OTA.bin właśnie w Firefox 132.0.2. [#21332121]

How do I flash an LN882H module over UART and make a full backup of the original firmware first?

Flashowanie i backup robi się w dwóch etapach. 1. Podłącz TX↔RX, RX↔TX, GND, 3.3V oraz BOOT/GPIOA9 do GND. 2. Zrób kopię poleceniem python LN882H_Flash_Dumper.py COMx flashdump; narzędzie zapisze dump flash i OTP. 3. Wgraj nowy firmware poleceniem LN882H_CMD_Tool.exe COMx download flash 921000 0x0 flashimage.bin, a po zakończeniu odłącz BOOT od masy i zrestartuj zasilanie. Po starcie urządzenie wystawia AP na 192.168.4.1. [#20905518]

What is the BOOT pin on LN882H, and why does GPIOA9 have to stay low during the whole flashing process?

BOOT na LN882H to pin wejścia do bootloadera, a w praktyce jest nim GPIOA9. Musi pozostać niski przez cały proces, bo tylko wtedy układ pozostaje w trybie programowania; autor porównał go wprost: „BOOT is like IO0.” Odłączenie BOOT w trakcie potrafi przerwać procedurę lub zablokować kolejną próbę do czasu pełnego odcięcia zasilania. Dlatego BOOT zwiera się do GND przed podaniem zasilania i trzyma nisko do końca flashowania. [#20923772]

Why does LN882H_CMD_Tool show "Fail. Error downloading file." and what fixes actually worked, like using 115200 baud, shorter wires, or a different USB-to-TTL adapter?

Najczęściej ten błąd znikał po zmianie parametrów transmisji i procedury zasilania. Skuteczne poprawki to: użycie 115200 zamiast 2000000, skrócenie przewodów, pełne odłączenie zasilania i USB-TTL po każdej nieudanej próbie oraz podmiana adaptera USB-UART. Pomagało też upewnienie się, że wgrywany jest zwykły plik binarny, a nie plik OTA. Kilku użytkowników potwierdziło, że samo ustawienie 115200 natychmiast rozwiązało Fail. Error downloading file. [#20996463]

Which USB-to-UART adapters work best for LN882H flashing, and how do CH340, CP2101, FT232RL, PL2303, and NodeMCU compare in practice?

Najlepiej wypadały adaptery CH340 i CP2101, ale LN882H bywa wybredny. W wątku potwierdzono sukces na CH340, CP2101, adapterach FTDI w części konfiguracji oraz nawet na NodeMCU ESP8266 z CH340. FT232RL działał u jednych, a u innych nie; PL2303 też działał, ale częściej zgłaszano z nim problemy. Jeden użytkownik potwierdził, że LN882H można było flashować przez NodeMCU z CH340, a inny odzyskał stabilność dopiero po przejściu z FTDI na CH430/CH340. [#20958756]

What is LittleFS in OpenBeken/OpenLN882H, and what features depend on it on the LN882H platform?

LittleFS to system plików w pamięci flash, potrzebny do plików takich jak autoexec.bat, skryptów i funkcji opartych o lokalny storage. Na początku LN882H go nie miał, więc przycisk „List Filesystem” nic nie pokazywał, a tworzenie plików nie działało realnie. Po późniejszym wdrożeniu potwierdzono, że pliki przetrwały kilka aktualizacji OTA. Dodanie LittleFS zwiększało rozmiar binarki LN882H o około 42 KB, ale odblokowywało skrypty i trwałe pliki konfiguracyjne. [#21069454]

How can I flash an LN882H module without desoldering it from the PCB, and what board connections can interfere with RX, TX, or BOOT access?

Da się flashować bez wylutowania, jeśli masz fizyczny dostęp do BOOT i nic nie obciąża linii RX/TX. Problemem bywają przyciski, kondensatory debounce, ścieżki do innych układów lub trudny dostęp do samego BOOT. W takich przypadkach trzeba czasem przeciąć ścieżkę, usunąć kondensator albo bardzo precyzyjnie dolutować cienki przewód tylko na czas programowania. W wątku potwierdzono też przypadek, gdzie moduł LN-02 udało się zaprogramować in-circuit bez wylutowania i bez cięcia RX/TX. [#20924089]

What’s the difference between the regular LN882H firmware binary and the OTA file, and which one should be used for UART flashing versus Web App updates?

Do UART używa się zwykłego pliku binarnego, a do aktualizacji przez Web App używa się pliku OTA. Pomylenie ich jest częstą przyczyną błędów flashowania. Wprost zalecono: wybierz poprawny plik binarny do flashowania, nie plik OTA. Ta różnica wracała też przy Web App, gdzie użytkownicy trafiali na nie-OTA pliki i update nie przechodził. Reguła jest prosta: UART = pełny bin, Web App = OTA.bin. [#20955856]

How do I recover an LN882H device when I can no longer access the web UI, including safe mode, erase commands, and reflashing original firmware?

Najpierw spróbuj safe mode przez 5 szybkich cykli zasilania. 1. Wyłącz i włącz urządzenie 5 razy z krótką przerwą. 2. Po wejściu w safe mode połącz się z AP i popraw konfigurację. 3. Jeśli to nie pomoże, użyj LN882H_CMD_Tool.exe COM# flash erase_all albo wgraj z powrotem oryginalny firmware z backupu. W jednym przypadku dopiero reflashing oryginalnego firmware przywrócił dostęp do sieci domowej, gdy urządzenie po zmianach nie wracało do UI. [#21021640]

Why does changing the MAC address on some LN882H devices make them disappear from the network, and how can I verify the new IP afterward?

Po zmianie MAC urządzenie zwykle dostaje nowy lease DHCP, więc znika spod starego adresu IP. Samo ustawienie MAC może działać poprawnie, ale po zapisie trzeba szukać nowego IP w routerze albo skanerze sieci. Jeden użytkownik potwierdził zmianę MAC bez problemu i dodał, że trzeba upewnić się, że adres MAC jest prawidłowy, a następnie sprawdzić nowy adres w routerze. Jeśli urządzenie nadal znika, warto wrócić do dumpu i powtórzyć konfigurację od zera. [#20996463]

What is PowerSave on LN882H in OpenBeken, and how do PowerSave 0, 1, and 2 affect temperature, current draw, Wi-Fi stability, and BL0937 energy metering?

PowerSave zmniejsza pobór prądu i temperaturę LN882H, ale wpływa na sieć i pomiar energii. PowerSave 0 to tryb bez oszczędzania. PowerSave 1 obniżał temperaturę i prąd umiarkowanie. PowerSave 2 dawał największy efekt, np. spadek z 64.0°C do 36.0°C, ale podnosił ping do 56–73 ms i mógł psuć pomiary BL0937 oraz powodować reconnecty Wi‑Fi. Dla pojedynczego modułu raportowano też spadek poboru z około 90 mA do 50 mA przy trybie 1 i 35 mA przy trybie 2. [#21064064]

Why doesn’t static IP work on LN882H builds, and what is currently unimplemented in the wifi_init_sta code path?

Static IP nie działał, bo ścieżka LN882H była wtedy po prostu niezaimplementowana. Wprost wskazano funkcję wifi_init_sta(const char* oob_ssid, const char* connect_key, obkStaticIP_t *ip) jako miejsce wymagające aktualizacji w pliku hal_wifi_ln882h.c. Dlatego wpisy statycznego IP były ignorowane, a urządzenie wracało do DHCP. Dopóki ten fragment nie został uzupełniony, jedynym praktycznym obejściem było przypisanie stałego adresu po stronie routera. [#20997185]

How do I start and configure extra drivers like NTP, DHT, SSDP, or Wemo on LN882H, including backlog commands and startup command syntax?

Sterowniki uruchamiasz komendami, a kilka poleceń łączysz przez backlog. Przykład: backlog startDriver ntp; ntp_timeZoneOfs +2 albo backlog startDriver SSDP; startDriver Wemo. NTP wymaga ręcznego startu, a serwer ustawia się komendą ntp_setServer <IP>. DHT był obsługiwany per-pin, ale w części buildów LN882H nie był jeszcze aktywny. Wemo wymagał startu sterownika i sprawdzenia, czy działa endpoint /setup.xml, bo sam komunikat „OK” nie gwarantował wykrycia przez Alexę. [#21028427]

Why does OTA updating LN882H often fail in Firefox but work in Chrome or Chromium, and what was the root cause of the HTTP/OTA crash?

Problem nie leżał w samym pliku OTA, tylko w błędzie obsługi bufora HTTP/OTA po stronie LN882H. Firefox częściej wysyłał nagłówki i payload w układzie, który ujawniał błąd: kod OTA zbierał dane do bufora 4 KB, ale nie sprawdzał poprawnie sytuacji, gdy pojedynczy fragment mógł zapełnić bufor więcej niż raz. To kończyło się zapisem poza pamięcią i crashem wątku HTTP Clie. Po poprawce autorzy potwierdzili udane OTA w Firefox 132.0.2. [#21332121]

What’s the best way to remove or recover a forgotten OpenBeken web password on an LN882H device without losing control of it permanently?

Najpewniejsza metoda to wgranie przez UART builda bez wymuszania hasła albo builda recovery. Wskazano plik http_basic_auth.c i opcję kompilacji bez ALLOW_WEB_PASSWORD, co powoduje akceptację każdego połączenia. Później pojawiła się też wersja recovery: po restarcie i ponad 5 błędnych próbach logowania urządzenie mogło zaproponować pełny reset konfiguracji. To rozwiązanie było traktowane ostrożnie ze względów bezpieczeństwa, więc najbezpieczniejszy pozostaje własny build ratunkowy flashowany przez UART. [#21084206]

How can I flash LN882H from Linux or macOS instead of Windows, and which tools from the thread support that workflow?

Na Linuxie pojawiło się natywne narzędzie LN882Loader, opublikowane jako projekt do flashowania LN882H bez Windows. Wcześniej użytkownicy próbowali Wine, QEMU i VirtualBox z mieszanymi wynikami; GUI pod Windows działało w VM, ale bywało zawodne. Dla Windows później polecano też GUI flash tool, natomiast w samym wątku jedynym jasno wskazanym rozwiązaniem linuksowym był właśnie LN882Loader. Dla macOS nie podano gotowego natywnego narzędzia, więc praktyczna ścieżka z wątku to Linux tool albo Windows VM. [#21376296]
Generated by the language model.
ADVERTISEMENT