Every way of changing the house's lights now goes through one switchEvery way of changing the house's lights now goes through one switch

September 25, 2026 · Every trigger that changes the house's lighting (arriving home, leaving, an Alexa scene, a spoken command) now writes one shared switch instead of touching a bulb directly.Every way of controlling the house's lights (arriving home, leaving, an Alexa scene, or a spoken command) now goes through one shared setting instead of switching bulbs directly.

One switch for every light trigger

"I'm here" and "I'm leaving" used to enumerate every light.* entity in the house and fan a power call out across all thirteen, which meant two places decided what the lights should be doing and no way to say the office belongs to Day, Bright and Off and none of the other seven modes. Both intents now write input_select.light_mode once and leave it to the light_mode_apply automation, watching that select, to run the scene. The Apple TV still hangs off "I'm leaving" rather than off the Off mode, because turning the lights off during a film has to leave the film running, and a dropped socket on that second call is now caught and spoken as "The TV didn't respond." instead of failing the whole intent. Probed against the live Home Assistant instance, the select carries all ten mode names exactly as declared and all ten scenes exist, but the instance has no media_player entity at all, so the Apple TV call is a silent no-op until that integration gets added by hand.

Getting a mode said out loud turned out to be the harder half. Alexa's /smarthome route gained nine scene endpoints today, one per mode besides Off, each writing the same select and nothing else. But "Alexa, discover devices" found none of them, because a Smart Home Skill's endpoint has to be a Lambda function, and the only Big Brain skill on the account is a Custom Skill, a different kind of thing entirely. The fix was a new intent on that Custom Skill instead: "ask Big Brain for dinner mode" writes the select directly, and a matching "what are my modes" answers with the nine names and nothing else, read from the same list, so the two can't drift apart. Shortening that to "Alexa, dinner mode" still needs a Routine built by hand in the Alexa app for each mode, and testing the first batch ran into Alexa's own guard against one Routine calling another. It kept refusing even after the old ones were deleted. Still unresolved.

The email project moved in with CRM

The Email Organizer, which read and filed a personal Gmail account, is no longer its own listed project. Its code is now CRM's email/ package, merged in with all 27 of its original commits still reachable in history rather than squashed into one. The move exposed a real gap in the old repo's own tests: eight test files checked that nothing under the package required a hardcoded '/email-organizer/src/' path, and six of those asserted an empty filtered list, which had been passing whether or not anything was actually being checked. All eight now assert the list is non-empty before filtering it, proven by deliberately breaking each check four separate ways first.

That project's page on this site is deleted rather than folded in, since it had never gone live (it was still marked in-progress), and the substance behind it, the measured 7.2% of one mailbox that turned out to be political fundraising, the three separate switches required before it touches real mail, moves to CRM's own page instead.

One shared setting for every light trigger

Two voice commands, "I'm here" and "I'm leaving," used to turn every light in the house on or off one by one, thirteen separate commands sent out every time. That meant two different pieces of code both had opinions about what the lights should be doing, and neither could say that the office belongs to only three of the ten lighting modes and not the other seven. Both commands now do one thing instead: they set a single shared switch to the mode they want, and a separate automatic rule, watching that switch, is the only thing that actually turns lights on or off. The TV is a special case tucked inside "I'm leaving" rather than the "lights off" mode itself, because turning the lights off during a movie needs to leave the movie running. If the TV doesn't respond it now says so out loud instead of failing the whole command. Checked against the real system running the house, the switch offers exactly the ten modes it's supposed to, and all ten lighting scenes exist. But the house currently has no smart TV device registered in it at all. Turning the TV off through voice does nothing yet, silently, until that gets set up by hand.

Making a mode work as a spoken command turned out to be the harder half of the job. Alexa was given nine new "scenes" today, one for each mode except off, each one just setting that same shared switch and nothing more. But saying "Alexa, discover devices" found none of them, because the kind of Alexa skill that can offer scenes has to run on a particular kind of cloud function, and the household's assistant is built as a different, simpler kind of skill that can't. The actual fix was to teach that existing skill a new spoken phrase instead: "ask Big Brain for dinner mode" sets the switch directly, and a matching "what are my modes" reads back the nine names and nothing else, pulled from the exact same list, so the two can never fall out of sync with each other. Shortening that to a plain "Alexa, dinner mode" still needs a manual step for each mode: building a separate Alexa Routine, a saved shortcut, in the Alexa phone app. Testing the first batch ran into a wall: Alexa refused to let one saved shortcut trigger another, and kept refusing even after the old shortcuts were deleted. Still unresolved.

The email project moved to a new home

The Email Organizer, a separate tool that read and filed a personal email inbox, is no longer listed as its own project on this site. Its code has moved into another project, CRM, as a package inside it, carried across along with all 27 of its original commits, its full change history, rather than being squashed down into one. The move uncovered a real gap in the old project's own tests: eight test files were supposed to check that nothing in the moved code still pointed at the tool's old file location, and six of those tests worked by checking that a filtered list came back empty. They had been passing whether or not anything was actually being checked, because an empty list looks the same whether the check ran correctly or never ran at all. All eight tests now check that they found something before they filter it, and that fix was proven by breaking each check on purpose, four different ways, and watching it catch every one.

That project's own page on this site is being deleted rather than merged into the other one, because it had never actually gone live: it was still marked as in-progress and no visitor had ever seen it. The details behind it move to the other project's page instead, including its most interesting finding: a full 7.2% of one real inbox turned out to be political fundraising email, and three separate settings all had to agree before the tool was allowed to touch a real inbox at all.