Search
MENU
- • Editing multiple devices
- • Basic Blinds Setup
- • Blinds configuration wizard
- • Light switching
- • Lighting timer basics
- • Heating and Cooling modes
- • Power limiting
- • Notification on high temperature
- • Configuring hysteresis control via Equation smart rule
- • Equithermic regulation
- • PID Temperature regulation
- • PID Cascade
- • Regulation of Boiler Cascade
- • Using statistic values in smart rules
- • Integrate multiple Core control units
- • Safe Values
- • How to combine two daily schedules in one day
- • Simple thermostat with hysteresis
- • Simple Heating management using Weekly schedule and Presence switch
- • Dimmer limits
- • Grouping or linking devices together
- • Access control
- • Static IP address configuration
- • 2019.1 - release planned for Q3 2019
- • 2018.1
- • 2017.1 - Charts updated
- • 2017.1 - Blinds automation - Depth of sun rays
- • 2017.1 - Blinds automation - angle control update
- • 2017.1 - Replace module action
- • 2017.1 - Expose devices
- • 2017.1 – Daily schedule smart rule
- • 2017.1 - Permissions
- • 2017.1 - Double click and triple click
- • 2017.1 - Set to Automatic mode - "Push buttons event" smart rule
- • 2017.1 - Multi-value switch
- • 2017.1 - Core update from the app
- • Firmware changelog
2017.1 - Expose devices
In large projects with multiple Cores it is required to network them together and have one Core 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 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.
