---
title: "Party Mode: 49 Ramps Blocked, Zero During a Six-Hour Party"
description: "My house's evening wind-down lived inside its motion automations, so Party Mode had to block all 49. I checked the logbook afterwards: zero ramps fired."
image: https://willcurran.com/hubfs/will-curran-brand/party-mode-cover-nolane.png
---

[Skip to content](https://willcurran.com/blog/party-mode#main)

[Will Curran](https://willcurran.com/)

[Home](https://willcurran.com/) [Portfolio](https://willcurran.com/portfolio) [Press](https://willcurran.com/media) [Blog](https://willcurran.com/blog) [Favorites](https://willcurran.com/favorites) [Speaking](https://willcurran.com/speaking) [Consulting](https://willcurran.com/consult) 

[Hire Will](https://willcurran.com/hire)

[Writing](https://willcurran.com/blog) Home — Party Mode: 49 Ramps Blocked, Zero During a Six-Hour Party [Subscribe](https://willcurran.com/blog/subscribe)

Home

# Party Mode: 49 Ramps Blocked, Zero During a Six-Hour Party

![](https://willcurran.com/hs-fs/hubfs/will-curran-brand/will-curran-avatar.jpg?width=44&height=44&name=will-curran-avatar.jpg)

Will Curran Sep 30, 2026 · 6 min read

<https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwillcurran.com%2Fblog%2Fparty-mode>

On this page

![An abstract dark graphic: a grid of small grey bars with one marigold line cutting across them, next to the title Party Mode, 49 ramps blocked.](https://willcurran.com/hs-fs/hubfs/will-curran-brand/party-mode-cover-nolane.png?width=1600&height=900&name=party-mode-cover-nolane.png)

My house dims itself in the evening. Lights go warm, then down to a nightlight glow, and that is exactly what you don't want at a party. The obvious fix is to switch off the evening scene. There was no such scene to switch off. The wind-down was spread across the motion automations as time conditions, so Party Mode had to block all 49 of them. Over a party that ran just past six hours, zero evening or night ramps fired. I know that because I checked the logbook afterwards rather than assuming it.

## Wind-down was never a scene

My lighting runs on Home Assistant and Philips Hue. Motion in the late evening picks the warm scene. Later on, motion picks the nightlight. Nothing ever "starts" the evening. The evening is just which automation's time condition happens to be true when someone walks into a room.

That changes the job. You can't pause one thing. You have to tell every motion automation to stand down while the party is on. And that includes the daytime ones: a party that starts before the evening window would get stomped by the normal day scene the first time someone walked past a sensor.

## One switch, one condition, added everywhere

The build was a single on/off helper called Party Mode and a handful of automations around it:

- **Activate:** when Party Mode turns on, each room gets its party scene.
- **Motion:** while Party Mode is on, motion re-applies the party scene instead of the time-of-day one.
- **Auto-off:** a scheduled backstop, in case nobody turns it off.
- **Deactivate:** turns the party lights off so normal lighting can take over.

Then every one of the 49 motion automations got the same extra condition at the front: only run if Party Mode is *not* on.

The wording of that condition matters more than it looks. "Not on" means that if the helper ever goes missing or unavailable, the condition passes and normal lighting keeps working. The opposite wording, "only run when Party Mode is off", fails closed: lose the helper and the whole house stops responding to motion. When you bolt a mode onto dozens of existing automations, make it fail toward the behaviour people already rely on.

![Diagram of how one motion automation decides. Motion comes in. If Party Mode is on, the normal time-of-day path is skipped and the party motion automation re-applies the room's party scene. If Party Mode is not on, or is unavailable, the normal path runs and the time window picks the day, warm evening or nightlight scene.](https://willcurran.com/hs-fs/hubfs/will-curran-brand/party-mode-decision.png?width=1440&height=912&name=party-mode-decision.png)

## What I deliberately left alone

- **Movie Mode.** That is a deliberate act by a person, so it should win. If someone starts a movie mid-party, the next motion event puts the party back anyway.

## Measured afterwards, not assumed

After the party, I went back through the logbook. A mode like this can look perfect on the night because the room happens to be busy and lit. The question was whether anything leaked.

- **Suppression held completely.** Over a little more than six hours, zero evening or night ramps fired.
- **Motion kept working throughout.** The motion automation was still re-applying party scenes two seconds before the switch went off.
- **Restore needed no help.** Normal lighting came back about three minutes after Party Mode turned off. Nothing had to be re-enabled by hand.

## The parts that were not magic

**The re-apply-on-motion design had a side effect nobody predicted.** In one room, a smart plug powering something that isn't a light was a member of that room in the Hue app. Applying any Hue scene to that room switched the plug off. Party Mode re-applied the room's party scene on every motion event, so over the six hours that plug power-cycled 139 times. The logbook gave it away: the flapping started one second after Party Mode turned on.

**My own deactivate step was a regression.** The first version turned off every light in the party rooms, and "every light" included things that are lights only as far as Home Assistant is concerned. I fixed it with the house's standard reject list, then had to fix it again. Hue room groups contain their member devices, so excluding a plug by name did nothing if the group it sat in was still targeted. Checking the top-level list told me it was clean, and that was a false green. Expanding every group and checking the members was the real test.

## If you are about to try this

- **Find where your "evening" actually lives.** If it's time conditions on motion automations, a party mode has to touch every one of them, the daytime ones included.
- **Write the condition so it fails open.** "Not on" keeps normal lighting working if the helper breaks.
- **Decide what outranks the party** before you build it.
- **Look for non-lights hiding in light groups.** Smart plugs inside a room group get every scene and every "all off" sent to that room.
- **Measure the first real run from the logbook.** Check the last activation time of the scenes that should not have fired.

## Build it yourself

What it does: one switch that holds every room in a party look, keeps motion lighting alive, and hands back to normal lighting cleanly when it turns off.

- **Home Assistant** with a toggle helper for the mode.
- **A party scene per room**, made in your lighting app (Hue in my case).
- **Small automations:** activate, re-apply on motion, a scheduled auto-off, and deactivate.
- **One condition** added to the front of every existing motion automation: the mode is not on.

How the pieces fit: the condition takes the normal motion automations out of the way, the party motion automation takes over their job, and turning the mode off lets them pick up again on the next motion.

Give this to your AIHelp me add a Party Mode to my Home Assistant lighting. First, list every automation that changes lights on motion or on a schedule, and show me where the evening and night behaviour actually lives (a scene, a schedule, or time conditions inside motion automations). Then propose: a toggle helper; an automation that applies each room's party scene when it turns on; one that re-applies the party scene on motion while it's on; a scheduled auto-off as a backstop; and a deactivate step. Add a "mode is not on" condition to the front of every motion automation, including daytime ones, worded so it passes if the helper is unavailable. Before any "turn off all lights" step, expand every light group and list the members, and flag anything that isn't a room light, such as smart plugs. Tell me which automations you would leave unsuppressed and why. Afterwards, give me a checklist to verify the first real run from the logbook.

If you have built a mode like this and found a different thing hiding in a light group, I would like to hear about it.

Filed under [Home](https://willcurran.com/blog/tag/home)

![](https://willcurran.com/hs-fs/hubfs/will-curran-brand/will-curran-avatar.jpg?width=64&height=64&name=will-curran-avatar.jpg)

Will Curran

I spent sixteen years building one company, and I have been in the event industry since 2007. These days I write about the technology I actually use — trucks, radios, home infrastructure, and the tools that survive past the first invoice.

[All posts by Will →](https://willcurran.com/blog/author/will-curran)

Get the next one by email

One email per post. No digest, no sponsors.

[← Previous A Check That Can't Fail Is Worse Than None](https://willcurran.com/blog/a-check-that-cant-fail) [Next → How I Pick the Best Live Sets for a Playlist](https://willcurran.com/blog/best-live-sets-playlist)

## Related reading

[Home The Heat Rating That Decides a Desert Garage Mini-Split 4 min read](https://willcurran.com/blog/desert-garage-mini-split-heat-rating) [Home Movie Mode Means the Robot Vacuum Waits 6 min read](https://willcurran.com/blog/movie-mode-vacuum) [Home A Holiday Color Engine with a Calendar Computed to 2099 7 min read](https://willcurran.com/blog/holiday-color-engine)

[Will Curran](https://willcurran.com/)

[LinkedIn — 29,339+ followers](https://www.linkedin.com/in/willcurran) [GitHub](https://github.com/rancur) [YouTube](https://www.youtube.com/channel/UCJgscc27l4fpkWx1SeK05xg/) [Spotify](https://open.spotify.com/user/rancur) [SoundCloud DJ mixes](https://www.soundcloud.com/thewillsee) [Twitch](https://www.twitch.tv/thewillsee) [Last.fm](https://www.last.fm/user/default) [Trakt — movies & TV](https://trakt.tv/users/willcurran) [Goodreads](https://www.goodreads.com/user/show/55302838-will-curran) [Will See Music](https://www.thewillsee.com) [Arizona Meshtastic](https://azmsh.net) [Electric Forest Meshtastic](https://efmesh.com)

© 2026 Will Curran — All rights reserved. [RSS](https://willcurran.com/blog/rss.xml) [Back to top](https://willcurran.com/blog/party-mode#main)

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Will Curran",
    "url" : "https://willcurran.com/blog/author/will-curran"
  },
  "dateModified" : "2026-10-22T18:10:53.442Z",
  "datePublished" : "2026-09-30T16:00:00.000Z",
  "headline" : "Party Mode: 49 Ramps Blocked, Zero During a Six-Hour Party",
  "image" : [ "https://willcurran.com/hubfs/will-curran-brand/party-mode-cover-nolane.png" ],
  "mainEntityOfPage" : {
    "@id" : "https://willcurran.com/blog/party-mode",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://willcurran.com/hubfs/image-1.png"
    },
    "name" : "Will Curran LLC"
  }
}
```