Chapter 1: Introduction
Building automation systems have traditionally required extensive programming knowledge and specialized technical expertise; HSYCO changes that equation by providing a unified platform that integrates diverse systems while remaining accessible to users without programming backgrounds. This chapter introduces you to what HSYCO is, how it works, and what you can accomplish with it.
Chapter 2: Installation and Setup
HSYCO is delivered as a preconfigured HSYCO Server, designed to be powered on and accessed through a web browser.
Chapter 3: The Manager Interface
In Chapter 2, you completed HSYCO's initial setup understand what each tool actually does, configure the system parameters your installation needs, and prepare for connecting devices and building automation.
Chapter 4: I/O Servers and Device Integration
In the previous chapters, you learned about HSYCO's architecture, installed the software, and explored the Manager tools. Now it's time to connect HSYCO to actual building automation systems.
Chapter 5: Project Editor
Every HSYCO installation needs a face; a way for people to control lights, check temperatures, open blinds, or see what's happening in a building. That face is called a project: a custom user interface that runs in a web browser, accessible from any phone, tablet, or desktop computer.
Chapter 6: Introduction to EVENTS Programming
In Chapter 4, you connected HSYCO to its first I/O Servers and worked with real datapoints. You could read device states in Status Browser and send commands manually. Now it's time to make HSYCO respond on its own, to watch what's happening in your building and act without anyone pressing a button.
Chapter 7: User Interface Integration
In the previous chapter you learned how EVENTS automation rules respond to device states, schedules, and timers. Those rules can sense a motion detector, react at sunset, or fire after a delay, but all of that happens invisibly in the background. This chapter adds the missing piece: the connection between your automation and the people who use it.
Chapter 8: Data Loggers
The data logger in HSYCO is the tool used to store historical data for any value managed by the system, whether it comes from a datapoint acquired from an external device or from an internal variable generated by automation logic or calculations. This allows building managers and integrators to look back in time, spot consumption patterns, compare periods, and make informed decisions based on real historical data rather than guesswork.
Chapter 9: The Scheduler
The Scheduler is a visual, calendar-based tool built directly into the HSYCO user interface. Think of it as a smart calendar for your building: you define time rules, when something should be ON and when it should be OFF, and HSYCO automatically fires the corresponding events at exactly the right moment.
Chapter 10: Protocols Integration
10.1 KNX Integration
Chapter 11: System and Strato I/O Servers
Most I/O Servers in HSYCO connect outward, to KNX buses, Modbus devices, BACnet controllers, cameras, and other building systems. This chapter covers two I/O Servers that connect inward, to the server hardware itself.
Chapter 12: Catalog
Every I/O Server you configure in HSYCO exposes a set of datapoints, the individual values and states that HSYCO reads from and writes to your devices. A dimmer's current level, a shutter's position, a switch's on/off state: these are all datapoints.
Chapter 13: Cameras
Video is one of the most common reasons to deploy HSYCO, and cameras run on the same platform as everything else: a motion event can start a recording, a recording can be embedded in a page, and a rule can e-mail a frame.
Chapter 14: The Wiring Editor
The Wiring Editor is HSYCO's no-code automation tool. Where EVENTS (Chapter 6) asks you to write rules as text, the Wiring Editor lets you connect an input to an output visually, with no code at all. It covers the automations that come up most often in a home or small building: make a button toggle a light, dim a lamp from one button, drive a blind from a pair of buttons, or run a scenario on a schedule.