logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda
UV printer on your desk?
UV printer on your desk? Discover eufyMake E1 »
ADVERTISEMENT
Dostępna jest polska wersja

Czy wolisz polską wersję strony elektroda?

Nie, dziękuję Przekieruj mnie tam

Hosting OpenBekenIOT Web App's 'Logs' function in the LittleFS of the Device (BK7231T)

jkwim 6141 60
Best answers

Can I enlarge LittleFS on a BK7231T to host the OpenBeken web app files locally, and will a larger LittleFS break OTA updates?

Yes — you can enlarge LittleFS with `lfs_format`, and OTA may erase the LittleFS contents, so keep a backup; it does not sound like a blocker if you can restore the files afterward [#20928195] A 128 kB LFS was not enough for the original unmodified web app files, and because LittleFS uses 4 kB blocks, you need to budget space per file in whole sectors rather than raw file size [#20930090] The thread’s working setup used about 212 kB (`0x34000`) and later even 196 kB (`0x30000`) after minifying the `.vue` files and `httpVueLoader.js`; the key missing file was `filesystem.vue`, and `startup.js` had to be pointed at `/api/lfs/` paths with `indexdevice.html`/`indexlocal.html` adjusted accordingly [#20944917][#20946139] Large-file uploads were unstable until a fix was added: a small RTOS delay in the file upload function made drag-and-drop uploads work reliably [#20941452] For the final result, the web app was served from the device itself, and the “Logs” and filesystem pages worked in a closed network [#20944917][#20947236]
Generated by the language model.
ADVERTISEMENT
Report a violation of the law
Reply | New topic
  • #31 20947236
    jkwim
    Level 13  
    Posts: 186
    Help: 4
    Rate: 25
    I tried to build a small shell script to do the minification using my laptop by accessing the API's given for the tools.
    It works except I am having an issue with the large chunk of javascript found in filesystem.vue.
    Anyway that is trivial as I don't mind having to do that manually.

    With your help I now have a means of running OpenBK devices in a closed WiFi network and have access to Logs & Filesystem interfaces for on and off maintenance.

    I even tested configuring the other devices also to use same FS. So these files need to be stored in one device only.

    I also have Tasmota device with a RTC and it is running a NTP Server.

    So for my specific closed network I can now freely add more OpenBK devices.
  • ADVERTISEMENT
  • #32 20955109
    Angel0fDeath
    Level 13  
    Posts: 118
    Help: 2
    Rate: 33

    @jkwim I'm very glad everything is okay with you.
    Finally had some time to test it - I confirm it works like a charm... although I'm not going to use it.
    Please consider writing a tutorial and posting it.

    EDIT: To be clear - I used your tar file for the test
  • #33 20955148
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14622
    Help: 655
    Rate: 12638
    That's a very good news, it indeed deserves a tutorial! I would be able to link it from a Github to your work @jkwim then.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #34 20955352
    Angel0fDeath
    Level 13  
    Posts: 118
    Help: 2
    Rate: 33

    @p.kaczmarek2 I'm pretty sure without your help (RTOS delay) this couldn't happen, so thank you for the work you are doing and keep going. Personally, I will help with whatever I can for further development. Thank you.

    EDIT: And I already have a list for you to implement, but you probably already know my list from my posts
  • #35 20955878
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14622
    Help: 655
    Rate: 12638
    Angel0fDeath wrote:

    @p.kaczmarek2 I'm pretty sure without your help (RTOS delay) this couldn't happen, so thank you for the work you are doing and keep going. Personally, I will help with whatever I can for further development. Thank you.

    Do you know how to do online builds? It would be great if you had time to try playing around this RTOS delay, maybe it's possible to get better settings/better stability somehow, but the delay may need to be adjusted. Maybe delay must be more frequent or longer? You can do it fully online, without having any toolchain on your PC.
    See:
    OpenBeken online building system - compiling firmware for all platforms (BK7231, BL602, W800, etc)


    Angel0fDeath wrote:

    EDIT: And I already have a list for you to implement, but you probably already know my list from my posts

    I like your suggestions, but I am just a single person and it's sometimes hard for me to track things. So, please, feel free to repost your requests or open a separate topic about them. Don't worry, it will be considered helpful and not rude, altough the final decision of implementation depends on many factors, for example, on useability versus implementation difficulty ratio.

    In general, to anyone reading - any suggestions and help is welcome, feel free to post questions and requests on our forum. We're here to help. It's just as I said, I'm just a one person, it's hard to reply to every request quickly. You can support me via: https://www.paypal.com/paypalme/openshwprojects
    Helpful post? Buy me a coffee.
  • #36 20955948
    Angel0fDeath
    Level 13  
    Posts: 118
    Help: 2
    Rate: 33
    Will check it :)
    Concerning the list - it is not so long... currently:
    1. Smaller block size for Little FS if possible. 4K block size is too much for small partitions
    2. Flags 0 doesn't clear all flags. I also don't know why this command behaves differently on T and N devices setting different flags on...
    3. Flags page in device - the number in the beginning is not giving any useful information, unless you are very good in converting the number from dec to bin and see which bits are on - without calculator of course. More informative will be just to list the numbers of active flags, if someone can remember the meaning of all of the flags.... In general not needed...
  • #37 20956315
    jkwim
    Level 13  
    Posts: 186
    Help: 4
    Rate: 25
    p.kaczmarek2 wrote:
    That's a very good news, it indeed deserves a tutorial! I would be able to link it from a Github to your work @jkwim then.


    Give me a couple of days. I will try to put things together for a tutorial. For me it works to my liking now.
  • #38 21587296
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14622
    Help: 655
    Rate: 12638
    I am working on a feature that may be related to this topic.

    I am going to try moving LFS to external flash chip, currently interfaced by software SPI. I am not sure about the perfomance yet, but I'll just check this once it works.

    This would mean that we could get like even 4MB or 8MB of LFS.
    Hosting OpenBekenIOT Web App's 'Logs' function in the LittleFS of the Device (BK7231T)
    Anyone interested in testing that? @divadiow do you have any flash chips? You know, like from old laptop, etc?
    Helpful post? Buy me a coffee.
  • #39 21587304
    insmod
    Level 31  
    Posts: 1397
    Help: 164
    Rate: 436
    Why flash chips and not SD? SD can be used over SPI.
    With them we can get gigabytes of space, and adapters are usually very cheap.
  • #40 21587324
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14622
    Help: 655
    Rate: 12638
    SD card is also good idea, but I chose SPI Flash chips for a start because I just have lots of them from various scrap devices and they are also easier for install to me - no need to buy adapter, just a piece of proto board is enough (sample: https://www.elektroda.pl/rtvforum/topic3993012.html )

    My personal end use for such large LFS would be something like a measurements history, so I don't really need tens of megabytes, 4 or 8MB will be enough.

    Still, everything depends on speed and stuff, I will probably try to rewrite read/write routines to be faster and non-portable. As far as I remember, when testing bit bang WS2812, I managed to narrow down BK7231 port operations down to registers, and I guess they will be much faster than using SPI_Write HAL with platform HAL and Beken HAL.
    Short sample of what I attempted in the past:
    Code: C / C++
    Log in, to see the code
    Helpful post? Buy me a coffee.
  • #41 21587342
    divadiow
    Level 38  
    Posts: 5065
    Help: 438
    Rate: 893
    p.kaczmarek2 wrote:
    @divadiow do you have any flash chips?

    not as many as I would like. 512k, 2mb, 1mb, 8mb maybe

    I do have BK7252N/U, TXW817 (😁) and of course XF16 cams with micro-SD in place
  • #42 21587410
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14622
    Help: 655
    Rate: 12638
    It seems it's almost working. Currently I decided to hardcode LFS switch to SPI chip, but I am not sure.... but still, who else would use it? It's in obk_config.h
    Hosting OpenBekenIOT Web App's 'Logs' function in the LittleFS of the Device (BK7231T)
    I am doing final fixes, then I will check if it's even useable in current state.
    Helpful post? Buy me a coffee.
  • #43 21587412
    Angel0fDeath
    Level 13  
    Posts: 118
    Help: 2
    Rate: 33
    Hm. 4 - 8 MB of data is not so much. You can store your history on home automation server. Bigger LFS will be great if SD card used.. In this case FS will not be deleted (hopefuly) during OTA update. But in general idea is good to move FS outside of the flash.
  • #44 21587418
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14622
    Help: 655
    Rate: 12638
    I can think about SD card solution for you later, as @insmod also requested it, but for my target purpose (measurements storage for history) flash chips are perfect.

    However, as far as I remember, I will probably need to pick some existing FAT32 library for SD card. Still, it was some time since I did SD card support on PIC32 or whatever it was.

    Added after 1 [minutes]:

    PS: I love this tool:
    Hosting OpenBekenIOT Web App's 'Logs' function in the LittleFS of the Device (BK7231T)
    With this (and OBK simulator) I can developer for OBK even while extremaly low on free time.

    Added after 4 [minutes]:

    Interesting, it writes in 16 byte chunks internally.
    Hosting OpenBekenIOT Web App's 'Logs' function in the LittleFS of the Device (BK7231T)

    Added after 13 [minutes]:

    http_rest_post_lfs_file has a delay... inside,
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #45 21587442
    Angel0fDeath
    Level 13  
    Posts: 118
    Help: 2
    Rate: 33
    >>21587418 16 bytes chunks I think is ok for this cpu. Maybe more cash is needed for more. But in general flash chips dont give big performance... Btw, Im not going to use obk devices as hard drives 😀. Just remembered an year ago a guy wanted to host web app on one of his devices and we both helped him. Thats the reason Im saying it will be better with SD card. And make this feature optional or via flag, i.e. not by default

    Added after 5 [minutes]:

    And why you use http to write over spi, no spi fs library?
  • #46 21587455
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14622
    Help: 655
    Rate: 12638
    600 kB file uploaded... but it took way too long.
    Hosting OpenBekenIOT Web App's 'Logs' function in the LittleFS of the Device (BK7231T)


    I am using my own SPI write/read bitbang code (not yet optimized, I am going to optimize it A LOT) and I write to it through LittleFS
    Helpful post? Buy me a coffee.
  • #47 21587458
    Angel0fDeath
    Level 13  
    Posts: 118
    Help: 2
    Rate: 33
    >>21587455 I think the problem is with the size of your internal variables. An year ago I told you you dont host the flags correctly, because variables are max 32 bits. So for larger values you should make 2 (or 3) variables and to calculate them correctly. Negative values in your post mean variable is overflowed and not clear how much times.
    Each overflow of the variable leads to negative values, if not declared as byte or word, but even if declared on some cpus after overflow it is interpreted as negative value
  • #48 21587487
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14622
    Help: 655
    Rate: 12638
    What? This has nothing to do with flags and it's not negative. It's by @btsimonh design the size is shown after a dash. Sample:
    Hosting OpenBekenIOT Web App's 'Logs' function in the LittleFS of the Device (BK7231T)

    I was just showing the size of uploaded file. 600kB.
    Helpful post? Buy me a coffee.
  • #49 21587490
    Angel0fDeath
    Level 13  
    Posts: 118
    Help: 2
    Rate: 33
    >>21587487 ok, then sorry. My mistake 😀
    Didnt been here more than an year - personal problems... Sorry
  • #50 21587493
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14622
    Help: 655
    Rate: 12638
    Don't worry, it's nice to see you here again.

    There was (or maybe still is?) a flags issue, but as far as I know it's related to printing 64-bit variable to string. Not sure about it.

    Ok, I'm trying to make bit bang SPI faster now.
    Helpful post? Buy me a coffee.
  • #51 21587517
    Angel0fDeath
    Level 13  
    Posts: 118
    Help: 2
    Rate: 33
    >>21587493 with the flags - not only printing, clearing also (didnt tested). ClearFlags command didnt clear all. Maybe already fixed...
    Nevertheless, Im back, and thank you for all your work.
  • ADVERTISEMENT
  • #52 21587542
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14622
    Help: 655
    Rate: 12638
    Fast bitbang SPI path for Beken almost ready:
    Code: C / C++
    Log in, to see the code

    Maybe I will also unwind and inline read/write loops
    Helpful post? Buy me a coffee.
  • #53 21587591
    Angel0fDeath
    Level 13  
    Posts: 118
    Help: 2
    Rate: 33
    >>21587542 the code looks good,and probably will do the trick. Unfortunately cannaot help you (testing) - no flash chips 😞
  • #54 21587596
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14622
    Help: 655
    Rate: 12638
    Well, are you able to get access to some scrap TV, DVD player, laptop, PC, anything? That's where I get most of my flash chips.
    Helpful post? Buy me a coffee.
  • #55 21589234
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14622
    Help: 655
    Rate: 12638
    I think the 16 byte writes are caused by LFS cache limited to 16 bytes. I will try increasing it. Maybe we should also increase it in the main tree?
    Hosting OpenBekenIOT Web App's 'Logs' function in the LittleFS of the Device (BK7231T)

    Added after 30 [minutes]:

    Comparison, first with 16 cache, second 128. LFS on Software SPI Flash.
    Hosting OpenBekenIOT Web App's 'Logs' function in the LittleFS of the Device (BK7231T)
    Hosting OpenBekenIOT Web App's 'Logs' function in the LittleFS of the Device (BK7231T)

    Added after 4 [minutes]:

    For comparison - stock OBK. LFS on internal flash with cache 16. Crashed on the last entry.
    Hosting OpenBekenIOT Web App's 'Logs' function in the LittleFS of the Device (BK7231T)
    Helpful post? Buy me a coffee.
  • #56 21589333
    DeDaMrAz
    Level 22  
    Posts: 603
    Help: 34
    Rate: 129
    Well this also seems rather promising in relation to the topic of this thread, hosting webapp on a device.

    I have some chips as well 😁 so adding some of them for testing will probably be soon. Can be great for the purpose of logging and storing thing on the module.

    But overall I'll second the idea of an SD card instead of the chips just because of space and possibly speed. With that we can host the webapp and have "unlimited" log space which is always nice.

    @Angel0fDeath

    Glad to see you back on the project!
  • #57 21589422
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14622
    Help: 655
    Rate: 12638
    Large files are still slow, I need to check how would it behave with many smaller files.

    I want to use it to store measurements history on device.
    Helpful post? Buy me a coffee.
  • #58 21654248
    divadiow
    Level 38  
    Posts: 5065
    Help: 438
    Rate: 893
    divadiow wrote:
    I do have BK7252N/U, TXW817 (😁) and of course XF16 cams with micro-SD in place

    :D

    MicroSD card reader module on a blue PCB Micro SD card adapter with six pins labeled CS, SCK, MOSI, MISO, VCC, GND
  • #59 21654251
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14622
    Help: 655
    Rate: 12638
    What is this chip on board? Voltage levels converter?
    Helpful post? Buy me a coffee.
Reply | New topic
Report a violation of the law

Topic summary

✨ The discussion focuses on hosting the OpenBekenIOT Web App's 'Logs' function within the device's LittleFS filesystem on BK7231T and BK7231N devices. The default LittleFS size is 32kB, which is insufficient for hosting multiple web app files such as startup.js, httpVueLoader.js, vue.min.js, and logs.vue. Users experimented with increasing LittleFS size up to 256kB and 200kB (0x32000), with mixed success due to device reboots and low heap warnings during large file uploads. A key finding was that adding RTOS delays during file upload improved stability, as implemented in a test firmware build. Firmware upgrades to versions around 1.17.404 and above were recommended for better performance. Minification of JavaScript and Vue files significantly reduced storage requirements, enabling hosting within the constrained LittleFS space. The memory layout of BK7231T and BK7231N devices was reviewed to understand partitioning and avoid overwriting OTA or application partitions. Alternative hosting solutions suggested include running the web app on a NAS or router with OpenWrt. Further development includes moving LittleFS to external SPI flash chips (4-8MB) or SD cards to expand storage capacity for logs and web app files. Fast bitbang SPI implementations and increased LittleFS cache sizes were tested to improve performance. The community encourages creating tutorials for these solutions and ongoing firmware improvements to enhance stability and usability of hosting web apps directly on BK7231 devices.
Generated by the language model.
Today's popular

FAQ

TL;DR: With a 196–212 kB LittleFS and the upload fix, OpenBeken can host Logs locally; one tester confirmed it “works like a charm.” This FAQ helps BK7231T/BK7231N users run Logs and Filesystem pages inside a closed network without external hosting. [#20955109]

Why it matters: Hosting the WebApp on-device lets OpenBeken devices expose Logs and Filesystem pages even when the network has no internet or permanent NAS/Docker host.

Option Typical LittleFS target Result from the thread Main trade-off
Default internal LittleFS 32 kB Too small for the needed WebApp files Not enough space
Enlarged internal LittleFS 128–212 kB Works after path fixes and upload workarounds May trigger low-heap warnings or uploads failing
External SPI flash LittleFS 4–8 MB Under development in 2025 Much more space, slower for large files
SD card over SPI Much larger than flash chips Suggested, not implemented in-thread More space, more integration work

Key insight: The biggest blocker was not raw flash size alone. Large-file uploads became stable only after an RTOS delay was added, and final success also required correct /api/lfs/ paths plus inclusion of filesystem.vue.

Quick Facts

  • OpenBeken LittleFS used 4,096-byte blocks, so even tiny files could consume a full 4 kB block; real storage use was much higher than file size alone suggests. [#20930090]
  • A working self-hosted setup used 0x34000 = 212 kB LittleFS, then later shrank to 0x30000 = 196 kB after manual minification of .vue, JavaScript, and CSS content. [#20944917]
  • vue.min.js was about 92 kB, httpVueLoader.min.js was reduced from 10,890 bytes to 5,867 bytes, and these savings helped fit Logs plus Filesystem into internal flash. [#20928161]
  • Upload behavior differed by chip family: BK7231T devices were easier to fill reliably, while BK7231N often failed on direct upload of vue.min.js but could accept it via a .tar backup workaround. [#20942411]
  • OTA could erase LittleFS, but the thread confirmed you can back it up and restore it; OpenBeken also preserved the configured LittleFS size across one tester’s OTA cycle. [#20933489]

How do I host the OpenBekenIOT Web App Logs function directly from LittleFS on a BK7231T or BK7231N device?

Use a larger LittleFS, upload the required WebApp files, then point OpenBeken to indexdevice.html served from /api/lfs/. A confirmed working setup used 0x34000 LittleFS, modified startup.js paths, and configured the device WebApp URL to the on-device page. The final result loaded Logs and Filesystem from the device itself inside a closed network. [#20944917]

What is LittleFS in OpenBeken, and how is it used to store WebApp files on BK7231 devices?

“LittleFS” is a lightweight embedded filesystem that stores files in flash memory, uses fixed-size allocation blocks, and lets OpenBeken keep WebApp assets such as .js, .vue, HTML, and backup archives directly on the device. In this thread it was used to hold files like vue.min.js, startup.js, logs.vue, and filesystem.vue so the device could serve its own WebApp pages through /api/lfs/. [#20928161]

Why does a BK7231N or BK7231T device reboot when uploading a large file like vue.min.js to LittleFS?

The reboot happened because the upload path was unstable during long writes, especially for large files such as the 92 kB vue.min.js. Testing reproduced the issue, and adding an RTOS delay inside the file upload function improved stability. BK7231N remained harder than BK7231T, and some N devices still needed a .tar workaround after the fix. [#20941452]

How would increasing LittleFS to 128kB or more affect OTA updates and the risk of the filesystem being erased?

Increasing LittleFS can work, but OTA may erase the filesystem contents. The thread explicitly says this is acceptable if you keep a backup, because LittleFS backups can be downloaded and restored later. One tester also noticed that after OTA, files were wiped but the remembered configured LittleFS size still appeared as 0x40000 on the next format step. [#20933489]

Which WebApp files actually need to be stored in LittleFS to make the OpenBeken Logs page work in a closed network?

You need more than just the Logs component. The final working set included startup.js, vue.min.js, httpVueLoader.min.js, filesystem.vue, logs.vue, info.vue, myComponent.vue, and indexdevice.html; the author first failed because filesystem.vue was missing. That missing file was described as the most important omission in the earlier attempts. [#20944917]

What changes are required in startup.js, window.root, and window.device so indexdevice.html or indexlocal.html can load files from /api/lfs/?

Set window.root to /api/lfs/, set window.device to the device IP, and load startup.js from /api/lfs/startup.js. Then update startup.js so component paths use window.root+'logs.vue', window.root+'filesystem.vue', and similar on-device paths instead of external ones. Using / as window.root caused partial loading, while /api/lfs/ matched the working setup. [#20944917]

Why does LittleFS block size matter so much on OpenBeken, and how do 4KB blocks change the real space used by each file?

Block size matters because each file consumes whole 4,096-byte blocks, not exact byte counts. The thread explains that if a file occupies even 1 byte in a block, another file cannot reuse that remaining space, so sizing based only on raw file totals fails. A practical formula given was (((filesize div 4096) + 1) * 4096) for estimating space per file. [#20930090]

What’s the best way to calculate the LittleFS size needed for files like vue.min.js, httpVueLoader.js, logs.vue, and filesystem.vue on BK7231?

Calculate per-file space in 4 kB blocks, then add headroom. A direct rule from the thread was: (((filesize in bytes) div 4096) + 1) * 4096) for each file, then sum the results. That method explained why a file set totaling about 147 kB of real data still occupied about 156 kB in LittleFS. [#20931925]

How do I use lfs_format and lfs_size in OpenBeken to create and verify a larger LittleFS partition?

Use a format command, reboot if needed, then verify with lfs_size. 1. Run lfs_format 0x20000 or another target size. 2. Reboot the device after formatting. 3. Run lfs_size and confirm messages such as configured 0x20000. The thread shows this exact workflow for a 128 kB LittleFS on BK7231N. [#20928296]

What is an RTOS delay, and why did adding it to the OpenBeken file upload function improve LittleFS upload stability?

“RTOS delay” is a scheduler pause inside firmware code that briefly yields execution, reduces long uninterrupted loops, and helps watchdog, networking, or memory-sensitive tasks continue running during heavy operations. In this case, adding that delay inside the upload function stopped many mid-write reboots and let a tester drag and drop all WebApp files onto LittleFS successfully. [#20941452]

How can I work around large-file upload failures in OpenBeken by using tar backups or uploading the biggest files first?

Upload the largest files first, or move them through a LittleFS .tar backup instead of direct file upload. One tester copied vue.min.js to a BK7231T first, downloaded the resulting .tar, and then restored that archive onto a BK7231N, where direct upload had failed. Another practical note was that large files could take 30–40 seconds to copy. [#20942411]

Which firmware versions or test builds fixed the LittleFS upload instability on BK7231T and BK7231N modules?

The key fix was the test build from pull request 1056, named with delay_for_littlefs and later used as OpenBK7231N_1056_merge_ad333e21dec2 or similar board-specific binaries. It fully solved uploads on several BK7231T tests and improved BK7231N enough that a final 128 kB setup succeeded, though N still showed direct vue.min.js upload issues. [#20943770]

What causes the OpenBeken ‘Low heap warning’ after enlarging LittleFS, and how should that influence the filesystem size you choose?

The warning indicates memory pressure, so you should stop increasing LittleFS just because flash space exists. The thread reports Error:MAIN:Low heap warning! at 256 kB, also still at 212 kB and even 196 kB, which means the safest choice is the smallest filesystem that still fits your files. In practice, users converged on about 200–212 kB rather than 256 kB. [#20946139]

How can I minify JavaScript, CSS, and .vue files from the OpenBeken WebApp to fit the Logs and Filesystem pages into a smaller LittleFS partition?

Minify the contents inside <script> and <style> sections separately, then save the reduced .vue files under new names such as logs.min.vue. The thread reports shrinking httpVueLoader.min.js from 10,890 bytes to 5,867 bytes and reducing the whole LittleFS target from 212 kB to 196 kB. That made a self-hosted Logs plus Filesystem setup fit more comfortably. [#20946139]

SPI flash chips vs SD cards for external OpenBeken storage: which is better for hosting the web app and keeping larger log or measurement history files?

SPI flash chips were the practical choice in the thread, while SD cards were the larger-capacity idea. The developer chose spare SPI flash first because 4–8 MB was enough for measurement history and easier to wire on a proto board, but other participants preferred SD for much larger space and better fit for WebApp hosting plus long-term logs. Large-file speed on software SPI flash was still a concern. [#21587418]
Generated by the language model.
ADVERTISEMENT