[Collection] Production-Grade Climate, Lighting & Shades Blueprints (ASHRAE-55, EN 16798, Humidity-Aware)

Blueprints Exchange
, , ,
1

Hey everyone! :waving_hand:

I’m excited to share a collection of 5 production-ready blueprints I’ve been developing for my own home automation. These focus on implementing proper building science standards (ASHRAE-55, EN 16798) rather than simple fixed thresholds.

:globe_with_meridians: Website with one-click imports: schoolboyqueue.github.io/home-assistant-blueprints

:package: GitHub: github.com/schoolboyqueue/home-assistant-blueprints

The Blueprints

1. Adaptive Comfort Control Pro (HVAC)

For: Thermostats (Ecobee, Nest, Honeywell, generic)

Implements the ASHRAE-55 adaptive comfort model — your ideal indoor temperature shifts based on outdoor conditions, not arbitrary fixed setpoints.

Highlights:

  • Psychrometric calculations (dew point, enthalpy, absolute humidity)
  • Natural ventilation with muggy air blocking
  • Machine learning from your manual adjustments
  • Sleep mode with tighter comfort bands
  • Smart HVAC pause when doors/windows open (with freeze/overheat protection)
  • U.S. regional climate presets (all 50 states)
  • Auto-detects thermostat vendor profiles (minimum separation, etc.)

2. Bathroom Light & Fan Control Pro

For: Bathroom exhaust fans + lights

Uses the “Wasp-in-a-Box” dual-sensor pattern (motion + door) for accurate occupancy detection, plus humidity-delta-based fan control.

Highlights:

  • Delta humidity control (bathroom minus baseline) — works even on naturally humid days
  • Hysteresis prevents fan chattering (separate ON/OFF thresholds)
  • Rate-of-rise boost — fan starts early when humidity spikes
  • Rate-of-fall hold — prevents premature shutoff
  • Night mode with dimmed lights and warm color temp
  • Manual override detection with configurable duration

3. Multi Switch Light Control Pro

For: Z-Wave, Zigbee, and Lutron switches/remotes

Universal switch automation that auto-detects your hardware and adapts trigger mappings automatically.

Supported devices:

  • Zooz ZEN71/72/73/74/76/77
  • Inovelli Blue (VZM31, VZM35) via Zigbee2MQTT or ZHA
  • Inovelli Red (LZW30/31/36)
  • Lutron Pico remotes (2/3/4/5-button)

Highlights:

  • Auto-detection of device model and protocol
  • Unified dimming across all trigger types
  • 5x multi-tap support for custom actions
  • Hold-to-dim with release detection
  • Switch state sync (optional)

4. Adaptive Shades Pro

For: Motorized blinds/shades/covers

Solar-aware shade positioning based on the research paper Energies 13(7):1731.

Highlights:

  • Uses sun azimuth/elevation and window orientation
  • Direct vs. diffuse light classification
  • Temperature-biased: opens for passive solar gain in winter, closes for cooling in summer
  • Glare protection with optional lux sensor
  • Supports slat (venetian) and zebra shade modes
  • Quiet hours and manual override support

5. Ceiling Fan Climate Control Pro

For: Ceiling fans with HVAC coordination

Implements EN 16798 / ASHRAE 55 adaptive comfort for ceiling fan control.

Highlights:

  • Dynamic comfort band based on outdoor temperature
  • Heat index integration (humidity-aware)
  • HVAC coordination — works with heating/cooling cycles
  • Deviation-based speed (not fixed thresholds)
  • Optional reverse mode for winter heating

Why These?

I built these because most blueprints I found used fixed thresholds that don’t account for:

  • Humidity — 77°F at 30% RH feels different than 77°F at 70% RH
  • Outdoor conditions — Your body adapts to seasonal temperatures
  • Real building science — ASHRAE-55 and EN 16798 exist for a reason

These aren’t just “turn on at X degrees” automations. They implement the actual math from building science standards.

Requirements

  • Home Assistant 2023.4+
  • Appropriate sensors for each blueprint (temp, humidity, motion, etc.)
  • See individual README files for detailed requirements

Feedback Welcome!

These are actively maintained. If you find bugs or have feature requests, please open an issue on GitHub. PRs are welcome too!

Let me know if you have questions. Happy automating! :house:

1 Like
2

Hello Jeremy Carter,

Thanks for contributing to the community with a new Blueprint.
I have a suggestion for you. Many people who are not familiar with directory structures will have problems installing this without the Home Assistant MY tools.

Adding a MY link for this Blueprint to your top post would help them a lot.
Here is the link to make that.
Create a link – My Home Assistant

1 Like
3

This looks awesome, but I have some questions on configuration. I have a single story home with two separate HVAC units controlled by their own Ecobee thermostat, and about 10 room sensors across the two thermostats that Ecobee uses to balance the temperature across the house.

How do I configure the blueprint work with both sensors?
The same question applies to presence sensors. I have tried a binary sensor group, but the picker does not let me choose it. The house is large, so I can’t just choose a single sensor.

I’m looking forward to your help.

4

I decided to create two versions of the blueprint - one for each Ecobee. In addition I created a binary_sensor group for the presence sensors, then edited the configuration directly to include the binary_sensor name. It all worked great.

For the temperatures, I used a two averaged sensor groups using the sensors for each side of the house, and then fed the value into the configuration. Again, I manually edited the configuration file and everything is working great.

I have one final question. My Ecobees have predefined schedules for setting the comfort levels. Should I disable them so that the climate automation takes over the setting of heat/cooling?

5

I replied to my own learning curve in a separate post, but basically my sensor logic was all wrong. My problem was solved by tweaking the blueprint to add the learning sensor id to the set_variable event. My trigger now has two logic paths for set_variable, both which ensure they look at the sensor id in the event to exclude updating the wrong information. It now works perfectly for me.