Search
MENU
- • Simple thermostat with hysteresis
- • Simple Heating management using Weekly schedule and Presence switch
- • Power limiting
- • Notification on high temperature (DEPRECATED)
- • Configuring hysteresis control via Equation Smart Rule
- • PID Temperature regulation
- • PID Cascade
- • Regulation of Boiler Cascade
- • Equithermic regulation
- • Heating control in high electricity tariff via load management tariff indicator input
- • Boiler and pump control
- • Heating and Cooling modes
- • Editing multiple devices
- • Integrate multiple control units Core
- • Safe values
- • How to combine two daily schedules in one day
- • Grouping or linking devices together
- • Using statistic values in Smart Rules
- • Hot water circulation pump control
- • Exporting data from TapHome into Google Spreadsheet using Integromat
- • 2021.2
- • 2021.1
- • 2020.1
- • 2019.1
- • 2017.1 - Blinds automation - angle control update
- • 2017.1 - Blinds automation - Depth of sun rays
- • 2017.1 - Charts updated
- • 2017.1 - Core update from the app
- • 2017.1 - Double click and triple click
- • 2017.1 - Expose devices
- • 2017.1 - Multi-value switch
- • 2017.1 - Permissions
- • 2017.1 - Replace module action
- • 2017.1 - Set to Automatic mode - "Push buttons event" Smart Rule
- • 2017.1 – Daily schedule Smart Rule
- • Firmware changelog
- Documentation
- Software release notes
- 2017.1
- 2017.1 - Expose devices
2017.1 - Expose devices
In large projects with multiple Core control units it is required to network them together and have one Core control unit operating as a master. Examples would be floors in a hotel or an office tower where it may be suitable to have a standalone Core control unit on each floor in order to have a certain level of decentralization.
Expose devices feature makes IO modules or virtual devices of one Core discoverable on backbone Modbus network. When looking at device list of the master Core, it looks like as if all these devices where connected or running directly on the master Core.
