[APP] Smart (Components) Toolkit (was: Boolean Toolbox) - Create advanced logic with simple formulas [v1.9.2 stable / v1.10.2 test — NEW: Circadian pre-warm auto-detection]

[Tiwas]

Smart (Components) Toolkit — v1.9.2 stable / v1.10.2 test

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

---

New in test (v1.10.2): Circadian Light Group

A virtual light device that adjusts brightness and color temperature for a group of real lights — automatically following a circadian rhythm. Available now in the test channel only; the stable channel still ships v1.9.2 without this device.

New in v1.10.2

• Pre-warm auto-detection during pairing. A new wizard step tests each light by briefly cycling it off, pre-setting dim / light_temperature / light_hue / light_saturation, then turning back on to verify the value persisted. Each capability is marked ✓/✗ per device. No more guessing whether a lamp tolerates pre-warming — and no more turning lights on with the wrong colour.
• Re-test from Repair. Each managed light has a “Test pre-warm” button so you can re-run the test after firmware updates or when adding new devices.
• Smarter candidate filter. Lights registered as socket with virtualClass: light (Hue/Z2M-bridged lamps) and Z-Wave dimmer modules with a dim capability are now picked up automatically.
• New flow action: “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, all in one step. Avoids the brief flash at the previous brightness for lamps that don’t support pre-warming.
• Master “Prewarm before on” toggle is now a fallback for untested capabilities only; tested capabilities use the actual test result.

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). 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.
• 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

25 new 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, 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).

→ Read full Circadian Light Group guide

→ Install v1.10.2 test version

---

What’s already in stable (v1.9.2)

Device	Purpose
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.
Waiter Gates	Pause flow until a device capability reaches a target value.
Evaluate Expression	Range checking and value mapping with AND/OR logic.

→ 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: Wait 5 minutes
THEN: Pop state (restore previous)

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

Waiter Gate waiting for temperature:

WHEN: Button pressed
THEN: Turn on coffee machine
THEN: Wait until coffee machine temperature ≥ 90°C (timeout 5 min)
  → YES: Send notification "Coffee ready!"
  → NO:  Send notification "Coffee machine timeout"

---

Documentation

• Getting Started Guide
• Device Types Guide
• Circadian Light Group (test only)
• State Device
• State Capture Device
• Conditional Gates
• Waiter Gates
• Flow Cards Reference

---

Installation and Links

• Homey App Store (stable v1.9.2): Install Smart (Components) Toolkit
• Test channel (v1.10.2 — Circadian Light Group + pre-warm auto-detection): 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!

Test-channel feedback on Circadian Light Group is especially appreciated — that’s where polish happens before stable release.

---

Support the Project

If you find Smart (Components) Toolkit useful, consider supporting its development:

---

Smart (Components) Toolkit — Simplify complex logic, state management and circadian lighting in your Homey flows

[Tiwas]

[placeholder]

[Patrick_Van_Deursen]

going to follow this! great idea. Had for myself already built out the various logic gates and how to do that in flows, but would applaud doing that easier:

[Tiwas]

Yeah, that’s why I started this project. I was sick and tired of having to think boolean in new ways. And starting out in electronics, not being able to deal with boolean logic was a bummer.

Would love to find a better action card for it, but this is making it one heck of a lot easier to create logic. And I finally have an output that will be false if the logic didn’t stick.

Please tell me if you test it with some fancy formulas. I still haven’t had time to be really creative with it yet. But I will - because now I can

[Tiwas]

I need to try this. I need to find a scenario where this would fit

F(A,B,C,D,E)=(((A∗!B)⊕(C∗B))+(D∗(A⊕E)))⊕((C+E)∗(!D+B))

Returns TRUE for the following, with all five inputs used

| A | B | C | D | E |
| FALSE | FALSE | FALSE | FALSE | TRUE |
| FALSE | FALSE | FALSE | TRUE | TRUE |
| FALSE | FALSE | TRUE | FALSE | FALSE |
| FALSE | FALSE | TRUE | FALSE | TRUE |
| FALSE | FALSE | TRUE | TRUE | TRUE |
| FALSE | TRUE | FALSE | FALSE | TRUE |
| TRUE | FALSE | FALSE | FALSE | FALSE |
| TRUE | FALSE | FALSE | TRUE | FALSE |
| TRUE | FALSE | FALSE | TRUE | TRUE |
| TRUE | FALSE | TRUE | TRUE | FALSE |
| TRUE | FALSE | TRUE | TRUE | TRUE |
| TRUE | TRUE | FALSE | FALSE | TRUE |
| TRUE | TRUE | FALSE | TRUE | FALSE |
| TRUE | TRUE | FALSE | TRUE | TRUE |

[Patrick_Van_Deursen]

why not use + for and and / for or? would be a bit more logical and readable

and what is the circle with the plus sign in it, and the !?

[Tiwas]

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 +

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 !=

[Tiwas]

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

[Tiwas]

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

[Tiwas]

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!

[Tiwas]

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.

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

1. Add a new Device: Go to Devices → + → Boolean Toolbox → State Device.
2. Select Scope: Choose which Zones (Rooms) you want to capture. You can select “Whole House” or pick specific rooms like “Living Room” and “Kitchen”.
3. 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.
4. 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.
5. 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:

1. Open the State Device in the Homey app.
2. Go to Settings (gear icon) → Advanced Settings.
3. Look for the Configuration (JSON) field.
4. 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).
5. 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.

---

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!

[Peter_Kawa]

Hi,

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

[App][Pro] Zone Memory - Save and Restore Device Configurations

Zone Memory [large] App Store: Zone Memory Frequently Asked Questions Change Log Supported Languages English German 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…

[Tiwas]

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

[Peter_Kawa]

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

[Tiwas]

Thanks for the kind words and for great feedback.

@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

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.

@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?

@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?

@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?

[Tiwas]

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

[Peter_Kawa]

No problem!

@Tiwas

But I had to choose beween keeping it really simple or really powerful.

Throw in the “I know what I’m doing” button

@Tiwas

@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?

No, it was a misunderstanding from my side because of the zones I selected.
After some new tests I noticed there’s nothing wrong with it

@Tiwas

Adding an optional delay for every level (global, zone, room, device) that will override or add to the global delay

That sounds like a plan.

@Tiwas

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.

+1

@Tiwas

As for getting the checklist again, I had that on my todo, too, but couldn’t find a good way to do it.

I had the screens of the < group > app in mind;
it has an edit screen, which is, to the user, the same screen as the initial selection screen; it uses the Maintenance > Try to repair route
This is the edit screen:

[Tiwas]

@Peter_Kawa

This is the edit screen:

Hmmm…so what you’re after is to be able to re-do the selection process? I guess this is doable, but I’m not sure how to do it and not change any of the settings.

Would you want a new snapshot, a new snapshot for any new devices, or to reselect from the old snapshot? The last one would require that I save every single device state in the json, and only make a new snapshot for new devices.

I guess I can create an option in the pairing dialog to save all devices and use a key to say it’s active or not. The json could be REALLY big for some installations, though. And if I were to save all devices to the json object, should I just include the ones in the selected zones or all devices in all zones?

I could make a web app that would let people edit the json object they already have, and getting a fresh object should be fairly easy by creating a new device and then just copy the json to the old one.

If you have any ideas I will see if I can do it in the app, or if it’s better done in a standalone json editor just for this app. I guess I could also create a function to import a new json, but only include new objects?

[Tiwas]

How about something like this? This should give a lot more value, and be very helpful to inexperienced users.

State Device Editor - Boolean Toolbox

[Peter_Kawa]

Well, that’ll do, Lars!