wrapup: matter code-gen requires on-network phone; bunkhouse ZW1405 note; fix boat keywords typo
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
@@ -34,12 +34,12 @@ user-invocable: true
|
||||
<references>
|
||||
<reference file="reference/boat.md"
|
||||
categories=["water"]
|
||||
keywords=["boat", "dock, "launch"] />
|
||||
keywords=["boat", "dock", "launch"] />
|
||||
</references>
|
||||
|
||||
<references>
|
||||
<reference file="reference/home-assistant.md"
|
||||
summary="Home Assistant: access/WS+Supervisor API, dual Nest integration, matter.js 9.0.4 new fabric + re-commissioning procedure (1/8 done, addon-restart gotcha), first backup taken, main Lovelace dashboard"
|
||||
summary="Home Assistant: access/WS+Supervisor API, dual Nest integration, matter.js 9.0.4 new fabric + re-commissioning (1/8 done, blocked on on-network code generation, addon-restart gotcha), first backup taken, main Lovelace dashboard"
|
||||
categories=["home-automation"]
|
||||
keywords=["home assistant", "HA", "home.thelonglakelodge.com", "matter", "nest", "thermostat", "climate", "dashboard", "lovelace", "HVAC", "in floor heating", "environmentals", "core_matter_server", "172.24.24.50"] />
|
||||
</references>
|
||||
|
||||
@@ -78,11 +78,14 @@ migration from the Python server lost the fabric — new fabric_id 2; the old
|
||||
fabric `1E5211CA4C7B5275` is gone. All 8 Nest thermostats need re-commissioning
|
||||
onto the new fabric. DONE: Lodge Kitchen (node 16, `climate.lodge_kitchen_nest`,
|
||||
device labeled `matter_nest`+`matter_hvac`, bridged temp sensor "Kitchen").
|
||||
REMAINING: Office, Primary Bathroom, Bunkhouse Kitchen, Eat-in Kitchen,
|
||||
Basement Bedroom, Tub Room, Basement Living Room. All stale old-fabric devices
|
||||
REMAINING (blocked until someone is on the lodge network to generate codes):
|
||||
Office, Primary Bathroom, Bunkhouse Kitchen, Eat-in Kitchen, Basement Bedroom,
|
||||
Tub Room, Basement Living Room. All stale old-fabric devices
|
||||
deleted from the registry.
|
||||
|
||||
Procedure (works fully remotely):
|
||||
Procedure (requires phone ON the lodge network — Google Home refuses to
|
||||
generate a Matter code off-network, verified 2026-07-05; commissioning itself
|
||||
is then drivable remotely via WS):
|
||||
1. Google Home app (lodge account) → thermostat → Settings → Linked Matter
|
||||
apps & services → Link apps & services → 11-digit code (single-use, ~5 min).
|
||||
2. WS `{"type":"matter/commission","code":"<code>"}` (or HA UI Add device).
|
||||
|
||||
@@ -36,6 +36,11 @@ Error `userCode for code slot N not found` from `zwave_js.set_lock_usercode`
|
||||
problem. The sync script's pre-`get` prevents it; manual fix:
|
||||
`zwave_js.invoke_cc_api {device_id, command_class: "99", method_name: "get", parameters: [N]}`
|
||||
then re-run the sync.
|
||||
|
||||
Bunkhouse lock (Z-Wave node 8) intermittently returns `ZW1405 - node failed to
|
||||
decode the message` on commands (seen 2026-07-05 on unlock + usercode set).
|
||||
Sync tolerates it (continue_on_error + daily self-heal retries); if it
|
||||
persists, suspect S2/RF health on that lock.
|
||||
</troubleshooting>
|
||||
|
||||
<backup>
|
||||
|
||||
Reference in New Issue
Block a user