The following article will explain what major changes may affect your site and what migrations may be required in the event of data conflicts. These migrations introduce profile support from the cloud to your controller. A minimum firmware version of 0.8.15 will be required.
Major changes that may have an affect on existing sites:
- The cloud will begin writing and maintaining controller to controller security keys
- Automatic migration will allocate default profile numbers based upon database row order
- Automatic migration will link profile schedules with generated profiles
If the migration fails to automatically align profiles across the site, a site user will be required to continue migration manually. All values indicated as inconsistent will require user input aiming to resolve conflicting profile data synchronised to the cloud.
The following scenario will step through a manual migration process and what gateway settings would result in requiring manual intervention.
Controller A's offline commission tool profile view:
Controller A's offline commission tool profile schedule view:
Controller B's offline commission tool profile view:
Controller B's offline commission tool profile schedule view:
Inconsistencies can occur when values on certain rows don't match up correctly. The easiest way to solve those inconsistencies is to right click in grid view on the cell with the inconsistency and click Apply current value. Alternatively, if the inconsistent value is incorrect, just update the value to the correct one. In the above example, we are creating row order conflicts which the automatic migration is unable to migrate.
The following steps will show you how to manually resolve the profile and schedule inconsistencies inside of grid view.
Go to the Profile schedule view first and resolve all issues (if any exist). The "Profile" values are seen as syncing because the automatic migration attempted to move them to their correct profile. In the current use case, the purple inconsistent row represents a schedule that was found on one control system but not the other. The "Saturday - After hours" schedule row can be seen before migration on controller A's offline commission tool profile schedule view but is not found on controller B.
It was deemed that the "Saturday - After hours" schedule was not required and was mistakenly left on a single control system and therefore we wish to remove it. After resolving the inconsistent state and it can be seen that there are no more inconsistencies, the profile schedules will migrate.
Once resolving issues on the profile schedule view, the site may continue migration (no inconsistent states remain). If there are still inconsistencies, grid view will continue to indicate that the user must fix the remaining issues before synchronization will continue.
Go to the Profile assignment page to resolve the remaining issues. A control system's profiles are shown in purple indicating that there is an inconsistency. Controller A's profile row order is inverted compared to Controller B's profiles. If you read the labels of the inconsistent row, it will show "0 - Normal hours" & "1 - After hours". Take note of the label of the profile as its the value that is actually on the control system. Click the drop down, and match the label up with the correct profile that should be in that position. In this example, Profile #1 on the first row would become "1 - Normal hours" & Profile #2 would become "0 - After hours". Do not attempt to change profile numbers from this view or you may lose data. After migration is completed, the profile numbers can be changed from the Profile view, if the numbers need to be switched around.
After all profile assignment inconsistencies are resolved, the system will attempt automatic migration again and if it succeeds , the warning message at the top will disappear.
After all the values have synchronized, the profiles and schedules will match what was on the control systems before migration began.
After migration completed successfully for profiles.
After migration completed successfully for profile schedules.
After migration completed successfully for profile assignment.
Article is closed for comments.