eightctl

eightctl covers the operations people actually want from a smart bed: status, on/off, temperature, alarms and schedules. The thing to plan around is the dependency model: the underlying API is unofficial and rate-limited, and the skill explicitly warns against repeated logins, so caching the session rather than authenticating per call is not optional. Temperature and alarm writes are also the kind of change a human notices immediately, so they belong behind a confirmation step instead of an autonomous loop. Keep EIGHTCTL_EMAIL and EIGHTCTL_PASSWORD in a secret store, not a committed config.

Use case: Adjusting sleep pod temperature and alarms from a scheduled automation.

# eightctl quick guide Pod control is split cleanly between read-only status and state-changing writes, and treating those two groups differently is the main operational decision. ## Auth Credentials come from a config file or from `EIGHTCTL_EMAIL` and `EIGHTCTL_PASSWORD`. The underlying API is unofficial and rate-limited, so authenticate once and reuse the session rather than logging in per command. ## Reads ```bash eightctl status eightctl alarm list eightctl schedule list eightctl audio state eightctl base info ``` ## Writes ```bash eightctl on|off eightctl temp 20 eightctl alarm create eightctl schedule update ``` Temperature and alarm changes are physically noticeable, so they belong behind a confirmation step rather than in an autonomous loop. Keep credentials in a secret store rather than a committed config file.