feat(airconditioner): filter alarm interval on legacy ARTIK051 boards
Adds the Select the official app offers next to the filter reminder -- 180/300/500/700 hours -- which this board generation keeps as a FilterAlarmTime_ token in /mode/vs/0's options[] rather than on a /filter/* resource. Confirmed on hardware: stepping through all four radio positions in the app moved that one token and nothing else across all 19 resources, so the token carries the hour count verbatim; and a local write of 500 to a unit sitting on 700 was accepted and kept, surviving a restart. The cloud exposes none of this, so it is only available locally. Gated with the counter it belongs to, so boards carrying a real /filter/airdustfilter/vs/0 threshold keep using that one -- the gate is covered by a test that injects the token into a newer board's dump, since no non-legacy fixture carries it and the assertion would otherwise pass for the wrong reason. Also settles what filter_time measures: it counts UP -- running time accumulated since the last filter reset, not time remaining -- which an earlier revision of that comment explicitly left open. Three independent things agree: the token rising while the unit runs, FilterAlarmTime_ being the threshold it is measured against, and /alarms/vs/0's filter entry tracking the counter across two units on one site (a live unsuffixed 'FilterAlarm'/'Created' at FilterTime_5595 against the 'FilterAlarm_OFF'/'Deleted' placeholder at 1915). The alarm clearing by itself the moment the counter dropped under the threshold is the causal half of that, not just correlation. Resetting the counter is NOT solved and no reset entity is added. The descriptor records what was tried, and what the failures do and do not prove, so the next attempt starts from evidence instead of from scratch. Short version: the reset is a *command* (custom.dustFilter/resetDustFilter), not a value write, which is why nothing that writes the counter works; I could not work out how to drive that command locally. /actions/vs/0 is the obvious local command channel but publishes no schema, and I did not enumerate guessed action names against a live appliance. Written with Claude (AI), on the author's own hardware; every result quoted above is measured on the device rather than inferred.
This commit is contained in:
1 parent
eb938205ab
commit
9ee0dbb8f9
7 files changed
+199
-8
No files matched your search
@@ -9,6 +9,7 @@
|
||||
"diagnosis_status",
|
||||
"display_light",
|
||||
"energy_kwh",
|
||||
"filter_alarm_time",
|
||||
"filter_time",
|
||||
"good_sleep",
|
||||
"humidity",
|
||||
|
||||
@@ -9,6 +9,7 @@
|
||||
"diagnosis_status",
|
||||
"display_light",
|
||||
"energy_kwh",
|
||||
"filter_alarm_time",
|
||||
"filter_time",
|
||||
"good_sleep",
|
||||
"humidity",
|
||||
|
||||
@@ -9,6 +9,7 @@
|
||||
"diagnosis_status",
|
||||
"display_light",
|
||||
"energy_kwh",
|
||||
"filter_alarm_time",
|
||||
"filter_time",
|
||||
"good_sleep",
|
||||
"humidity",
|
||||
|
||||
Reference in new issue
Block a user