Repository navigation
v0.3.0
The v0.2.0 tag never reached PyPI (it pointed at a commit still versioned 0.1.0), so this release carries 0.2.0's changes too.
Breaking Changes
- Tool Namespacing: All MCP tools are now prefixed with
harmony_(harmony_get_status,harmony_list_activities,harmony_list_devices,harmony_list_commands,harmony_start_activity,harmony_power_off,harmony_send_command) to avoid naming collisions in MCP clients when run alongside sibling smart home servers. - CLI Shorthand: The
callCLI subcommand accepts both prefixed (harmony_get_status) and legacy/shorthand names (get_status,status).
Security
- Network Topology Masking: Internal hub LAN IPv4 addresses in
harmony_get_statuspayloads are sanitized withmask_ip(e.g.192.0.2.20->x.x.x.20) to prevent leaking local network topology to LLMs over stdout.
Documentation
HARDWARE_VALIDATION.mdstep 7: the Office Hub results forhold_ms(held presses acted as one tap on the LG TV and Onkyo).H-HOLDis unchanged inassumptions.pyuntil a configured hold action is checked.HARDWARE_VALIDATION.mdsteps 6, 8 and 9: results of the 2026-11-04 run on the Office and Bedroom hubs (presses, start/switch, multi-hub power off, the busy guard, config push, reconnect), with what each did not show.
Assumptions (hardware, 2026-11-04)
H-FORCE-OFFis nowhardware-contradicted: a forced power off sent during a start from the physical remote was refused by the hub ("Activity in progress").power_off(force=true)is unchanged; it still skips this server's own busy guard, but the hub can refuse it. README and CLAUDE.md say so. Whetherforcehelps a hub that is really stuck is untested.H-CONFIG-PUSHis nowhardware-verified: an activity renamed in the Harmony app showed up inharmony_list_activitieswith no restart.H-RECONNECTstayssimulator-only, with a note: a hub unplugged and replugged came backreachable: trueon its own, but the re-read of state after a reconnect wasn't exercised.