cjkas fa7aaf0d49 refactor: hold shade settings in ShadeSettings and RemoteSettings ... The shade behaviour module (SHADE_BEHAVIOUR_PLAN.md, PR B) reads its settings through read-only structs, so they get one home each: RemoteSettings (flipCommands, bitLength, repeats) under SomfyRemote, shared with groups, and ShadeSettings (types, travel times, step size, flipPosition, simMy, sunSensor) under SomfyShade. Both are base structs, so shade->upTime and group->repeats keep working. A shade's flags byte is split by owner: simMy and sunSensor are settings, light is a field, and the sun flag, sunny, windy, demo mode and lighted bits are stateFlags. getFlags()/setFlags() put the byte together and take it apart for the config file, JSON, MQTT, events and group flags, so nothing saved or sent changes. Groups keep their own flags byte. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>		2026-10-16 20:31:39 +02:00
..
adr	docs: plan domain modules behind a LoopQueue	2026-10-15 21:38:43 +02:00
KNOWN_ISSUES.md	refactor: split the transports into the modules GLOSSARY.md names	2026-10-16 13:47:56 +02:00
LOOP_QUEUE_PLAN.md	refactor: split the transports into the modules GLOSSARY.md names	2026-10-16 13:47:56 +02:00
NICE_TO_HAVE.md	docs: add agent testing instructions and the RMT transmit idea	2026-10-16 09:11:17 +02:00
SHADE_BEHAVIOUR_PLAN.md	refactor: hold shade settings in ShadeSettings and RemoteSettings	2026-10-16 20:31:39 +02:00
SOMFY_SPLIT_PLAN.md	refactor: move the transports into entryPoints and outputs	2026-10-15 19:41:49 +02:00