# Home Hardware, Part 1: My Control4 Revenge Arc

DevFeed: [Home Hardware, Part 1: My Control4 Revenge Arc](<https://devfeed.tech/articles/home-hardware-part-1-my-control4-revenge-arc-35169.md>)

Original publisher: [Read original article](<https://blog.jessfraz.com/post/home-hardware-part-one/>)

Published: 2026-09-08T00:34:58Z

Content type: opinion

Language: en

Sources: [Jessie Frazelle](<https://devfeed.tech/sources/jessie-frazelle.md>)

Topics: [Home Assistant](<https://devfeed.tech/topics/home-assistant.md>), [Hardware](<https://devfeed.tech/topics/hardware.md>), [Bluetooth](<https://devfeed.tech/topics/bluetooth.md>), [Homekit](<https://devfeed.tech/topics/homekit.md>), [codex](<https://devfeed.tech/topics/codex.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [bluetooth](<https://devfeed.tech/tags/bluetooth.md>), [codex](<https://devfeed.tech/tags/codex.md>), [connect](<https://devfeed.tech/tags/connect.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [home-assistant](<https://devfeed.tech/tags/home-assistant.md>), [homekit](<https://devfeed.tech/tags/homekit.md>), [sensor](<https://devfeed.tech/tags/sensor.md>), [sensors](<https://devfeed.tech/tags/sensors.md>)

## 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