Additional passive signatures¶
The October 3 source update adds 15 enabled rules, bringing the pack to 82 enabled rules across 21 categories. Three additional candidates are compiled out. The additions were selected from Fieldwatch catalog 90 and checked against original protocol, registry or interoperability sources where available. This is source and synthetic-packet validation; no new product has passed a controlled RF test on Hound yet.
Enabled coverage¶
| Addition | Match and interpretation |
|---|---|
| Axon / TASER | Assigned services FE6B, FE6C, FC81, plus Axon Body and Axon Fleet name prefixes. Medium ecosystem clues; no claim of an active camera or trigger. |
| Brilliant Labs Frame | Manufacturer-advertised service 7A230001-5475-A6A4-654C-8431F6AD49C4. Medium. The different suffix in Fieldwatch catalog 90 is not used. |
| Snap | Assigned service FE45. Low generic ecosystem clue, not confirmed Spectacles. |
| Omi | An Omi/omi name or Omi-/omi- prefix and service 19B10000-E8F2-537E-4F6C-D104768A1214 in the same advertisement. Medium. This UUID is shared with Arduino examples, so it never matches alone. |
| Bee / Limitless | Service UUIDs 03D5D5C4-A86C-11EE-9D89-8F2089A49E7E / 632DE001-604C-446B-A80F-7963E950F3FB, cross-checked against Omi's device integrations. Medium; a connected-only service will not be visible to Hound. |
| DULT tags | Structured FCB2 service data following the draft-00 header and length bounds. Medium protocol clue, without inferring the manufacturer from the network byte. |
| Wi-Fi Remote ID | Beacon vendor IE FA:0B:BC, type 0D, version-2 message pack with exact size/count and a valid supported Basic ID, Location or System message. High protocol match; unauthenticated. |
| Eddystone | Structured UID, URL, unencrypted TLM and EID frames on FEAA. Informational; Find Hub 40/41 frames are excluded. URLs are neither retained nor opened. |
| Estimote / Kontakt | Assigned services FE9A / FE6A. Informational vendor-service clues, without a retail operator or collection-activity claim. |
New WEARABLE and DULT_TAG categories have detector and alert toggles, field-guide cards, Ignore/Snooze, log entries and simulator samples. Wearables use a pendant/microphone snack and DULT uses a tag snack. Existing category numbers remain unchanged.
Eddystone and the two new vendor-beacon clues appear under the existing IBEACON category in the log. Their score is 19: they cannot trigger a pop-up, sound, vibration, display wake, Travel Watch, meals, XP, discovery unlock or unique-device reward, even with the lowest alert threshold and low feeding enabled. The existing generic iBeacon rule retains its earlier behavior and separate alert control. Informational records still use the existing bounded log/cache and emission limits.
Tracker state and Travel Watch¶
DULT details show the advertised near owner or separated state. A valid near-owner report silences ordinary alerts for that sighting and resets its Travel Watch presence window, matching the existing Samsung owner-connected policy. Reserved flag bits or incomplete payloads do not receive a state classification.
Find Hub details now distinguish normal 40 and separated/protection-mode 41 advertisements. Normal mode is not treated as proof of owner proximity and does not suppress Watch. These states are unauthenticated claims, not proof of safety, movement, ownership or unwanted tracking. State is volatile and is not added to logs/exports. Existing public export fields and privacy boundaries remain unchanged.
DULT identities use the existing keyed radio/address/type identity. The update does not correlate rotating identifiers or merge tags by brand, and it does not fix the separate limitation where a previously ignored tag changes its identity. State transitions can be emitted before the ordinary 30-second interval, subject to the existing 100 ms global limit.
Wi-Fi Remote ID bounds¶
The parser checks every vendor IE in a beacon, including packs appearing after ordinary vendor IEs. It validates up to nine 25-byte messages without increasing the 128-byte vendor buffer or 512-byte raw-frame limit. Existing AP fingerprints retain their first-IE behavior. The first supported message in a valid pack is retained for the volatile detail cache; later supported messages are validated but not all displayed from that packet. Repeated packs may therefore leave some detail fields unavailable.
BLE and Wi-Fi drone detail caches distinguish their radio transport. Message packs with only unsupported message types do not match. Unsupported protocol versions, malformed packs and invalid supported-message contents are rejected. Wi-Fi NAN, French drone identification and legacy DJI DroneID remain planned. No radio connection, probe, advertisement or transmission is added.
Disabled candidates¶
| Candidate | Why it is not enabled |
|---|---|
Target-associated iBeacon UUID 5993A94C-7D97-4DF7-9ABF-E493BFD5D000 |
Fieldwatch's author describes observations at two Florida stores. Hound has no independent captures. The candidate also requires valid iBeacon framing; bare B1BB does not establish a retailer. Production sees only generic iBeacon. |
| Nest Weave camera / doorbell product IDs | The original source confirms the identification-block layout and numeric Quartz/SmokyQuartz codes, but not every retail model mapping in Fieldwatch. Full version/vendor/product guards are implemented for tests; enablement awaits model/capture evidence. Bare FEAF, partial product fields and thermostats are not camera signatures. |
PLAUD name prefix |
Editable name and insufficient passive model/firmware evidence. Broad service 1910 is not adopted as a product identifier. |
Experimental rules have experimental=true, enabled_by_default=false and are excluded from the production header and binary pack. They cannot be enabled through the ordinary detector toggle. Further camera vendors, Even/RayNeo glasses, broad company IDs and generic module names have not been imported wholesale.
Saved data and resource bounds¶
Settings version 4 and Companion version 3 append the two new categories. The loader preserves existing detector/alert bits, ignores, outfit, discoveries, pet progress, calibration, appearance and identity key. New category bits start enabled for existing nonzero masks; an explicit all-off mask stays off. Frozen 19-category Pet, Companion V1/V2 and legacy state readers preserve historical layouts. New per-category counters start at zero. Power-interruption tests cover the migration's write boundaries.
The current Pet grows by 8 bytes and Companion by 48 bytes; their existing bounded copies remain. Detection keeps its compile-time 80-byte ESP32 budget. No new task, heap-owned collection, capture queue or evidence-cache slot is added. Device heap/stack measurements with SD remain a hardware acceptance step. Older firmware cannot read the upgraded saves: preserve an NVS backup before downgrading.
Sources and validation¶
Rule-level sources, interpretation limits and retrieval dates are recorded in data/provenance.yaml. Fieldwatch's MIT notice is retained in LICENSES/Fieldwatch-MIT.txt; no Kotlin detector or vendor lookup database is embedded. The implementation and synthetic fixtures are original C++.
- Fieldwatch catalog 90
- Bluetooth SIG service assignments
- Frame advertising implementation
- Omi integration definitions
- DULT draft-00 and Find Hub specification
- OpenDroneID Wi-Fi framing
- Eddystone frame specifications
- Weave BLE block layout and Nest product codes
The signature_expansion host suite covers positive packets, near misses, byte order, truncation, protocol overlap, quiet informational behavior, existing ignores/toggles, state transitions and Wi-Fi packs beyond the old vendor buffer. The production persistence suite covers migration and interrupted writes. See testing guide for actual build/test results; host success does not establish RF accuracy.