browse

| Overview

MyStat Pro Pack Site Preconfiguration simplifies deploying and commissioning MyStat devices by letting you prepare device addresses and site configurations before the hardware reaches the installation location.

The feature extends the existing VVT-C Pro Pack Site Preconfiguration workflow to support CCU-connected MyStat devices.

This workflow lets you assign communication addresses to MyStat devices during warehouse preparation. Installers can then configure the site, define floors and zones, associate the prepared MyStat devices with their respective zones, and generate a commissioning passcode through the Facilities App.

Once the hardware is installed, the installer can retrieve the preconfigured site on the Central Control Unit (CCU) using the generated passcode. The CCU retrieves the prepared configuration and completes the commissioning process.

This approach reduces on-site configuration effort, minimizes manual device-address assignment, and ensures that the intended device-to-zone associations are maintained during commissioning.

| Feature Objectives

The MyStat Pro Pack Site Preconfiguration feature is designed to:

  • Reduce installation time by preparing device addresses and site configurations before shipment.
  • Provide a standardized MyStat configuration with two heating stages, two cooling stages, and one fan stage.
  • Reuse the existing VVT-C Facilities App sign-up, authentication, configuration, and passcode-generation workflow.
  • Simplify CCU commissioning by retrieving an already prepared site configuration.
  • Maintain the intended association between individual MyStat devices and their assigned zones.
  • Preserve the prepared configuration during the transition from preconfiguration to operational site commissioning.

| Feature Scope

The feature consists of four primary functional stages.

Warehouse Device Preparation

Each MyStat device is prepared before shipment.

The preparation process includes:

  • Programming the approved communication address.
  • Configuring the required heating, cooling, and fan relay stages.
  • Verifying the programmed device address and relay configuration.
  • Checking the device firmware against the minimum supported version.
  • Applying zone and device-address identification labels.
  • Recording the device details in the warehouse packing record.

Site Preconfiguration Through the Facilities App

The installer or authorized user uses the Facilities App to prepare the site configuration.

The configuration includes:

  • Site identification and contact information.
  • Floor and zone definitions.
  • MyStat device identification.
  • Device communication addresses.
  • Applicable device profile settings.

The configuration can be entered directly in the application or submitted using an image of the completed preconfiguration form through the existing supported workflow.

After reviewing and submitting the configuration, the application generates a commissioning passcode.

CCU Commissioning

Once the MyStat devices and CCU are installed, the installer retrieves the prepared site configuration using the commissioning passcode.

The CCU retrieves the site information, validates the supported firmware requirements, and proceeds with commissioning.

Operational Site Persistence

After successful commissioning, the prepared configuration becomes the operational site configuration.

The device-to-zone associations are retained, allowing the site to be managed through the existing configuration and reconfiguration capabilities.

| MyStat Pro Pack Hardware Configuration

Supported MyStat Device

The feature is designed for the following MyStat hardware:

MyStat Part Number: 7X-TS-C2K-X

Each device follows the approved Pro Pack relay configuration.

Standard Relay Configuration

The MyStat Pro Pack uses the following functional relay allocation:

Relay FunctionConfiguration
Heating Stage 1Enabled
Heating Stage 2Enabled
Cooling Stage 1Enabled
Cooling Stage 2Enabled
Fan Stage 1Enabled

This provides a standardized configuration with two-stage heating, two-stage cooling, and a single-stage fan.

The actual relay and terminal mapping must follow the approved MyStat hardware configuration.

Proposed Package Composition

The proposed packaging structure follows the existing three-zone base pack and one-zone expansion model.

ComponentThree-Zone Base PackOne-Zone Expansion
MyStat 7X-TS-C2K-X31
Compatible CCU1 (SKU pending approval)Existing site CCU
Site Preconfiguration Form1Address and zone record
Zone and Address LabelsOne per MyStatOne per MyStat
Wiring and Mounting AccessoriesAs per approved BOMAs per approved BOM

Final kit SKUs, CCU selection, accessory quantities, and service inclusions are subject to product approval.

| Device Addressing and Identification

Device Communication Address

Each MyStat device must have a unique, approved communication address programmed before shipment.

The address is used by the CCU to identify and communicate with the corresponding MyStat device within the site network.

The proposed default address allocation is:

DeviceProposed AddressZone Identification
MyStat 11000Zone 1
MyStat 21001Zone 2
MyStat 31002Zone 3
Expansion MyStatNext approved unused addressAssigned expansion zone

Important: The addresses listed above represent the proposed allocation and require final approval against MyStat firmware and address-allocation requirements.

Device Identification Labels

Each MyStat device must have a label containing:

  • Assigned zone number.
  • Exact programmed device communication address.

The warehouse packing record must additionally capture:

  • Device identifier.
  • Programmed communication address.
  • Firmware version.
  • Assigned kit.

The device identifier and communication address are separate identification details.

The preset communication address must not be confused with the MyStat BLE MAC address.

Address Verification

Before shipment, the warehouse preparation process must verify that:

  1. The programmed device address matches the intended address.
  2. The relay configuration matches the approved Pro Pack baseline.
  3. The physical device label displays the correct zone and address.
  4. The packing record contains matching device and address information.

Any mismatch must be resolved before the device is released for shipment.

| Site Preconfiguration Workflow

The site preconfiguration process reuses the existing VVT-C Facilities App workflow.

Access the Facilities App

Sign in to the Facilities App using the existing supported sign-up and authentication process.

  • Initiate adding a preconfiguration site process.
  • Select the Mystat Pro Pack type of preconfigured site.
  • Initiate the conversation with the AI chat bot to asssit further.
  • Select Configuration Method from the list provided.

Users can check with the AI assistant for all help features that it could provide as below.

The AI assistant provides the list of items it could help the users with

Users can either:

Configure Manually

  • Enter the required site information directly into the online form.

  • Enter Site Information

    Provide the required site details, including

    • Site name.
    • Organization.
    • Site address.
    • Region.
    • Facility contact information.
    • Installer details.

Configure Floors and Zones

Define the floors and zones associated with the site.

For each zone, provide the relevant zone name, floor information, and MyStat device association.

Associate MyStat Devices

Assign each prepared MyStat device to its intended zone.

Enter the exact communication address programmed into the device during warehouse preparation.

The device identifier and communication address should correspond to the physical device and its identification label.

Review and Submit Configuration

Review the site configuration, including:

  • Floor and zone information.
  • MyStat device assignments.
  • Device communication addresses.
  • Applicable profile settings.

Submit the configuration through the Facilities App.

Generate Commissioning Passcode

After submission, the application generates a site commissioning passcode.

This passcode is used by the CCU to retrieve the prepared site configuration during installation.

Users can refresh the code to generate a new code if required.

Users can use the 3-dot menu to access site modification options.

Upload a Prefilled Form

  • Download or use the prefilled site configuration form.

  • Manually enter the required site information in the form.

  • Upload the completed form for site configuration.

| CCU Commissioning Workflow

Once the hardware installation is complete, the prepared site can be commissioned through the CCU.

Install Hardware

Install the MyStat devices and compatible CCU according to the approved installation requirements.

Ensure that the installed devices correspond to the devices recorded in the site preconfiguration.

Navigate to Site Creation

On the CCU, select:

Create Site from Preconfigured Details

This option initiates the retrieval of the previously prepared site configuration.

Enter Commissioning Passcode

Enter the passcode generated through the Facilities App.

The CCU uses this passcode to retrieve the associated preconfigured site.

Review Retrieved Site

Confirm that the retrieved site corresponds to the intended installation.

Verify the site information and prepared device-to-zone associations before proceeding.

Verify Firmware Compatibility

The participating devices must meet the minimum supported firmware requirements.

Devices running older, unsupported firmware must be updated before the commissioning process can proceed.

Complete Commissioning

Proceed with commissioning and verify communication with each addressed MyStat device.

The CCU must identify the prepared devices and associate them with their intended zones.

Persist Operational Configuration

After successful commissioning, the prepared configuration becomes the operational site configuration.

The site can subsequently be maintained using the existing site configuration and reconfiguration capabilities.

| Supported Use Cases and Expected System Behaviour

New Three-Zone Deployment

For a new deployment, the warehouse prepares three MyStat devices with their respective addresses and relay configurations.

The installer creates the site through the Facilities App, assigns the three devices to their intended zones, and generates the commissioning passcode.

The installer then retrieves the configuration on the CCU and completes commissioning.

Expected Behaviour: After successful commissioning, all three MyStat devices are associated with their intended zones.

One-Zone Expansion

When an additional zone is required at an existing site, an expansion MyStat device can be introduced.

The device must receive an approved unused communication address and be assigned to the intended expansion zone.

The existing operational site must be updated through the supported existing-site process.

Expected Behaviour: The additional MyStat device is incorporated into the existing site without recreating the operational site.

Changes Before Commissioning

If the site configuration needs to be modified before commissioning, the existing preconfiguration edit workflow can be used.

The installer can update the prepared configuration before retrieving it on the CCU.

Expected Behaviour: The CCU retrieves the updated preconfiguration rather than relying on the previous configuration.

Multiple Kits at the Same Location

When multiple MyStat kits are deployed at the same location, device addresses must be checked for uniqueness within each CCU mesh/network.

Expected Behaviour: Address conflicts are identified and resolved before commissioning.

Hardware and Form Mismatch

A mismatch may occur when the physical MyStat device address differs from the address recorded in the preconfiguration form.

Expected Behaviour: The mismatch must be identified and corrected either by updating the record or correcting the device configuration before commissioning is completed.

Older Firmware

Devices that do not meet the minimum supported firmware requirement cannot proceed through the feature workflow.

Expected Behaviour: The required firmware update must be completed before commissioning can continue.

Post-Commissioning Configuration Changes

Once the site is commissioned, subsequent configuration changes must use the existing site configuration and reconfiguration capabilities.

Expected Behaviour: The operational site configuration remains the source for ongoing site management.

Device Replacement

When a MyStat device needs replacement, the approved replacement process must be followed.

The replacement must retain the intended zone association and must not introduce duplicate active communication addresses.

Expected Behaviour: The replacement device is correctly associated with the intended zone without creating an address conflict.

| Preconfiguration Form – Required Information

The preconfiguration form captures the information required to prepare and commission the site.

SectionRequired Information
SiteSite name, organization, address, region, installer and facility contact details
KitMyStat package identification and packing record reference
ZoneFloor, zone name, MyStat device identifier, exact preset address and applicable profile settings
Relay BaselineHeating Stage 1, Heating Stage 2, Cooling Stage 1, Cooling Stage 2 and Fan Stage 1
CommissioningGenerated site passcode and resulting commissioning status

The information recorded in the form must correspond to the physical hardware and warehouse packing records.

| Configuration Lifecycle and Persistence

The feature follows a two-stage configuration lifecycle.

Before Commissioning:

  • The Facilities App creates and maintains site configuration.
  • MyStat devices are associated with their intended floors and zones.
  • Device communication addresses are recorded.
  • The configuration remains stored as a preconfigured site.
  • Changes can be made through the existing edit workflow.

After Commissioning:

  • The CCU retrieves the prepared site using the commissioning passcode.
  • Device communication is verified.
  • The prepared configuration becomes the operational site.
  • Device-to-zone associations are retained.
  • Subsequent changes use existing site configuration and reconfiguration capabilities.

| Important Considerations

  • This feature is intended for CCU-connected MyStat deployments.
  • The existing VVT-C CCU commissioning experience is reused.
  • Each MyStat device must have an approved and verified communication address.
  • Device identifiers must be recorded separately from communication addresses.
  • BLE MAC addresses must not be used as substitutes for the preset communication addresses.
  • Device firmware must meet the minimum supported version.
  • Address conflicts must be resolved before commissioning.
  • Device labels, preconfiguration forms, and warehouse packing records must contain consistent information.
  • The MyStat address plan, kit SKUs, hardware quantities, warehouse programming method, and expansion/replacement behaviour require final approval.
Previous
Next

Comments

0 comments

Please sign in to leave a comment.

Was this article helpful?

0 out of 0 found this helpful
Powered by Zendesk