Find the camera on the network instead of asking for its address

Browse Source

The add-camera form asked for an IP address, and a shop owner does not
know their camera's IP address - it is on a sticker under the camera or
in a menu that differs by make. That field is where onboarding stopped
for anyone who was not an installer.

behavision/discover.py: one ONVIF WS-Discovery multicast (names the
camera and often its make) merged with a TCP sweep of port 554 across
the local /24 (misses nothing that streams). Stdlib only, ~4 s on the
office network, both cameras found. The add-camera sheet leads with
'Find cameras on this network'; picking a row fills the address and,
when the make is recognisable, the stream path.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KGcjxF1cNLcuwc3DAPcnfj

...

This commit is contained in:

Suriyakumarvijayanayagam

2026-09-21 12:27:47 +05:30

parent f88d441bbf

commit 1607f4ce74

13 changed files with 388 additions and 43 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

40

desktop/frontend/dist/assets/index-C-oYbwC6.js vendored

File diff suppressed because one or more lines are too long

2

desktop/frontend/dist/assets/index-Z_jL3Bie.css → desktop/frontend/dist/assets/index-CGAmTH1J.css vendored

File diff suppressed because one or more lines are too long

40

desktop/frontend/dist/assets/index-uOKaPIDr.js vendored Normal file

File diff suppressed because one or more lines are too long