#Make harmony hub discoverable how to

In a few cases, I have a Hass.io component to control a device from Hass.io AND a Homebridge plug-in to control it from Apple Home (in this case I hide the Hass.io device from Homebridge via config options). Since I needed a z-wave server and some other capabilities I now run Hass.io with a z-wave stick and run Homebridge as an add-on under Hass.io to make my z-wave devices (among others) visible to my Apple Home app. In these Hass.io forums, if you ask about Homebridge (other than the add-on itself), you’ll get pointed over to the pages for Homebridge and its plug-ins for answers.

#Make harmony hub discoverable how to

As a separate system, you must learn how to configure Homebridge separately (it uses a config.json file and has its own qwerks and issues). I installed and was using Homebridge on my Pi long before I discovered Home-Automation and Hass.io. Unfortunately, it does get a little in to computer coding and technical details.įor clarity, (hopefully), Homebridge is a separate system from Home-Assistant intended to make non-HomeKit devices visible in the Apple Home app (“HomeKit support for the impatient”). Often these are security keys, customizing names, identifying IP addresses, etc.

But, I’ve also found in most cases devices require, or work better, with additional manual configuration. Auto-discovery seems to be more about seeing one of those platforms or devices, and automatically including that “component” without you having to specify it. Hass works by loading “components” to support various platforms and devices. There are “two different methods” because they are two different platforms. Depending on what devices you have working in Hass.io, you may not need anything more than the homeautomation plugin in Homebridge, which makes most of the Hass.io devices visible to Apple Home.