Sniffer: HTML page

Open
#35 0 comments 0 reactions 0 assignees View on GitHub

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

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from distante/esphome-components

All issues in distante/esphome-components

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.