You can now disable the HTTP server if you do not use it. - #69 - @svenove

This fixes a bug where command were not being executed correctly - fixes #51 - @farooqu

Fixes a crasher - #53 - @farooqu

Fixes a crasher noted in #47 - @farooqu

This fixes a bug when querying activity commands.

• Fixing issue with querying activity commands - #46 - @farooqu

2.3.0 adds the ability to send remote commands that are then interpreted by the harmony hub based on the current active activity. It also adds a way to repeat a command with a single command.

• activity based commands - #38 - @jawilson
• key repeats - #43 - @farooqu
• Forever fixes - #40 - @pogil

Harmony API now supports listing individual devices, their supported commands, and executing discrete commands on them.

This works for both HTTP and MQTT. Check out the docs in the README to learn more.

Thanks to @jawilson for this, awesome addition!

Harmony API 2.0

Harmony API now supports multiple Harmony hubs.

Breaking Changes

HTTP endpoints and MQTT topics have changed. They are now namespaced by your hub's name.

An example HTTP endpoint is: /hubs/family-room/activities. An example MQTT state topic is harmony-api/hubs/family-room/activities/watch-tv/state.

Anything you're integrating with Harmony API, needs to update the HTTP endpoints it's using, or the MQTT topics that it's using.

How to upgrade to 2.0

run script/upgrade from the root of the project.

Change all of your HTTP endpoints and MQTT topics to use the new correct format.