Heatmiser | HeatmiserNeo | 1.0

Introduction

This driver has been designed to provide control of Heatmiser neoHub and associated Heatmiser neoStat thermostat devices via TCP/IP. Ensure that the neoHub device is connected to the same network as the RTI processor and is accessible through its app interface. Please make sure the device is correctly set up and working independently before integration with this driver.

Driver Features

High-level overview of the driver’s features.

• Communication via TCP/IP

• Thermostat monitoring and adjustment

Version History

Version 1.0 – 03-June-2026

• Initial Release

System Requirements & Pre-requisites

RTI System Requirements

• Integration Designer: Apex ID 10.8

Manufacturer’s Device Requirements

• Heatmiser neoHub G3

• Firmware Version v2218

Driver Configuration

Gateways

• Number of Gateways: The number of neoHub devices for the driver to connect to. This must be at least 1, or the gateways will not configure propertly.

• Polling Interval: The interval between polls of each neoHub device and their associated thermostats.

Gateway Information (one section per gateway)

• IP: The IP address of the neoHub device that the driver is connecting to.

• Port: The port through which the driver connects to the neoHub device.

• Gateway Type: The type of device the driver is connecting to.

• Gateway Name: The friendly name of the gateway used by the installer to differentiate.

Once this information is set, press Discover Devices in order to discover the thermostats associated with all gateways.

Device Friendly Names (displays after Discover Devices pressed)

• Enter the friendly names for each device.

Once these names are set, the driver will generate the appropriate system functions, variables, tags, and Integration Designer sources for each thermostat that you can add from the driver to the source list to assist in auto-programming.

Apex Actions

• Discover Devices: This is the method by which thermostats are discovered. This must be pressed after entering the gateway information in order to add the associated thermostats to Integration Designer and the driver.

Driver Functions

Send Command

Sends a command directly to a neoHub through the TCP/IP connection. Sending a json string to the neoHub can allow for direct commands to the device.

Parameters:

• Json – The string being sent directly to the neoHub.

• Gateway – The neoHub gateway which the driver is sending the command to.

For each thermostat, there are the following functions:

Set Setpoint

Sets the setpoint of a thermostat to a specified value. This should only be done when the thermostat frost mode is set to false. The NeoStat setpoint can be set from 5 to 35 degrees.

Parameters:

• Temperature – The desired temperature for the thermostat.

Increase Setpoint

Increases the setpoint of a thermostat by 1 degree. This should only be done when the thermostat frost mode is set to false.

Decrease Setpoint

Decreases the setpoint of a thermostat by 1 degree. This should only be done when the thermostat frost mode is set to false.

Set Frost

Set the frost mode of a thermostat. When set to On, the thermostat will maintain their frost protection temperature.

Parameters:

• State – On or Off. The state which the thermostat frost mode will be set to.

Driver Variables

Connection Status
String indicating whether the driver is currently connected (True = connected).

For each thermostat, there are the following variables:

Connected
Boolean; True when connected to the neoHub.

Temperature
Integer; The current temperature measured by the thermostat.

Mode
String; Either Heating or Off, depending on the standby status of the thermostat.

UF Temperature
Integer; The current floor temperature measured by the thermostat.

Setpoint

Integer; The current target setpoint temperature of the thermostat.

Demand
Boolean; The current demand status of the thermostat, True when thermostat is heating.

Has Floor Sensor
Boolean; True when floor sensor is configured, if floor temperature is 127.5 or higher then set to False as this represents the floor sensor not being configured for neoStat thermostats.

Frost On
Boolean; True when frost mode is set to on.

Friendly Name

String; friendly name of the thermostat, as set in the system configuration.

Tags

Stat Setpoint (F/V)

• Function usage: Sets Setpoint of a thermostat.

• Variable usage: Current setpoint of a thermostat.

Stat On (F)

• Function usage: Enables frost mode for a thermostat.

Stat Connected (V)

• Variable usage: Current connection status of a thermostat.

Stat Temp Floor (V)

• Variable usage: Current floor temperature measured by a thermostat.

Stat Demand (V)

• Variable usage: The heating demand of a thermostat.

Stat Floor Sensor (V)

• Variable usage: A Boolean value representing whether a thermostat has a configured floor sensor.

Stat Friendly Name (V)

• Variable usage: The friendly name of a thermostat, as entered in the System Configuration.

Stat Frost On (V)

• Variable usage: A Boolean value representing whether a thermostat is currently in Frost mode.

Troubleshooting

If the driver cannot control a Heatmiser neoHub system, confirm the following:

• The correct IP address and Port are defined in the RTI driver properties for each neoHub gateway.

• The neoHub is configured and working, which can be confirmed by connecting to the Heatmiser Neo app and connecting to the correct location.

If a thermostat is not responding to commands:

• Make sure that the thermostat is set to thermostat mode rather than timeclock mode.

System Testing

Integration Designer: Version 11.15

XP Processor Model: XP-3

XP Processor Firmware: 25.9.24

Device Models: Heatmiser neoHub G3, Heatmiser neoStat v1

Device Firmware: v2218, v108

Support Contact

If you encounter any issues with the driver, please contact us at https://support.janustechnology.co.uk, and we will be happy to assist however needed.

Disclaimer of liability

The company shall not be liable for any issues, damages, or costs that may arise from the use of our driver software. While we strive to ensure that all versions of our driver are backward compatible, we cannot guarantee that this will always be the case. Users are advised to thoroughly test the driver in their specific environments and configurations before deployment to ensure compatibility and proper functionality. The company makes every effort to provide a reliable and functional product, but the driver is provided “as is” without warranties of any kind, either express or implied. The user assumes full responsibility for any loss, damage, or disruption caused using our driver, including, but not limited to, hardware malfunctions, data loss, or system failures. By using our driver, you acknowledge that you have read and understood this disclaimer, and you agree to release and hold harmless the company from all liabilities associated with its use.