HomeKit server foundation on ESP8266 with an API approach
Please read the message in issue 41 about the switchover to Maxim Kulkin code base.
Public Apple's HomeKit protocol code has been around for some time for more potent processors (notably HAP-NodeJS). This is a rewrite for the ESP8266 to make the server foundation. This project uses ESP8266_RTOS_SDK and WolfCrypt 3.9.8 for the crypto. It will however NOT deliver a certified HomeKit device.
For build instructions please refer to the wiki.
If you use the Demo Code from ESP8266-HomeKit-Demo you get this...
The code provides all the services required to pair iOS with an IP device and to operate that device once paired with multiple iOS devices. It runs on even the smallest ESP8266 device like the ESP-01. It creates
an API level to create your HomeKit device without descending to the lower levels of the HAP protocol.
See the ESP8266-HomeKit-Demo for the details.
Here are some preliminary timings.
Pairing is dominated by the SRP algorithm which is very slow and expensive. Fortunately this only happens once when the iOS device is being associated with the HomeKit device:
Time1: 25 seconds from boot till start of server, so that initial interaction is split second.
Time2: 30 seconds (based on a build with DEBUG logging which is slow).
Verify happens every time an iOS device reconnected to the HomeKit device. Ideally this should be as fast as possible.
The HomeKit code is approximately 400K and about 18K of RAM is left for other purposes. During Pairing so much RAM is used that it is required to launch most code after pairing is done.
I want to thank a number of projects which made this possible:
HAP-NodeJS - which documents the HomeKit protocols for IP and allowed me to guess how they were implemented.
https://awesomeopensource.com/project/aanon4/HomeKit - which inspired this README and should inspire us to look into assembly.
ESP8266_RTOS_SDK - Espressif for their great product
WolfCrypt - For a great one stop crypto library
Please note that this software was produced without any reference to any proprietary documentation or information. I am not a MFi licensee, nor do I have access to any related information.
Espressif uses MIT license. WolfCrypt uses GPLv2 or higher license. For the purpose of this distribution you should use GPLv3.
This is based on the changes I had to make to Wolfcrypt and to be compatible with Apache-2.0 license.
Copyright 2016-2017 HomeACcessoryKid - HacK - [email protected]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.