BLAUBERG VENTO Smart Home Integration Guide

Purpose

This manual is intended for connecting VENTO series installations to a "Smart Home" system. Control is achieved via Wi-Fi, connecting to Master devices, Slave devices, mobile phones, and the "Smart Home" system. Slave devices are controlled by commands from Master devices.

Connection Schemes

Two wireless connection schemes are available:

Scheme 1: Master Device with its Own Wi-Fi Access Point

A Master device creates its own Wi-Fi access point, allowing up to eight Slave devices to connect. Note: If eight Slave devices are connected, a mobile phone or "Smart Home" system may not be able to connect to the Master's access point.

Diagram Description: A central "Master (leading) device with Wi-Fi access point" is shown wirelessly connected to three "Slave" devices (Slave N°1, Slave N°2, Slave N°N) and a "Mobile device".

Scheme 2: Connection via Router Wi-Fi Access Point

Master devices, Slave devices, mobile phones, and "Smart Home" systems connect to a router's Wi-Fi access point. The maximum number of connected devices depends on the router's capabilities. If the router cannot support the required number of ventilators, an additional Wi-Fi access point can be used. Multiple Master devices can be connected to the router's network for zonal control.

Diagram Description: A "Router with Wi-Fi access point" is shown wirelessly connected to a "Master (leading)" device, which in turn is connected to "Slave" devices and "Mobile devices". Another diagram illustrates an "Additional Wi-Fi access point" connected to more "Slave" devices and "Mobile devices".

Connection setup is performed using the mobile application in the "Connection -> Wi-Fi Setup" menu (refer to the product passport).

Network Parameters

Data exchange occurs via the UDP transport protocol (broadcasting is supported).

• Master Device IP Address:
  • 192.168.4.1 when the Master device operates without a router (Scheme 1).
  • Configurable via the mobile application (Scheme 2), allowing static or DHCP assignment.
• Master Device Port: 4000.
• Maximum Packet Size: 256 bytes.

Data Packet Structure

Data packets follow a specific structure:

[0xFD][0xFD] [TYPE] [SIZE ID] [ID] [SIZE PWD] [PWD] [FUNC] [DATA] [Chksum L] [Chksum H]

• 0xFD 0xFD: Packet start marker (2 bytes).
• TYPE: Protocol type (1 byte). Value = 0x02.
• SIZE ID: Size of the ID block (1 byte). Value = 0x10.
• ID: Controller ID number (16 characters). This number is located on the device's label. The code word "DEFAULT_DEVICEID" can be used for management or device discovery.
• SIZE PWD: Size of the PWD block (1 byte). Possible values: 0x00 to 0x08.
• PWD: Device password (characters "0-9", "a-z", "A-Z"). Default password is "1111".
• FUNC: Function number (1 byte). Defines the action and DATA block structure:
  • 0x01: Read parameters.
  • 0x02: Write parameters (no response on status).
  • 0x03: Write parameters with response.
  • 0x04: Increment parameters with response.
  • 0x05: Decrement parameters with response.
  • 0x06: Controller response to requests (FUNC = 0x01, 0x03, 0x04, 0x05).
• DATA: Data block, containing parameter numbers and values.
  • For FUNC = 0x01, 0x04, 0x05: [P1] [P2] ... [Pn]
  • For FUNC = 0x02, 0x03, 0x06: [P1] [Value 1] [P2] [Value 2] ... [Pn] [Value n]
• P: Parameter number (lower byte). Special commands use values from 0xFC to 0xFF:
  • 0xFC: Change function (FUNC).
  • 0xFD: Unsupported parameter.
  • 0xFE: Change parameter value size.
  • 0xFF: Change high byte of parameter numbers within a packet.
• Value: Parameter value (default 1 byte).
• Chksum L, Chksum H: Checksum (2 bytes). Calculated as the sum of bytes from TYPE to the end of the DATA block.

Command Examples

The document provides examples of data packets for various operations:

• Write Request (FUNC = 0x03): Demonstrates writing multiple parameters, including using the 0xFE command to specify a 4-byte value for parameter 0x0070.
• Controller Response (FUNC = 0x06): Shows the controller's confirmation response to a write request, confirming the values written.
• Read Request (FUNC = 0x01): Illustrates requesting specific parameters, using the 0xFF command to set the high byte for parameter numbers.
• Controller Response (FUNC = 0x06): Displays the controller's response to a read request, including values for supported parameters and indicating unsupported parameters with 0xFD.

Full packet examples for "Smart Home -> Controller" (read request) and "Controller -> Smart Home" (response) are also provided, detailing the complete byte sequences and checksums.

Parameter Table

The following table details the available parameters for controlling the VENTO system:

* Available for all models except VENTO Expert A30 W V.2

** Available for VENTO Expert A50-1 W V.3

Code Examples

The document includes C code examples demonstrating how to process data packets for communication with the BLAUBERG VENTO system. These examples cover:

• Defining constants for special commands (e.g., BGCP_CMD_PAGE, BGCP_CMD_FUNC).
• Implementing a checksum verification function (check_protocol) to ensure data integrity.
• Parsing received data, including checking the protocol type, device ID, and processing function and data blocks.
• Handling special commands like changing the function, parameter size, or indicating unsupported parameters.
• Processing supported parameters and updating device states (e.g., State_Power, State_Speed_mode).

These code snippets are useful for developers integrating the VENTO system into custom applications or firmware.