Repository navigation
Web interface: recordings, people in boxes, and a tracking video - #463
Conversation
PR Summary by QodoRefresh WebUI gallery with playback, detection, and tracking video
AI Description
Diagram
High-Level Assessment
Files changed (18)
|
The gallery on /web-interface was shot before 339 WebUI commits: no playback from the card, no detection, and maintainers asked for both on the site itself, so a sceptic can be sent a link. Reshot from the lab hi3516av300 on WebUI master 25daa80 and firmware master+2061035. New tiles: Recordings, Camera - Settings - Motion detection, SD Card, OpenWall. Below the grid, a person tracking video and what object detection reports and where it goes. The motion detection tile is staged, and the page says so: the lab build has no person detector, so a street frame stands in for the picture and its three boxes are fed to the WebUI's own overlay over a mocked /ws/analytics. The video is a tracker prototype on a recorded street; burned-in boxes inpainted out, every head pixelated, including behind the tree where the reference tracks lose her. tools/webui-gallery, from what this run found: - the dashboard's snapshot tile showed the lab's real view: the scene now covers every camera picture, and the run fails if any is left uncovered; - WebRTC lines in the log printed public addresses: public IPv4 is now rewritten to 203.0.113.10 and audited (the firmware version is not one); - the scene goes in beside the player, so overlays still draw over it; - sign-in lands on live.cgi now; per-screen scene, analytics fixture, click; - the camera's crash notice is hidden for the shutter.
288f1f0 to
0422955
Compare
Code Review by Qodo
1.
|
…quad-dash-word The public-address rule let any dotted quad followed by "-letter" through as a firmware version, so "8.8.8.8-relay" in a log line would have passed both the redaction and the audit (Qodo, #463). The tool now reads the version the camera prints off the dashboard and keeps exactly that one; unread, nothing is kept, and the version would show as the documentation address instead.
…era so its pad shows The dashboard draws its graphs from samples it takes while open, over two minutes: shot after 2.5 s they were empty axes, now after 100 s. The Live page shows its PTZ pad only on a camera with a head to turn, so that tile comes from the lab's GK7205V510 stepper head, on WebUI master 62e4bcc.
… typical camera writes The tile showed 1.2 GB per 20 minutes: the lab camera is a 4K imx415, and its clips were H.264 for the shoot, at Automatic's 9088 kbit/s for that size. Reshot from clips recorded at 1920x1080 H.264 with bitrate Automatic (3200 kbit/s, 141-220 MB per 20 minutes); the camera is back on its own defaults. The click to the previous day goes, and with it the unused click option.
Maintainers asked for the site to show what the WebUI does now — playback from the card, people detected in a box — so a sceptic can be sent a link rather than an argument.
What changes on /web-interface
25daa80, firmwaremaster+2061035.public/video/), what object detection reports and where the boxes go, in en/ru/zh. Only what is already public (WebUI, the 2026-10-09 news post) is stated.Honesty and privacy
/ws/analytics.Gallery tool fixes (found by looking at the captures)
203.0.113.10and audited; selftest covers it.scene,analytics,click; camera crash notice hidden for the shutter.Checked: frontend lint, typecheck,
npm test(893) green; gallery selftest + verify clean; every capture reviewed by eye.