FIN 5.2.0
Overview
[Release date: November 5, 2025 - v5.2.0.1920]
The FIN 5.2.0 release is considered an 'extension pack' release which typically contain enhancements and functional improvements.
Notable Fixes & Enhancements
Migration
Upon startup, an automatic migration is performed for schedule, weather, and alarm records. While the system attempts to map all schedule events, we cannot guarantee 100% accuracy. Please review your schedules carefully to ensure everything is configured correctly. If any discrepancies are found, you may need to manually edit the affected records.
Additionally, some updates require manual action, including:
Updating to the latest MQTT connector configurations
Updating alarm topicOn filters
Reviewing and adjusting schedule and alarm references
After upgrading, it is strongly recommended not to revert to a previous version, as the updated records may cause compatibility issues with older versions.
Link: See Migrations for additional details.
New apps
We're excited to unveil a set of newly developed apps in this release, designed to enhance functionality, improve user experience, and streamline workflows across your system.
Known Limitations & Important Notices
Alarms
Plaintext alarms must be reconfigured to match the new setup.
FIN Network
Support for Alarm sync is temporarily unavailable.
All linked instances must share the same software version, as updates to key record types—Alarms and Schedules—can cause compatibility issues if versions differ.
NHaystack
Support for Alarm sync and Schedule sync is temporarily unavailable.
Schedules
BACnet Calendar objects are not supported by the FIN schedule user interface.
Existing relative schedule hyperlinks will open to the full app without context.
Various references
Update any saved Favorites, user HomePath, Top Level Graphic, Custom Header, custom apps or models, or custom graphic programs referencing the new apps to reflect the latest versions.
Alarms
The Alarms app has been completely rebuilt from the ground up, featuring a modern interface, enhanced functionality, and a powerful new alarm engine. It provides a centralized, streamlined experience for monitoring, acknowledging, and managing system alerts—making it easier to stay on top of critical events and respond quickly across your building automation environment.
This update introduces a new rules engine, alarm router, and notification extension. The notification extension is flexible and can be used not only for alarms but also extended to other record types within the database. Additionally, alarm history is now stored in a time-series database, offering improved performance and readability for historical data.
All functions have been newly introduced or updated. Please review and revise any existing logic that references these functions to ensure compatibility with the latest implementations and parameters.
Note: The periods tag has been removed from alarm records. Previously used to track historical alarm data, this functionality is now replaced by the readAlarmHistory() function, which should be used to access historical transitions of alarms.
Link: See Alarms, Rule Engine, Alarm Router, and Notifications docs for additional details.
Schedules
The Schedules app has been completely redesigned with a sleek, modern interface and improved usability, including new calendar views for enhanced scheduling clarity. It provides a powerful and intuitive platform for automating the timing and control of building systems. Users can easily create and manage schedules based on data types, time zones, and recurring events, and link them to calendars for handling special occasions. This seamless integration simplifies the coordination of both routine operations and exceptional activities across your building infrastructure.
Link: See the Schedules for additional details.
Historian 2.0 Builder and Viewer
The newly designed Historian 2.0 Builder and Viewer apps make it easier than ever to create charts and visualize historical data. With an intuitive interface and enhanced functionality, users can quickly build, customize, and explore trends across their building systems for better insights and decision-making.
Unlike the other two redesigned apps, Historian 2.0 will run in parallel with the original Historian app for a transitional period. Eventually, the legacy Historian app will be phased out.
Links: See the Historian 2.0 Builder and Historian 2.0 Viewer for additional details.
New FIN build documentation
We've enhanced the built-in documentation in this build to improve accessibility and usability. The updated documentation offers clearer explanations and better organization. The improved structure makes it easier to find the information you need and understand how to get the most out of the platform.
New MQTT connector
This build introduces a new open-source MQTT connector that enables seamless integration with MQTT brokers. Users can establish connections using mqttConn records, publish messages, and subscribe to topics via Tasks. While this core connector does not enforce a standard point model due to the flexible nature of MQTT payloads, it introduces the mqttPoint object, allowing users to define custom points and handle updates or history logging based on incoming messages. Future enhancements will focus on developing a point-based model informed by community feedback and real-world use cases.
Link: See the MQTT Connector for additional details.
New Trend connector
This build introduces a powerful new Trend Connector, enabling seamless integration between the FIN Framework and Trend Building Management Systems (BMS).
Trend systems are widely adopted for optimizing energy efficiency and maintaining comfortable building environments through precise monitoring and control of HVAC and other building services. With this new connector, users can now:
Easily access and interact with Trend BMS data directly within the FIN Framework.
Simplify integration workflows, eliminating the need for complex architecture or configuration.
Unify diverse device types into a cohesive system for streamlined building management.
Enhance energy optimization and building performance through improved visibility and control.
This integration empowers users to monitor and manage HVAC and building services data more efficiently, supporting smarter, more sustainable operations.
Link: See the Trend Connector for additional details.
New Life Safety objects and service
We now support BACnet Life Safety Point and Life Safety Zone objects, along with the associated service, to enable more accurate monitoring and control of fire and safety devices within building systems.
Life Safety Point
Object_Name
Present_Value
Tracking_Value
Status_Flags
Mode
Silenced
Operation_Expected
Maintenance_Required
Direct_Reading
Units
Life Safety Zone
Object_Name
Present_Value
Tracking_Value
Status_Flags
Mode
Silenced
Operation_Expected
Maintenance_Required
Link: See the BACnet Connector Details doc for additional details.
BACnet protocol revision 1.23
We have updated to BACnet protocol revision 1.23. This release introduces support for the BACnet Staging object type and WriteGroup service, enhancing control and coordination across devices. The Staging object enables mapping of numeric values to multiple binary stages, allowing fine-grained control of outputs like lighting or HVAC. Meanwhile, the WriteGroup service facilitates efficient, unconfirmed distribution of values to large groups of devices, streamlining updates to Channel objects within defined control groups.
Link: See the BACnet Connector Details doc for additional details.
Supporting SkyFoundry database v3.1.5
We now support SkyFoundry database v3.1.5.
All Fixes & Enhancements
| Alarms: The Alarms app has been completely rebuilt from the ground up, featuring a modern interface, enhanced functionality, and a powerful new alarm engine. |
| Alarms: Alarm notifications now support "return to normal" events. When an alarmed condition clears, a notification is sent to indicate that the point has returned to its normal state—providing better visibility and closure for alarm events. |
| Alarms: Resolved an issue in the legacy alarm engine where alarms were incorrectly sent at midnight. With the new alarm engine, this behavior no longer occurs, ensuring more accurate and timely alarm notifications. |
| Alarms: Resolved an issue in the legacy alarm engine where acknowledgement information was not retained past midnight, causing it to be lost the following day. This issue has been addressed in the new alarm engine, which now preserves acknowledgement data reliably across days. |
| Alarms: The new Alarms app now includes an enhanced table view that allows users to accurately view the history of alarm records. |
| Alarms: Resolved an issue in the legacy alarm engine that caused alarms to reactivate at midnight, making it difficult to determine the original trigger time. This has been resolved in the new alarm engine, which now reliably preserves alarm trigger time, ensuring accurate historical tracking. |
| App Launcher: The App Launcher now automatically closes when clicking outside its window, improving user experience and interface responsiveness. |
| BACnet: We have updated to BACnet protocol revision 1.23. |
| BACnet: We’ve expanded our BACnet integration to include proprietary Siemens objects that utilize non-standard BACnet data types for their present value. These objects are now fully supported in alarm processing, ensuring that alarms are triggered and handled as expected. |
| BACnet: We now support Life Safety Point and Zone objects and Service to ensure more accurate monitoring and control of fire and safety devices. |
| BACnet: Introduced a new function, bacnetSyncObjectProperty(), to synchronize the unit property from a BACnet device point to its corresponding FIN point. This ensures consistent and accurate unit metadata across both systems. |
| BACnet: Alarms for AV, AO, and AI points can now be acknowledged without issues. |
BACnet: Supported OS and architecture: | |
| BACnet Server: Resolved an issue in the BACnet Server where connector threads could become stuck, potentially impacting performance and communication. The threading mechanism has been optimized to prevent this behavior, ensuring more stable and reliable operation. |
| Batch Record Editor: Resolved an issue where his related tags were not removed when a point with history enabled was overwritten by a point library with history disabled. The Batch Record Editor now correctly removes his tags during such overwrites, ensuring accurate point configuration. |
| Binding: Improved binding behavior by excluding his related and connector type tags from bindings. This prevents binding issues and ensures more reliable point associations. |
| Connector Extension: Resolved a timing issue where, under high connector load, queued houseKeeping messages could trigger outdated write operations due to delayed updates of writeLastArg. The connector now handles message sequencing more reliably, preventing unintended overwrites and ensuring accurate point state updates. |
| Dashboard app: Previously the dashboard chart tree navigation required manual clicking through each level instead of dynamically responding to cursor movements. Now when the cursor overlays a level, it automatically expands. |
| DB Builder: Corrected the issue where the point search and filter function was not working for some columns after switching to a new equip context. |
| DB Builder: The filter icon now turns blue when a filter is applied, providing a clear visual indication that filtering is active. |
| DB Builder: The Sites/Floors/Equips/Points summary view has been improved: |
| FIN Docs: We've significantly enhanced the built-in documentation in this build to improve accessibility and usability. |
| Folders: You can now expand tree nodes that contain folders with Chinese characters in DB Builder > Connectors tree. |
Framework: We now support SkyFoundry database v3.1.5. | |
| Historian: The newly designed Historian 2.0 Builder and Viewer apps make it easier than ever to create charts and visualize historical data. |
| Historian: The Historian 2.0 Chart now supports displaying data in a 24-hour format. |
| Historian: Fixed an issue in the legacy Historian app where attempting to download a chart as a PDF would result in an error. Users can now successfully export charts in PDF format without issue. |
| Historian: The new Historian app now displays all available historical data by default, improving visibility and ease of access. This is a change from the legacy Historian app, which required additional clicks to view complete historical data. |
| Historian Viewer: Resolved an issue where setting the Week Start Day (WSD) to Monday caused the history view for "last week" to incorrectly include dates from the current week, and display Sunday as an empty entry. The issue no longer occurs when WSD is set to Monday—history data now aligns correctly with the selected week range. |
| Host ID: We've enhanced the Host ID generation process on Windows machines to prevent issues such as null Host IDs and unexpected changes due to hardware modifications. |
| KNX: The KNX Connector now supports opening and unlocking password-protected KNX project files. |
| KNX: All characters are now supported in passwords for KNX projects. |
| KNX: We’ve added support for additional KNX units related to the "Element" type—for example, Element 16. This enhancement improves compatibility and flexibility when working with a wider range of KNX devices. |
| KNX: The default individual address for the KNX connector is now configurable via Folio. Use knxUpdateIndividualAddress(conn, addr) to set a custom address, enabling more flexible integration and improved network communication. |
| Language Translation Update: Chinese |
| Logic Builder: When editing a tag variable of type "Date Time" using the right menu edit button, an error message ("DefVal type does not match selection") was displayed if no changes were made to the default value. This prevented saving the variable configuration. This issue has been resolved. Users can now click "Next" and save changes without needing to modify the default value. |
Logic Builder: Resolved an issue where default values were ignored when fewer arguments were passed to a block, causing the LB program to fail. Default values are now properly recognized, preventing errors and ensuring stable block execution. | |
| Schedules: The Schedules app has been completely redesigned with a sleek, modern interface and improved usability, including new calendar views for enhanced scheduling clarity. |
| Schedules: The Schedules app now supports locale settings, enabling proper display of 24-hour format. This enhancement improves usability and aligns the interface with regional standards. |
| Schedules: Long schedule names now display more cleanly in the UI. Instead of overflowing, names are truncated with an ellipsis (...) and a tooltip is provided to show the full name on hover. |
| Schedules: The new Schedules app now includes a Calendar feature. It's a configurable collection of dates that defines when specific operations or events are eligible to occur. This feature focuses solely on date-based scheduling and does not include time-of-day details. Only the selected days are considered active or valid. |
| Settings: Resolved an issue where the Purge Settings were not visible when FinDBBuilderFormsExt was disabled. The visibility of purge settings is now independent of the FinDBBuilderFormsExt configuration. |
| Snapshots: The progress bar for restoring snapshots has been improved to reflect progress more accurately. |
Templates: Resolved an issue where restoring an FST template would result in an error if a reference record was missing from the template. Template restoration now completes successfully, even when reference records are not included. | |
Tools: Previously filtered query results did not allow scrolling in the Filter tool. | |
| Tools: Fixed an issue where modifying actions using the Action Category Permission tool did not preserve the correct category order. The tool now maintains the intended order of action categories during updates. |
| Tools: The Clone Equip tool now allows users to clone equipment across all sites and floors, regardless of the current navigation context. |
| Tools: Improved the Clone Tags tool to prevent tags from being applied to schedule records that also contain the point tag. This change avoids accidental tagging of the schedule records and ensures more accurate tag cloning behavior. |
| Trend connector: This build introduces a new Trend connector, designed to provide an easy interface to a Trend Building Management System from the FIN Framework. |
| Tuning Policy Tree: Improved behavior when editing a tuning policy. Now the right-hand grid view automatically refreshes to reflect the latest changes. |
| Watch: Resolved an issue where finWatcherExt attempted to commit a tag named "transient", which is a restricted tag name. The tag has been renamed to comply with system constraints, eliminating the error and ensuring smooth operation. |
