For details on how to install and configure this adapter, please see the Wiki
Before you can install the Adapter, you have to some packages (for Linux):
sudo apt-get install libavahi-compat-libdnssd-dev
Just hit the "+" button behind "Homekit yahka adapter" in the ioBroker Admin Panel on the "Adapter" page.
If you want to be on the edge and test the latest beta, you could install the adapter via a GitHub url.
(Sometimes an additional upload (e.g. iobroker upload yahka) and adapter restart is necessary)
Attention: To be able to restore ioBroker.yahka on another system, in addition to the usual iobroker backup and iobroker restore, the yahka.X.hapdata folder under /opt/iobroker/iobroker-data must also be backuped and, if necessary, restored. Wiki / Issue
Another option for a backup and restore is the Backitup adapter. This automatically backs up the yahka.X.hapdata folder.
A restore is also possible via the BackItUp GUI.
You can find a detailed description here.
Try to change the MAC/Username of the bridge or activate the ciao advertiser
If not all new features are available after a yahka update, try an upload (e.g. iob upload yahka) and restart the adapter.
If you are having the following error in the log:
Error: 2016-07-26 18:57:17.989 error at Error (native)
Error: 2016-07-26 18:57:17.989 error dns service error: unknown
uncaught 2016-07-26 18:57:17.985 error exception: dns service error: unknown
You have to do some additional steps:
-
install avahi daemon:
sudo apt-get install avahi-daemon -y -
Edit avahi-daemon.conf
sudo nano avahi-daemon.conf
change the following variables:
host-name=\<put in your hostname\>
domain-name=local
use-ipv4=yes
use-ipv6=yes
enable-dbus=yes
If you are having the following error in the log:
../authenticate_pam.cc:30:31: fatal error: security/pam_appl.h: Datei oder Verzeichnis nicht gefunden
#include <security/pam_appl.h>
You have to install the pam-devel package:
- install avahi daemon:
sudo apt-get install pam-devel -y
- Download:
https://www.samuelattard.com/files/bonjourcore2.msi - Execute:
msiexec /i bonjourcore2.msi /qn - remove:
del bonjourcore2.msi - Download:
https://www.samuelattard.com/files/bonjoursdksetup.exe - Execute:
bonjoursdksetup.exe /quiet - Remove:
del bonjoursdksetup.exe - Set:
set BONJOUR_SDK_HOME=C:\Program Files\Bonjour SDK
And after that install yahka adapter.
The architecture of HomeKit is as follows:
There are devices as logical entities. Each device can have multiple services and each service has multiple characteristics.
At the end, a characteristic is an endpoint where values could be read from or write to.
Which characteristics a service could have, is defined by Apple/HomeKit and determined by the service type. The service types are also defined by Apple/HomeKit.
Example:
A Garage Door opener is a device that could have two services:
- Garage Door Opener
- Light
The Garage Door Opener Service itself could have different characteristics like: CurrentDoorState, TargetDoorState and many more.
Also, the Light Service could have different characteristics, like: On (and many others for changing the light color etc.)
With Yahka it is possible to map an ioBroker Datapoint to a HomeKit Characteristic.
Since sometimes mappings are necessary (e.g., the "State" values of a garage door are different between HomeKit and other systems), there is also the possibility to specify Functions to convert the values. This is described below.
To avoid too much administration work, all Devices you create in Yahka are behind a so-called "Bridge". With this bridge, you only need to pair the Bridge with your iOS device to get access to all devices. Otherwise, you would need to pair every Yahka device with Homekit.
Each device that needs to be paired with Homekit needs a "username" which has the form of a mac-address. Yahka automatically generates a random username for each yahka instance.
Important: if you change the username after pairing Yahka with HomeKit, you need to reconfigure all devices in iOS (room assignment, position etc.). Changing the username means to iOS that it is a completely new device!
Besides the username, you need to specify a PIN code which needs to be entered on the iOS device. This could all be specified by clicking on ":yahka.0" in the admin panel of Yahka. (Expand the Panel on the right side after clicking on the list entry). The name of the bridge could also be changed there.
After setting up the bridge, you could add the devices you like with the "Add Device" Button on the top. Once a device is added/selected, you could add services to this device.
It is necessary to specify a service name and a service type.
Depending on the service type, the list of available characteristic changes.
If you want to support a characteristic, you have to tick the "enabled" checkbox on the left side of the characteristic. For each characteristic, you could specify the following properties:
- InOutFunction: you could specify a predefined function which is responsible for passing the values from HomeKit to ioBroker and vice versa
- InOutParameter: here you could specify parameters for the selected InOutFunction. The available/expected Parameters depend on the selected Function. A brief overview of the Functions and Parameters are stated below.
- ConversionFunction: additionally to the InOutFunction, you could also specify a function which converts a value coming from HomeKit to ioBroker (and vice versa)
- ConversionParameter: same as InOutParameter - the available/expected params depend on the selected function.
| Function | Expected Parameter | Description |
|---|---|---|
| const | Value | The const function always passes the value specified in "InOutParameter" to Conversion Function if HomeKit reads the value. If HomeKit wants to write the value, this action is denied |
| ioBroker.State | name of a ioBroker datapoint | With this function, the adapter uses the specified ioBroker datapoint for read and write operations. All operations are done immediatelly without buffering or filtering (values are passed to the specified Conversion functions) |
| ioBroker.State.Deferred | name of a ioBroker datapoint | With this function, the adapter uses the specified ioBroker datapoint for read and write operations. Write operations from HomeKit are directly passed to the conversion function. Changes from ioBroker are debounced for 150ms - which means that the value is only transmitted to HomeKit if no other change occured within 150ms. |
| ioBroker.State.OnlyACK | name of a ioBroker datapoint | With this function, the adapter uses the specified ioBroker datapoint for read and write operations. Write operations from HomeKit are directly passed to the conversion function. Changes from ioBroker are only forwarded to HomeKit if the "Acknowledged"-Flag of the value is set. Otherwise, the last acknowledged value is getting transmitted to HomeKit |
| ioBroker.homematic. WindowCovering.TargetPosition |
Id of the HomeMatic Level Datapoint or String-Array with the Id of the Level Datapoint and the Id of the Working Datapoint |
This function is especially for controlling the HomeMatic Window Covering. This function defferes the transmission of values to HomeKit while the Window Covering is moving. This is necessary to avoid flickering of the window covering slider in iOS |
| Function | Expected Parameter | Description |
|---|---|---|
| passthrough | <none> | The value from ioBroker is passed to HomeKit without conversion (and vice versa) |
| HomematicDirectionTo HomekitPositionState |
<none> | This function maps the direction enum of Homematic window covering to the PositionState enum of HomeKit (and back) |
| HomematicControlModeTo HomekitHeatingCoolingState |
<none> | This function maps the ControlMode enum of Homematic to the HeathingCoolingState enum of HomeKit (and back) |
| level255 | <none> | This function scales an ioBroker value with a value range from 0 to 255 to a HomeKit value with a value range from 0 to 100 (and back). Example: 255 in ioBroker is transformed to 100 for HomeKit. |
| scaleInt scaleFloat |
{ "homekit.min": <number>, "homekit.max": <number>, "iobroker.min": <number>, "iobroker.max": <number> } |
This function is similiar to "level255" but it's more generic. It transforms an ioBroker value with an range from "iobroker.min" (0 if omitted) to "iobroker.max" to a HomeKit value with a value range from "homekit.min" (0 if omitted) to "homekit.max" (and back). Example: If the parameter field is: { "homekit.max": 500, "iobroker.max": 250} the value of ioBroker is in fact multiplied by 2 before sending it to HomeKit. The min-Parameters are only available in version 0.8.0 and higher |
| inverse | number | This function is used to "inverse" a value from ioBroker. The parameter specified the maximum of the value in ioBroker. The formula is: Parameter - valueExample: If the parameter field is 100, the value 100 from ioBroker is send as 0 to HomeKit, the value 80 is send as 20 to HomeKit etc. |
| hue | <none> | This function is specialized version of scaleInt with the parameters iobroker.max=65535 and homekit.max=360. |
To integrate the Homematic Blind Actuators (like HM-LC-Bl1PBU-FM), the following settings are necessary:
- Add a service to a device
- Set Service Name to some name and service type to "WindowCovering". Service subtype could be left blank
- Enable and fill in the following characteristics:
| Characteristic Name | 1: InOut Function 2: Conversion Function |
1: InOut Parameters 2: Conversion Parameters |
|---|---|---|
| CurrentPosition | 1: ioBroker.State.OnlyACK 2: passthrough |
1: <path to homematic object>.1.LEVEL 2: <empty> |
| PositionState | 1: ioBroker.State.OnlyACK 2: HomematicDirectionToHomekitPositionState |
1: <path to homematic object>.1.DIRECTION 2: <empty> |
| TargetPosition | 1: ioBroker.homematic.WindowCovering.TargetPosition 2: passthrough |
1: <path to homematic object>.1.LEVEL 2: <empty> |
The value <path to Homematic object> needs to be replaced with the actual path to the device (e.g., hm-rpc.0.NEQ0012345)
For general Information about the Configuration Mask, see: TODO
For more information about the Configuration, the InOut Functions and Conversion Functions, see: Wiki
This repo includes one submodule, so before building you need to also close/init this one, e.g., use git submodule update --init --recursive to update and fetch it's content.
- Corrected Admin GUI
- (tarikweiss) Fixes errors with non-existing service types
- (tarikweiss) Fixes errors with non-existing service types
- (bluefox) Revert renaming of states back:
HomematicControlModeToHomekitHeatingCoolingState => HomematicControlModeToHomekitHeathingCoolingState, Deferred => Defered
- (Apollon77) Important: js-controller 5.0 is required at least
- (tarikweiss) Rewrote community types from submodule (js) to typescript
- (tarikweiss) Added the ability to set an ioBroker state for the availability indication in HomeKit
- (TA2K) Corrected empty device list with rebuild
- (foxriver76) we ensured controller 5 compatibility
- (bluefox) Formatting
- Added AVAHI advertiser as default and updated HomeKit Library to improve performance and stability
- Update release and test scripts
- (jw) added support to group devices in Admin Interface
- (jw) added support to mark services as "primary" and as "hidden"
- (jw) added ioFunctions "round" and "invert"
- (jw) updated dependencies
- (jw) Updated to HAP-Node.js 0.9.2
- (jw) Fixed crashes due to changes in used HomeKit Library
- (nh) improved changelog in readme
- (jw) switched to HAP-Node.js 0.9.0-beta.113 and added useLegacyAdvertiser option
- (jw) fixed bug which prevented cameras from deletion and duplication
- (jw) updated dependencies
- (jw) improved state selector (scrolling and refresh on open)
- (jw) updated dependencies
- (jw) added support for linking services to support Television Services
- (jw) added possibility to publish devices without the bridge (necessary for TV service)
- (jw) added support for audio stream in camera
- (jw) added support for custom characteristics on the services (e.g., to add Wattage characteristic to plugs)
- (jw) added support for additional services to camera (to enable usage of doorbell service)> (many20) fixed scaleInt conversion - results are now rounded
- Intermediate release
- (apollon77) updated dependencies, Node.js 12 support
- (jw) updated dependencies
- (apollon77) removed support for Node.js 4 - Node.js 6 is now the minimum required Node.js version (merged #109)
- (yaming116) fixed scale conversion to support min values others than 0
- (jw) fixed a bug where the adapter didn't start anymore
- (jw) removed the reference to the git repository of the hap community types
- (jw) fixed a bug where the adapter crashes if a state does not exist
- (jw) added io functions for HomeMatic dimmers (#30 and #75)
- (jw) fixed a bug where adapter didn't start anymore when using the conversion function "inverse" (#98)
- (jw) updated to a latest HAP-Node.js library to support TV services and characteristics (available since iOS 12.2 beta 1)
Note: that's still in development, not all services are working correctly. For more information see: (#89)
- (jw) added more services and characteristics (from https://github.com/homespun/hap-Node.js-community-types)
- (jw) improved admin interface to support individual editors for IO/Conversion functions
- (jw) added new conversion function "script" which adds the ability to run JavaScript functions as conversion functions
- (jw) fixed a bug in the scaleInt and scaleFloat methods (thanks to balzreber)
- (jw) added ioFunction "MultiState" to get multiple states and/or separate between read and write states
- (jw) added conversion function "map" to customize mappings between ioBroker and HomeKit
- (jw) added possibility to specify IP for Bonjour broadcasting (for bridge configuration and camera configuration)(#86)
- (jw) switched to webpack and refactored admin interface and io/conversion functions
- (jw) fixed a problem where numeric values where transmitted to homekit as strings (#87)
- (jw) added possibility to specify "firmware" version for bridge and devices (#90)
- (jw) added Internet Explorer / MS Edge detection to print error message in admin panel (#83)
- (jw) added support for new compact mode (#95)
- (jw) added support for specifying device information via data points (#91)
- (SchumyHao) added Chinese support
- (jw) Removed a bug which flooded logging when starting/stopping the adapter which led to excessive memory consumption
- (jw) updated dependencies
- (jw) change default name of new instances
- (foxriver76) remove excessive logging
- (mdietz666) scaleInt and scaleFloat now supports min-values (this allows mapping from e.g. -90 to 90 to 0 to 180)
- (arichter83) added "Duplicate Device" functionality
- (jw) fixed a bug where state selection with admin 2.0.9 did not work anymore
- (jw) restructured repository to support install via url
- (bluefox) Fixed the ID select dialog in Admin3
- (jw) updated hap-Node.js to support the following new services: Faucet, IrrigationSystem and Valve
- (jw) added ip-package to dependencies to avoid errors on some installations
- (jw) fixed startup crash
- (jw) add support for IP-Cameras
- (jw) included iOS 11 device definitions
- (jw) allowed negative temperatures for temperature sensors
- (jw) fixed crashes due to duplicate device names
- (oliverschulze) added conversion functions "hue" and "level255"
- (jw) added conversion functions scaleInt, scaleFloat and inverse
- (jw) devices are now sorted by name in the admin panel
(bluefox) allow select ID in configuration dialog
- (jw) improve log output
- (jw) added HomematicControlModeToHomekitHeathingCoolingState mapping
- (jw) internal release
- (jw) fixed issues with empty characteristic values
- (jw) fixed issue with empty adapter.systemConfig.system object
- (jw) fixed issue with wrongly displayed logo
- (jw) initial release
The MIT License (MIT)
Copyright (c) 2016-2024 Jens Weigele ([email protected])
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.