RN200963: Known issue in Raynet One 2026.1 [RTM]

RN200963: Known issue in Raynet One 2026.1 [RTM]

RAYNET ONE 26.1 MIGRATION GUIDE (FROM 25.3)

This document describes the required steps and breaking changes when upgrading Raynet One to version 26.1.

Important: 
The actions described in this document are only required when upgrading an existing Raynet One installation. 
Fresh installations of Raynet One 26.1 are not affected and do not require any of the steps outlined below.

1. MESSAGING NAME PREFIX CHANGE (RABBITMQ)

Starting with Raynet One 26.1, the messaging infrastructure requires an updated configuration for the messaging name prefix.

Required Action

The Messaging__NamePrefix value in the Docker Compose file or Helm charts must be adjusted before starting Raynet One 26.1 containers.

Important Notes

• The name prefix can be freely chosen.
• The chosen prefix must not already be in use within the same RabbitMQ vhost.
• This change prevents naming conflicts between messaging components such as exchanges and queues.

If the name prefix is not adjusted, messaging conflicts or startup issues may occur.

2. REQUIRED DATABASE MIGRATION SCRIPTS (HOSTNAME / FQDN CHANGE)

Raynet One 26.1 introduces a data model change related to the handling of hostnames and fully qualified domain names (FQDNs).

When Is This Required?

• This step is required for all databases that already contain device data.
• It only applies to upgrades from Raynet One 25.3.
• It is not required for fresh installations.

Why Is This Required?

If the migration scripts are not applied, Raynet One will continue to operate. However, duplicate device entries may be created for certain devices due to the updated hostname and FQDN handling.

RECOMMENDED MIGRATION STEPS

Please follow the steps below in the given order to ensure a safe and successful migration.

1. Deactivate all schedules and automations.
2. Shut down Raynet One completely.
3. Update the deployment configuration:
   • Update Docker Compose or Helm charts to use the Raynet One 26.1 image tag.
   • Adjust the Messaging__NamePrefix value.
4. Start Raynet One:
   • Ensure the frontend container starts successfully so that all automatic database migrations are applied.
5. Open your database management tool:
   • Microsoft SQL Server
   • MariaDB / MySQL
   • PostgreSQL
6. Retrieve the migration scripts:
   • Download the appropriate script according to your database.
7. Apply the migration script:
   • Execute the script corresponding to your database provider.
   • Verify that the script completes successfully.
8. Reactivate schedules and jobs.

SUMMARY

• Two breaking changes must be considered when upgrading Raynet One to 26.1.
• The Messaging__NamePrefix must be adjusted before starting Raynet One.
• Database migration scripts must be applied for databases containing existing device data.
• Skipping the migration scripts may result in duplicate device entries.
• None of the steps are required for a fresh Raynet One 26.1 installation.