# Homekit HomeKit is documented by Apple for enabling HomeKit in an app. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Home Hardware, Part 1: My Control4 Revenge Arc DevFeed: [Home Hardware, Part 1: My Control4 Revenge Arc]() Original publisher: [Read original article]() Published: 2026-09-08T00:34:58Z Content type: opinion Language: en Sources: [Jessie Frazelle]() Topics: [Home Assistant](), [Hardware](), [Bluetooth](), [Homekit](), [codex]() Tags: [api](), [bluetooth](), [codex](), [connect](), [hardware](), [home-assistant](), [homekit](), [sensor](), [sensors]() ### AI overview The author describes designing consumer hardware for a Home Assistant-based smart home, including a Bluetooth sensor hub and a maintenance display. The post discusses Bluetooth proxy range, regulatory constraints, testing considerations, and the use of NFC stickers for maintenance tracking, while reflecting on using Codex during the project. ### Source excerpt Fuck1 it, we're doing consumer hardware for ourselves now and getting fucked by economies of scale, I guess. This all started with me buying some Olimex Bluetooth proxies for Home Assistant. Then I started looking at the components and wondering if I could get better range. Now I'm designing boards, displays, and enclosures, and emailing manufacturers because their bezels are enormous. I've ordered the first two boards: a Bluetooth sensor hub and a little maintenance display. I've been working on this in Codex, and this post is going to go through what it was good at, where it got stuck or got things wrong, and where I had to step in. Why build this? Honestly, Control4, Savant, and the rest of these fucking systems seem built for rich people who don't know how to turn on their TV and would rather call someone. I want to program the fucking thing. Control4 puts HomeKit integration in its paid Connect tier.2 Why am I paying a recurring fee to connect things I already bought? I don't want to call a Control4 or Savant dealer, either, just because I want to change how something works. Give me API access or give me death. Source works too. I'll pick the hardware and connect it to Home Assistant, HomeKit, or my own code. If I want another sensor or some weird maintenance reminder, I can write that. It's my fucking house.31 Back to the Bluetooth proxies With a Bluetooth proxy, I can put the BLE radio near the sensors and get back to Home Assistant over the network.4 The machine running Home Assistant doesn't have to be within range of every sensor. When I mentioned my plans to Paul (paultag) over Slack, he pointed out that Olimex might be constrained by what the FCC allows, not just the components it picked. A radio supporting more transmit power doesn't mean you can use all of it.5 I hadn't thought about that. These are boards for my house. I'm not selling them. Fuck it, I'll build them and test them. I still have to measure the range; a bigger number on the radio's datash ## One Java API for HomeKit, Matter, and Google Home DevFeed: [One Java API for HomeKit, Matter, and Google Home]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-08-24T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [Matter](), [API](), [Homekit](), [Java](), [Google](), [Android]() Tags: [android](), [api](), [google](), [google-home](), [homekit](), [java](), [matter](), [release]() ### AI overview Codename One introduces a capability-driven Java API for smart-home accessories across HomeKit and Matter, with support for traits, scenes, change subscriptions, Matter commissioning, native backends, and simulation. The release documents platform-specific conversions, availability states, and setup requirements for Google Home APIs. ### Source excerpt Codename One now exposes smart-home accessories, traits, scenes, change subscriptions, and Matter commissioning through one capability-driven API with native and simulated backends. ## openHAB 5.1 Release DevFeed: [openHAB 5.1 Release]() Original publisher: [Read original article]() Published: 2025-12-22T19:00:00Z Content type: release Language: en Sources: [openHAB]() Topics: [Release notes](), [ui](), [Homekit](), [JavaScript](), [Python](), [GitHub](), [pull-requests]() Tags: [apple](), [bug-fixes](), [features](), [github](), [javascript](), [pull-requests](), [python](), [release](), [release-notes](), [updates]() ### AI overview openHAB 5.1 is a release featuring a modernized Main UI, a HomeKit Binding for importing Apple-ecosystem devices, and updates to JavaScript and Python Scripting. It also includes enhancements, bug fixes, breaking changes, and an upgrade script. The supplied text reports 124 contributors and 1,967 commits during the release period. ### Source excerpt But that's not all! Following the release of openHAB 5.0 this summer, this release includes many enhancements and bug fixes. Several changes of the openHAB 5.1 release are "under the hood", but often those are the important changes that make our codebase ready for the future, so openHAB can continue to develop steadily. ## Automating garage doors with Shelly1, ESP8266, sensors, and HomeKit DevFeed: [Automating garage doors with Shelly1, ESP8266, sensors, and HomeKit]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2023-11-07T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Homekit](), [ESP8266](), [Embedded Software Dev]() Tags: [esp8266](), [firmware](), [homekit](), [integration](), [sensor]() ### AI overview The article documents a HomeKit integration for two garage doors using Shelly1 relays, an ESP8266, garage-door contact sensors, and modified remotes. The second design uses sensor state to choose whether to open or close the door. ### Source excerpt This is how I automated my garage doors without using a BTN interface. ## Integrating Alarm Systems with Homekit DevFeed: [Integrating Alarm Systems with Homekit]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2023-11-04T00:00:00Z Content type: article Language: en Sources: [Carlos Becker]() Topics: [Homekit](), [API](), [App](), [Cloud](), [Chat Bot](), [Zip](), [C#](), [Java]() Tags: [api](), [app](), [chat](), [cloud](), [homekit](), [integration](), [password](), [whatsapp](), [zip]() ### AI overview This post documents the author's effort to integrate an Intelbras AMT8000 alarm system with HomeKit after finding the vendor's apps unreliable and difficult to integrate. It describes obtaining the API documentation through Intelbras support and receiving a ZIP archive containing spreadsheets, text files, and Java and C# files. ### Source excerpt This post documents my journey implementing a Homekit integration for my Intelbras AMT8000 alarm system.