u/Sensitive-Phrase-332

Image 1 — *DirectorLink* Tired of paying your dealer for every small change? I built a free, open-source Control4 app so you can do it yourself
Image 2 — *DirectorLink* Tired of paying your dealer for every small change? I built a free, open-source Control4 app so you can do it yourself
Image 3 — *DirectorLink* Tired of paying your dealer for every small change? I built a free, open-source Control4 app so you can do it yourself
Image 4 — *DirectorLink* Tired of paying your dealer for every small change? I built a free, open-source Control4 app so you can do it yourself
Image 5 — *DirectorLink* Tired of paying your dealer for every small change? I built a free, open-source Control4 app so you can do it yourself

*DirectorLink* Tired of paying your dealer for every small change? I built a free, open-source Control4 app so you can do it yourself

Hi everyone,

The thing that bothered me most about Control4: every small change means calling the dealer, waiting, and paying. A new scene, a schedule, a different time for the garden lights, access for the kids.

So I built **DirectorLink**, a free, open-source driver and app. Once it's installed, you make those changes yourself, from your phone. No dealer visit, no service call, no subscription.

** Try it first (2 minutes, nothing to install): https://directorlink.io/try/ **

**What you can do yourself, any time, for free**

- **Scenes:** make and change them, run with one tap ("Good Night": lights off, blinds down, AC to 23°)

- **Schedules:** by the clock, sunrise or sunset, the weather, or when you arrive home

- **Family access:** each person gets their own rooms, devices, cameras and scenes. Add or remove people yourself

- **Rooms and favorites:** order them, hide rooms, pick favorites

- **Alerts on your phone:** doorbell, cameras, doors and gates

- **Remote access** from anywhere, encrypted end to end

- **History** of who did what, and **automatic backups**

It controls lights, AC and floor heating, blinds, fans, Sonos, cameras, doors and gates.

**What still needs your dealer:** adding the DirectorLink driver once, and adding new devices or drivers later. That's it. Your Composer programming and keypad buttons stay as they are, and your dealer can still see everything DirectorLink runs.

**Privacy:** at home the app talks straight to the controller. Away from home, requests go through our relay, encrypted end to end: it passes them on but can't read them. The code is open source (Apache-2.0), so anyone can check it.

**Requirements:** Control4 OS 3.3 or later. I run it every day on a CORE-1 with X4.

- Website: https://directorlink.io

- Free drivers (Samsung refrigerators, Hikvision cameras): https://directorlink.io/drivers/

- Source: https://github.directorlink.io

Questions and feedback are welcome. What's the change you've been waiting for your dealer to make?

*DirectorLink is an independent project, not affiliated with Control4 or Snap One.*

u/Sensitive-Phrase-332 — 10 days ago

DirectorLink: a free, open-source Control4 driver and app (looking for testers)

Hi all,

I've been building DirectorLink, a free and open-source driver for Control4 plus an app for phones and computers, and I'm looking for people to try it.

What it does

- Controls lights (including KNX switches and dimmers), thermostats and AC (e.g. CoolMasterNet), blinds, IP camera pictures, KNX door and gate relays, and DoorBird.

- One-tap scenes. For example "Good night" turns all lights off, sets the bedroom AC to 24 and closes the blinds. You can pick single lights, or copy the house as it is right now.

- Schedules by the clock, at sunrise or sunset, or by the weather (heat, wind, rain, from Open-Meteo). The controller runs them itself, even when no phone is open.

- Works at home and away. At home the app talks to the controller directly. Away, and on iPhone, it goes through your Google account, locked end to end, so the servers in between can't read it.

- Family access with roles: view only, control, doors, or admin. Everyone keeps their own language, theme and favorites. English and Hebrew.

For installers

Automation that homeowners make is hard to troubleshoot when you can't see it. DirectorLink shows its own in Composer: Schedule Status (what is on and what runs next), Last Automation (what ran, when and why, e.g. "Cool the house, heat rule, 31C outside"), an action that prints every schedule and scene to the Lua output, and a Schedules switch that pauses all of it.

Trying it (about 15 minutes)

  1. Download DirectorLink.c4z from https://github.directorlink.io/releases/latest
  2. Add it to the project in Composer Pro. It finds the rooms and devices by itself and loads without a reboot.
  3. On the DirectorLink device, choose Actions > New Pairing Code (8 digits, valid for 15 minutes, works once).
  4. On a computer on the home network, open https://app.directorlink.io and enter the controller's IP address and the code.
  5. For phones and remote access, set Remote Access to On in Composer, sign in with Google in the app and link the home, then use "Add my other device".

Good to know

- It's an early release, used every day in one home so far (CORE-1, OS 3.4.3). It needs OS 3.3.0 or newer.

- It doesn't read or change your Composer programming. Its scenes and schedules are its own.

- Opening doors and gates stays off until you enable Door Control in Composer.

- Your data stays on the controller. The cloud keeps only accounts and which home each belongs to. No ads or tracking.

Feedback, bugs and device requests are welcome at https://github.directorlink.io/issues. More at https://directorlink.io

DirectorLink is an independent project, not affiliated with Control4 or Snap One.

u/Sensitive-Phrase-332 — 15 days ago
▲ 5 r/C4diy

DirectorLink: a free, open-source Control4 driver and app (looking for testers)

Hi all,

I've been building DirectorLink, a free and open-source driver for Control4 plus an app for phones and computers, and I'm looking for people to try it.

What it does

- Controls lights (including KNX switches and dimmers), thermostats and AC (e.g. CoolMasterNet), blinds, IP camera pictures, KNX door and gate relays, and DoorBird.

- One-tap scenes. For example "Good night" turns all lights off, sets the bedroom AC to 24 and closes the blinds. You can pick single lights, or copy the house as it is right now.

- Schedules by the clock, at sunrise or sunset, or by the weather (heat, wind, rain, from Open-Meteo). The controller runs them itself, even when no phone is open.

- Works at home and away. At home the app talks to the controller directly. Away, and on iPhone, it goes through your Google account, locked end to end, so the servers in between can't read it.

- Family access with roles: view only, control, doors, or admin. Everyone keeps their own language, theme and favorites. English and Hebrew.

For installers

Automation that homeowners make is hard to troubleshoot when you can't see it. DirectorLink shows its own in Composer: Schedule Status (what is on and what runs next), Last Automation (what ran, when and why, e.g. "Cool the house, heat rule, 31C outside"), an action that prints every schedule and scene to the Lua output, and a Schedules switch that pauses all of it.

Trying it (about 15 minutes)

  1. Download DirectorLink.c4z from https://github.com/IsraelCIL/DirectorLink/releases/latest

  2. Add it to the project in Composer Pro. It finds the rooms and devices by itself and loads without a reboot.

  3. On the DirectorLink device, choose Actions > New Pairing Code (8 digits, valid for 15 minutes, works once).

  4. On a computer on the home network, open https://app.directorlink.io and enter the controller's IP address and the code.

  5. For phones and remote access, set Remote Access to On in Composer, sign in with Google in the app and link the home, then use "Add my other device".

Good to know

- It's an early release, used every day in one home so far (CORE-1, OS 3.4.3). It needs OS 3.3.0 or newer.

- It doesn't read or change your Composer programming. Its scenes and schedules are its own.

- Opening doors and gates stays off until you enable Door Control in Composer.

- Your data stays on the controller. The cloud keeps only accounts and which home each belongs to. No ads or tracking.

Feedback, bugs and device requests are welcome at https://github.com/IsraelCIL/DirectorLink/issues. More at https://directorlink.io

DirectorLink is an independent project, not affiliated with Control4 or Snap One.

u/Sensitive-Phrase-332 — 17 days ago
▲ 9 r/C4diy

C4Bridge - open-source local Control4 management for homeowners

Hi everyone,

We're (me as 20+ years software engineer + Cloud) planning a new open-source project called C4Bridge, and we'd like feedback from the C4diy community before we start coding.

What is C4Bridge?

C4Bridge is intended for Control4 homeowners who want simple control and automation without having to use Composer Pro for everyday changes.

The goal is not to recreate all of Composer Pro.

Composer is extremely powerful, but for a homeowner who just wants to manage devices, schedules and basic automation, it can be much more complicated than necessary.

Our goal is:

Install C4Bridge once, then handle normal everyday Control4 management through a simple local interface without needing Composer Pro.

Initial target:

Control4 OS 3.3.x and newer.

Proposed architecture

User interface / web app
↓
C4Bridge API
↓
C4Bridge.c4z
↓
Control4 Director
↓
Existing Control4 devices

C4Bridge.c4z would run directly inside the Control4 project using DriverWorks.

Composer would only be needed for the initial driver installation.

After that, normal operation should not depend on Composer.

Planned functionality

The first versions would focus on the everyday things homeowners actually need:

  • Discover rooms and devices
  • See current device state
  • Lights on/off/dim
  • HVAC control
  • Shades/blinds/windows open/close/stop
  • Scenes/routines
  • Schedules
  • Day-of-week schedules
  • Sunrise/sunset automation
  • Persistent schedules that survive Director reboots

Examples:

Every day at 23:30 → turn downstairs AC off + lights off

30 minutes before sunset → turn outdoor lights on

07:00 Monday–Friday → open bedroom shades

Run "Leaving Home" → lights off + AC off + shades closed

Simple device API

We don't want applications using C4Bridge to need knowledge of internal Control4 commands.

For example, instead of exposing something like:

RAMP_TO_LEVEL

C4Bridge would expose:

set_brightness(70)

Internally, C4Bridge would translate that into the appropriate Control4 command for that device.

We currently imagine adapters such as:

  • Light
  • Thermostat/HVAC
  • Shade/Cover
  • Relay
  • AV devices

This should also make it easier for the open-source community to add support for more device types later.

Local-first

C4Bridge should be LAN-only by default.

We don't want to expose a Control4 Director directly to the Internet.

Even on the LAN, access would require authentication/pairing.

Later, an optional secure remote-access component could be considered.

Open source

The project would be fully open source.

The Control4-specific layer would be separated from the UI so people could potentially build:

  • Web interfaces
  • Mobile apps
  • Home Assistant integrations
  • Voice integrations
  • Custom dashboards
  • Other automation systems

on top of the same C4Bridge API.

What C4Bridge is NOT

It is not intended to completely replace every advanced Composer Pro feature.

We are mainly targeting homeowner functionality:

control, monitoring, schedules, scenes and simple automation.

Things such as adding complex drivers, building large AV projects, controller upgrades and advanced project programming may remain outside the initial scope.

Why build this?

The experience we're trying to improve is:

Current:

Control4 homeowner
→ Composer Pro
→ complicated UI
→ authentication/version issues
→ make one small change

What we'd like:

Control4 homeowner
→ C4Bridge
→ simple interface
→ make the change

Once the bridge is installed, the homeowner shouldn't need to understand the internal complexity of Composer just to change a schedule, control a device or create a simple routine.

Questions for the community

Before we start coding, we'd really appreciate feedback:

  1. Is OS 3.3+ a reasonable minimum version?
  2. What are the most common things you currently open Composer for as a homeowner?
  3. Which device types should we support first besides:
    • lights
    • thermostats
    • shades/blinds
  4. Which scheduling/automation features are most important?
  5. Are there important OS 3.3/3.4 vs X4 differences we should account for from day one?
  6. Would LAN + VPN remote access be enough for you, or would you eventually want an optional remote-access service?
  7. Are there Control4/DriverWorks limitations we should know about before designing the API?
  8. What would make a project like this genuinely useful enough that you would install it?

We're asking now because we'd rather get the architecture right before writing a large amount of code.

Any technical criticism, edge cases, feature requests or experience with similar projects would be very welcome.

reddit.com
u/Sensitive-Phrase-332 — 20 days ago