P1 Meter on a Belgian Fluvius meter (SMR 5.0), firmware 6.0503, polling /api/v1/data once per second.
Response time is normally 121 ms median, p95 161 ms. Every 300 seconds one response takes between 837 ms and 2044 ms. Zero failed requests, wifi_strength 100 throughout, no disconnects.
I set cloud_enabled: false via PUT /api/v1/system and the stall persisted, unchanged in both period and phase — so it isn’t cloud upload.
Questions:
- What is this 300-second task ( interval aggregation, a flash write, something else)?
- Can the local API serve from cache during it rather than blocking?
Why it matters: a Marstek Venus E3 polls this meter for zero-export regulation and treats a delay of this length often as loss of the meter, triggering a full-power ±2500 W re-detection cycle. HomeWizard is listed by Marstek as a supported meter, so a non-blocking response would fix this for that whole class of consumer.