Sniffer: HTML page
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- html, javascript, node.js
- Domain
- embedded-iot, frontend, tooling
Research direction
Read the page spec and prototype C in prototype/sniffer-page; the page logic and tests belong under components/sec_touch_sniffer/web/. Start with the node --test harness from issue #39 and use its coverage list to map the required behavior. Done means the page implements the listed polling, merge, storage, and export behavior, with the described tests passing and a build step that embeds the gzipped page in flash.
Written by the indexing model from the issue text.
Description
Spec: Page. Prototype: variant C on prototype/sniffer-page.
- ID map, drawer, change feed with per-ID mute, filters, scan control with progress labels.
- Type guessing per value and per ID; wall time from uptime.
- Polling: 1 s, 5 s backoff, resync on first load / boot change / seq going down. Reboot merge (device wins, browser-only IDs stale).
- Browser storage keyed by MAC; JSON + CSV export with notes.
- Build step that gzips the page into a
constexpr uint8_t[]served from flash.
Tests (harness from #39): the page logic lives in plain modules under components/sec_touch_sniffer/web/, with node --test coverage for type guessing (per value and per ID), wall time from uptime, the reboot merge (device wins, browser-only IDs stale), resync triggers (first load, boot change, seq going down), the poll backoff and the CSV/JSON export shape.
- Dominant language
- C++
- Stars
- 8
- Forks
- 4
- Avg merge
- 15h 58m
- Merged PRs (30d)
- 5
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from distante/esphome-components
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Sniffer: hub message tap with raw strings and scan outcomePossibly taken @distante claimed this today. Open
Difficulty 4/5 3-5 days Newbie friendliness 53/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
All issues in distante/esphome-components
Similar issues
-
upstream-blocked
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ROCm/FastFlowLM#1057 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
NatronGitHub/openfx-gmic#45 ·
Maintainers usually reply within 1 day
-
app area::installer bug wg::gui-app
Difficulty 1/5 Under an hour Newbie friendliness 88/100
lemonade-sdk/lemonade#4186 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100