Web App Flash Tab: Inconsistent Status Messages for Tuya GPIO and Custom Dump Buttons

Question 1

Download actions now log “downloading…” instead of “reading…”, while read actions continue to log “reading…”. This fixes the earlier mismatch where the Tuya GPIO and Custom downloads could show read-style messages and Custom lacked a final ready log. The Full Dump already confirmed completion correctly. [Elektroda, divadiow, post #21800096]

Answer

Download actions now log “downloading…” instead of “reading…”, while read actions continue to log “reading…”. This fixes the earlier mismatch where the Tuya GPIO and Custom downloads could show read-style messages and Custom lacked a final ready log. The Full Dump already confirmed completion correctly. [Elektroda, divadiow, post #21800096]

Question 2

Use the Full 2MB dump action. Internally it calls startDumpJob with parameters like name, job type “FullDump”, start=0, size=2097152, mode="QIO". Expect a completion message when the dump finishes. This maps to a 2,097,152‑byte image suitable for full backup. [Elektroda, p.kaczmarek2, post #21801475]

Answer

Use the Full 2MB dump action. Internally it calls startDumpJob with parameters like name, job type “FullDump”, start=0, size=2097152, mode="QIO". Expect a completion message when the dump finishes. This maps to a 2,097,152‑byte image suitable for full backup. [Elektroda, p.kaczmarek2, post #21801475]

Question 3

startDumpJob centralizes dump setup to remove duplicated logic. It takes arguments for label, job type, start offset, size, and flash mode, then starts the dump. This refactor improves maintainability and ensures consistent status messaging across Full, Tuya GPIO, and Custom operations. [Elektroda, divadiow, post #21801456]

Answer

startDumpJob centralizes dump setup to remove duplicated logic. It takes arguments for label, job type, start offset, size, and flash mode, then starts the dump. This refactor improves maintainability and ensures consistent status messaging across Full, Tuya GPIO, and Custom operations. [Elektroda, divadiow, post #21801456]

Question 4

The workflow is currently BK7‑centric. The UI now greys out certain RF/TLV tools when the detected chipset does not start with “bk7”, signaling features are scoped to BK7. Broader platform read support remains an open consideration. [Elektroda, divadiow, post #21802297]

Answer

The workflow is currently BK7‑centric. The UI now greys out certain RF/TLV tools when the detected chipset does not start with “bk7”, signaling features are scoped to BK7. Broader platform read support remains an open consideration. [Elektroda, divadiow, post #21802297]

Question 5

After conversion, the TLV block can be gone, so a scan returns nothing. Screenshots in the thread show a converted BK7238 image with TLV missing, implying the original factory TLV was overwritten during the process. [Elektroda, divadiow, post #21802340]

Answer

After conversion, the TLV block can be gone, so a scan returns nothing. Screenshots in the thread show a converted BK7238 image with TLV missing, implying the original factory TLV was overwritten during the process. [Elektroda, divadiow, post #21802340]

Question 6

Flash vars overwrite it. An expert confirmed, “Flash vars” are the component responsible for overwriting, which explains missing TLV post‑conversion and failed TLV detection. [Elektroda, insmod, post #21802415]

Answer

Flash vars overwrite it. An expert confirmed, “Flash vars” are the component responsible for overwriting, which explains missing TLV post‑conversion and failed TLV detection. [Elektroda, insmod, post #21802415]

Question 7

Back up the entire flash before conversion. Users often reassemble devices only to realize they need RF, and Easy Flasher does not require a full backup by default. Do a full 2 MB dump first to preserve RF data. [Elektroda, divadiow, post #21802348]

Answer

Back up the entire flash before conversion. Users often reassemble devices only to realize they need RF, and Easy Flasher does not require a full backup by default. Do a full 2 MB dump first to preserve RF data. [Elektroda, divadiow, post #21802348]

Question 8

Yes. The maintainer reviewed the improvements and stated, “Way better, I will merge it now,” referring to the startDumpJob refactor and parameterization shown with a Full 2MB example. [Elektroda, p.kaczmarek2, post #21801475]

Answer

Yes. The maintainer reviewed the improvements and stated, “Way better, I will merge it now,” referring to the startDumpJob refactor and parameterization shown with a Full 2MB example. [Elektroda, p.kaczmarek2, post #21801475]

Question 9

Here, “Tuya” refers to the Tuya GPIO configuration dump/download option in the Flash tab. The change ensures its button shows “downloading…” while read actions retain “reading…”, aligning logs with the operation. [Elektroda, divadiow, post #21800096]

Answer

Here, “Tuya” refers to the Tuya GPIO configuration dump/download option in the Flash tab. The change ensures its button shows “downloading…” while read actions retain “reading…”, aligning logs with the operation. [Elektroda, divadiow, post #21800096]

Question 10

OpenBeken is the project whose Web App received PRs that fixed messaging and added BK7‑specific tooling. The maintainer discussed merge and future string cleanup around startDumpJob, indicating active development. [Elektroda, p.kaczmarek2, post #21801475]

Answer

OpenBeken is the project whose Web App received PRs that fixed messaging and added BK7‑specific tooling. The maintainer discussed merge and future string cleanup around startDumpJob, indicating active development. [Elektroda, p.kaczmarek2, post #21801475]

Question 11

The scan reads 0x1000‑byte (4096‑byte) chunks. A TLV header crossing chunk boundaries can be missed if you only check within each chunk. Use overlapping or carry‑over buffers to avoid boundary misses. “You won’t find it that way.” [Elektroda, p.kaczmarek2, post #21802316]

Answer

The scan reads 0x1000‑byte (4096‑byte) chunks. A TLV header crossing chunk boundaries can be missed if you only check within each chunk. Use overlapping or carry‑over buffers to avoid boundary misses. “You won’t find it that way.” [Elektroda, p.kaczmarek2, post #21802316]

Question 12

Yes. The maintainer noted flash vars are not critical and can be moved globally elsewhere. Even if some updates break minor things, the trade‑off favors preserving RF data integrity across updates. [Elektroda, p.kaczmarek2, post #21802420]

Answer

Yes. The maintainer noted flash vars are not critical and can be moved globally elsewhere. Even if some updates break minor things, the trade‑off favors preserving RF data integrity across updates. [Elektroda, p.kaczmarek2, post #21802420]

Question 13

Answer

Open Flash tab and select the Full 2MB dump action.
Confirm it runs startDumpJob with start=0, size=2097152, mode="QIO".
Wait for the completion message, then save the file. [Elektroda, p.kaczmarek2, post #21801475]

Question 14

Custom previously lacked a final “ready!” log. With the update, downloads show “downloading…”, bringing parity with other buttons. The Full Dump already indicated completion correctly, so user feedback is now consistent. [Elektroda, divadiow, post #21800096]

Answer

Custom previously lacked a final “ready!” log. With the update, downloads show “downloading…”, bringing parity with other buttons. The Full Dump already indicated completion correctly, so user feedback is now consistent. [Elektroda, divadiow, post #21800096]

Question 15

Yes, the maintainer suggested possibly removing one string name in the future, since all three may not be required. That would further streamline startDumpJob usage and UI text. [Elektroda, p.kaczmarek2, post #21801475]

Answer

Yes, the maintainer suggested possibly removing one string name in the future, since all three may not be required. That would further streamline startDumpJob usage and UI text. [Elektroda, p.kaczmarek2, post #21801475]

Question 16

If the UI greys out BK7‑specific tools, avoid those steps and do a standard full dump first. That preserves data while you verify hardware support and tool compatibility. Then proceed with targeted operations. [Elektroda, divadiow, post #21802297]

Answer

If the UI greys out BK7‑specific tools, avoid those steps and do a standard full dump first. That preserves data while you verify hardware support and tool compatibility. Then proceed with targeted operations. [Elektroda, divadiow, post #21802297]

Web App Flash Tab: Inconsistent Status Messages for Tuya GPIO and Custom Dump Buttons

Post #1

Post #2

Post #3

Post #4

Post #5

Post #6

Post #7

Post #8

Post #9

Post #10

Post #11

Post #12

Post #13

Post #14

Post #15

Post #16

Post #17

Post #18

Post #19

Post #20

Post #21

Post #22

Post #23

Post #24

Post #25

Post #26

Post #27

Post #28

Post #29

Post #30

Topic summary