# connect Published articles for connect. 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 ## Connecting to an External Database in Craft CMS DevFeed: [Connecting to an External Database in Craft CMS]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2024-08-06T14:03:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Databases](), [Content Management System](), [configuration](), [MySQL](), [MariaDB](), [PostgreSQL](), [SQLite](), [legacy]() Tags: [application](), [built-in](), [cms](), [components](), [configuration](), [connect](), [craft](), [database](), [external](), [flexibility](), [how-to](), [insights](), [learn](), [legacy](), [leveraging](), [mariadb](), [mysql](), [postgresql](), [sqlite](), [using]() ### AI overview A tutorial explaining how to connect Craft CMS to an external database using Twig and configuration in config/app.php, without requiring the deprecated Connect plugin. It covers Craft application components and database types supported through Yii2. ### Source excerpt Learn how to connect to an external database using Craft CMS by leveraging the built-in flexibility of application components ## Thorium Core DevFeed: [Thorium Core]() Original publisher: [Read original article]() Published: 2014-01-06T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Operating system](), [Cloud](), [Development]() Tags: [cloud](), [connect](), [development](), [free](), [open-source](), [os](), [react](), [reactos](), [win32](), [winapi]() ### AI overview ReactOS community members launched the Thorium Core Kickstarter appeal to fund a commercial project based on ReactOS. The proposed product is a remotely accessible desktop environment running in the cloud, with development intended to contribute back to ReactOS. ### Source excerpt Right before Christmas, Aleksey Bragin and Steven Edwards launched the Thorium Core Kickstarter appeal. At its most basic level, the goal is to advance ReactOS development by creating a commercial project using it. The proposed product, as it were, is a remotely accessible desktop environment, basically a computer in the cloud. No longer does one need to shuffle around USB sticks or reinstall applications from computer to computer, simply connect to Thorium and you'll be back to your familiar setup.