Version 2026.1

Version 2026.1 is one of the largest TapHome updates. It brings a new way of evaluating smart rules, new and reworked smart rules, device default values, manual mode tracked separately for each value, new device types, the Read-only permission and a much faster app connection. Existing smart rules and device groups are converted to the new format automatically during the update.

Much faster connection#

The app connects noticeably faster when you return to it, change networks or switch locations, especially in large installations and over the cloud. It keeps a local copy of the location’s devices, interfaces and values, and on reconnection the control unit sends only what has changed in the meantime instead of the whole list.

Default values for devices#

Devices with controllable values have a new Default values setting. It determines what happens to a value when nothing is controlling it — no smart rule, group or manual mode:

• Do not change — the value stays as it is;
• Last manual value — the last value from a manual change is restored;
• Set to value — the device goes to the value you enter.

After the update, all devices have the Do not change option. A light switched on by a motion sensor therefore stays on after the smart rule ends; if it should turn off, choose the Set to value option and enter 0%. The helper smart rule Keep default values is no longer needed for this — existing smart rules of this type remain and keep working.

Default values

Do not change

Last manual value

Set to value

Level100%

Angle50%

Show more Cancel OK

Default values

Level

Do not change

Last manual value

Set to value

100%

Angle

Do not change

Last manual value

Set to value

50%

Cancel OK

The option applies to the whole device; use the Show more button in the dialog to set it for each value separately. Default values have the lowest priority and are always last in the Affected by section of the device detail. When a default value is currently in control of the device, the Default mode icon shows it (documentation).

Manual mode for each value separately#

Manual and automatic modes are tracked separately for each value of a device, so manual changes and smart rules no longer conflict. For example, when you change the brightness of a light manually, only the brightness goes into manual mode, and smart rules can keep controlling the other values, such as the color temperature. When the values are in different modes, the device detail shows the mode next to each value; mode changes are written to the device log.

Set how long manual mode lasts in the device detail with the Manual override button. This setting and its time are shared by all values of the device.

Manual override

If a user makes a change despite automatic Smart rules:

Keep manual mode for a limited time

Keep manual mode for a limited time and then until next automatic change

2 hours

Keep manual mode until next automatic change

Keep manual mode until ended by user

Overriding automatic mode or default value is disabled

Do not allow manual mode

Cancel OK

• New option Keep manual mode for a limited time and then until next automatic change: when the time runs out, the device does not switch back to automatic mode right away; manual mode lasts until the next automatic change.
• Disabling manual changes now has two separate options. The Overriding automatic mode or default value is disabled option rejects a manual change while a smart rule or the Set to value default holds the value; the Do not allow manual mode option prohibits manual changes completely.
• When you add a virtual device or change the type of a device, the app prefills the option by type — for example, a circulation pump gets the Keep manual mode for a limited time option set to 15 minutes.

New smart rule evaluation#

The detail of every device has a single list of everything that affects the device — smart rules, groups and default values. The list is in the Affected by section and its order is the priority; to change it, tap the Edit button and move the rows.

• Each value of a device is evaluated separately. A smart rule with a higher priority takes only the values it sets; smart rules with a lower priority can keep controlling the other values.
• Safety is no longer a separate type of smart rule but an action mode: every action can be in Manual, Automatic or Safety mode. Several safety smart rules can therefore act on one device at the same time, and their priority decides between them.
• Evaluation order: safety actions first, followed by a manual change from the app or directly on the device, then manual and automatic smart rule actions by priority, and default values last.
• The original safety smart rules keep the highest priority after the update.

For example, the Protect blinds from wind smart rule keeps the blinds raised in safety mode while the wind speed exceeds the strong wind threshold, and then works in automatic mode.

A smart rule can also be disabled for a single device with the Disable on this device option in the Affected by section or in the list of the smart rule’s inputs and outputs; it keeps controlling the other devices.

Blind

0%20%

Affected byEdit

Protect blinds from wind

0%

Blinds adjustment according to sun

100%20%

Scheduler

100%70%

Default values

100%50%

Add new smart rule

Statistics

Rename

Remove

Manual override

Service settings

Blinds adjustment according to sun

Rename

Disable

Disable on this device

Duplicate smart rule

Change permissions

Uninstall

New and reworked smart rules#

Several single-purpose smart rules have been replaced by more universal ones. They are converted automatically during the update:

Condition is a new smart rule that performs actions when a condition on a device value or a time condition is met (Device value or Time mode). It has an ordered list of universal triggers, each with its own actions, and the first trigger that is met applies. For example, three triggers based on one temperature — heat at full power below 18 °C, at reduced power below 20 °C, and switch off at 21 °C and above — fit in a single smart rule. See the Condition smart rule documentation for the setup.

Condition

Trigger mode

Device value

Time

Input devices

Motion sensor

Add Device

1

Triggers

1

MotionMotion spotted

Turn on

2

MotionMotion cleared

Turn off

Add trigger

1. The number in the circle is the order of the trigger; change it by moving the row. A filled circle marks a state trigger, a hollow one an event trigger.

Other new and reworked smart rules:

• Scheduler (new) performs actions at specific times of a recurring period — day, week, workday and weekend, month or year. The times can be fixed or relative to sunrise or sunset (documentation).
• Delay (new) waits for the Start delay after it is triggered, performs the Start actions and holds them until the End delay expires; then it can perform the End actions. For example, a bathroom exhaust fan turns on 4 minutes after someone leaves the bathroom and runs for 10 minutes (documentation).
• Light Controller (new) controls one or more lights with push buttons as well as motion and presence sensors in one smart rule. A short press turns the lights on or off, holding the button dims them, and a button press temporarily suppresses the sensors, so a motion sensor does not turn on a light you have just turned off. Push buttons can also have custom actions for the lights of this smart rule, for example a double click activates a color scene; for actions on other devices, use Condition (documentation).
• Energy manager (new) turns devices on and off according to the surplus power measured by the electricity meter and according to their priority; it regulates analog outputs smoothly. For each device, you can set, for example, its power, minimum run time or active time intervals; the smart rule keeps the grid draw within the set limits. This lets water heating or pool filtration run mainly on solar surplus (documentation).
• Open window notification (new) sends a notification or performs actions when a window, door or garage gate stays open longer than the set time. It can be restricted by a presence device; by default, it is active in the Away and Vacation states (documentation).
• Protect blinds from wind (reworked) protects against strong wind immediately in safety mode; its adjustment in windy conditions has configurable sensitivity, and the Return back to normal after and Do not disturb at night options are new (documentation).
• Blinds adjustment according to sun (reworked) handles blinds with different service settings in the Sun orientation (window orientation relative to north, window height, distance from the floor to the window) or Slats angle adjustment sections in one smart rule. Such blinds used to need several smart rules (documentation).
• PID controller (reworked) regulates based on any device with a setpoint, not only temperature, and writes the correction to analog outputs, variables, blinds or thermostats. For each output, set the Positive, Negative or Both mode and a range from minimum to maximum; the heating and cooling mode can come from a device or be fixed. You can also use it with the new humidity, CO2 and water level controllers, for example.

App#

The TapHome desktop app has been rebuilt using new technology and is available for Windows, macOS and Linux. It renders more smoothly and adds:

• animated drag-and-drop reordering, with the list scrolling automatically;
• automatic switching between the light and dark themes according to the system;
• video playback from cameras;
• a Remember password option on the login screen (Windows and macOS): saved accounts are offered after you click into the user name or password field, can be removed from there, and passwords are stored encrypted.

The icon of a device, including the icons of individual Multi-Value Switch values, can be customized further once you have chosen it: Appearance (Default, Black and white, Off or Accent color), Background (Circle or Square), an Overlay with an adjustable position, and, for text icons from the Text (editable) category, your own text or emoji. A garage gate can, for example, have a lock in the corner of its icon (documentation).

A device on a scheme has a new Controls option in the Visualization section: its control buttons appear next to the device, and you control it from the scheme without opening the detail. From the statistics in a graph detail, the Detail item goes straight to the device detail.

Lists show the relations between devices and smart rules:

• the All devices list (also on interface pages) has a Show affected by and assigned smart rules switch in the menu; when you turn it on, each device shows its safety, affecting and assigned smart rules and limiting conditions, and disabled relations are gray;
• in the Smart rules list, the Show inputs and outputs switch shows the input and output devices of each smart rule;
• every smart rule has an Inputs and outputs page in its menu;
• the All devices list has a Devices without a smart rule overview.

Android displays the app edge to edge and supports the predictive back gesture (Android 16). On iOS, animations are smoother, synchronized with the display refresh rate.

Devices#

Settings has its own Device groups item, where you create a group of analog outputs, blinds, electricity meters or water meters.

• For each value of the group, choose the calculation method: MIN, MAX, AVG, SUM, OR or AND.
• Controlling the group affects each member in the same way as if you controlled that member directly.
• The group reports an error when one of its devices is in error or when groups refer to each other in a cycle.

A device made up of other devices — typically a group, but also an electricity meter with sub-meters or a virtual RGB light — has a Devices section in its detail, where you can open and control these devices directly.

The new virtual devices Humidity controller, CO2 controller and Water level controller have an adjustable setpoint. You assign them a sensor that supplies the current value, and the setpoint can be used in triggers and actions of smart rules — for example, the PID controller can regulate toward it.

Other device changes:

• The detail of every blind has quick actions: fully raising and lowering (0%, 100%, or 100% with the slats at 0%) and Stop.
• Multi-State Sensor is a new device type with named states: each numeric value has its own name and icon, up to 32 values. It can be created as a virtual device, in Packet parser and in Modbus.
• Multi-Value Switch can have up to 32 values instead of 10.
• If a device has a conversion, for example a variable converted to temperature, the converted value can also be changed manually in the detail, and the change is written back to the original value. Until now, the converted value in the detail was read-only.

Settings has a new Client devices section (for administrators and service technicians) listing all phones, tablets and computers that have connected to the location: name, platform and app version, online status, time of last access, and the This device label on the device you are using. Settings shows the number of currently connected devices directly. The detail of a client device also shows its creation time and identifiers, and the device can be renamed there — for example, the tablet at the entrance, which you can then pick as a recipient of notifications.

Notifications#

My location has a Test notification item in the Attributes section, which immediately sends a test notification to selected users, groups or client devices. In the Alarm smart rule, you choose on which client devices the alarm will beep.

Every notification in any smart rule has the Use fixed text or Generate content dynamically option in the Content settings section. The dynamic title and message are created by the Title script and Message script, which can read device values as well as data such as the name of the smart rule or location — a notification about an open window can thus also state the outdoor temperature, for example. Older notifications with placeholders are converted to scripts automatically.

Read-only permission for devices#

Devices that are outputs (actuators) have a new Read-only permission level. A user with this permission sees the device, its values, graphs and statistics, but cannot change the values — for example, the thermostat setpoint. For devices, the previous lowest level, which allowed changing values, is called Control.

Universal triggers#

Smart rules have a new common trigger system: instead of the fixed conditions of individual smart rules, there is one flexible trigger that works the same everywhere. A trigger can be:

• Device value — either a state that applies while the condition lasts (for example Value equals, Value is greater than, Value is within interval, Has no value, Has error), or an event that fires once on a change (for example Value changed to, Value rose above, Value fell below, Got error or a push button press);
• Time — a specific time or a time interval in a recurring period (day, week, workday and weekend, month, year), also relative to sunrise or sunset.

A trigger can watch several devices at once (the All devices must fulfill the state option). In the Additional settings section, set the minimum and maximum duration, delay, delay queue and hysteresis.

For example, the Value equals state on a motion sensor keeps the light on while motion lasts, whereas the Value changed to event turns it on only once, at the moment motion starts.

Universal triggers are used by these smart rules:

• Condition — an ordered list of triggers, each with its own actions;
• Formula and Script — after you choose On custom event, the calculation or script does not run on every input change but on a universal trigger;
• Delay — the trigger determines the start and end of the cycle and watches device values only; the time settings of a trigger are not available here; the smart rule has its own two delays instead;
• Sequencer — in the Controlled by triggers mode, the sequence is started, stopped, paused or restarted by triggers.

The condition types and other trigger settings are described on the Triggers page.

Timeline#

The new Timeline section shows time settings graphically over the whole period (day, week, month, year), so you do not have to read them from a list of times:

• Scheduler — when each scheduled action will be active;
• time-based Limiting condition (new Time type) — when the smart rule will work and when it will be limited;
• Condition in Time mode — when each trigger will be active, including which higher-priority trigger overrides the others.

Each action or trigger has its own color, which also colors its icon in the list below the timeline. Times tied to sunrise and sunset are drawn according to the actual time at the location, so for blinds that are raised at sunrise you can see how that time shifts through the year.

More smart rule changes#

• The Equation smart rule has time settings for both the True and the False result. For the False result, there is a new minimum duration — the result stays False for at least the set time, even if the condition is met in the meantime. For the True result, there is a new Reset maximum duration after option.
• Energy manager and Light Controller keep their own log of decisions, for example, a device turned on and why, power exceeded, or an automatic turn-on by a sensor. The smart rule shows the latest entries; open the full log with the Show all logs button.
• In an action on a device, besides Set value you can also choose Add or Subtract: the new value is calculated from the current value of the device and stays within its range. This works, for example, for the position and slat angle of blinds, analog outputs, brightness, color, variables and setpoints of temperature, humidity, CO2 and water level — a push button can thus raise the brightness in steps.
• The Limiting condition of any smart rule can also be of the Time type: the smart rule then works only in the chosen intervals of a recurring period (day, week, workday and weekend, month, year), for example only in winter (documentation).

Expose Devices#

Exposing devices over Modbus TCP, Modbus RTU and Modbus ASCII (Modbus slave) has been completely rebuilt:

• Instead of a fixed block of 20 registers per device, you pick specific values and actions of the device, and each has its own register. For each one, set the register type (H, A, C, D), register index, data type, byte order and multiplier.
• Many more device types can be exposed — sensors (temperature, humidity, CO2, pressure, wind and more), electricity, gas and water meters, groups, controllers, color lights and more.
• The Modbus master can also trigger device actions, such as blind commands, not only write values.
• A validity register can be added to each value to tell the master whether the value is valid (for example, whether the device is available); when it is not, the configured fallback value is returned.
• Overlapping register ranges and interface conflicts (the same port and Slave ID, a missing serial port) are shown directly in the list.
• Several Modbus TCP interfaces can share one port if they have different Slave IDs.

Existing Modbus slave interfaces are converted automatically during the update, keeping the same register addresses and Slave ID.

Modbus TCP now responds only to the Slave ID (Unit ID) set in the app. If your master has been sending a different Unit ID, for example 0 or 255, change it. Reading an address that is not assigned to any value returns an error.

The TapHome API interface can be added several times, each with its own token, and each one can be renamed — the name appears in the list of interfaces. The new Read-only token option creates a token that can only read device values, not change them.

Integration protocol can also expose a Multi-State Sensor, and several clients can connect over Integration protocol TCP at the same time; all connected clients receive value changes.

Scripts, Packet parser and Modbus#

• Value history. In scripts (the Formula and Script smart rules, device scripts), you can choose the Value info of … variant of a value, and such a variable gives access to the previous value and its time (Current.PreviousValue, Current.PreviousValueTime, Current.LastKnownValue and more) and, for statistics, also to values from previous completed periods (History.Values, where [0] is the previous period).
• Write verification. For devices on the TapHome bus, the control unit compares the value read from the hardware with the written one after each write. If they do not match, it retries the write several times and then reports a device error, which disappears when the values match or a new value is written. Scripts in Packet parser and Modbus have a new DEBOUNCE(deviceVariable, durationMillisec) function, which ignores read values for the given time after a write, so the value does not jump back during the transition.
• Block reading and writing of registers. Modbus scripts have functions for a whole block of registers at once: MODBUSRBLOCK(type, address, count) reads a block in one request, MODBUSWBLOCK(...) writes it, and MODBUSWBLOCKNE(...) writes it only if it has changed. UNPACKVALUE(...) and PACKVALUE(...) read a value of a given data type (Int16/32, UInt16/32, Float, Bool, String) from a block or write it into one, with an optional byte order. The UINT16COLLECTION(count) and BOOLCOLLECTION(count) functions create a collection. Variables of Modbus devices can have the collection<uint16> or collection<bool> type and hold a whole block of registers.
• Modbus RTU over TCP. The Modbus TCP interface has a new Modbus RTU over TCP option for transparent serial-to-Ethernet converters that tunnel RS485 unchanged.

Fixes and improvements#

• Faster rendering of lists and schemes.
• The TapHome bus reconnects automatically after the USB port is disconnected and connected again.
• More stable communication over Integration protocol (UDP and TCP).