With this app you can pair Homey to HomeKit and control your Homey devices using iOS, Siri and Shortcuts.
HomeyKit is currently an SDKv2 app. This means that it’s not possible to run it on the new 2023 Homey Pro.
Also, Athom will remove all SDKv2 apps from the App Store on January 1st 2023, meaning that after that date it won’t be possible for older Homey Pro’s to receive HomeyKit updates or install the app until it’s updated to SDKv3.
Because I don’t use Homey for my own home automation, spending €400 on a new Homey Pro to spend more free time on supporting HomeyKit is not an option.
If you want me to port HomeyKit to SDKv3, please make a donation.
Current Donated Amount: €437,03
You can make a donation through Paypal: PayPal.Me
NB: while it’s not a necessity to have the new Homey Pro to port an app to SDK3, due to the massive internal changes that the new Homey Pro brings, and the relative complexity of an app like HomeyKit, it’s not possible to do an SDK3 rewrite without the ability to fully test the app on the new platform.
Please read this post about future plans for HomeyKit.
With the current iOS 16.2 beta, Apple has introduced a new Home architecture (including support for Matter/Thread).
Upgrading to this architecture is optional. Given that the current beta is giving issues with HomeBridge and HomeyKit (at least for some people), my advice is to wait to upgrade.
For those that have upgraded already and are experiencing issues with HomeyKit (devices being unresponsive), the current test version (v4.3.0) should fix those issues. Be aware that test versions of apps can be subject to frequent changes and updates, and as a result, it may be required to do a full Home(y)Kit reset.
After installing the app grab your iPhone or iPad, open the Home app on your iOS device and then:
- Click the
+at the top of the screen and choose Add New Home (name it anything you like)
- Once the new home is created, choose Add Accessory > More options…
- (If your Homey isn’t already visible in the list of accessories, try My Accessory Isn’t Shown Here)
- Pick Homey (because HomeyKit isn’t officially certified by Apple, you’ll get a question about adding an uncertified accessory)
- Enter the code: 20020200 and Continue.
After Homey has paired with your iOS device your Homey devices will be added. When you add or remove a device from Homey the same wil happen in HomeKit. In the application settings for HomeyKit you can select which devices you want to pass (and not pass) to HomeyKit. By default, all supported devices will be passed.
The following classes are supported:
- Lights (with RGB or Temperature)
- Motionsensors (with lux and temp)
- Door/Window sensors (with temp)
- Window coverings (blinds, curtains, sunshades)
- Most on/off devices
- Home Alarm
- Most sensors
Donations are very welcome, though they come with no guarantees, warranties, or preferential treatment (just think of it that you’re donating for the work already done, not the work to be done).
For now, Paypal only: PayPal.Me
A lot of issues with HomeyKit are not related to the app but have external causes, like Homey’s networking being unstable (especially after a firmware update). Typically, when you have issues with any app, the first recourse is to PTP.
If your problems with HomeyKit are persistent, you can perform a full reset from the App Settings.
If you are sure you found an actual bug with the app you can create an issue on Github .
- Added link to community forum page
- Support for “remote” devices with onoff capabilities and fixed issues with “locked” subcapabilities.
- Make sure all devices are ready before being added to the bridge.
- Catching more Web API error.
- More small fixes
- Work around yet more issues with the Web API
- Catch errors when starting the bridge
- Limit the number of bridged accessories
- Work around more issues in the Web API
- More fixes to work around issues in v7.4.X-rc.Y
- Changes for Homey v7.4.0-rc.X
- Added support for state blinds/curtains/sunshades
- New stable release
- Added support for curtains and generic window coverings
- Added support for blinds (#180 and hopefully #159)
- Stability changes (hopefully fixes #137)
- Allow user to set different bridge identifier (#151)
- Added support for curtains (#153)
- Fixes #149 (issue with CO2 and CO sensors)
- Removing explicit subscription for device update events (not required anymore)
- Some fixes for Satel Integra support
button/homealarm_systemdetection to work better with Heimdall
- Support for device class
- Fixed issue with settings
- Configurable settle time
onofffor device class
dimfor device class
- Removed log tab from settings page (wasn’t being used anyway)
- Wait longer after a reboot for devices to settle to prevent iOS from not recognizing devices anymore
- Prevent non-existent capabilities from being accessed/used
- Debouncing dim so it doesn’t glitch as much
- Better check on required capabilities for devices to prevent crashes
- Also check
device.virtualClassduring device discovery.
- Fix to prevent issues due to Athom’s implementation hijacking our TCP port
- Fixed an issue with the settings page not being shown
- Homey v2 firmware support
- Changes to settings pages
- Option to clear persistent storage to resolve issues with Homey not being found by iOS
- Delay start of Homekit server until device count has settled (#93)
- Trying to fix #82
- Reintroduced settings page
- Other small fixes
- Filename uppercase fix
- Updated hap-nodejs, lodash and athom-api
- Added alarm system support for Heimdall
- Added fan support
- Fix for sensors
- Bugfixes in smoke and temperature class
- Multiple devices added (see Added support for various devices by nhassink · Pull Request #54 · swttt/com.swttt.homekit · GitHub )
- Fixed color bulbs
- Fixed thermostat
- Small fixes
- Small fixes
- Thermostat display units added
- Fixed contact sensor
- Beta appstore release
- Initial release where has-node got replaced by hap-nodejs