Sniffer: property record store, memory caps and text sensor rewrite
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- cpp
- Domain
- embedded-iot, testing-qa
Research direction
Start with the linked .specs/sniffer.md sections for property records, memory caps, text sensor, and configuration, then inspect sec_touch_sniffer.h and the hub frame buffer to check the specified limits. The issue names no test file; use the GoogleTest harness from #39 for the record store, history pool, text sensor builder, and config cases. Done means acceptance criteria 1–6 and 9 pass.
Written by the indexing model from the issue text.
Description
Spec: Property records, Memory caps, Text sensor, Configuration
- Store: 256 slots indexed by ID (fields block ~6 KB + raw block 256 × 48 B), u32 uptime seconds, change and query status rules. IDs above 255 are dropped and counted.
- History pool: 2 KB of variable-length previous values, depth 8 per ID, evicts from the ID with the most entries. Allocated only with
web_page: true. static_assertties the 48 B raw cap to the hub's frame buffer.- Text sensor:
id=rawfor unregistered records with a raw value, 2048 cap with, …+N more, built in a heap string. Removetime/RTC use. - Config errors: non-ESP32 target,
time_id,scan_end > 255. Add theweb_pageboolean (no effect yet). - Drop the stale memory comments in
sec_touch_sniffer.h.
Done: acceptance criteria 1–6 and 9 in the spec.
Tests (harness from #39): host GoogleTest for the record store (change rules, failures, IDs above 255), the history pool (depth, eviction from the ID with the most entries) and the text sensor builder (selection, 2048 cap, marker). Config tests for non-ESP32, time_id and scan_end > 255.
- 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
-
Sniffer: HTML pageOpen
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 52/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