RS485 Integration ProtocolUpdated 13 days ago

WARNING: Only intended for customer integration companies or professional integrations. Not intended for the end user or Smart Homes Systems such as Alexa, Google, etc... Please consult a professional integration expert before exploring the RS485 Communication Protocol.

RS485 Serial Communication Interface

For Building Automation and Control Systems

Compatible with:

• Building Management Systems (BMS)
• Hospitality Automation Systems
• Smart Home Controllers
• Third-party Automation Platforms

Document Information

Protocol Summary

1. Introduction

This document describes the RS485 communication protocol used to control Aquafire® Pro fireplaces from external automation systems.

The RS485 interface allows integration with a wide range of automation platforms including:

• Building Management Systems (BMS)
• Hospitality Automation Systems
• Residential control systems
• Third-party automation controllers supporting RS485 serial communication

The fireplace operates as a child device and responds to commands sent by a parent controller.

The communication protocol has been designed to be:

• simple
• reliable
• easy to integrate

Typical applications include:

• hotels
• restaurants
• commercial spaces
• residential installations
• automation systems

2. Integration Responsibility and Support Scope

Aquafire fireplaces operate as RS485 child devices.

External automation systems such as Building Management Systems (BMS), smart home platforms, or custom integration controllers operate as parent devices and are responsible for communication management, programming logic, and overall system integration.

Aquafire provides the RS485 communication protocol and device functionality required for integration with external automation systems.

Because automation platforms vary between installations, the configuration, programming, and troubleshooting of third-party automation systems must be handled by the system integrator or the manufacturer of the automation platform.

Aquafire technical support covers:

• device operation
• RS485 protocol documentation
• command structure
• how the fireplace responds to commands

Aquafire does not provide programming or configuration support for third-party automation systems, including:

• BMS configuration
• smart home controller programming
• automation platform configuration
• network or Wi-Fi infrastructure issue
• troubleshooting unrelated to the fireplace hardware

For integration issues, the system integrator should verify that the automation controller configuration and RS485 communication setup follow the protocol described in this document before contacting Aquafire support.

3. Safety and Integration Notice

The RS485 interface is intended for integration by qualified installers or system integrators.

Before connecting the RS485 interface:

• Ensure the fireplace is properly installed
• Follow all applicable electrical regulations
• Use a shielded twisted-pair communication cable

The automation controller must manage communication timing and system supervision.

4. Quick Start for Integrators

To integrate the fireplace into an automation system:

1. Connect RS485 A and RS485 B to the automation controller
2. Configure the device address if required
3. Send commands using the frame format defined in this document
4. Use the status query command to monitor device status

Communication parameters:

Baud Rate: 9600

Data Bits: 8

Stop Bits: 1

Parity: None

5. System Architecture

The fireplace communicates using a parent / child architecture.

The automation controller operates as the parent device.

The fireplace operates as a child device.

Example RS485 network:

Controller

│

│ RS485 BUS

│

────────────────────────

Fireplace #1 (Address 01)

Fireplace #2 (Address 02)

Fireplace #3 (Address 03)

────────────────────────

System behavior:

• The parent sends commands or queries
• The fireplace responds only when addressed
• Invalid addresses are ignored
• Invalid commands are ignored
• If communication is interrupted, the fireplace maintains its current operating state
• A watchdog mechanism is implemented in the device

Maximum devices per RS485 bus:

30 devices

Device address range:

01 – 255

Default device address:

01

6. Physical Layer Specifications

Recommended cable:

• Shielded twisted-pair cable

Typical specification:

• 18 AWG – 20 AWG

Important note:

If communication does not work, verify that RS485 A and RS485 B lines are not

reversed.

7. RS485 Connector

RS485 communication is provided through an aviation connector.

Two connector versions exist depending on the production batch.

Version 1 – Early production units (2-pin connector)

Units shipped in early production batches were equipped with a 2-wire RS485 aviation connector without ground.

Pin Function

Pin 1 RS485 A

Pin 2 RS485 B

Ground is not required for RS485 communication.

Version 2 – Current production units (3-pin connector)

Current production units use a GX12-3 aviation connector.

Pin Function

Pin 1 RS485 A

Pin 2 RS485 B

Pin 3 GND (optional)

The ground connection is optional but may improve communication stability in certain

installations.

8. Communication Frame Structure

All communication frames follow the structure below:

START CODE + ADDRESS + COMMAND + DATA + END CODE

Example frame format:

55 5A AA CC DD FE FF

Field Description

55 5A Start code

AA Device address

CC Command code

DD Command data

FE FF End code

9. Frame Example

Example command frame:

55 5A 01 31 01 FE FF

Byte Value Description

1   55   Start byte 1

2   5A   Start byte 2

3   01   Device address

4   31   Command

5   01   Data

6   FE   End byte 1

7   FF   End byte 2

This frame structure is used for all commands and responses.

10. Command List

11. Status Query

Status request command:

55 5A 01 50 00 FE FF

Device response format:

55 5A 01 50 X1 X2 X3 X4 X5 FE FF

12. Status Byte Definition

Bits 4–7 are reserved for future use and are currently not used.

13. Parameter Levels

Total levels:

5 levels

14. RGB Color Mapping

15. Communication Behavior

Communication rules:

• The controller manages communication timing

• The fireplace responds only when addressed

• Invalid addresses are ignored

• Invalid commands are ignored

• The controller must manage communication timeout

• If several consecutive queries receive no response, the connection should be

considered lost

• The fireplace maintains

16. Troubleshooting

17. Communication Timing

Recommended communication parameters:

• After sending a command, wait 100 ms for a response

• If no response is received, retry up to 3 times

• If repeated queries fail, the connection should be considered lost

Document Version

Document Title: RS485 Integration Manual

Manufacturer: Aquafire®

Product Series: Pro Series

Document Version: 1.0

Release Year: 2026