PROMIN Cloud User Guide

1.1. Purpose

The manual describes the setup and daily use of PROMIN Cloud. The first part is intended for the company owner, administrator and system commissioning engineer. The second part explains the end user experience in Customer UI.

1.2. Document scope

The guide covers Projects, Controllers, Cloud Actions, UI, Calendar, Permissions, Logs, and PWAs.

1.3. Requirements

• Active PROMIN Cloud account.
• Modern browser with cookies and JavaScript enabled.
• Stable Internet access.
• Compatible PROMIN Controller for remote functions.
• Owner or Administrator permission to configure the project.

Facility security

Remote commands can change the state of real lighting equipment. Before running the action, check the project, controller, target and expected result. PROMIN Cloud is not an emergency or life-safety system.

1.4. Conventions

The names of interface elements are given in English and highlighted as Projects, Push UI or Scheduler. The word "project" means a Cloud project, not a local controller project file.

2.1. Three parts of the system

1. PROMIN Cloud Workspace stores projects, users, interfaces, the calendar, and commands.
2. PROMIN Controller Performs local hardware management and exchanges state with the Cloud.
3. Customer UI provides the end user with authorized buttons, zones, calendar and diagnostics.

2.2. Owner

Owner manages the company, projects, controllers, Interface Users and Administrators. Only the Owner sees the section Administrators. This role should be left to the responsible system owner.

2.3. Administrator

Administrator performs operational configuration of projects, controllers, interfaces, calendar and users, but does not manage the list of company administrators.

2.4. Interface User

The Interface User logs into the Customer UI and sees only the projects assigned to them. Their access is determined simultaneously by the status of the account and the link to the project.

2.5. Statuses

2.6. How data and commands flow

Project settings, Cloud Actions, interface and calendar are stored in the Cloud. When a user clicks a button or an event occurs, Cloud determines the associated targets and issues commands to the appropriate controllers. The controller executes the command locally and returns the available state. Therefore, the presence of a card in the Cloud does not guarantee execution: the controller must be correctly bound, be Online and contain the required trigger or UI button.

Two access levels The role determines which application sections a user may access, while project bindings determine which projects they can see. Active status without a project assignment does not make the project available in Customer UI; a project binding does not override Disabled status.

2.7. Division of responsibilities

3.1. Login

Open PROMIN Cloud, enter Login and Password, then press the login button. If there is an error, check your keyboard layout, spaces, and account status.

3.2. Acceptance of legal documents

If there is no acceptance record for the current version of the terms, Cloud displays the Terms of Service and Privacy Notice after login. Read the documents, select the required checkbox, and confirm acceptance. The workspace may remain unavailable until this step is complete.

3.3. Main menu

• Projects — list and workspaces of projects.
• Controllers — general list of company controllers.
• Account — profile of the current account.
• Users — end users of Customer UI.
• Administrators - administrators; available only to Owner.
• About — information about the service and legal documents.

The selected menu item determines the operating context. In lists, first use search, then open the card of the required item. Before changing, always check the page title, project name and role of the current account in the header. This is especially important when the company has similar projects or controllers.

3.4. Project workspace

After opening the project, tabs become available Overview, Cloud Actions, User interface, Calendar and Logs. The project title remains common, but each tab is responsible for its own data type. If the change is "not visible", first make sure that the correct tab and project are open.

• Overview — general parameters, metrics, local time and bindings.
• Cloud Actions - reusable sequences or groups of commands.
• User interface — appearance and user-accessible controls.
• Calendar - events, recurrence rules, astronomical rules, and imports.
• Logs — checking the result and finding errors.

3.5. Saving, waiting and errors

After submitting the form, wait for the operation to complete and do not click the button again. Then refresh the data or reopen the item and confirm that the values were saved. If an error occurs, do not create a duplicate blindly: record the message, time, project, and action, then check the logs and controller status.

4.1. Preparation

Before starting work, obtain the site address, the required time zone, coordinates or city, a list of controllers, a list of user scenarios and a list of people who need access. Separately, agree on which commands are safe to run during the inspection and who verifies the results on site.

4.2. Project infrastructure

First create a project and set its local time. Then a controller is attached to it and Online, Last seen, versions, Remote Web UI and trigger catalog are checked. Checkpoint: the engineer clearly understands which controller belongs to the project and can safely execute the test trigger.

4.3. Logic and user interface

Reusable commands are implemented as Cloud Actions. After this, Branding, Themes, Screens and Buttons are configured. Each target is checked first in the administrative interface, then in Preview, and only then published via Push UI. Checkpoint: The user screen contains only approved functions, and the captions describe the result of the action, not the internal name of the trigger.

4.4. Schedule, access, and handover

Set up the calendar after local time and targets. Create test single and recurring events, check their future occurrences, and only then enable Scheduler. After that, create an Interface User, assign projects, install Customer UI as a PWA and perform the check under the user role.

4.5. Completion record

• Record the name and identifying information of the project and controller.
• Record versions, Online/Last seen and date of review.
• List validated actions, buttons, and calendar events.
• Specify the state of the Scheduler after completion of the work.
• Record the accounts created and how the credentials were provided.
• Record known limitations and support contacts.

5.1. Current profile

In Account, you can change Name, Surname and Login. Fill in the new password field only when the password really needs to be changed. After saving, check the data in the block Current account.

5.2. Security

• Do not share one account with multiple people.
• Choose a unique password and do not save it on a publicly accessible device.
• After working on someone else's device, press Logout.
• If you suspect compromise, immediately change your password and notify the company owner.
• Assign users only to the projects they need.

5.3. Changing your profile and password

• Check the current Login and role in the block Current account.
• Change only the required Name, Surname, or Login fields.
• Leave the new password field blank if you do not need to change the password.
• After saving, reopen Account and check the result.
• When changing Login or Password, complete your current work and check the new login in a separate private tab.

Changing Login affects subsequent logins, but should not be used as a way to transfer the account to another person. Create a separate account for the new employee and then disable the previous employee's access.

5.4. Ending a session

Button Logout ends the current session. Use it after working on a shared computer and before signing in with another account or role. If you need to check Customer UI, it is more convenient to open a separate browser profile: this way the administrative and user sessions will not interfere with each other.

6.1. Creating a project

• Open Projects.
• In the panel New project fill in Project name.
• Enter a clear Description.
• Click the create project button.

The name must clearly identify the site, building, or installation. Do not include passwords, access codes or personal information in the title.

6.2. Project Overview

Once you open a project, its name and description appear at the top of the work area. The Overview shows the number of Controllers, Screens and Events, as well as the status of the Scheduler. Users, controllers and local time settings are also located here.

6.3. Location, Time zone and DST

Select a city in the field City. For a known city, Cloud fills in the coordinates, time zone and a suitable DST preset. If the site is not in the predefined list, select manual mode and check Latitude, Longitude and Time zone.

Project settings are used for calendar and astronomical events. An error in the time zone or coordinates results in an incorrect execution time.

6.4. User and controller bindings

In Users access, select the user who needs the project. In Controller binding, select the controller associated with the site. Removing a row from either block removes the binding but does not delete the account or controller itself.

6.5. Deleting a project

Operation requires confirmation

Deleting a project also removes the Cloud Actions associated with it and unbinds controllers. Before confirming, check the project name and whether its data must be backed up.

6.6. Naming and search rules

In a multi-site company, use a consistent naming pattern such as City – Facility – Zone. The description should explain the purpose of the project, the responsible person, and the management boundaries, but must not contain secrets. Before creating a project, search for the key part of the name to avoid duplicates.

6.7. Project Overview checklist checklist

• The number of Controllers corresponds to the actual connected devices.
• The number of Screens and Events corresponds to the prepared configuration.
• Scheduler is enabled or disabled according to the current stage of work.
• City, coordinates, Time zone and DST refer to the physical site.
• In Users access there are no extra people, and in Controller binding there are no other people’s controllers.

Changing local time After changing Time zone, DST or coordinates, be sure to double-check all upcoming calendar occurrences. For astronomical events, additionally compare the estimated time of sunrise or sunset with the expected time for the site.

7.1. List of controllers

Section Controllers is the company's device inventory. Before opening the card, use a search by name or serial and compare Status and Last seen. Similar names must not be the sole identifier: the serial number and the associated project are more reliable.

7.2. Adding and pairing

The recommended connection method is pairing code. In the section Controllers click Pairing code, copy the code and use it in the procedure for connecting the controller to PROMIN Cloud. The code is valid for 30 minutes and can only be used once.

After generating the code, go straight to the controller-side procedure. If the code has expired, has already been applied, or was copied in error, create a new one - the old code cannot be extended or reused. After pairing is complete, update the Cloud list and wait for the transition from Pending to Online.

7.3. Controller Overview

Open a controller from the list. On Overview, check Status, Model, Serial, Backend version, Last seen, creation and update dates, and related projects. For remote operations, the controller must be Online.

Last seen should be updated at the expected interval. Model and Serial confirm the selected physical device, and versions help identify feature incompatibilities. If the Online status is displayed but the catalog or commands are unavailable, update the card and check the logs rather than re-pairing unnecessarily.

7.4. Remote Web UI

The remote web interface button is available for the Online controller. After “WEB UI open” clicking, Cloud creates a limited remote session and opens the controller interface in a new tab. Allow the browser to open the tab if the pop-up blocker is triggered.

The remote session is temporary. Do not copy its URL into emails or documents and do not save it as a bookmark. After diagnostics, close the tab. If opening is blocked, allow pop-up only for the trusted PROMIN Cloud domain and repeat the action once.

7.5. Triggers

On the Triggers tab, Cloud loads the controller trigger catalog. It may contain Soft Triggers and UI Buttons. Click Run, On, or Off only after checking the target name and the affected physical equipment.

Before Run, match the target type, its name, and the expected physical change. For Switch, check On and Off separately. If the catalog is empty, first click Refresh and check Online, the agent version and the presence of items in the local controller project.

7.6. UI Sync and Push UI

This block is designed to synchronize the user interface between the cloud platform and the controller. In UI sync, select project and Scope:

• Full app - complete project interface.
• Related screens — screens related to the selected controller.

Click Push UI. The button is active only for the Online controller and the selected associated project. After submitting, test the Customer UI on a real device.

7.7. Disconnect and rebind

Removing the controller binding from a project does not remove the device from the company. The Disabled status should be used as an administrative block when remote operations need to be stopped while retaining its record. Before unlinking, check Cloud Actions, UI buttons and Calendar: their targets may remain logically configured, but will no longer be executed through this controller.

8.1. Purpose

A Cloud Action combines one or more targets into a project action. Target can refer to the trigger or UI button of the associated controller. The action can be triggered manually, from a user button, or from Calendar.

8.2. Creating an action

1. Open the project and tab Cloud Actions.
2. Fill in Name and Description.
3. Select Mode: parallel or sequential.
4. Specify general Timeout ms.
5. Click Add action.

In parallel mode, targets are launched as a group. In sequential mode they are processed sequentially. For a critical sequence, first test each target separately.

8.3. Targets

For a regular Advanced action, select Controller, target type and element from the trigger catalog, then click Add target. An individual target can be Disabled, Enabled or deleted. Managed actions created from UI or Calendar are edited from their source.

8.4. Testing

• Make sure the action is Enabled and contains at least one target.
• Warn people on site about the test run.
• Click Run.
• Check the physical result and Project Logs.

8.5. Mode selection and timeout

The name of the action should describe the expected result - for example, “Lobby - evening scene”, and the Description should explain the purpose and limitations. Do not name the action only "Trigger 12": after changing the local project, such a name will not help the operator.

8.6. Managed and Advanced actions

Advanced actions are created and edited in Cloud Actions. Managed action is generated by another section - for example, the UI Constructor or Calendar - and maintains a connection with the source. For a managed entry, first find the source and change the source button or event. Use conversion to a normal action only when the connection with the source is no longer needed and the consequences are clear.

8.7. Action acceptance check

• All targets refer to the correct controllers and are available in the catalog.
• The execution order and mode correspond to the script.
• Disabled targets should indeed be excluded.
• Manual Run is completed during a safe test window and confirmed on site.
• In Logs you can see the expected actor, target and final status.

9.1. Recommended order

• Set up General and Branding.
• Select or save Theme.
• Create Screens.
• Assign Home screen and, if necessary, All Zones.
• Add Action, Switch and Zone Card buttons.
• Link buttons to triggers, Cloud Actions or other screens.
• Check the result in Preview.
• Perform Push UI to the desired controller.

9.2. General and Branding

General specifies the Installer and Customer logos, customer name, background, global colors and styles. Here you can select Home screen and All Zones, and also turn on the read-only RDM Diagnostics screen.

9.3. Themes

The Theme stores a consistent set of global styling options. You can apply a preset, save the current theme, rename, overwrite or delete a custom theme. The Apply to Existing Buttons option modifies elements that have already been created, so check the Preview before confirming.

9.4. Preview

Preview shows the Customer UI in the selected device preset. Check long titles, text wraps, number of buttons, bottom navigation, and all transitions between screens. Preview is not a substitute for testing on a real phone or tablet.

Customer UI preview.

9.5. Screens & Buttons

Create screens with short, unambiguous titles. For each button, select a type:

• Action - one action.
• Switch — separate actions On and Off.
• Zone card — zone card with navigation and actions.

9.6. Screen structure design

Start with user scenarios, not colors. Home should contain the most frequent actions and clear transitions to zones. All Zones provide a general overview, and individual zone screens are for detailed control. Don't duplicate the same function under different names: the user should predict the result before clicking.

9.7. Types of buttons and bindings

The Binding can refer to a controller trigger, UI button, Cloud Action, or Cloud UI element. If you change the source catalog, reopen the button editor and ensure that the link has not become unavailable.

9.8. Themes, accessibility and real devices

• Check the contrast of text and buttons on a light and dark background.
• Use short captions; test long titles on the narrowest supported screen.
• Don't convey the meaning with color alone: the state should be understandable from the label or the position of the Switch.
• Check logos without distortion and backgrounds without loss of readability.
• After Push UI, close and reopen Customer UI on your phone, tablet, and desired desktop browser.

9.9. RDM Diagnostics

RDM is enabled in General as a separate read-only screen. Only show it to users who need diagnostic information. Having RDM in the UI does not replace Cloud Logs or provide administrative editing of the controller.

10.1. Preconditions and timing model

1. The project contains the correct City, Latitude, Longitude, Time zone and DST.
2. The necessary controllers are associated with the project and have an up-to-date trigger catalog.
3. Commands or Cloud Actions are verified by manual safe execution.
4. Determine whether Scheduler should be enabled during setup.

The date and time are entered in the context of the project's Time zone, and not necessarily the time zone of the engineer's computer. When switching between standard time and daylight saving time, check the actual occurrences around the changeover date. For sites without seasonal clock changes, ensure that the appropriate DST preset is selected.

10.2. Navigation and views

10.3. Week and Year

In Week, compare the times of several events within a day and week. This is the main view for accepting the schedule: here it is easier to notice duplicates, commands scheduled too close together and an event that falls on the next day. In Year, open months in sequence with seasonal changes, holiday exceptions, or the beginning and end of a series.

10.4. Selected day and All Events

Clicking on a date opens a day window with all calculated occurrences. Use it to create a new event, open an existing one, or compare the order of commands throughout the day. Side List All Events shows the original events regardless of the current calendar window and is convenient for searching for rarely repeated series.

10.5. Single event

• Select the desired date and open event creation.
• Enter a short, unique Name that describes the result.
• In Schedule, select single mode and check Date and Time.
• Add at least one target or select a proven Cloud Action.
• Review the final settings and create the event.
• Find the occurrence on the selected date and reopen Event Settings.

Single mode is suitable for a one-time command: a test, a special day, or a temporary change. Do not create multiple identical one-time events instead of a recurring event; they are more difficult to maintain and disable.

10.6. Event targets

An event can trigger a controller Trigger, controller UI button, Cloud UI button or a pre-created Cloud Action. For direct target, select controller, type and specific element, then click Add target. Added lines are executed in preserved order; remove the extra line before saving.

10.7. Simple recurring event

In Schedule, select recurring, specify the Start date and a simple preset. Options are available by minute, daily, on weekdays, weekly with selected days of the week and monthly by date. Set the ending for the series Never or Until. Until must not be earlier than Start date.

10.8. Advanced repeat controls

An advanced editor is needed for rules that cannot be expressed with a simple preset. Open it only when there is a clear calendar requirement and record the rule in the site documentation. Main fields:

Several restrictions apply together. Therefore, after saving, you cannot limit yourself to checking one closest occurrence: open Week, Month and Year and check the beginning of the series, the typical period, the boundary of the month or season, and the Until condition.

10.9. Multiple RRULEs and exceptions

Combined rule allows you to store several RRULE strings for one event. Each line adds its own series, so matching occurrences are possible. Normalize the requirement before saving: if it is expressed in one simple rule, do not create several.

Exceptions remove a specific date and time from the recurrence. This is suitable for a holiday, site closure, or one-time rescheduling. The exception does not remove the original rule or affect other dates. After adding it, confirm that the required occurrence has disappeared while the neighboring occurrences remain. For a permanent schedule change, edit the rule instead of accumulating many exceptions.

10.10. Astronomical event

Astronomical mode is available for recurring events. Select Sunrise, Sunset, Moonrise, Moonset or Moon quarter and set the offset in minutes. A positive or negative offset shifts the command relative to the calculated phenomenon; the sign must be verified using a specific example. For Moon quarter, select the required phase.

Sunrise, Sunset, Moonrise, and Moonset depend on the site's coordinates; the displayed local time also depends on Time zone and DST. After saving, compare several dates in different seasons. Do not copy an astronomical event to another project without checking its location settings.

10.11. Editing, disabling and deleting

Open an event from the calendar, day window, or All Events. In mode Event Settings you can change the schedule and targets, save or delete the event with confirmation. Before deleting a series, check the Name, Start date and the rule: the operation relates to the original event, and not just to one visual card.

If execution needs to be temporarily stopped, it is preferable to disable the event or Scheduler according to the operational scenario, saving the configuration for analysis. After any change, refresh the Calendar and check the upcoming occurrences and Project Logs.

10.12. Import and Scheduler

Import replaces Cloud Calendar Importing events from the selected controller replaces the project's current Cloud Calendar events. Before confirming, make sure that the correct Online Controller is selected and saving the current calendar is not required.

In Calendar, first select the specific associated controller, then click Events import and read the confirmation. Import transfers controller events to Cloud and replaces the current Cloud events for that project. Before the operation, record the number and composition of current events; after import, check the names, rules, targets, and local time.

Scheduler is the general executor of the project schedule. Its state is visible on Project Overview. The end user may have access to a switch in Settings, so before site handover, agree whether they have the right to stop the schedule. During mass editing, Scheduler is usually placed in a pre-agreed safe state and returned only after verification.

10.13. Calendar acceptance check

1. Check the local project time with an independent source.
2. Check one single event from creation to recording in Logs.
3. For each series, check at least three occurrences, including a week or month boundary.
4. For Until, make sure there are no occurrences after the end date.
5. For exception, check the excluded and two adjacent dates.
6. For an astronomical event, compare the calculation in winter and summer and check the offset sign.
7. Verify each target and the result of a safe test execution.
8. Capture the final state of the Scheduler and check the Customer Calendar.

The calendar is ready for handover

The engineer can explain the source of each event, show the next occurrences, justify the Time zone and targets, and the user sees the expected plan in the Customer UI without unnecessary administrator rights.

11.1. Interface Users

Section Users creates accounts for Customer UI. Fill in Name, Surname, Login and Password. After creation, set the desired Status and assign projects through Project Overview.

11.2. Administrators

The Administrators section is available only to Owner. Create a separate account for each administrator. The Administrator gets broad access to the company's operational functions, so don't use this role for the regular Customer UI.

Before creating an Administrator, determine which work tasks require the administrative level. After granting access, perform a test login and make sure that the Administrators section is not displayed. Regularly review the list and disable the accounts of employees who no longer require access.

11.3. Modification and deletion

Edit allows you to change the profile and, if necessary, the password. Disabled blocks access without immediately deleting the entry. Before Delete, check whether historical records must be retained and which projects are assigned to the user.

11.4. Access lifecycle

• Create a separate entry and assign the minimum required role.
• Assign only the required projects and perform a test login.
• When temporarily suspending, use Disabled without deleting the entry immediately.
• When changing responsibilities, review projects and the role, not just the password.
• Before final deletion, clear the project assignments and record the reason.

The Invited status means an unfinished invitation stage, Active means that access is allowed within the limits of the role and assignments, Disabled means blocking. After changing the status, check the behavior in a new private browsing session; a previously opened user tab is not a reliable check.

12.1. Project Logs

Project Logs contains activity related to the project, controllers, calendar and UI, as well as commands from the Customer UI. Use Search, Event type, Actor and date range. Last 24 hours, Last 7 days, Last 30 days, Last 90 days and Custom range are available.

12.2. Offline controller diagnostics

• Check Status and Last seen on Controller Overview.
• Make sure the controller is turned on and has internet access.
• Check if Status Disabled is set.
• Refresh the page and reload the trigger catalog.
• View Project Logs for the moment the connection was lost.
• If the problem persists, prepare Serial, Versions, Last seen and error time.

12.3. Finding an event in the logs

• Record the local time of the problem and the Time zone of the project.
• Select the narrowest date range that includes a few minutes before and after the event.
• Filter Event type by category: controller, UI, calendar, access or configuration.
• If the user is known, select Actor; if the affected item is known, use Search.
• Click Refresh and correlate adjacent entries by time, target and status.
• Expand the range and remove filters one at a time if the entry is not found.

12.4. Support data

Send the prepared information to PROMIN Controller technical support at: [email protected].

• Project and controller name, Model and Serial.
• Exact date and time indicating Time zone.
• Role and demo user Login without password.
• Expected and actual behavior, reproduction steps.
• Controller status, Last seen and displayed versions.
• Screenshot of the message and relevant log entries before and after the error.

13.1. Login and project selection

13.2. Home and zones

Home opens the screen designated as the Home screen in UI Constructor. The bottom navigation can contain Home, All Zones, RDM and Calendar. The set of items depends on the project configuration.

The active bottom-navigation item identifies the current section. Home is the starting point, Zone Card opens a specific zone, and All Zones provides a summary list. If an expected item is missing, the corresponding screen is usually not assigned in UI Constructor; this is normally not an application installation error.

13.3. Action, Switch and Zone Card

• Action runs the configured command and can show loading/error state.
• Switch toggles On and Off and requires both sides to be configured correctly.
• Zone Card opens the zone screen and can contain quick actions.

After clicking, wait until the loading state completes and do not send the same command multiple times. If there is an error, remember the time, button name and selected project, then inform the administrator. Interpret the Switch position only in conjunction with the actual state of the equipment if the site is temporarily Offline or the connection is unstable.

13.4. Customer Calendar

Customer Calendar shows the events of the selected project. Click Create Event for a new event or select an existing one to edit. Available bindings are determined by the UI and project settings. After the change, use Refresh and check the result.

For regular tasks, use simple presets. Advanced controls, multiple RRULEs, exceptions, and astronomy require the same checks described in Chapter 10. After a change, click Refresh, find at least three future occurrences, and confirm that the event belongs to the required project. Scheduler in Settings affects schedule execution, not whether calendar entries exist.

13.5. RDM Diagnostics

RDM is visible only if the feature is enabled in UI Constructor. The screen provides read-only status information and a list of RDM devices. If the snapshot is unavailable, check the Online controller and the project RDM setting.

Compare Online/Offline and snapshot relevance time. RDM in Customer UI is intended for read-only monitoring and does not allow the user to change device settings. If the list is empty, record the project, controller and time and pass the data to the engineer.

13.6. Settings

Settings shows Customer UI version, username, Scheduler, Project change if there are multiple projects, About, Fullscreen and Log Out. On the iPhone, the interface separately prompts you to add it to the Home Screen, which is necessary for standalone/fullscreen mode.

1. Scheduler — permitted control of the project schedule; change only according to the agreed procedure.
2. Project change — return to selection from assigned projects.
3. About — information about the application and documents.
4. Fullscreen — display mode without unnecessary elements, if supported by the platform.
5. Log Out — ending the user session on the device.

13.7. Installation on iPhone or iPad

• Open Customer UI in Safari.
• Click Share.
• Select Add to Home Screen.
• Check the name and click Add.
• Launch the application with a new icon on the Home Screen.

Use Safari: the item and behavior may differ in another browser. On the add screen, enable Open as Web Appif this option is displayed, and keep the friendly name. After installation, close Safari, launch a new icon and check login, the selected project and standalone mode in Settings.

13.8. Installation on Android

• Open Customer UI in Chrome.
• Open your browser menu.
• Select Install app or Add to Home screen.
• Confirm installation and launch the application from Home Screen.

The name of the command depends on the version of Chrome and whether PWA installation is available. If the Install app is missing, refresh the page, check the Internet and try Add to Home screen. After installation, launch the new icon, then make sure that the Customer UI of the desired domain opens and Settings correctly shows the application mode.

13.9. Installation on Windows

• Open Customer UI in Edge or Chrome.
• Click the install icon in the address bar or select Install app from the menu.
• Confirm installation.
• If necessary, pin the application to the taskbar or Start.

13.10. Standalone mode and updates

In the installed application, Settings shows Running in standalone mode. Customer UI automatically checks the build version and updates resources if necessary. If the old version is displayed, close the application completely, connect to the Internet and open it again.

After updating, check the displayed version in Settings and one safe user scenario. Clearing site data removes your local session and browser settings, so only use it after a normal restart and be prepared to log in again. Removing a PWA icon does not delete the Cloud project or account.

13.11. Check after installation

• The application launches with a new icon and shows the expected branding.
• The user logs in with their own account and sees only assigned projects.
• Home, Zones, All Zones, Calendar and RDM correspond to the configuration.
• One safe Action and both sides of one Switch are tested.
• Settings shows the current version and expected state of the Scheduler.
• Log Out returns you to the login screen, and relaunching it does not open someone else's session.

14.1. Preparing for acceptance

Designate a review window, a responsible engineer, and a person on site who will confirm the physical result. Record the initial state of the equipment and Scheduler. For tests, use predefined safe commands; emergency, security and critical scenarios are checked only according to a separate facility procedure.

The checklist is performed in order. Verbal confirmation is not enough: for each questionable item, keep the time, the expected result and the corresponding entry in Logs. If an item is not applicable, note the reason rather than assume it is automatically completed.

14.2. Technical checklist

• The project title and description refer to the correct site.
• City, Latitude, Longitude, Time zone and DST are checked.
• The desired controller is associated with the project and has the Online status.
• Last seen is updated and controller versions are displayed.
• Remote Web UI opens without exposing the temporary URL.
• Trigger catalog is loaded, test triggers are executed safely.
• Cloud Actions are enabled, targets are checked, Run gives the expected result.
• Home screen and All Zones are assigned.
• Action, Switch and Zone Card are tested in Preview and on device.
• Push UI is completed with the correct Scope and Project.
• Calendar uses the correct Time zone and contains expected occurrences.
• Scheduler is in the agreed state.
• Interface User has access only to necessary projects.
• Customer UI is installed as a PWA and runs in standalone mode.
• Project Logs do not contain unexplained errors from the test period.
• The customer has been provided with the URL, login, password and the procedure for contacting support.

14.3. Verification as Interface User

• Open a separate private session or device without an administrative login.
• Log in as a test Interface User and compare the list of projects with assignments.
• Go through Home, each zone, All Zones, Calendar, RDM and Settings.
• Perform one safe Action, both sides of the Switch and a Zone Card transition.
• Check the calendar and Scheduler management rights as required.
• Install PWA, check standalone mode, then Log Out.

14.4. Handover materials

• Cloud Workspace and Customer UI addresses.
• List of projects, controllers, roles and responsible persons.
• Approved layout of screens, buttons and main Cloud Actions.
• Description of the calendar, Time zone, astronomical rules and Scheduler status.
• Procedure for changing your password, disabling access and contacting support.
• Known restrictions and unfinished items with owners and deadlines.

Handover outcome The user must be able to log in, select a project, manage allowed zones, check Calendar, open Settings, and log out correctly without administrative access to Cloud Workspace.

15.1. Quick checks

15.2. Additional Calendar diagnostics

15.3. Isolating the root cause

1. Access: check Login, Status, Role and Project Assignment.
2. Context: check the project name, controller and Time zone.
3. Communication: check Online, Last seen and trigger catalog availability.
4. Configuration: open the target, binding, Cloud Action, or original calendar event.
5. Execution: check Scheduler, enabled states, timeout and replay once safely.
6. Evidence: map Time, Actor, Target and Status in Logs.

15.4. When to contact support

Technical support Email: [email protected]. Include “PROMIN Cloud” and the project or facility name in the email subject.

Contact support if the problem persists after checking the role, project, communication, and configuration; if the interface reports a system error; if the correct command does not appear in Logs; or if an import or save operation produces an unexpected result. Do not repeatedly delete and recreate records, because this may destroy useful diagnostic context.

Include the project, Model/Serial of the controller, versions, role, exact time with Time zone, reproduction steps, expected and actual results, screenshot and relevant log entries. Passwords, pairing codes and temporary Remote Web UI URLs must not be sent.