This is a project to control Seeley MagIQTouch based HVAC System using an ESP32. It replaces the official IOT/WiFi module for remote access and emulates the responses sent by the original unit. The device will proxy modbus messages inbetween the primary control panel and other devices. A web server is run on the ESP module for access and control. Designed to be used as a basic API for other automation systems to control.
Working with configuration:
- Evaporative Cooler
- Gas Heater
- 2 Zones
- 2 Wall Controllers.
Current Limitations:
- Refrigerated Cooling
- Zones 3 & 4 (Values are likely next in order from existing zone data)
- Untested support of systems that do not have the original IOT Module already configured with their MagiqTouch panel. (Response to module discovery process)
- Zone 1 temp sensor is not always updated, update only occurs when using a Cooler/Heater on temperature mode. Additional zones are reported accurately using their update message to primary control panel. (Temp reporting issue seems to occur in official module too, incorrectly reports temperature on app when using Fan mode).
- Has only been tested with controller version R719
Hardware List:
- FireBeetle ESP32 (DFRobot) - Any ESP32 that has 2x additional UART ports for the RS458 modules should work.
- 2x RS485 Modules (SeeedStudio - 103020193) - Available in AUS at Element14 as "Serial Communication Board, RS485"
- 2x RJ45 Connectors (Regular network jack)
- 2EDGRK Connectors (Optional)
- Ethernet Cable Wire (Solid Core)
- Groove to Female Pin cables (SS110990028 / Seeed Grove - 4 pin Female Jumper to Grove 4 pin Conversion Cable)
Tools:
- Krone Tool
- Wire Strippers
- Screw Driver
Connection list for the RS485 Modules to the ESP Module.
| ESP32 PIN | RS485 Module |
|---|---|
| D0/IO16 | Module 1 - TX |
| LRCK/IO17 | Module 1 - RX |
| IO26/D3 | Module 2 - TX |
| IO27/D4 | Module 2 - RX |
Basic steps of this project:
- Purchase the required hardware.
- Download and Install Arduino IDE (Free).
- Update the WiFiSettings.h file under ArduinoControlLAN-AirconControl with your SSID/Passkey to connect to the WiFi network.
- Under Tools, Board manager install the package for your ESP32 device. FireBeetle works with "esp32 by Espressif Systems" - Version 2.0.17 Tested. v3 has serial issues with the Gen1 Firebeetle.
- Open the ArduinoControlLAN-AirconControl.INO file under ArduinoControlLAN-AirconControl and upload it to your ESP32 with the Arduino IDE.
- Check the serial output for the IP Address which will be printed at startup after WiFi connects, recommend reserving the address on your DHCP server.
- Connect RS485 Modules to the ESP32 as per above pinout list above.
- Disconnect the existing original WiFi IOT Module.
- Connect cables to the ESEP32-RS485 Modules (See connector info below for more detail).
ArduinoControlLAN-AirconMonitor code can also be used as a monitor of the modbus. (Useful for testing new configurations).
Connector Info: The cables from the control panel and control board use a 6P6C male connector. To avoid cutting the original cables, a standard 8P8C / RJ45 female jack can be used to connect to the individual wires.
The connector that goes to the control board only needs A,B and a single ground. The connector to the wall control panel requires both GND and 5V connected as this powers the panel.
I have used a female DC barell cable to re-use the original 5V Power supply from the IOT/WiFi Module. This 5v power is connected to the ESP32, both RS485 modules and one of the RJ45 ports to power the control panel.
The pinout on the rear of an RJ45 jack can vary with A/B positions, the colours need to be matched for the correct wire position.
| RS485 Module | RJ45 Wire (A Wiring) |
|---|---|
| 5V (Control Panel Port Only) | Solid Green and Solid Orange |
| GND | Brown/White and Blue/White. |
| RS485 A | Orange/White |
| RS485 B | Solid Blue |
The devices wired up inside 3d printed housing, STL files for 3d printing available in the Housing-CAD-STL folder. (Image reflects older wiring with 9/10 pins, has been moved to use alternate pins since photo was taken.)
Mounted inside the return air wallspace:
Here's the pin layout for the original Connector too.
The GND and VCC are linked, purpose is likely to reduce cable resistance.
| Pin | Wire Colour | Function |
|---|---|---|
| 1 | Blue | VCC |
| 2 | Yellow | RS485 |
| 3 | Green | RS485 |
| 4 | Red | Ground |
| 5 | Black | VCC |
| 6 | White | Ground |
Tested VCC to Ground Voltage: 5.4V
A GET Request to the module will return status info in JSON format. Example of returned output.
{
"module_name": "ESP32-HVAC-Control",
"system_power": 1,
"system_mode": 2,
"target_temp": 20,
"target_temp_zone2": 11,
"evap_mode": 37,
"evap_fanspeed": 8,
"heater_mode": 0,
"heater_fanspeed": 0,
"heater_therm_temp": 31,
"heater_zone1_enabled": 1,
"heater_zone2_enabled": 1,
"zone1_temp_sensor": 27,
"zone2_temp_sensor": 24,
"panel_command_count": 458
}Sending commands is simple using a POST request in plain/text to the path /command EG: http://192.168.20.112/command The body should have a single command in the format setting=value
List of available commands, where x is the value.
| Command | Available Values | Purpose |
|---|---|---|
| power=x | on/off | System Power On or Off |
| zone1=x | on/off | Enable/Disable Zone 1 for Heater |
| zone2=x | on/off | Enable/Disable Zone 2 for Heater |
| fanspeed=x | 1-10 | Set Fan Speed for Fan, Cooler |
| mode=x | 0-4 | Device Mode 0 = Fan Mode (External) 1 = Fan Mode (Recycle) 2 = Cooler (Manual) 3 = Cooler (Auto) 4 = Heater |
| temp=x | 0-28 | Temperature Target for Cooler, Heater (Zone 1) |
| temp2=x | 0-28 | Temperature Target for Heater Zone 2 |
| serial=x | on/off | Enables output of Modbus messages to Serial Works with ModBusLogger tool on Serial message mode. |
The Modbus Codes.xlsx file contains information about the modbus messages used on the network. Messages are sent in pairs with a request and response message. The document formats these by the Slave ID, Function Code, Request, Response with notes about the information found in these message pairs.
All devices are on the same single network, the primary / zone 1 control panel is the authorative device that sends the requests, all other devices respond. Data that is requested from the control panel is typically sent with function 0x03 (read request) and information sent (write request) is with 0x10.
Known Slave IDs:
| Slave ID | Related Purpose |
|---|---|
| 0x01 | Unknown |
| 0x02 | Evap Unit |
| 0x8C (140) | Unknown |
| 0x8D (141) | Heater Unit |
| 0x97 (151) | Control Panel 2 |
| 0xA5 (165) | Unknown |
| 0xD4 (212) | Zone Controller by elimination – may also be shared heater |
| 0xEB (235) | IOT WiFi Module |
| 0xF4 (244) | Unknown |
| 0xFA (250) | Unknown |
| 0xFE (254) | Unknown |