hc

This kind of pushed me away from HA. I've ended up using integrations built using hc [0] to bridge devices to HomeKit, either existing or ones I've built, and then using Promtheus to collect metrics. It's not something that 'just works', but I feel much happier with how it works than HA. [0] - https://github.com/brutella/hc

This is great news. I've written a HAP Server[1] in Swift, which proved quite difficult as there was no complete specification available. I've written my implementation based on various non-offical HAP Server implementations (written in Go[2], JavaScript[3] and Java[4]). The major difficulties I ran into while implementing were; * No debug messages from iOS client. It would fail without telling me why. * Incompatible SRP implementations (3, 6 and 6a) that slightly differ. * Chacha20-Poly1305 are provided by libsodium, however the parameters of the variant (IETF) differ from the RFC. I hoped to run this code on my Raspberry Pi, but Swift and Swift-Foundation are not quite on-par with their macOS counterparts. Hopefully the cross-compiling effort will allow me in the future to run my HAP Server on this machine. [1]: https://github.com/Bouke

I don't believe you need a custom chip, but HomeKit does require some advanced crypto that many low-end embedded devices probably can't support. See the dependency list for this open source Go implementation of the HomeKit Accessory Protocol: https://github.com/brutella/hc#dependencies Edit: Missed this line in the original article: The issue, according to Lombard, is that Apple HomeKit certification requires a co-processor to handle device authentication. That co-processor is where the device’s encryption key is stored and handles the computing associated with encryption. Looks like (for security purposes) Apple wants a dedicated crypto co-processor. Probably a tamper-proof chip that stores a private key, similar in concept to Apple's Secure Enclave.

I went through Apple's DMCA requests sent to Github and the only one that is remotely similar is this: https://github.com/github/dmca/blob/master/2014-11-04-Apple.... But even then they weren't claiming it was reverse engineered material, but instead material ripped directly from Apple's copyrighted and confidential docs. I think both Apple and Github understand the boundaries of the DMCA pretty well. According to Github they haven't attempted to take down any of the following: https://github.com/nygard/class-dump https://github.com/nst/iOS-Runtime-Headers https://github.com/brutella/hc https://github.com/KhaosT/HAP-NodeJS https://github.com/nfarina/homebridge https://github.com/lisimia/piMessage https://github.com/stefanesser/dumpdecrypted https://github.com/comex/imaon2 … etc