TapHome 2026.1
Fewer smart rules. More possibilities.
Version 2026.1 tidies up smart rules: universal ones do the work of several, specialized ones handle a whole scenario, such as solar surplus or lights. Existing ones convert automatically.
Version 2026.1 is still in beta. It needs the TapHome Next app. Our support assistant switches your control unit over for you — via WhatsApp or email, with a backup before the change.
Any user with the Admin or Service right to the installation can ask for it.
01 · Energy manager
The first smart rule for energy. Water heats up from the sun.
Energy manager is the first TapHome smart rule built to control consumption according to the power measured by an electric meter. It switches devices on according to the surplus and their priority, regulates analog outputs smoothly and keeps grid import within the set limits. Water heating or pool filtration thus run mainly on solar power.
Demo
Without a surplus the smart rule switches nothing on, unless Minimum day run time requires it.
- Without a surplus the smart rule switches nothing on, unless Minimum day run time requires it.
- The surplus is not enough for water heating. Pool filtration switches on, as it needs less, even though its priority is lower.
- The surplus is not enough for both. After the filtration's minimum run time, the smart rule swaps it for the heating, which has a higher priority.
- The surplus is enough for pool filtration too. Both devices run and the rest of the surplus goes to the grid.
The demo takes into account only the surplus, the order and the minimum run time; it ignores the other time settings of the devices.
How to set it up / what gets converted
In the Electric meter section you choose the meter on the grid connection. Setpoint is the target balance with the grid. When import reaches Maximum imported power, the smart rule immediately dims or switches off devices starting with the lowest priority, those past their minimum run time first. The order of the devices is their priority; you change it by moving them. For each device you set the power to switch on and off, the minimum run time and the times when it may run. The default Minimum day run time of 1 hour starts the device before the end of the interval, even from the grid, if the surplus was not enough. An analog output also has a minimum power and a choice of taking the whole surplus or sharing it.
02 · Installation overview
The whole installation as a tree. For every device, the list shows what controls it.
When servicing, you see right away what controls which device: the All devices list shows, for every device, the smart rules and groups that control it, in order of priority — right in the list, not only in the device detail. It shows the installation as a tree: interface, module, device. A row above the tree counts the Devices without a smart rule.
Demo
Hardware view: the interface, below it the modules, below them the devices. You see the values and control the devices right from the tree.
- Hardware view: the interface, below it the modules, below them the devices. You see the values and control the devices right from the tree.
- You turn on Show affected by and assigned smart rules. Above a device you see, in order of priority, what controls it, and below it what it triggers.
- Dependencies view: devices one after another by name, members below their group. Each member is also in the list on its own.
How to set it up / what gets converted
In the list menu, in the View section, you choose Hardware (interface, module, device), Dependencies (a group or virtual device, with the devices it is made of or calculated from listed below it), Hardware + dependencies or Simple. Views other than Simple are only visible to users with the right to see interfaces. The Show affected by and assigned smart rules switch adds the relations and the Devices without a smart rule row. Search then also finds a device by the name of a smart rule. The Smart rules list shows the inputs of a smart rule above it and its outputs below it; the Inputs and outputs page lists them by section. Dependencies and Hardware + dependencies need a 2026.1 control unit. The app also connects faster: it tells the control unit which devices and values it already has and receives only compressed changes (control unit and app 2026.1).
03 · Condition and universal triggers
Three heating levels. One smart rule.
The Condition smart rule combines several triggers, each with its own actions, and the first one that applies wins. A single smart rule thus has three heating triggers: below 18 °C heat at full power, below 20 °C heat economically, from 21 °C turn heating off. Condition replaces Daily schedule, Push button event and others.
Demo
At 22 °C only trigger 3 applies and the smart rule turns the heating off.
- At 22 °C only trigger 3 applies and the smart rule turns the heating off.
- At 20 °C no trigger applies. The smart rule releases the heating, and with the Do not change option it stays as the smart rule left it.
- At 19 °C trigger 2 applies and the heating runs economically.
- At 17 °C triggers 1 and 2 both apply. The first in order wins: heating at full power.
So order the triggers starting with the narrowest condition.
How to set it up / what gets converted
A trigger watches the value of one or more input devices (Device value mode) or a time and an interval in a repeating period, including relative to sunrise and sunset (Time mode). The order of the triggers is their priority; you change it by moving a row. A state trigger applies while the condition lasts; an event trigger fires once on a change. A filled circle is a state trigger, an empty one an event trigger. On the trigger page, in the Additional settings section, you set a delay, a duration and a hysteresis. The same triggers are used by Formula and Script (the On custom event option), Sequencer (the Controlled by triggers mode) and Delay, which is always driven by device value triggers.
taphome.com/en/docs/smart-rules/condition/ ↗taphome.com/en/docs/smart-rules/triggers/ ↗
04 · Light Controller
Motion turns the light on. Presence only keeps it on.
Light Controller is a specialized smart rule for complete light control: buttons, dimming, motion and presence together. What is new is the split of roles — motion turns the light on, a presence sensor does not turn it on but only keeps it on while someone is in the room, and the smart rule's own Turn-off Delay starts only after the presence signal ends.
Demo
Evening, the study is empty and the light's Default values are set to 0 %. Motion will turn it on, Presence will keep it on.
- Evening, the study is empty and the light's Default values are set to 0 %. Motion will turn it on, Presence will keep it on.
- You walk in. Walking triggers both Motion and Presence, and Motion turns the light on to 100 %.
- You sit at the desk. Motion soon ends, Presence holds and the light stays on.
- You leave. Presence ends only 10 minutes after the last motion, then the Turn-off Delay runs.
- The delay passes, the smart rule releases the light and the Default values of 0 % turn it off.
How to set it up / what gets converted
The Motion signal of a presence sensor belongs in the Automatic Turn On section, Presence in the Automatic Turn Off section; when you add the smart rule from the detail of a device in a zone, the app fills them in. With a sensor in Automatic Turn Off, the For a specified time row disappears; the Turn-off Delay (5 minutes by default) starts only when no sensor is active. Then the smart rule releases the lights: Default values set to Set to value with 0 % turn them off (chapter 8); with Do not change, which a new light has, they stay on. A light turned on with a switch does not go off by default until you turn it off with the switch. Lighting timer had all sensors in one list with one time, and each of them also turned the light on; the conversion puts them all into Automatic Turn On, so move Presence yourself.
05 · Scheduler, Timeline and Limiting condition of type Time
Day, week, month and year. By the clock and by the sun.
The new Scheduler replaces Weekly schedule: it repeats actions at fixed times or relative to sunrise and sunset every day, week, month or year. Timeline shows on a chart which action applies when, and in a Condition in Time mode also which trigger overrides the others.
Between two times, the action that ran last applies: the blind keeps its position until the next action. The black line is the current time.
To: 01.05., 00:00
To: 01.09., 00:00
To: next year
Limiting condition of type Time “outside summer”: in the green period the smart rule works, in the pink one it is limited.
Demo
Trigger 1 takes precedence: over lunch it lowers the blind to 50 %. Then trigger 2 applies again.
- Trigger 1 takes precedence: over lunch it lowers the blind to 50 %. Then trigger 2 applies again.
- After the move, the trigger from sunrise to sunset is first and covers the whole lunch break. The lunch trigger never applies.
At night no trigger applies: the smart rule releases the blind, and with the Do not change option it stays raised.
How to set it up / what gets converted
The Timeline section is in Scheduler, in Condition in Time mode and in a Limiting condition of type Time. Each action or trigger has its own color, the same as its icon in the list below the axis. It gets the color by its order in the list and keeps it when you move the row. The axis draws sunrise and sunset by the real times at the location. Like Weekly schedule, Scheduler has the periods Day, Week and Workday/Weekend and a timeline; new are Month, Year and times by the sun. The Limiting condition of any smart rule can be of type Time: the smart rule then works only in the chosen intervals, for example outside summer, not just in one daily window.
taphome.com/en/docs/smart-rules/scheduler/ ↗taphome.com/en/docs/release-notes/2026-1/#timeline ↗taphome.com/en/docs/smart-rules/limiting-condition/#time ↗
06 · Who decides
Everything that controls a device. In one order.
The Affected by section shows everything that acts on a device: besides smart rules also groups, default values and a manual change, in one order of priority. Safety is a new action mode, so several safety smart rules can act on one device. You can also disable a smart rule for a single device.
You choose the mode on the action page. The Protect blinds from wind smart rule does not have this option: in strong wind it uses Safety by itself.
Demo
No wind. Blinds adjustment according to sun holds both the position and the slat angle, because the app ranks a smart rule of this type above Scheduler.
- No wind. Blinds adjustment according to sun holds both the position and the slat angle, because the app ranks a smart rule of this type above Scheduler.
- Strong wind. The default strong-wind action in Safety mode raises the blind. It does not set the slat angle.
- The wind has dropped. Protect blinds from wind keeps holding the position, now in automatic mode.
- After the time set in the Return back to normal after option, the sun-tracking smart rule takes over the position again.
- In the bedroom, Scheduler should take precedence. Moved higher, it holds both the position and the slat angle, and the sun-tracking smart rule no longer applies.
- Scheduler is disabled on this blind only. The sun-tracking smart rule controls it again; Scheduler keeps controlling the other blinds.
- No smart rule controls the blind any more. Default values apply and the detail shows the Default value mode.
How to set it up / what gets converted
You change the order with the Edit button and by moving rows. Safety actions apply first, then a manual change, smart rules and groups by priority, and finally default values. A manual change is shown by the Manual control row above the smart rules; it cannot be moved and safety actions apply even before it. How long manual mode lasts is set with the Manual override button (chapter 7). A value set by an action in Safety mode is shown in Safety mode. The Disable on this device option is in the smart rule menu under the three dots.
07 · Manual mode for each value
You change the brightness by hand. Color temperature stays automatic.
Each value has its own mode, for example manual or automatic. After a manual change of brightness, color temperature stays automatic and a smart rule keeps changing it with an action that has the None option for brightness. The exception: while the manual override time is running, the light rejects the entire action if it sets both brightness and color temperature.
For a light the app also lists Brightness when turned on and Digital output; they switch to manual mode together with the brightness.
Demo 20:00
Manual override: Keep manual mode for a limited time and then until next automatic change, 2 hours.
In the evening, Scheduler sets both brightness and color temperature. Both values are in automatic mode.
- At the start, 20:00In the evening, Scheduler sets both brightness and color temperature. Both values are in automatic mode.
- Step 1, 20:15A manual change switches only the brightness to manual mode. Color temperature stays in automatic mode.
- Step 2, 21:00The 21:00 action has the None option for brightness and changes the color temperature. No smart rule holds the brightness: Manual only mode.
- Step 2 – action with brightness tooThe light rejects the whole 21:00 action with both brightness and color temperature. The color temperature stays at 3000 K until 23:00.
- Step 3, 22:15The manual override time has run out. The brightness stays in manual mode until a new smart rule action sets it.
- Step 3 – Keep manual mode for a limited timeWith the option Keep manual mode for a limited time, all values would return to automatic mode at once after 2 hours.
- Step 4, 23:00An action that sets the brightness ends manual mode. The brightness is automatic again, just like the color temperature.
How to set it up / what gets converted
How long manual mode lasts is set by Manual override for all values. For a new virtual device or a change of type, the app prefills it by type, for example 15 minutes for a circulation pump. A device has one manual override time: every manual change starts it again. The new option Keep manual mode for a limited time and then until next automatic change keeps the value manual after the time runs out, until a new smart rule action. Also new is the option Overriding automatic mode or default value is disabled: it rejects a manual change while the value is held by a smart rule or by Default values set to Set to value. The existing option Do not allow manual mode blocks manual changes completely.
08 · Default values
When nothing controls a device, you decide.
Default values decide what a device does when no smart rule, group or manual mode controls it: it keeps its value, returns to the last value set by hand or sets the one you enter. Until now, a separate smart rule Keep default values held the entered value; now it is a setting of every device.
Default value
Level is the position of the blind, Angle the slat angle.
Demo
The light has the Do not change option, like every device after the update. Try what the other options do.
- At the startThe light has the Do not change option, like every device after the update. Try what the other options do.
- Point 1You set the brightness to 40 % by hand. The light switches to manual mode, by default until the next automatic change.
- Point 2The motion sensor detects motion and Light Controller (chapter 4) turns the light on to 100 %. The new action ends manual mode.
- Point 3 – Do not changeMotion has stopped and once the For a specified time period has passed, Light Controller releases the light. The Do not change option leaves it at 100 % in automatic mode.
- Point 3 – Last manual valueMotion has stopped and once the For a specified time period has passed, Light Controller releases the light. Last manual value returns 40 % in manual mode.
- Point 3 – Set to value 0 %Motion has stopped and once the For a specified time period has passed, Light Controller releases the light. The value 0 % turns it off in Default value mode.
How to set it up / what gets converted
The Default values row is always last in the Affected by section, with the lowest priority. The options are Do not change, Last manual value and Set to value; with the Show more button you set each value separately. When a default value controls a device, the Default value mode icon shows it. Default values are also in the device's Service settings, and a user with the right to change service settings may edit them. After the update, all devices have the Do not change option. The Keep default values smart rule is no longer needed; while an existing one runs, the device's Default values do not apply.
09 · Device groups
All blinds at once. The order decides what applies.
You can again create a group of analog outputs or blinds and control it with one command. The group detail shows each member with its value, mode and any error. On a member, the group is a row of the Affected by section, and the order decides whether the group or the member's smart rule applies.
Demo
The group's Scheduler sends 50 %. On the blind, the group row stands above the blind's Scheduler, so the group applies.
- MorningThe group's Scheduler sends 50 %. On the blind, the group row stands above the blind's Scheduler, so the group applies.
- WindA strong wind is blowing. Protect blinds from wind in Safety mode raises the blind; the slat angle stays as the group set it.
- By handThe group's manual 0 % command goes through, because the group row stands above the blind's Scheduler. The blind switches to manual mode.
How to set it up / what gets converted
Settings has a Device groups item: with the Add group button you choose a type and add members of that type. A short press of the up or down button on the Groups page tilts the slats by 10 %, for a group on all its members. You add a smart rule for the whole group in its detail with the Add new smart rule button. Each value of a member is set by the highest row of its Affected by section that holds it or is sending a command right now; safety actions always apply first. The row of a new group first stands at the end, just above the Default values row; after the next change of smart rules it moves above Scheduler and Condition and below Protect blinds from wind. You move it with the Edit button.
10 · Other changes in brief
What else is new in smart rules, devices and the app.
Open window notification
Reports a window, door or gate open longer than the set time; you can limit it with a presence device, for example to the Away and Vacation states only.
Delay
Replaces Delayed start and end and Countdown timer: a device value starts it and you set the actions at the start and at the end yourself.
Add / Subtract
The action calculates a new value from the current one, so a button raises the brightness step by step.
Read-only
A new permission for every device: the user sees values, charts and statistics but cannot change them. After the update, the existing device permission with this name is called Control.
Test notification
An item in the Attributes section on the My location page sends a test notification right away, also to client devices.
Notifications from a script
The Generate content dynamically option: a script puts, for example, the outdoor temperature into the message.
Client devices
A list of the phones, tablets and computers that have connected to the location; administrators and service users see it.
Alarm on selected client devices
In the Alarm smart rule you choose on which client devices it beeps, including several; until now only the device on which you created the smart rule beeped.
New controllers
Humidity controller, CO2 controller and Water level controller with an adjustable setpoint.
PID controller
Regulates by the setpoint of any device, not just temperature, for example a humidity controller.
Quick blind actions
The blind detail has buttons to fully raise and lower the blind, and Stop.
Multi-Value Switch
Can have up to 32 values instead of the previous 10.
Multi-State Sensor
Up to 32 numeric values, each with its own name and icon.
Equation
New time settings: the False result lasts at least the set time, even if the condition is met.
Control blinds with push buttons
One smart rule replaces the two previous ones: for a single button and for an Up and Down pair.
Control from the scheme
Control buttons can sit next to a device on the scheme, for example up and down arrows next to a blind, so you control it without opening the detail; you turn them on with the Controls option in the object settings.
Overlay icon
You can add a smaller icon in the corner of a device icon, for example a lock on a garage gate, or write your own text or emoji into it.
Android
Android shows the app edge to edge.
For integrators
Modbus slave
Exposing devices via Modbus TCP, Modbus RTU and Modbus ASCII has been reworked. Instead of a fixed block of 20 registers per device, you pick specific values and actions, and each has its own register with a type (H, A, C, D), index, data type, byte order and multiplier. Sensors, electric meters, gas meters, water meters, groups, controllers and color lights can be exposed too. Actions, for example blind commands, can also be triggered by the master. A validity register reports whether a value is valid; if not, a substitute value is returned. Interface conflicts are shown in the interface list, overlapping register ranges in the interface detail. Several Modbus TCP interfaces can share one port if each has a different Slave ID.
TapHome API
The Read-only token option creates a token that can only read device values.
Integration protocol
Also exposes the Multi-State Sensor. Several clients can connect at once via Integration protocol TCP, and with the Auto send (push all) option on, they all receive value changes. Communication over both UDP and TCP is more stable.
Value history in scripts
A value variant, for example Value info of Temperature, gives access to the previous value and its time (
Current.PreviousValue,Current.PreviousValueTime,Current.LastKnownValueand others), and for statistics also to the values of completed periods (History.Values,[0]is the previous period). It works in the Formula and Script smart rules and in device scripts.Write verification and DEBOUNCE
For devices on the TapHome bus, the control unit compares the value read back with the value written after each write; if they differ, it repeats the write and then reports a device error. The
DEBOUNCE(deviceVariable, durationMillisec)function in Packet parser and Modbus ignores values read for the given time after a write, so the value does not jump back.Block reading and writing of registers
MODBUSRBLOCK(type, address, count)reads a block with one request,MODBUSWBLOCK(...)writes it andMODBUSWBLOCKNE(...)only on a change.UNPACKVALUE(...)andPACKVALUE(...)read and write a value of type Int16, Int32, Int64, UInt16, UInt32, UInt64, Float, Double or Bool with an optional byte order; String can only be read.UINT16COLLECTION(count)andBOOLCOLLECTION(count)create a collection, and a variable can have the typecollection<uint16>orcollection<bool>.Modbus RTU over TCP
A new Modbus TCP interface option for transparent serial-to-Ethernet converters that tunnel RS485 unchanged.
taphome.com/en/docs/release-notes/2026-1/#expose-devices ↗taphome.com/en/docs/release-notes/2026-1/#scripts ↗
When updating
Converted automatically
- Smart rules are converted to the new ones:
- Push button event, Switch event, Notification, Doorbell ring action, Daily schedule and others → Condition; they keep their priority, and some are split into several smart rules, for example Notification into one for each device, so there will be more smart rules after the update;
- Weekly schedule → Scheduler;
- Delayed start and end, Countdown timer → Delay;
- Lighting timer, Push button dimming → Light Controller;
- Temperature PID controller → PID controller; with a switching or PWM output → Temperature hysteresis controller;
- The original (safety) Protect blinds from strong wind, Adjust blinds on windy conditions → the new Protect blinds from wind;
- Control blinds with single push button, Control blinds with Up and Down push buttons → Control blinds with push buttons;
- Watchdog → Sequencer.
- The original safety smart rules keep the highest priority.
- Device groups are converted to the new format. On every member they get a row in the Affected by section, and a group command no longer overrides a smart rule that stands above this row and is holding the value.
- Modbus slave interfaces keep their register addresses and Slave ID.
- Notifications with variables in the text are converted to scripts.
- Existing Keep default values smart rules remain and keep working.
- The existing device permission Read-only is called Control after the update and still allows changing values.
Check
Install the TapHome Next app on all phones, tablets and computers. A 2026.1 control unit does not connect to the TapHome app 2025.2 or older. TapHome Next 2026.1 is in the stores for Android 6.0 and later, iOS, macOS and Windows.
Default values have the Do not change option. This applies to all devices. A light that a smart rule turned on based on a motion sensor therefore stays on even after the smart rule releases it. If it should go off, choose Set to value with 0 % in its Default values row. While the old Keep default values smart rule runs on the device, the Default values do not apply.
On group members, check the order of the group row in the Affected by section. A member's smart rule that should give way to a group command must stand below the group row; you change the order with the Edit button.
A Light Controller converted from Lighting timer has all sensors in the Automatic Turn On section. Move the Presence signal of a presence sensor to the Automatic Turn Off section, so that it does not turn the light on but only keeps it on.
Modbus TCP responds only to the configured Slave ID (Unit ID). To any other Unit ID, for example 0 or 255, it returns exception 0x0A (Gateway Path Unavailable). If the master has been sending a different Unit ID, adjust its settings.
Coming soon
None of this is part of version 2026.1.
Wallbox
A charging station for electric cars with a built-in electric meter and card authentication.
Matter
Support for the Matter standard, for example for Apple Home and Google Home.
Core 3.0
A new generation of the control unit.
Mechanical button
A new TapHome wall button.
DALI-2 gateway
DALI on the TapHome bus with support for color temperature and RGBW.
Energy overview
Energy flow and a chart of production and consumption.
Circadian lighting
A smooth change of brightness and color temperature during the day.
Electric meters and spot prices
Improved electric meters and spot electricity prices.
New app design
A simplified view for users.