Question 1

How to organize Home Assistant configurations like Frenck does?

Accepted Answer

Frenck uses the packages pattern: create a minimal `configuration.yaml` that loads packages from an `integrations/` directory, with each integration in its own YAML file. This modular approach improves scalability and maintainability.

Question 2

What's the best way to test Home Assistant config changes automatically?

Accepted Answer

Frenck's config uses GitHub Actions for nightly validation against multiple Home Assistant versions. Set up a CI/CD pipeline similar to the provided workflows to run tests on commits and catch errors early.

Question 3

How to integrate ESPHome with Home Assistant using CI?

Accepted Answer

The repository includes an `esphome/` directory with configurations and CI workflows that compile and deploy ESPHome devices. This automates updates and ensures compatibility with the main Home Assistant setup.

Question 4

Frenck config vs other Home Assistant examples: which should I use?

Accepted Answer

Frenck's config is best for advanced users wanting scalability, CI/CD, and best practices from the project lead. Simpler examples are better for beginners or small setups due to less complexity and setup overhead.

Question 5

What linters are recommended for Home Assistant YAML files?

Accepted Answer

Frenck uses yamllint for YAML syntax, remarklint for Markdown, Prettier for formatting, and actionlint for GitHub Actions. Implementing these helps maintain code quality, as shown in the linting workflow.

Question 6

Is it worth setting up nightly testing for Home Assistant?

Accepted Answer

Yes, for complex setups or if using beta features, as Frenck's nightly validation catches breaking changes early. For simple configurations, manual testing might suffice without the CI infrastructure overhead.

Franck Nijhof

What is Franck Nijhof?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions