[xlarge] Smart (Components) Toolkit — v1.10.38 (store and test) :books: Full Documentation: Smart (Components) Toolkit for Homey Replace complex flow networks with powerful logic devices controlled by dynamic formulas. Make your flows cleaner, more readable, and easier to maintain. → Full Documentation & Interactive Tools What’s new in v1.10.38 v1.10.38 is now live in the Homey App Store, and the store and the test channel run the same version. If you come from the previous store version (v1.10.16), this is what you get: Presence+. Start a Flow only after one selected person, or everyone, has stayed away for a chosen number of minutes. A return cancels the pending trigger, so brief Home/Away glitches are filtered out. Presence+ guide Composite Device. Combine the same capability from several devices into one live value: average, minimum or maximum of numbers, any/all of alarms, or text and clock values, with triggers for every change or for changes above a threshold. Composite Device guide Circadian Light Group. The schedule follows your Homey’s time zone, mornings can have their own profile, and cards no longer hit Homey’s 60-second timeout. New … and report the result cards tell you which lights did not answer, and Collections pause, resume and switch more reliably. Circadian Light Group guide Waits longer than one minute. Start waiting… cards wait in the background and a …wait finished trigger continues your Flow, for both Conditional Gates and Waiter Gates. Conditional Gates · Waiter Gates New Flow cards. Math Compare, Gradient Map and Get the name of this Flow. Flow Cards Reference Logic Unit and Logic Device. The Formula result alarm works with Homey’s standard alarm cards again, new Formula changed triggers fire on every TRUE/FALSE change, and Logic Devices that depend on other Logic Devices keep working after an app restart. Diagnostic report. Generate a privacy-conscious report from App Settings and open a prefilled GitHub issue. Nothing is uploaded automatically. Reliability. Shared realtime subscriptions keep devices updated after network hiccups and stop the memory growth that could make Homey restart the app. Full version history (CHANGELOG) :house: Presence+ Homey’s presence can flicker between Home and Away. Presence+ waits until a person, or everyone, has really been away for the number of minutes you choose before it starts your Flow. A return before the delay expires cancels the pending trigger, a new departure starts a new countdown, and countdowns survive an app restart. WHEN: Everyone has been away for 15 minutes THEN: Turn off all lights THEN: Set the thermostat to 17 °C → Read the Presence+ guide :magnifying_glass_tilted_right: Debugging across Flows — Get the name of this Flow + Flow Doctor When Flows start each other, or several Flows send notifications, log lines or variables to the same place, it is hard to see which Flow actually did what. Get the name of [this Flow] (Advanced Flow) Put it in any Advanced Flow and use the Flow name tag in notifications, timeline entries, log lines or values you pass on to a shared Flow. You see at once which Flow sent each message. No hard-coded names that go stale: the name is read every time the card runs, so it follows when you rename the Flow. Flow id and Folder tags are there too, for example to group log lines by folder. A log never names the wrong Flow: if you copy the card or duplicate the Flow, Flow name shows [Duplicate], Has error turns yes and Error message names the Flows until you pick this Flow again in the copy. WHEN: This Flow is started THEN: Get the name of this Flow THEN: Create a notification with "[Flow name] ran" Flow Doctor: Flow tree and loop check The Flow tree tab shows all your Flows in their folders. Select one to see every Flow that starts, enables or disables it, through the whole chain, with flags for disabled Flows, unconnected cards, else branches and delays. Circular references: Flow Doctor warns about Flows that start each other in a loop, which can keep running forever. It tells active loops from inactive ones (through a disabled Flow or an unconnected card). The Flows view also reports references to deleted Flows. Deleted devices: the app keeps a record of Homey device IDs and names, so Flow Doctor can tell you which deleted device a broken Flow refers to. Together they cover both sides: Flow Doctor shows how your Flows are wired, and the card shows at run time which Flow actually ran. Get this Flow’s name — reference · Open Flow Doctor :light_bulb: Circadian Light Group A virtual light device that adjusts brightness and color temperature for a group of real lights — automatically following a circadian rhythm. Highlights No 60-second timeouts. Cards let the Flow continue as soon as every light has its commands; lights that don’t answer are retried in the background, and no card waits more than 50 seconds. Turn on / Turn off / Toggle and report the result (Advanced Flow) add All lights confirmed and Status tags, so you can see which lamps did not answer. Local time and morning profile. The schedule follows your Homey’s time zone, including daylight saving time. Tick Own morning profile to give mornings their own brightness and colour temperature. Fast, predictable group commands. Up to 5 lights are switched at the same time, and the newest command wins: “all off” right after “all on” supersedes the on instead of fighting it. The on/off state is verified afterwards and transient Z-Wave / Zigbee timeouts are retried. Collections. Combine several groups into one virtual light. Pausing or resuming a Collection reaches every member group, and Collection cards wait for all members before the Flow continues. Pre-warm auto-detection during pairing. A wizard step tests each light by briefly cycling it off, pre-setting dim / light_temperature / light_hue / light_saturation, then turning it back on to verify the value persisted. Each capability is marked ✓/✗ per device, with a re-test button available later via Repair. Smart light detection. Lights registered as socket with virtualClass: light (Hue/Z2M-bridged lamps) and Z-Wave dimmer modules with a dim capability are picked up automatically. “Turn on light at current circadian level”. Pick any member of the group from a dropdown — the action sets temperature/colour and dim, then turns the light on, in one step. Avoids the brief flash at the previous brightness for lamps that don’t support pre-warming. Why use it? Bright cool light during the day, warm dim light in the evening, deep red at night to preserve melatonin and night vision. Works at any latitude — pick clock times, solar events, or lux-sensor thresholds per phase. Doesn’t turn lights on or off; it only adjusts already-on lights, so it never fights with your other automations. Anchor modes (mix and match per phase) Mode Description Time Fixed clock time (HH:MM) in your Homey’s time zone. Best near the equator. Solar event Sunrise, sunset, civil/nautical/astronomical dawn/dusk, golden hour, blue hour, solar noon/midnight — with offset minutes and a polar fallback time. Lux sensor A real lux sensor crosses a configurable threshold (rising or falling). Falls back to a fixed time until the first crossing of the day. Light profile Per-phase dim and temperature with smooth interpolation between anchors, and an optional own morning profile. Red mode threshold: when the calculated temperature drops below the threshold, color-capable lights shift to red. Saturation scales with how deep below the threshold you are. Per-light tweaks: enable/disable, prewarm before on, allow red mode, min/max dim. Outdoor light source Choose how the device knows how bright it is outside: Astronomical (sun-elevation calculation) Homey lux sensor Open-Meteo / MET.no (radiation-based estimate) External value pushed from a Flow Flow cards Triggers: phase changed, red mode started/ended, paused/resumed, turned on/off, target changed, error, outdoor light requested. Plus an app-level “Solar event occurred” card with all 14 events + offset, usable from any flow. Conditions: is in phase, red mode active, is paused, is on. Actions: pause (sec/min/hour), pause until time, pause until solar event, resume, turn on/off/toggle (also as … and report the result with All lights confirmed and Status tags, Advanced Flow), set red threshold, apply temporary state (override dim/temp/saturation/red — restored on next tick, perfect for testing or quick “moods”), force red mode (with optional duration), apply now, set outdoor lux, turn on light at current circadian level (pick any group member from dropdown), turn on / off all members (group-level convenience). WHEN: Button "All on" pressed THEN: Turn on and report the result (Circadian Light Group Collection) AND: All lights confirmed is no THEN: Create a notification with "Lights: [Status]" Tip: a lamp that is unplugged slows every command down. Untick Enabled for it in the group’s light settings until it works again; the Status tag tells you which lamps don’t answer. → Read full Circadian Light Group guide Other devices and flow cards Device Purpose Composite Device Aggregate a shared capability across multiple devices as min/max/average, alarm, count, text, or clock time. Logic Device Boolean logic with visual wizard. Combine device states into TRUE/FALSE using formulas like A AND B. Logic Unit Advanced boolean logic with multiple formulas per device. JSON configuration. State Device Scene management — capture states at setup, apply with one action. State Capture Device Dynamic state capture at runtime. Push/pop stack for temporary changes, named slots, JSON backup/restore. Flow Card (no device needed) Purpose Conditional Gates Simple GO/NO GO flow control without variables or devices. Short waits in the card, long waits in the background with a “wait finished” trigger. Waiter Gates Wait until a device capability reaches a target value — in the card (up to 55 s) or in the background with a “wait finished” trigger. Presence+ Wait until one selected person, or everyone, has remained away for the configured minutes; any return cancels the pending trigger. Evaluate Expression Range checking and value mapping with AND/OR logic. Math Compare Compare a calculated number, e.g. Temperature + 3 against a threshold. Gradient Map Map a number from one range to another and pass the Mapped value tag to the next card. Get this Flow’s name Return the name, id and folder of the Advanced Flow the card is in as tags, e.g. for notifications and logs. → Complete Device Guide Quick examples Doorbell ring → push state, change lights, restore: WHEN: Doorbell rings THEN: Push current state to stack THEN: Set all lights to 100% THEN: Pop state (restore previous) [Homey Flow delay: 5 minutes] Conditional Gate gating two flows: Flow 1 — WHEN: Motion sensor triggered THEN: Modify Conditional Gate "allow_lights" → GO Flow 2 — WHEN: Door opened AND: Gate "allow_lights" is GO THEN: Turn on lights Long wait with a Conditional Gate (more than 60 seconds): Flow 1 — WHEN: Razor turned on THEN: Modify Conditional Gate "Razor" → NO GO THEN: Start waiting for Conditional Gate GO "Razor" (timeout 2 minutes) Flow 2 — WHEN: Conditional Gate wait finished "Razor" THEN: Turn off Razor (Result tag: GO = released early, TIMEOUT = 2 minutes passed) Waiter Gate waiting for a device (more than 60 seconds): Flow 1 — WHEN: Button pressed THEN: Turn on kettle THEN: Start waiting until Kettle onoff becomes false (timeout 10 min, id kettle_boil) Flow 2 — WHEN: Capability wait finished "kettle_boil" AND: "Value matched" tag is Yes THEN: Send notification "Water is ready!" Heat pump / aircondition fan speed with Math Compare and Gradient Map: WHEN: Temperature changes AND: Temperature is less than low_threshold_livingroom THEN: Set fan speed to 0% WHEN: Temperature changes AND: Temperature is greater than or equal to low_threshold_livingroom THEN: Map Temperature in range low_threshold_livingroom to high_threshold_livingroom into 100-500, round to 1 THEN: Set fan speed to Mapped value Homey stops every app Flow card after 60 seconds. The in-card waits (Conditional Gate: Wait for GO, Wait until device capability becomes value, Wait) therefore end after at most 55 seconds; use the Start waiting… cards plus their …wait finished trigger for anything longer. In an Advanced Flow both parts can live on one canvas. Pending waits are kept in memory and are lost if the app restarts. Documentation Getting Started Guide Device Types Guide Composite Device Circadian Light Group Presence+ State Device State Capture Device Conditional Gates Waiter Gates Flow Cards Reference Installation and Links Homey App Store (v1.10.38): Install Smart (Components) Toolkit Test channel (v1.10.38, same as the store): Install test version GitHub Repo: github.com/tiwas/SmartComponentsToolkit Online Emulator: Boolean Logic Emulator Formula Builder: Formula Builder Feedback & Support Found a bug or have a suggestion? Please report it: GitHub Issues: Report here This Forum Thread: Reply below! Circadian Light Group feedback is especially appreciated — Z-Wave/Zigbee mesh behaviour varies a lot between setups, so real-world reports help tuning. Support the Project If you find Smart (Components) Toolkit useful, consider supporting its development: [PayPal] Smart (Components) Toolkit — Simplify complex logic, state management and circadian lighting in your Homey flows :high_voltage:

Usually, in electronics we use + for OR, for AND, ! for NOT and the plus in the circle for XOR. It makes sense as AND is a more powerful “addition” than OR - * is more powerful than + :slight_smile: To make it easier to type, I’ve stuck with the +, * and ! that I’m used to. For XOR, I “created” a new easy to access sign with “^”. EDIT: If people want to, I can probably make aliases where AND could be either & or *, OR could be | or +, and XOR could be ^ or !=

I discovered two things the other day - my code was incomprehensible, and it didn’t work. I did a complete rehaul and pretty much made the whole thing from scratch again. The good thing now is that it works, and it’s better than the original :slight_smile: [image]

I’ve made some more major changes and launched v1. Should be plenty of reasons to try this one instead of the 0.7 launched earlier today :slight_smile:

I’ve made an update to the version on Github and would love some feedback! I’ve added a logic device, so you can make a virtual device made up of any (I hope…) device type and capability. For most people, this should be more user friendly than the logic unit (although not as flexible). Want to create a device that will be active when a door is open, there’s a water leak and the backyard camera is not active? Sure! Go ahead!

:rocket: New Feature: State Device (Snapshot & Restore) I’m excited to announce a major new feature currently available in the test version of Boolean Toolbox: The State Device. :link: Test Link: https://homey.app/en-no/app/no.tiwas.booleantoolbox/Boolean-Toolbox/test/ What is it? The State Device allows you to take a “snapshot” of the current state of your devices (lights, blinds, thermostats, etc.) in specific zones (rooms) or your whole house. You can then restore this state later using a simple Flow card. Think of it as creating your own complex Scenes on the fly, without having to manually add every single card to a Flow. How to use it Add a new Device: Go to Devices → + → Boolean Toolbox → State Device. Select Scope: Choose which Zones (Rooms) you want to capture. You can select “Whole House” or pick specific rooms like “Living Room” and “Kitchen”. Select Devices: You will see a list of all compatible devices found in those zones. Uncheck any devices you don’t want to include in the snapshot. Edit Configuration (Optional): You will see the generated JSON configuration. This contains the exact values captured (e.g., dim: 0.8, onoff: true). You can edit this manually if you want to fine-tune values or remove specific capabilities. Done! Editing an existing State Device You are not locked into the initial snapshot forever. If you want to add a new lamp, remove an old one, or tweak the brightness level: Open the State Device in the Homey app. Go to Settings (gear icon) → Advanced Settings. Look for the Configuration (JSON) field. Here you can manually edit the list. You can delete blocks for devices you want to remove, or adjust values (e.g., change "dim": 0.5 to "dim": 0.8). Click Save. Restoring the State Once the device is created, simply use the “Apply state” action card in any Flow to restore all the captured devices to their saved settings. :warning: Important “Gotchas” & Tips 1. The “Dim turns it back on” trap When capturing a state, the app saves all setable capabilities. If a light is currently OFF but has a dim level of 50% (0.5) in memory, the snapshot might look like this: "My Light": { "onoff": false, "dim": 0.5 } When restoring this state, Homey sends commands sequentially. If it sends onoff: false (Light turns off) and then dim: 0.5, many Zigbee/Z-Wave bulbs will turn back ON to 50% brightness automatically because they received a dim command. Solution: If you want a light to stay OFF in your scene, you should manually edit the JSON during the pairing wizard (Step 3) and remove the "dim" line for that device, leaving only "onoff": false. 2. Delays and Network Traffic Restoring a state for 50 devices at once can flood your Zigbee/Z-Wave network. The State Device has a built-in default delay (default 200ms) between each command to help with this. You can edit the default_delay in the JSON configuration (in Advanced Settings of the device) if you need it to go slower. 3. Missing Devices If you remove a physical device from Homey that is part of a State Device snapshot, the State Device will log an error when you try to run it. You can enable “Ignore Errors” in the JSON config ("ignore_errors": true) to make it skip missing devices silently. You can also enable Debug Mode in the App Settings to see exactly which device is failing. Feedback This is a powerful tool, but it’s complex under the hood. Please let me know if you encounter any issues or have suggestions for improvements! Happy automating! :hammer_and_wrench:

Hi, I wondered if you weren’t aware of this app? Or did you still like to build similar functionality yourself anyway? [image] [App][Pro] Zone Memory - Save and Restore Device Configurations Apps Zone Memory [large] App Store: Zone Memory Frequently Asked Questions Change Log Supported Languages uk English de German netherlands Nederlands Permissions homey:manager:api (required for controlling all devices on behalf of the user) Currently Supported Device Classes All device classes known by Homey as of 2020-06-14. The use of some classes in combination with Zone Memory might not make obvious sense. However, even a button might have additional custom capabilities to toggle…

Thanks. I’m aware of it, but I liked my way of doing it better. It might have gone a long way since I tested it, but I think mine makes it a lot easier (at least than it used to be) to configure and change the scenes. I’d love some feedback, though :slight_smile:

Ah wow! The states section is indeed a lot more user friendly, and not needing flows is a big plus. So I played a bit with it. It’s great we can edit the created JSON, but i can imagine it’s not for everyone. Maybe it’s possible to call the checklist again in edit mode, for changing devices Nice to have: Is it possible to add a capability (un)check list prior or following the zone checklist? This would be nice when I want to create lights-only scenes for example. Findings / remarks: When selecting a zone, devices in the subzone are listed in the selection list of the next screen. But the subzones were deselected. The activated tiles are switched off after a minute. I’d prefer the tile to stay on (but I can imagine others don’t). Additionally there will be a tag with the state available for use in flows. Issue: (My) RGBW lights are in white mode, temperature as capability. When saving it’s state, sometimes somehow it was in color mode When recalling the state, the lights turn into some color, like blue; I recall the dev of Zone Memory having troubles with this similar issue as well. → When I manually replace “color” by “temperature” in the JSON, and remove the saturation and hue capabilities, changing states goes well. Just an idea: have the user select if color mode is used? Or the other way round

Thanks for the kind words and for great feedback. [image] Peter_Kawa: It’s great we can edit the created JSON, but i can imagine it’s not for everyone. Maybe it’s possible to call the checklist again in edit mode, for changing devices Yeah, it’s probably more on the advanced side of things. I’ve been thinking about making a web page for my repo that will make it easier. But I had to choose beween keeping it really simple or really powerful. Those don’t always go hand-in-hand. Ask the maintainers of vi :stuck_out_tongue: I’ve been thinking about making it a little more user-friendly, though. Adding an optional delay for every level (global, zone, room, device) that will override or add to the global delay. I’ve also been thinking about grouping the devices in the json on a room basis to make it easier to get a good overview. As I’m using the devices’ id, changing the numbers of levels in the json (I’ll just flatten it internally) shouldn’t break anything. As for getting the checklist again, I had that on my todo, too, but couldn’t find a good way to do it. It’s no harder than just creating a new device, checking the devices you want, copy the json and cancel the creation. The other option is to make a web tool, but it seems to be a limit to the number of API hits (100, more than most people will need). Any thoughts? Making tools here and there will make it harder to maintain, so if the “almost create a new device to get a fresh json” is good enough, I might stick with that for the time being. [image] Peter_Kawa: When selecting a zone, devices in the subzone are listed in the selection list of the next screen. But the subzones were deselected. Could you explain this a little better? I’m not sure I understood. You have three levels (Home → Zone → Subzone), you deselct Home and Subzone so that only Zone is selected and you still get devices from Subzone? [image] Peter_Kawa: The activated tiles are switched off after a minute. I’d prefer the tile to stay on (but I can imagine others don’t). Additionally there will be a tag with the state available for use in flows. I’m very curious if you have a good solution for me here, because this was on my list. This is a solid idea, but I thought it might be a problem if you use them for “moods”. Like if you wanted to activate “Kitchen: romantic”, “Living room: pitch black” AND “Alarm sensors: Active, except cat door” so that you could mix and match. How about I add a selection (default: true) to turn off the other devices (but take no action, just “turn off” the device card), so if you activate a new scene using three devices you’d turn off others when starting the flow, then activate the rest with the option set to false? [image] Peter_Kawa: (My) RGBW lights are in white mode, temperature as capability. When saving it’s state, sometimes somehow it was in color mode When recalling the state, the lights turn into some color, like blue; I recall the dev of Zone Memory having troubles with this similar issue as well. → When I manually replace “color” by “temperature” in the JSON, and remove the saturation and hue capabilities, changing states goes well. Did it read the wrong capabilities? Or were you thinking more that when selecting devices you could select capability instead? Say a device has dim, on/off, hue, saturation - you want to select only dim and saturation, and move saturation to the top?

Ok, I’ve worked on this further. Would you mind testing the new version? There are some docs here: State Device - Boolean Toolbox for Homey I’ll see if I can make some sort of editor without using the Homey-API, but first I’d appreciate it if you could see if this fixes your problems :slight_smile:

[APP] Smart (Components) Toolkit (was: Boolean Toolbox) - Create advanced logic with simple formulas [v1.10.38 store & test - Presence+, Circadian Light Group, Composite Device]

Apps

Peter_Kawa November 28, 2025, 9:11pm 12

Hi,

I wondered if you weren’t aware of this app? Or did you still like to build similar functionality yourself anyway?

Topic		Replies	Views
[APP][Pro] Home Assistant - Community App Apps app , tools , homey-pro , home-assistant	1536	50538	October 31, 2026
[App][Pro] Zone Memory - Save and Restore Device Configurations Apps app , official , tools	110	8595	June 27, 2026
[APP][Pro] Device Capabilities - Enhance the capabilities of devices Apps flow , virtual-device , homey-pro , device-capabilities , avd	2269	72043	October 25, 2026
The Flow Exchange(r) - Exchange Your Flows with Others! Flows app , tools , advancedflow , device-capabilities , avd	50	27754	April 4, 2026
[APP][Pro] Advanced Virtual Device (Device Capabilities App) with Unique Text Status Indicator Apps app , tools , virtual-device , device-capabilities , avd	880	46612	October 26, 2026

[APP] Smart (Components) Toolkit (was: Boolean Toolbox) - Create advanced logic with simple formulas [v1.10.38 store & test - Presence+, Circadian Light Group, Composite Device]

Related topics