You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
initialize reports the package version as serverInfo.version (it was empty), so a bug report says which build answered.
harmony_get_status with no hub configured adds a hint saying how to add one, instead of an empty list alone.
scripts/smoke_stdio.py: launches an installed server over stdio as an MCP client does and checks the first exchange. CI's new wheel-smoke job runs it against the built wheel on Linux, macOS and Windows; the release workflow runs it before publishing.
Issue templates: a bug report and a hardware report.
harmony_describe_activity (read-only): the devices an activity involves, with expected power (on/off/unknown) and input, and which device gets each button group. The expected state comes from each activity's fixit in the hub's config (new assumption H-FIXIT, medium); without one it says unknown.
mcp-server-harmony export: per hub, the raw config (account identifiers removed; --redact masks addresses) and a Markdown worksheet for rebuilding the setup on another remote, both readable by the owner only. A record to rebuild from, not a backup.
migrate_to_another_remote(target) prompt: describes every activity and writes a rebuild checklist for the named remote.
harmony_set_sleep_timer(minutes, hub=None): turns a hub's TV system off after 1-720 minutes (0 cancels), replacing a timer already set. It runs the normal power off, so the busy guard, rate limit and dry run apply, and retries for five minutes if the hub is busy or unreachable. The hub going off first drops it; switching activities keeps it. Held in the server's memory only (it outlives the chat under serve --http, not over stdio).
harmony_get_status gives each hub sleep_timer (when it fires, minutes left, or null) and last_sleep_timer (how the last one ended: fired, cancelled or failed, and why). Both are always present, null when empty.
harmony_tune_channel: tune by pressing a channel's digits (702, 5.1, 5-1) through the running activity or a named device, or by a favorite's name from the hub's new channels map in config.json (shown in harmony://hubs/{hub}, kept by check). The digits go out as one sequence (HubClient.send_sequence): one busy check, one rate-limit charge refused whole, one dry-run report. enter adds the select button. New assumption H-DIGITS.
harmony_get_history(hub, limit, after_seq): a record of each hub's activity changes (when, from, to, how long the previous state lasted, and whether this server or something else such as the remote or app caused it), newest first or oldest first after after_seq, like sofabaton_get_recent_presses. The first state read after startup is a recording_started marker, not a change; a change found after a reconnect is marked noticed_late. Kept in memory and in a capped, owner-only history.jsonl in the config directory, names only, never addresses. Turn it off with HARMONY_HISTORY=off or "history": false in config.json. New assumptions H-ACTIVITY-PUSH (hardware-verified for starts from the remote) and H-OFF-PUSH. HARDWARE_VALIDATION step 10.
Fixed
doctor --dump could keep the Logitech account's e-mail address: a real config's global.timeStampHash embeds it mid-string, where neither the key list nor log redaction caught it. The scrub now drops that key and any value with an address inside it.
harmony_send_command could not tell the - and . buttons apart (both normalised to nothing, so the first one won). Exact names are now matched before the normalised match.
doctor --dump and export kept four more identifiers that a real firmware 4.15.600 config carries: uuid, setupSession, hubId and remoteId. They are now masked (test: test_scrub_masks_hub_and_setup_identifiers), and the first real captures from both hubs are in tests/fixtures/recorded/.
mcp-server-harmony call no longer adds recording_started markers to the activity history (every run appended one per hub). call now only reads history.jsonl, so call get_history still shows what a server recorded; serve records as before. A history file read while a server is mid-append, even cut inside a multi-byte character, no longer fails to load.
harmony://hubs and harmony://hubs/{hub} wait out the same startup connection grace as tool calls when read right after the server starts.
Documentation
Hardware run of HARDWARE_VALIDATION steps 10 to 13 on 2026-11-12 (two hubs, firmware 4.15.600): H-FIXIT, H-DIGITS, H-OFF-PUSH and H-CONFIG-SHAPE are now hardware-verified (scope and open items in each note); H-ACTIVITY-PUSH and H-RECONNECT gained notes. Untried: favorites, Bedroom channel entry, the remote's own button for history, the unplug test, the sleep timer's busy retry.
README: the status reflects the 2026-11-04 hardware run; a Claude Desktop config using uvx; absolute links, so they work on PyPI.