From b9a65e7b5f10dca8c005596bb63b17a9b7aada8e Mon Sep 17 00:00:00 2001 From: cjkas Date: Sat, 17 Oct 2026 23:43:16 +0200 Subject: [PATCH] docs: mark the Home Assistant apikey item fixed by ESPSomfy-RTS-HA#4 Co-Authored-By: Claude Opus 5.5 --- docs/LOOP_QUEUE_PLAN.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/LOOP_QUEUE_PLAN.md b/docs/LOOP_QUEUE_PLAN.md index 69a4f0f..29defcc 100644 --- a/docs/LOOP_QUEUE_PLAN.md +++ b/docs/LOOP_QUEUE_PLAN.md @@ -201,8 +201,7 @@ NVS stays at `0x9000`, so the rolling codes survive. The file system partition s ## Found during the review, not part of this plan -Still open: -- The Home Assistant integration sends no `apikey` header on `/shades`, `/groups` and the shade, group and tilt commands, so they fail with security on. The fix is [ESPSomfy-RTS-HA#4](https://github.com/cjkas/ESPSomfy-RTS-HA/pull/4), not yet merged. +Nothing is still open. Fixed by step 3: - The Ethernet pin conflict was only checked for the up pin, and the check used the shade's current protocol instead of the one being saved. @@ -222,3 +221,4 @@ Fixed later, each on its own: - A restore without shades skipped the shade and group records but not the room records, so it read the rest of the file from the wrong place. The skip is now `shadeModelBytes()` in `ConfigHeader.h`, with native tests (#54). - New ids stopped two short of the maximum: 30 shades, 14 groups and 14 rooms instead of 32, 16 and 16, an off-by-one from the first commit. They now run to the maximum (#57). - `SomfyGroup::fromJSON` read `linkedShades` into a local array and dropped it, and wrote past that array when a request listed more than 32 shades. The code is gone; members change only through `/linkToGroup` and `/unlinkFromGroup` (#58). +- The Home Assistant integration sent no `apikey` header on `/shades`, `/groups` and the shade, group and tilt commands, so they failed with security on. It now sends it on every call to a protected route ([ESPSomfy-RTS-HA#4](https://github.com/cjkas/ESPSomfy-RTS-HA/pull/4)).