📝 fix: gateway reads are no longer 403 for END_USER #59
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/gateways-enduser-access"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Live re-verification on 2026-09-06 (probe account, 1 site, 6 gateways: 3 ×
POWER_GEN_4, 2 ×MONITOR_GEN_4SmartPlugs, 1 ×ACCESSORY):GET /api/gateways/by-gateway-uid/{uid}→ 200 on all 6 uidsGET /api/gateways/{id}→ 200 on all 6 idsGET /api/gateways/{id}/with-sales-company→ 200 on all 6 idsChanges
devices.md— Gateways section rewritten: the three reads annotated200 for END_USER, gateway document shape documented (key names only, no personal values), dated correction block in the style of #58README.md—gateway-by-uiddropped from the list of 403 role-forbidden endpointsROADMAP.md— §1 checkbox drainedTests: 132/133 green; the single failure (
test_version_matches_installed_metadata) pre-exists onmain(installed egg-info 0.4.2 vs code 0.4.3) and is unrelated (docs-only change).Resolves ROADMAP item §1 (gateways no longer 403).
Live re-verification on 2026-09-06 (probe account, 1 site, 6 gateways: 3 × POWER_GEN_4, 2 × MONITOR_GEN_4 SmartPlugs, 1 × ACCESSORY): - GET /api/gateways/by-gateway-uid/{uid} → 200 on all 6 uids - GET /api/gateways/{id} → 200 on all 6 ids - GET /api/gateways/{id}/with-sales-company → 200 on all 6 ids Documented the gateway document's shape (key names only — no personal values), dropped gateway-by-uid from the README's list of 403 role-forbidden endpoints. Resolves ROADMAP item §1 (gateways no longer 403).