# Homekit Published articles for Homekit. 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. ## 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. ## I Automated Watering My Lawn & Garden! DevFeed: [I Automated Watering My Lawn & Garden!]() Original publisher: [Read original article]() Author: Techno Tim Published: 2023-07-04T13:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Automation](), [Home Assistant]() Tags: [automated](), [automation](), [home-assistant](), [homekit](), [hub](), [plugin](), [smart](), [vlog]() ### AI overview A tutorial describing how to automate lawn and garden watering without built-in irrigation using hose faucet timers, a manifold, sprinklers, and soaker hoses. It also explains integration with the b-hyve app, Home Assistant, and HomeKit. ### Source excerpt This week I finally decided to automate the watering of my lawn and garden without irrigation, here's how... 📺 Watch Video Automation Without Irrigation Since I don't have irrigation, I have to use hoses, but that's OK because I picked up these hose faucet timers. They're great because you can hook them up to any hose faucet. I picked up this manifold and connected 4 of these faucet timers, ... ## Scrypted Connects Cameras to Home Hubs DevFeed: [Scrypted Connects Cameras to Home Hubs]() Original publisher: [Read original article]() Author: Techno Tim Published: 2023-05-13T15:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Home Assistant](), [webcam](), [Open Source](), [Automation]() Tags: [alexa](), [automation](), [camera](), [devices](), [google-home](), [home-assistant](), [homekit](), [hub](), [integration](), [open-source](), [self-hosted](), [stream](), [unifi](), [unifi-cameras]() ### AI overview This article presents Scrypted, open source software hosted on a local machine that connects cameras from various manufacturers to home hubs such as Apple HomeKit, Google Home, Alexa, and Home Assistant. It describes how this can enable hub features including notifications and automation without replacing existing cameras. ### Source excerpt Meet Scrypted an Open Source app that will let you connect almost any camera to any home hub, certified or not! You can connect popular devices from UniFi, Amcrest, Hikvision, Nest & Google, Tuya, Reolink, and many others to your home hub of choice, whether that be Apple's HomeKit, Google Home, Alexa, or even Home Assistant.This lets you choose and reuse your own devices and take advantage... ## HomeKit on Espressif's ESP32 DevFeed: [HomeKit on Espressif's ESP32]() Original publisher: [Read original article]() Author: John Lee Published: 2019-02-10T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32](), [Espressif](), [SDK](), [SDKs](), [Internet of things](), [API](), [Network Configuration](), [configuration]() Tags: [api](), [blog](), [esp32](), [espressif](), [homekit](), [internet-of-things](), [iot](), [latency](), [network-configuration](), [product-management](), [sdk]() ### AI overview Espressif describes its HomeKit SDK for ESP32-based connected products. The SDK is designed to simplify common tasks such as network configuration, discovery, cloud communication, interoperability, and device control through an API, while remaining extensible for less typical applications. ### Source excerpt IoT is not one thing, it means different things to different people. So also, there are so many ways of building connected products. And that means there are so many questions for every aspect of your connected product: - What communication protocols do we use? - Which network configuration mechanism should we use? - What do we use for remote communication? - What's the most secure method for doing this? - Do we offer low-latency control options through local network access? ## Apple HomeKit DevFeed: [Apple HomeKit]() Original publisher: [Read original article]() Author: John Lee Published: 2018-10-24T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [SDKs](), [Espressif](), [API](), [Development]() Tags: [api](), [apple](), [blog](), [development](), [esp32](), [espressif](), [homekit](), [manufacturing](), [sdk](), [smart-home]() ### AI overview Espressif's HomeKit SDK is a certified SDK conforming to the latest HomeKit specification. It provides an accessible, flexible API for creating accessories and bridges, while supporting development, certification, and manufacturing workflows. ### Source excerpt Espressif's HomeKit SDK is a fully certified SDK that conforms to the latest HomeKit specification. The SDK is engineered to expose an easy to use API, while also being flexible enough to create a variety of accessories and bridges. Espressif supports the entire workflow from development to certification and manufacturing. This way you can focus on your product, and let the SDK manage HomeKit conformance. The SDK is available at: - Apple's HomeKit ADK: - Espressif's HomeKit SDK: More Details: ## Wi-Fi Certification with ESP32 DevFeed: [Wi-Fi Certification with ESP32]() Original publisher: [Read original article]() Author: John Lee Published: 2018-08-11T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Wi-Fi](), [ESP32](), [Internet of things](), [interoperability](), [Security](), [Protocol (disambiguation)](), [Espressif]() Tags: [blog](), [branding](), [building-products](), [certifications](), [company](), [compliance](), [esp32](), [fcc](), [homekit](), [interoperability](), [iot](), [marketing](), [module](), [money](), [protocol](), [regulatory](), [security](), [source](), [us](), [wi-fi](), [wifi]() ### AI overview This article explains Wi-Fi certification for IoT products using ESP32 modules. It distinguishes Wi-Fi Alliance certification from regulatory certification such as FCC approval, describes when Wi-Fi certification is required, and outlines derivative certification using already certified ESP32-WROVER and ESP32-WROOM-32D modules. ### Source excerpt A fair number of questions come up regarding Wi-Fi certification for Wi-Fi enabled IoT products. Here is an attempt to answer some of the relevant ones. Wi-Fi certification is a program by Wi-Fi Alliance that ensures that products that pass certification adhere to the interoperability and security requirements as laid out in the standard. It tests for protocol compliance. ## Creating Unique Factory Data Images DevFeed: [Creating Unique Factory Data Images]() Original publisher: [Read original article]() Author: John Lee Published: 2018-05-01T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [Embedded Software Dev](), [configuration]() Tags: [blog](), [building-products](), [configuration](), [esp](), [esp-idf](), [firmware](), [homekit](), [manufacturing](), [partition](), [password](), [wi-fi]() ### AI overview This tutorial explains how to use multiple NVS partitions in ESP-IDF to store per-device factory data separately from user configuration. It describes creating unique partition images for manufacturing and preserving the ability to erase user settings during a factory reset. ### Source excerpt A common requirement while building a device is to have some unique information programmed into the device at the time of manufacturing. This information could be a unique serial number, or a unique MAC address ; or it could be a unique secret like the default password, or the HomeKit pairing pin. We have seen quite a number of ways that customers have achieved this. - Some use a few NVS keys to store this information at the factory.