claude-botandClaude Opus 5
c0791e2747
The Wetterstation now carries a non-default reporting configuration: min interval 5s on all ten reportable attributes, and tighter reportable-change deadbands on temperature, humidity and pressure. None of it is expressible in configuration.yaml - Zigbee2MQTT has no settings-schema field for reporting configuration - so it lives only on the device and in Z2M's database.db. This documents it and how to restore it. min was 10s against an 8.8s transmit interval. Since min is a hold-off, every change-triggered report was held past a transmit cycle and landed on the next, so attributes reported at best every 17.6s and drifted out of phase. The published stream showed no 8.8s periodicity at all. At min 5 each attribute reports on its own transmit and the stream carries one publish per cycle, measured at a mean gap of 8.69s. Publish volume fell from ~631/h to ~445/h because each publish is now a whole cycle rather than a fragment. The deadbands come from the shared modernExtend helpers, which the WS90 definition composes without overrides. They are anti-chatter values sized for battery-powered indoor sensors. Temperature was 1.00 C, giving a staircase that moved about twice an hour; it is now 0.1 C, matching the resolution the device actually reports. Pressure was 5 kPa - 50 hPa, which real barometric pressure never traverses, so it only ever updated on the hourly heartbeat that pressure_trend and weather_condition derive from. Note the same library configures the identical ZCL attribute with a 5 hPa deadband in its older reporting.ts helper, so the two code paths disagree by 10x. Anything that makes Z2M re-run configure on the device reverts all of it, and a fresh PVC will not have it. The restore commands are written out literally rather than generated by a shell helper, because the nested quoting through `kubectl exec -- sh -c` is where this goes wrong; each was executed and verified as written, including the read-back, and re-applying is a no-op. No behaviour change from this commit itself - the device was reconfigured at runtime, this only records it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>