User Tools

Site Tools


supported_hardware:homekit

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
supported_hardware:homekit [2020/12/20 15:18] – [Requirements:] changed python 3.7 instructions James Sentmansupported_hardware:homekit [2023/02/13 14:52] (current) – external edit 127.0.0.1
Line 6: Line 6:
  
 ====Requirements:==== ====Requirements:====
 +
 +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 install instructions are preserved below:
 +
 The Home Kit plugin requires that Python 3.7 be installed on the host machine. It does not have to be the default python version in use if you have multiple installs and it can coexist happily with multiple python versions if you are using the environment management systems. If you use an installer from python.org the default install location will be in /Library/Frameworks/Python.framework/Versions/3.7 which is what is needed for this plugin to work properly. Download Python 3.7 from the [[https://www.python.org/downloads/mac-osx/|Python.org Releases]] page. Please download the 64 bit only version as 32 bit apps will not continue to run on newer OS versions. The Home Kit plugin requires that Python 3.7 be installed on the host machine. It does not have to be the default python version in use if you have multiple installs and it can coexist happily with multiple python versions if you are using the environment management systems. If you use an installer from python.org the default install location will be in /Library/Frameworks/Python.framework/Versions/3.7 which is what is needed for this plugin to work properly. Download Python 3.7 from the [[https://www.python.org/downloads/mac-osx/|Python.org Releases]] page. Please download the 64 bit only version as 32 bit apps will not continue to run on newer OS versions.
  
Line 70: 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:
 +<code>
 +tell xInterface “name of your Home Kit Interface” to listAIDs()
 +</code>
 +
 +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.
 +
 +<code>
 +tell xInterface “name of your Home Kit Interface” to verifyAIDs()
 +</code>
 +
 +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.
 +
 +<code>
 +tell xInterface “name of your Home Kit Interface” to resetAID( “name of the problem unit”)
 +</code>
 +
 +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 the Accessory type of a unit does not seem to ever be reflected in the Home Kit database. If you wish to do this you’ll have to remove the bridge from Home Kit and then use the Reset Bridge button to rebuild the pairing keys and then re-pair. This has the effect of removing all the shared units as well and any settings, scenes or shortcuts that you’ve created in home kit using them. I can see that the new information is properly broadcast to Home Kit but the App does not reflect the changes. I believe this is a bug, or an intrinsic limitation in the Home app or in Home Kit itself.+Changing the Accessory type of a unit does not seem to ever be reflected in the Home Kit database. If you wish to do this you’ll have to remove the bridge from Home Kit and then use the Reset Bridge button to rebuild the pairing keys and then re-pair. This has the effect of removing all the shared units as well and any settings, scenes or shortcuts that you’ve created in home kit using them. I can see that the new information is properly broadcast to Home Kit but the App does not reflect the changes. I believe this is a bug, or an intrinsic limitation in the Home app or in Home Kit itself.
  
 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 83: Line 110:
 ====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 /Library/Frameworks location in MacOS. See the Requirements section above for more info.
 +  * As of XTension 9.4.40 a separate python version install is no longer required.
supported_hardware/homekit.1608477524.txt.gz · Last modified: 2023/02/13 14:51 (external edit)