supported_hardware:homekit
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
supported_hardware:homekit [2019/02/21 16:35] – [Setup:] James Sentman | supported_hardware:homekit [2023/02/13 14:52] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 6: | Line 6: | ||
====Requirements: | ====Requirements: | ||
- | The Home Kit plugin absolutely requires Python 3.7 or newer. As of MacOS 10.14 this is not included in the standard software like Python 2.7 is. You must install it separately. The easiest way to do this is via one of the binary installers available from [[https:// | ||
- | If you use the above installer then the binary positions will be correct and you can ignore this paragraph. If you already have Python3 installed or decide to instead build from source please make sure that the python3 binary file, or a symbolic link to it, is available at / | + | As of version 9.4.40 a separate python install is no longer required. No other work is needed to run the homekit plugin. If you are working with a version prior to 9.4.40 |
- | The plugin | + | The Home Kit plugin |
+ | Xtension versions prior to 9.4.35 required python 3.7 be the “active” version of python meaning that typing “python3” from the command line would bring up the python 3.7 version even if others were installed. Versions 9.4.35 and later only require that the install be present in the default location but do not need it to be the default version on the system anymore. | ||
====Setup: | ====Setup: | ||
Line 73: | Line 73: | ||
====Color and Color Temperature Support===== | ====Color and Color Temperature Support===== | ||
If the XTension device that you are sharing supports color or color temperature settings select “Switch” as its device type and the color or color temperature will be automatically enabled for this unit in Home Kit. As of this first beta this works, but can be a bit finicky as the Home Kit interface tends to jump around a bit while you’re changing the colors. Changes to the color in XTension do show properly in the current color display in Home Kit. | If the XTension device that you are sharing supports color or color temperature settings select “Switch” as its device type and the color or color temperature will be automatically enabled for this unit in Home Kit. As of this first beta this works, but can be a bit finicky as the Home Kit interface tends to jump around a bit while you’re changing the colors. Changes to the color in XTension do show properly in the current color display in Home Kit. | ||
+ | |||
+ | ====Troubleshooting: | ||
+ | ===Duplicate AIDs:=== | ||
+ | Some folks have had problems with duplicate Accessory ID’s. I have never been able to fully duplicate the issue but I believe I have located and fixed the timing issue that caused it to get out of sync with the master database in XTension 9.5.1. There are also 3 scripting commands you can run to help to trouble shoot the problem should you have it and to fix it if you do. The plugin will validate the stored AID’s for the units as they are loaded and will log in red if there are any duplicates. It will not try to fix the problem at this point as it is important to NOT reset the one that is actually the correct Unit that Home Kit thinks it is, and only the one that is not that. | ||
+ | |||
+ | To get a list of all shared units from the plugin and their current AIDs: | ||
+ | < | ||
+ | tell xInterface “name of your Home Kit Interface” to listAIDs() | ||
+ | </ | ||
+ | |||
+ | That will write the name of every unit shared through this interface along with it’s AID to the log. To Verify that they are all different please use the verifyAIDs() command. | ||
+ | |||
+ | < | ||
+ | tell xInterface “name of your Home Kit Interface” to verifyAIDs() | ||
+ | </ | ||
+ | |||
+ | will write similar output to list aids but if 2 units have the same AID there will be a red log line giving you the name of both of them. You can then decide which one to perform a reset on vis the resetAID() command. If you perform this on a Unit that is working properly it will break it’s association with home kit in a way that might require a reset of the interface and rebuilding of all the sharing info so please pick the unit that is NOT the correct unit as far as your home kit settings are concerned. | ||
+ | |||
+ | < | ||
+ | tell xInterface “name of your Home Kit Interface” to resetAID( “name of the problem unit”) | ||
+ | </ | ||
+ | |||
+ | A new AID will be selected and assigned to the Unit and the interface will restart. After that you may have to re-assign its sharing setup and also click the “Update Config” button in the Interface setup dialog. That will bring the unit back to life for sharing. | ||
+ | |||
====Known Issues==== | ====Known Issues==== | ||
- | As of this first beta changing | + | Changing |
Changing the name of a unit in XTension also is not reliably reflected in Home Kit. Sometimes the name change will show up in it’s display some hours or even days later, sometimes never. I can see that the information is properly sent to Home Kit but the App rarely changes what it thinks it knows about a bridged accessory. If you need to change the name of a unit as far as Home Kit is concerned you can do so directly from the Home Kit app itself by using a 3D touch tap on the unit and clicking it’s “settings” button. There is no need for an Accessory in Home Kit to have the same name as it does in XTension. You may wish to keep your XTension named “Master Bedroom Overhead” but to change the name in Home Kit just to “my room” or something similar. That works fine. | Changing the name of a unit in XTension also is not reliably reflected in Home Kit. Sometimes the name change will show up in it’s display some hours or even days later, sometimes never. I can see that the information is properly sent to Home Kit but the App rarely changes what it thinks it knows about a bridged accessory. If you need to change the name of a unit as far as Home Kit is concerned you can do so directly from the Home Kit app itself by using a 3D touch tap on the unit and clicking it’s “settings” button. There is no need for an Accessory in Home Kit to have the same name as it does in XTension. You may wish to keep your XTension named “Master Bedroom Overhead” but to change the name in Home Kit just to “my room” or something similar. That works fine. | ||
Line 82: | Line 106: | ||
As of this moment Home Kit doesn’t seem to support running more than one bridge plugin instance on the same machine. Additional instances fail to pair properly. | As of this moment Home Kit doesn’t seem to support running more than one bridge plugin instance on the same machine. Additional instances fail to pair properly. | ||
+ | |||
+ | Any battery operated device currently reports a low battery status all the time to Home Kit and not just when the battery is low. This will be sorted out in the next release for now ignore the low battery flags. | ||
====History==== | ====History==== | ||
* The first beta of the Home Kit plugin was included in XTension version 9.4.16 in Feb of 2019 | * The first beta of the Home Kit plugin was included in XTension version 9.4.16 in Feb of 2019 | ||
+ | * As of XTension 9.4.35 it was no longer necessary that Python 3.7 was the “active” version on the system but it still requires that 3.7 be installed in the default / | ||
+ | * As of XTension 9.4.40 a separate python version install is no longer required. |
supported_hardware/homekit.txt · Last modified: 2023/02/13 14:52 by 127.0.0.1