This release focuses on the time drifting problem appearing in software. Other fixes improve stability of the system were made.

Fixes

• Fixed time driffting issue on Vertexes with no internet connection.

• Fixed DALI-POINT update error, visible in UI.

• Node-RED: Fixed issue with Vertex Target Action node when controling a single device.

This release introduces new MUI features, including Polish and German language support, zone-based scenario control, and the ability to reuse existing groups in UI configurations. Reliability improvements and multiple fixes address network stability, LED feedback issues, emergency reporting, and Node-RED deployment errors.

Features

• MUI: New languages support addded - Polish and German.

• MUI: Possibility to add zones to scenario. Users are able to control multiple groups with certain offset value.

• MUI: Added possibility to use already created group in scenario configuration in UI.

• Added new mode of operation for Manual off mode in scenario. Now users can select if they want to operate with standard Manual off mode, or prolong it when space is occupied.

• Node-RED: Added possibility to inject the configuration values to the scenario nodes in Node-RED allowing users to:

  • Change the node state on demand.

  • Integrate the scenario nodes with tablets/external integrations.

  • Change sensor hold and standby times in runtime.

• Node-RED: Added help documentation in Node-RED Vertex scenario profile node.

Fixes

• Increased reliability of network connection after restart.

• Fixed issue with frozen status update information in multiupdate.

• Fixed problem with switching feedback LEDs on push buttons.

• Fixed counting devices issue in emergency report.

• Fixed counting members of group after cleaning the port.

• Node-RED: Possibility to control the scenario node state from Tablets.

• Node-RED: Fixed issue with Node-RED deployment after adding new devices to cluster in netconfig (“Session expired, relogin to Node-RED”).

This release addresses a critical issue that could render the Vertex Application Controller inoperable during firmware updates from version 3.X.X to 4.X.X.

• Improved the safety and reliability of software updates from firmware version 3.X.X to 4.X.X.

This release addresses a critical issue that could render the Vertex Application Controller inoperable during firmware updates from version 3.X.X to 4.X.X.

Fixes:

• Improved the safety and reliability of software updates from firmware version 3.X.X to 4.X.X.

• Fixed system startup time synchronization using the Real-Time Clock (RTC).

The update resolves multiple UI and system bugs, including slow identification reactions, error messages in Time Settings, and issues with emergency luminaires such as flashing in inhibit mode and inaccurate test results. It also secures software update processes, USB log downloads, and Node-RED API behavior to prevent system freezes.

Fixes:

• MUI: Fixed the problem of slow identification reaction, when grouping triggered from modern UI identification view.

• MUI: Fixed issue in the Time Settings tab that caused the page to display the message 'Oops, something went wrong'.

• Fixed the problem with emergency luminaires flashing in active inhibit mode after a power failure.

• Fixed publishing of statuses for emergency luminaires after triggering tests.

• Fixed inaccurate duration test results when the emergency luminaire is in battery charging mode.

• Resolved the issue of missing DALI 25X standard in data models.

• Secured the case where the multiupdater would get stuck in the 'Waiting for other vertices to finish update' state after receiving invalid update statuses from neighboring devices.

• Resolved issue with the new software package incorrectly saving and not starting update on the Vertex.

• Resolved the issue with USB mounting on the front panel for versions 4.X.X not downloading logs.

• Resolved issue with Wi-Fi dongles not working.

• Node-RED: Securing the backend API for receiving an empty value messages from Node-RED, which might cause the system to freeze for up to 60 seconds.

This is a maintenance release focused on correcting the issues introduced in version 4.1.1.

Bugfixes

• MUI: Fixed problem with daylight calibration triggered from UI scenario view

• MUI: Fixed problem of missing information on UI home page about unconfigured network

• Node-RED: Fixed disappearing groups and devices in Node-RED

• Node-RED: Missing information on UI home page about unconfigured network

Software version 4.1.1 is a new common software that allows you to work on Vertex 3 and Vertex 4 in one cluster. This package can be installed on both Vertex 3 and Vertex 4. It comes with new versions of operating systems included in the system, ensuring longevity, but means you will not be able to downgrade to previous versions.

Attention! Important!

Features

• MUI: First release of simplified commissioning functionality of sensors and pushbuttons without entering Node-RED https://glamox.atlassian.net/wiki/spaces/ME/pages/3245015115 If you have used beta versions of this functionality you will find information on how to update with Scenario here: https://glamox.atlassian.net/wiki/spaces/ME/pages/3253665793

• MUI: NTP servers configuration for Vertex: Added possibility to change the configuration of NTP servers directly from UI https://glamox.atlassian.net/wiki/spaces/ME/pages/1953366042

• MUI: Multiupdate is now a generally available feature. From this version, it is not beta-feature anymore. https://glamox.atlassian.net/wiki/spaces/ME/pages/1766424636

• MUI: Improved order of tabs in Settings view. Now Vertex cluster tab is the first one.

• New operating system version. All system components (like Python libraries and Node-RED) have been updated to recent versions.

• Automatic adjustment of CPU to avoid the Vertex overheating.

• Node-RED: Activate/Deactivate Inhibit Mode in Vertex Action node for emergency lighting applications.

Fixes

• MUI: Fixed link to knowledge base/release notes on UI.

• MUI: Added warning when naming devices using special characters.

• MUI: In the control devices tab basic configuration of sensors and switches is no longer available.

• Resolved problem with creating groups when one of Vertexes within the cluster is offline.

• Improved reaction time of group events when having many input devices in the system.

• Fixed error with changing the DNS to default after a firmware update.

• Node-RED: Resolved the problem of logging into Node-RED after a factory reset.

• Node-RED: Improved process of booting up. (Very rarely Node-RED could launch before the rest of the system, which used to cause issues, e.g., missing events/data from other Vertexes, missing groups in Node-RED).

• Node-RED: Fixed Node-RED restart after deleting a used scenario template node, without deleting a scenario node itself.

Version 3.1.38 addresses critical issues identified in version 3.1.37. Due to these issues, version 3.1.37 has been removed from distribution, and we recommend using version 3.1.36 if you are experiencing problems. This resolves deployment and communication issues, ensuring system stability and reliability.

Resolved Issues

• Deployment Issues in Node-RED: When updating Vertex directly from version 3.1.30 (factory version) to 3.1.37, deployments in Node-RED sometimes failed.

• DALI Port Communication Failure: In version 3.1.37, the DALI port could stop communicating, affecting lighting control and automation.

• Improved time synchronization on Vertex from computer timezone.

This update brings several improvements to the system’s reliability, performance, and ease of use. We have enhanced the way device data is displayed, improved system logging, and introduced better support for various LED drivers. Additionally, we’ve fixed multiple issues to ensure smoother operation and better user experience.

Features:

• MUI: Easier Access to Update Details – A new link is available within the interface, providing descriptions of software changes directly from the UI.

• MUI: Improved Device Information – Clicking on status in the device information now displays failure levels, making system monitoring easier.

• MUI: Refined Control Device Settings – The instance settings page for control devices has been redesigned for better clarity and ease of use. https://glamox.atlassian.net/wiki/spaces/ME/pages/2979921925

• Expanded Data for Monitoring – Added publishing of data to MQTT API such as: active power, control gear temperature, light source current, light source voltage and light source on time. Previous versions talked about features like general lighting errors.

• Automatic Error Detection – If the system does not receive a status update within 30 seconds, an error will be displayed, improving issue detection - visible on front panel of device

• Broader LED Driver Support – Full support has been added for LED drivers that simultaneously support Emergency DALI standards IEC 62386 Part 202 and 207.

Fixes:

• MUI: Device List Updates Now Work Correctly – Fixed an issue where data on the device list was not refreshing properly.

• MUI: Faster Data Updates – Device information now updates more quickly for Control Groups in the UI, reducing delays.

• MUI: Scene Settings – Fixed an issue where some advanced scene settings were not saving correctly.

• MUI: Fixed issue with unjustifiable “Oops, something went wrong!” on some UI tabs.

• Emergency Logs Are More Complete – Missing records for emergency lighting actions are now properly logged.

• Fixed Device Identification Button – Some users were experiencing issues with identifying devices, which has now been resolved.

• Improved the way the system reads data from DALI Part 250, 251, 252, and 253 standards.

• Fixed an issue where light sensor data did not update correctly when the resolution parameter was set to 0.

• Backup & Restore Stability – Resolved an issue where users had trouble logging in to Node-Red and MUI after restoring a backup and after factory reset.

• Node-RED: Data Refresh Fixes – Device data in Node-Red now updates correctly.

• Node-RED: Persistent Settings – Fixed an issue where Node-Red settings were not being saved after closing a node.

• Node-RED: Fixed Deploy issues in Node-Red

• Node-RED: Fixed the issue with the VX scenario node side hanging

• Node-RED: Light sensor data readings for VX Scenario nodes are now scalled same as dali2-devs common node

• Node-RED: Reduced the 'winding' phenomenon in PID when using daylight harvesting with I gain > 0. This applies to both daylight harvesting and Vertex Scenario nodes. The fix enables the node to reset its history more frequently, resulting in smoother light transitions.

• Node-RED: The maximum step size for daylight harvesting has been limited to 10% to improve the smoothness of daylight regulation.

• Node-RED: Added support for profile templates in Vertex Scenario nodes. You can now create a single setup profile and apply it to multiple Scenario node instances. Profile settings are shared across all linked Scenario nodes. https://glamox.atlassian.net/wiki/spaces/ME/pages/2717024257

• Node-RED: Added possibility to change the P, I, D gains in VX Scenario Node on the runtime, by injecting the proper data structures. After injecting - data are stored in node context. https://glamox.atlassian.net/wiki/spaces/ME/pages/3129081896

This release focuses on fixing various bugs in the system, improving stability, and addressing issues related to UI behavior and system resets.

🚀 Features:

• MUI: Possibility to reset admin user password using service account https://glamox.atlassian.net/wiki/spaces/ME/pages/3015147642

• MUI: Panel label generator for Sunricher pushbuttons

• MUI: New settings tab allowing for creating commissioning reports https://glamox.atlassian.net/wiki/spaces/ME/pages/2111733793 and device data export https://glamox.atlassian.net/wiki/spaces/ME/pages/2366898291

• Node-Red: Added the ability to recall the last level actions in the Vertex action block. For this feature to work properly, the LED driver must support it

🔧 Fixes:

• MUI: Added missing confirmation of password change action

• MUI: Corrected the reverse logic in the instance activation button

• MUI: Fixed buttons in Emergency setup Schedule

• MUI: Added missing information about enabled instances

• MUI: Fixed an issue where the no fade time could not be set in versions 3.1.30-33

• MUI: Added Colour type filter in control groups

• Resolved the issue where it was not possible to log into the UI after a factory reset

• Resolved the problem where the LED on Sunricher pushbuttons would turn off during cyclical scans

• Fixed an issue preventing users from restoring factory settings in newer operating system versions

• Node-Red: Fixed the problem with the Daylight harvesting limiter not working correctly in VX Scenario node

The release mainly improves the emergency lighting support in the new user interface (UI glitches eliminated) and adds the possibility to change the admin password on Vertex.

Features:

• MUI: Admin password change added to user application https://glamox.atlassian.net/wiki/spaces/ME/pages/2965241941

• MUI: All emergency features are now accessible from one UI tab

• MUI: Device name displayed by default in emergency device list

• MUI: Added preview of disabled instances in device view and device details

• MUI: Added possibility to change events per instance on control devices

Fixes:

• MUI: Fixed problem with 0 devices in Emergency report

• MUI: Fixed problem with displaying incorrect firmware version in the settings tab, when entering from different Vertexes within the cluster

• MUI: Resolved problem with multi-update if the first Vertex on the list was not selected

• MUI: Resolved the problem with test group 256 occurring in the emergency test report

• MUI: Possibility to download the emergency report, while one or more Vertex are currently unavailable

• MUI: Fixed problem with setting a specific interval of emergency tests schedule

• MUI: Improved simple scene view

• MUI: Fixed problem with synchronization of time from the PC

• The maximum number of devices that Netconfig can handle has been increased

• Node-RED: The VX scenario nodes now are not turning off the lights after partial deploy

• Node-RED: Improved synchronization of the number of devices DALI-2 between Vertexes

• Node-RED: Fixed deployment to the entire cluster on OS 3.2 and later versions

• Node-RED: Problem with opening Dali2Devs node, after applying corrupted configuration to node (freezing Dali2Devs nodes)

New release of software has backward compatibility to version 3.1.30. The main fix of this version allows for connection to Wi-Fi from Windows 11.

Features:

• Added automatic change of default setting of the motion sensor (255 sec report timer), light sensor (60 sec report timer) and slider/rotary instance (deadtimer 0.5 sec) - happens after first scan of the device

• New System Log details

• Added logging DALI traffic into USB - function allowing to transfer data to USB and check system logs later on, great for troubleshooting and problem solving, used mostly by development teams

• Publishing of information about general lighting errors in the MQTT API has been added

• MUI: Change name of DAS switch in MUI to Double Address Solving

• MUI: Added function - Emergency test trigger from MUI automatically generates a report after the test has finished

• MUI: Added banner in multi-updater with warning displayed when we try to downgrade software.

• MUI: Added turn on / turn off modbus action

• MUI: Added new action on the cluster "Reboot all vertexes"

• MUI: Added new design for emergency tests

• MUI: Added Vertex topology to the system status (experimental graphical overview) 

• Node-RED: Added option to enable instances in the Dali 2 devs node

• Node-RED: Added support for RGB instances in block Dali 2 devs and DALI2 Devs Common 
  (the DALI2 button must support such mode and send values from 0-1023 or 1023-0)

• Node-RED: Added new action in Vertex Action node function: set direct value RGBWAF and XY on group

• Node-RED: Added scenes, levels and go to last level triggered in scenario node

• Node-RED: Scenario nodes merged, leaving only the MS+CP+LS node

Fixes:

• Fixed Wi-Fi can't connect from Windows 11

• Fixed an issue with generating reports from duration tests

• Resolved issue with changing device name

• MUI: Resolved issue with missing scroll bar in system status on Main Page

• MUI: The problem with entering the "Devices" tab and scrolling down the page an error appears has been fixed

• MUI: Fixed an issue with setting RGBWAF scenes

• Node-RED: Fixed an issue with CCT jumping

• Node-RED: Fixed ‘long wait time’ during sensor reset

• Node-RED: Resolved issue with hanging Dali 2 Devs Common node

This update introduces significant enhancements to the user experience and robustness of the system.

🆕 New User Interface Application

We are proud to present a completely redesigned user interface application featuring:

• A modernized commissioning approach.

• Simplified processes for device identification, naming, grouping, and parameter configuration.

• An intuitive workflow, making the setup process effortless and efficient.

• A beta tester Control Devices tab.

Open

Open

Open

Open

Open

🔧 NodeRed Integration

The inclusion of new nodes in NodeRed enables:

• Acceleration of the commissioning process, minimizing time consumption.

• Easy setup for most popular control scenarios such as:

  • Manual control

  • Motion detection

  • Daylight harvesting

• These can now be implemented within a few simple steps.

⚙️ Bulk Firmware Updates

Update multiple devices with ease:

• Capability to update multiple vertexes simultaneously from a single UI view.

• Eliminates the need to switch between browser tabs, saving time and reducing hassle.

📡 Disabling the unused instances in DALI-2 devices

During first scanning of a device, the DALI-2 input devices will have disabled instances by default. This action will help to limit unnecessary traffic on DALI buses. The instances can be enabled using UI or NodeRED nodes.

🔄 Enhanced Cross-Vertex Communication

Improvements in cross-vertex communication ensure:

• The system operates more robustly.

• Enhancements are less visible but equally vital for overall performance.

Features:

• New UI application for commissioning

• VX Scenario nodes available for beta tests

  • MS + CP - for quick commissioning Motion Sensor combined with Control panels

  • MS + CP + LS - for quick setup motion detection and Daylight Harvesting functionality

• Added functionality to Daylight Harvesting node, ability to set max/min output level

• Update on multiple vertexes in cluster - available as BETA feature

• Deleted unnecessary node-red blocks

• Optimising DALI bus traffic by disabling unused instances during first device scan

• Optimised internal vertex communication

Fixes:

• Netconfig - resolved problems with grouping VX2 and VX3

• Optimised amount of data sent to node-red in installations with lot of sensors