Roomify 1.6.1

Reliable Outcomes

Roomify 1.5 became better at deciding when to retain or resume automation authority.

Roomify 1.6 goes a step further: it is better at ensuring that the lighting outcome Roomify intended is actually achieved.

Why 1.6 Was Needed

Roomify operates on information reported by the devices and systems that connect your home to Indigo.

That information is useful, but it isn’t necessarily a perfect representation of what is happening physically.

A device may report a change later than it actually occurred. In some circumstances, a reported state may even temporarily differ from the device’s actual state.

This creates an important distinction:

The state reported by a device is not necessarily the same thing as the actual state of the device.

For an automation system, that distinction matters.

Roomify may issue an instruction and receive a report that appears to contradict the intended outcome. The report may represent a genuine change, a delayed report of an earlier state, or simply an inaccurate observation.

Roomify therefore cannot treat every device report as definitive evidence that the physical world has changed—or that someone has taken control.

Version 1.6 improves Roomify’s ability to operate in that uncertainty.

When Roomify still has authority and the evidence indicates that an automated lighting outcome has not been achieved, it can confirm the result and correct the lighting when necessary.

The goal is not to ignore device reports. It is to interpret them appropriately, in context, and to avoid abandoning an automation based on imperfect information.

What’s New

Automatic Confirmation and Correction

Roomify can now automatically confirm that lighting changes have reached their intended state and correct a device when necessary.

This feature is enabled by default and can be disabled in the plugin configuration.

When Roomify has issued a lighting instruction and remains in control of the room, an unexpected device state no longer necessarily means the automation must be abandoned. Roomify can verify the room’s state and, when appropriate, correct the discrepancy.

More Reliable Lighting Execution

Roomify now spaces lighting instructions to reduce command congestion when multiple devices are being controlled at once.

This helps prevent rapid bursts of commands from overwhelming the underlying lighting system and improves the consistency of multi-device lighting changes.

Better Recovery from Device Divergence

A device that fails to follow an automation instruction does not necessarily represent a change in homeowner intent.

Roomify can now do a better job of maintaining the intended room state when an individual device temporarily diverges from it, while continuing to respect genuine interventions.

This builds on the authority and deferral improvements introduced in Roomify 1.5.

The Goal of 1.6

The central goal of this release is simple:

Make the intended outcome more reliable.

Roomify should figure out what should happen next, respect you when you choose to intervene, and—when you haven’t—do a better job of making the automation actually happen.

Version 1.5 made Roomify more confident about when to keep control.

Version 1.6 makes it more capable of following through.

The result is a Roomify that is better able to understand the room, retain the right authority, and reliably deliver the lighting you’ve asked it to provide.

Roomify 1.4.0

Adaptive Conversation Tracing

When Roomify asks a device to change state, the interaction rarely ends with a single response. Many devices report their progress over a series of messages as they react to the request, update their state, or complete a fade. Roomify treats this entire exchange as a conversation.

A conversation begins when Roomify issues an intent. Until the device first reports compliance with that intent, every subsequent report is presumed to belong to the original conversation, regardless of how many intermediate states are reported or how long the device takes to settle.

Once compliance has been observed, Roomify begins evaluating subsequent reports to determine whether they are simply continuing the existing conversation or represent the beginning of an entirely new one.

To make that determination, Roomify 1.4.0 introduces adaptive conversation tracing. As devices respond to automation, Roomify learns each device’s normal response cadence. Reports that continue to arrive within that learned cadence are treated as part of the existing conversation. Reports that arrive significantly outside that cadence are interpreted as evidence that the device has begun participating in a different conversation.

That new conversation may have been initiated by a person, HomeKit, Alexa, Indigo, or another automation system. Rather than competing for control, Roomify listens. It recognizes that the conversation has changed and gracefully surrenders authority for the affected room, allowing the new conversation to proceed without interference.

By distinguishing between reports that belong to an existing conversation and reports that initiate a new one, Roomify significantly reduces false interruption detection while cooperating more naturally with people and other automation systems.

Startup error in 1.3.2 prevents device initialization. Apologies to anyone running 1.3.2 and please update.

to coordinate data with Securify plugin

Tring a new version number o this path, hoping Indigo will pick this up and publish it.

Fixes a syntax error in the heartbeat process that could result in rooms failing to resume previously suspended automations.

I noticed an error in my log file this morning, pertaining to the re-authorization of room automations once a room becomes off and vacant. The primary mechanism for this was working fine, but the failover executed in the heartbeat thread was failing.

Roomify Error Error in plugin execution runConcurrentThread:

  File "plugin.py", line 2836, in runConcurrentThread
  File "plugin.py", line 2605, in considerReauthorization
type: 'Dict' object is not callable

v1.1.2 resolves this.

I noticed an error in my log file this morning, pertaining to the re-authorization of room automations once a room becomes off and vacant. The primary mechanism for this was working fine, but the failover executed in the heartbeat thread was failing.

Roomify Error Error in plugin execution runConcurrentThread:

  File "plugin.py", line 2836, in runConcurrentThread
  File "plugin.py", line 2605, in considerReauthorization
type: 'Dict' object is not callable

v1.1.2 resolves this.

Adds four system-wide actions, so that you can apply certain changes to all rooms throughout the home.

These actions are useful when you want a particular outcome throughout all rooms of the home. Times when you want a temporary break from the automations, like when cleaning the house or hosting a party. Times when you want all the rooms to turn off, like when everyone has left the home or gone to bed.

These actions affect occupancy and authority state. They do not directly control lighitng, but rooms will typically respond by changing their lighitng where appropriate.

Roomify brings room-based automation to Indigo.

Instead of automating individual devices, Roomify allows you to think in terms of rooms. Lights, sensors, and other devices work together to create a room that understands occupancy, adapts to changing conditions, and responds intelligently over time.

Getting started is simple. Create one Roomify device for each room, identify the devices that belong to it, and you’re ready to go. Additional lighting and occupancy features can be enabled as needed and applied only where they make sense.

Whether you simply want lights to follow occupancy or you’re looking for more advanced adaptive lighting and room awareness, Roomify helps your home behave less like a collection of devices and more like a collection of spaces.

Smart Rooms. Adaptive Lighting.

First implemented in Indigo 2025.2. Backwards compatibility is unknown.