opencode/decisions.yaml, zigbee2mqtt/state.json
This commit is contained in:
@@ -642,4 +642,24 @@ notes:
|
||||
- matter
|
||||
- zigbee2mqtt
|
||||
pin: true
|
||||
status: superseded
|
||||
superseded_by: 2026-08-29-filter-plug-kasa-kp125m-on-native
|
||||
- id: 2026-08-29-filter-plug-kasa-kp125m-on-native
|
||||
date: 2026-08-29
|
||||
title: Filter plug = Kasa KP125M on native tplink; Matter path dropped
|
||||
decision: "Filter plug replaced: old Zigbee 0xffffb40e060893d8 was hardware-faulty (0xe1;
|
||||
do not re-diagnose). Replacement is a Kasa KP125M on the native tplink integration,
|
||||
NOT Matter. Entities renamed to filter_ prefix (switch.filter,
|
||||
sensor.filter_current_consumption, etc.); dashboard tile and health-alert refs
|
||||
cleaned."
|
||||
rationale: Outcome supersedes the earlier "KP125M Matter plugs" plan. Matter was verified
|
||||
to expose no power/energy entities, so tplink config-flow auto-discovery was used
|
||||
instead. Entity-IDs were client-renamed, so the dashboard tile had to be manually
|
||||
repointed to sensor.filter_current_consumption.
|
||||
entities:
|
||||
- switch.filter
|
||||
- sensor.filter_current_consumption
|
||||
integrations:
|
||||
- tplink
|
||||
pin: true
|
||||
status: active
|
||||
|
||||
Reference in New Issue
Block a user