PROMIN Controller User Guide

3.1. What pages and sections are available in the interface

3.2. License Agreement

When logging in for the first time, you must review and accept the License Agreement before accessing the controller interface. Read the agreement, select the confirmation checkbox, and click Accept and continue. This confirmation is required only during the initial login.

5.1. Status tab

The Status tab is suitable for a quick verification that the correct basic data is recorded on the controller.

• Check the controller name, location, time zone, and DST status.
• Verify the coordinates if the site uses geographic parameters.
• Review the time of the last settings update.
• Check the Notes block if it stores service notes for the site.

Working actions are available on the right or at the top of the tab:

• Refresh refreshes the status data.
• Reboot sends the controller for reboot.
• Schedule on / Schedule off enables or disables execution of the calendar schedule.

The Schedule off button is useful during commissioning when you need to temporarily exclude the effect of the schedule on the site. Before handover, make sure the schedule is returned to the required state.

5.2. Logs tab

The Logs tab helps you understand what happened on the controller: events, messages, and possible errors. You can also use filters to quickly find the required log entry.

Use it if something on the site is operating unstably and you need to review the latest events.

The filter panel allows you to narrow down the log list by:

• Search — searches by message text, UID, PID, device, or error details.
• Source — shows entries generated by a specific controller subsystem.
• Level — filters logs by severity, such as information, warning, or error.
• Event Type — shows only entries related to a specific operation or event.
• Actor — filters events performed by a particular administrator, user, or system process.
• From / To — limits results to a selected date and time range.

Click Apply filters to update the list. Click Reset to clear all selected filters.

Refresh reloads the log list.

The First / Previous / Next / Last navigation lets you move through journal pages.

Clear logs permanently clears the journal.

5.3. DMX Out tab

The DMX Out tab shows a live output monitor. It is one of the most useful engineering screens for quickly checking whether the controller is actually outputting data right now.

• Select the required output in the Output field.
• Check the Runtime: Live / Offline indicator.
• Review the number of active channels, peak level, and the time of the last update.
• In the Selected Output block you can verify which output and which scope the signal is going to.
• The 512 Channels grid shows the actual levels of all channels on the selected output.

This tab is especially useful when you need to understand:

• whether there is any outgoing DMX / Art-Net signal at all;
• whether transmission is going to the correct universe or output;
• whether the required channels show activity;
• whether the problem is in the controller or farther down the communication line / inside the fixture.

5.4. RDM tab

The RDM tab provides tools for monitoring, discovering, configuring, and diagnosing RDM-compatible lighting devices connected through Art-Net gateways or the controller’s native DMX outputs.

The summary at the top displays the current RDM status, Controller UID, last update time, and the number of gateways, RDM ports, responders, project devices, stale devices, devices requiring attention, and protocol errors. Click Refresh snapshot to reload the current information. This action does not start device discovery.

The navigation tree contains:

• Project devices — responders registered in the current project.
• Discovered gateways and responders — available gateways, output ports, and detected RDM devices.

Select an object in the tree to view its details and available actions.

For a gateway, the tab shows its connection status, IP address, firmware, RDM capability, compatibility information, output ports, and transport errors. Use Refresh all ports to update the Table of Devices (TOD) for all available ports.

For an output port, you can review its discovery state, responder count, RDM status, and communication errors. Depending on the transport type, the following actions may be available:

• Refresh TOD or Discover responders — updates the list of connected responders.
• Full rediscovery — clears the cached device list and performs a complete scan.
• Capability scan — updates the supported RDM parameters for detected devices.
• Incremental discovery override — controls background discovery for Art-Net ports.
• Broadcast SET — sends a parameter value to multiple responders. Broadcast commands do not return confirmation from individual devices and must be used with caution.

When a responder is selected, the interface displays its manufacturer, model, UID, online status, DMX configuration, supported parameters, sensor information, network settings, and diagnostics. The available sections are Overview, DMX, Parameters, Sub-devices, Status & Sensors, Network, and Diagnostics.

Use Identify to activate or deactivate the device’s identification mode, Refresh capabilities to update its supported parameters, and Add to project to register the responder for configuration monitoring and layout diagnostics. The View RDM logs button opens log entries filtered for the selected device.

Registered project devices retain their expected route and DMX configuration. If the detected configuration changes or the device is moved, the tab highlights the difference between the expected and actual values. You can accept the current configuration, adjust the layout mapping, or remove the device from the project.

Actions that may interrupt DMX output, change network connectivity, or modify multiple devices require confirmation. While discovery is running on a port, responder operations on that port are temporarily unavailable.

5.5. Network tab

The Network tab shows the current network status of the controller and the connected Art-Net environment. It displays the controller’s LAN and Art-Net IP configuration, including whether each interface is using DHCP or a static address. The tab also shows the last update time and allows the user to manually refresh the network overview.

Below the summary, the tab lists all detected Art-Net devices. For each device, it shows the device name, IP address, short name, input and output universes, Net/Subnet values, firmware version, MAC address, bind IP, last seen time, and node report when available.

If no Art-Net devices are found, the tab indicates that no devices are currently reachable and suggests checking that the devices are powered on and connected to the Art-Net interface.

5.6. API tab

The API tab is service-oriented. It contains documentation on how commands can be sent to the controller from other devices, interfaces, applications, and so on using HTTP requests.

6.1. Top layouts panel

The very top of the page contains switching between different layouts.

• The + button creates a new layout.
• You can switch between layouts using the tabs.
• A layout name can be renamed by double-clicking the name.
• An unnecessary layout can be removed by clicking the cross.
• The Layout page should be viewed as a way to create new control zones, allowing scenes in each zone (Layout) to be switched independently.

6.2. Left Groups panel

• Search filters groups and pixels by group name and by x and y coordinates.
• Add group creates a new group.
• Expand all and Collapse all expand or collapse all group lists.
• Each group name can be changed.
• Each group has a delete button.
• Inside a group you can use Select all, Unselect, or delete the selected pixels in that group.

Groups should be treated as physical DMX bus connection groups. All fixtures are addressed automatically when added; the address can be changed on the Patch page.

6.3. Right Fixtures and Properties panel

The right panel is used to select the fixture type and view / edit the properties of selected pixels.

• In the Fixtures block, the fixture type is selected, for example White, RGB, RGBW, RGBCW, and other channel-order variants.
• In the Properties block, you can view the properties of the selected pixels.
• If one fixture is selected, you can usually change its Name.
• Coord. X and Coord. Y show the coordinates of the selected point.
• Type lets you change the type of the selected fixture or a group of selected fixtures.
• Address is displayed for reference but is edited on the Patch page.

6.4. Central workspace

The center of the page contains the main workspace where the fixture map is drawn.

• Grid sets the size of the working grid.
• Group defines which group new points will be added to.
• Tool switches between Draw (to add fixtures) and Select (to select fixtures).
• Fill, when enabled, automatically fills the selected area according to the pattern chosen on the right. When disabled, fixtures are added according to the mouse cursor position.
• Undo and Redo allow you to revert and restore actions.
• Center centers the workspace.
• Fullscreen expands the workspace to full screen.
• Clear Sel clears the current selection.
• Clear clears the layout.
• Export PNG saves the layout map as a PNG.
• The Channels indicator shows the total channel usage.
• The Image tool is used to move the layout background image on the grid.
• The Background selector adds an image from the File Manager as a layout reference background.
• Reload refreshes the list of available background images from the File Manager.
• When a background image is selected, Visible shows or hides it, and Lock prevents it from being moved accidentally.
• Opacity controls background transparency.
• W, H, X, and Y define the background image size and position on the grid.
• Fit scales and positions the background image to match the full grid.
• Clear Bg removes the background image from the current layout.
• Del Sel deletes the selected fixtures from the layout.
• The Pointer indicator shows the current cursor position on the grid.

6.5. Basic workflow in Layout

1. Create a new layout or select an existing one.
2. Create one or more groups for different site zones.
3. Select the required fixture type in the right Fixtures panel.
4. Select the active group in the Group field.
5. Switch to the Draw tool and place points on the grid.
6. If the placement needs correction, switch to Select, select the fixtures, and move them.
7. If necessary, adjust the names and types of selected fixtures in the Properties panel.
8. When finished, save the map using Export PNG if you need to share the scheme or keep it in the site archive.

6.6. Practical mouse and keyboard actions

• Mouse wheel or pinch changes the zoom.
• Middle mouse button or a two-finger gesture is used to move the workspace.
• In Draw mode, normal drawing adds fixtures to the grid.
• In Draw mode, deletion is done with Alt + drawing or the right mouse button.
• In Select mode, selecting an empty area creates a box selection.
• Shift helps add new points to the existing selection.
• Dragging selected fixtures moves them on the grid.
• Arrow keys move the selection, and Delete removes the selected points.
• Undo and Redo are best used immediately after a mistaken action instead of trying to restore everything manually.
• In Select mode, dragging an already selected fixture moves the whole selected set.
• In Select mode, dragging a non-selected fixture first selects it and then moves it.
• Shift + Arrow keys moves the selected fixtures by 10 grid cells.
• In Image mode, dragging with the left mouse button moves the layout background image.
• If the background image is locked, it cannot be moved until Lock is disabled.
• Clear Sel removes the current selection without deleting fixtures.
• Del Sel deletes only the selected fixtures.
• Clear deletes all fixtures from the current layout.

6.7. What to pay attention to

• Clear clears the current layout. Use it deliberately.
• Deleting a group is irreversible if you cannot restore it from a backup.
• If the system reports that the channel limit has been reached, reduce the number of active points or revise the layout structure.
• If you edit the layout on a live site, it is better to save a backup of the current project first

7.1. What the top bar shows

The top of the page displays short statistics for the current active group.

• Pixels shows the number of fixtures in the group.
• Used shows how many channels are occupied.
• Free shows how many channels are still available in the 1–512 range.

This line is especially useful when you need to quickly understand whether the group fits into a single 512-channel block and how much capacity remains.

7.2. Left Groups panel

The list of all groups available for patching is displayed on the left.

• The search field helps quickly find a group by name.
• Only one group can be active at a time.
• After selecting a group, its patch is displayed in the center and its output configuration on the right.

7.3. Central patching field

The central workspace shows the channel grid from 1 to 512. Each fixture or fixture segment occupies its own channel range in this grid.

• The Zoom slider changes the display scale.
• The blocks in the field correspond to fixtures in the selected group.
• The label on a block helps identify which fixture it is and which address it currently starts from.
• By dragging, a fixture can be reassigned to a different start address.

The easiest way to think about this screen is: you do not draw a layout here; you distribute already created fixtures across DMX / Art-Net channels.

7.4. How to change a fixture address

1. Select the required group on the left.
2. Find the required fixture or group segment in the field.
3. Hold the block and drag it to a new start address.
4. Release the block if the new position is correct.
5. After that, check that the fixture occupies the expected channel range.

If the new position overlaps with already occupied channels or goes beyond the allowed range, the interface will show a conflict, and that move cannot be considered correct.

7.5. Right Group configuration panel

The right panel defines where the selected group will be output.

• Output switches the output type: DMX or Artnet.
• If DMX is selected, you need to specify the DMX port.
• If Artnet is selected, you can enable or disable Broadcast.
• If broadcast is disabled, you need to fill in the IP address.
• For Art-Net, the Universe is also specified.

7.6. Recommended workflow in Patch

1. First prepare the groups and fixtures in Layout.
2. Open Patch and select the required group on the left.
3. Configure the group's output type: DMX or Artnet.
4. If it is DMX, select the correct physical port.
5. If it is Art-Net, set broadcast or unicast, IP address, and universe.
6. Arrange the fixtures by addresses within the 1–512 grid.
7. Check that there are no overlaps and that the number of used channels looks expected.
8. When finished, if necessary, go to Dashboard -> DMX Out and verify that the signal is going to the correct channel / output.

7.7. What to pay attention to

• If the group contains many fixtures, it is convenient to first estimate the total channel consumption using the top statistics.
• If the site uses Art-Net unicast, do not forget to disable broadcast and set the IP address.
• If a fixture does not respond after patching, first check the Patch page, and only then move on to the physical line and the fixture itself.
• After changes in the patch, it is convenient to verify the picture on Dashboard -> DMX Out.

8.1. Top control bar

The top part of the page is responsible for launching and organizing timelines.

• The current time position is displayed on the left.
• Play/Pause starts and stops playback of the active timeline in the engineer's browser, so you can understand how the effects will work.
• Home returns the playback pointer to the beginning.
• Bake rebuilds timelines after changes.
• Loop enables looping for the active timeline.
• The + button creates a new timeline, and the tabs at the top let you switch between timelines, rename them, reorder them, and delete unnecessary ones.

8.2. Left Library panel

The content library that can be used in the timeline is located on the left.

• Media upload uploads video and audio files.
• Files in the list can be dragged onto tracks in the center area.
• Each file shows its name and duration, so it is easy to verify the required material right away.
• Unneeded files can be removed from the library with the delete button.
• Below is the Effects list, which can also be dragged onto tracks.

8.3. Central Timeline area

The center contains the main time scale with tracks. This is the workspace where you place clips in time.

• At the top there is a time ruler and the current position indicator.
• The Zoom slider changes the scale and helps you work more accurately with short or long clips.
• Below are the video and audio tracks, where you can drag files and effects from the library.
• A clip on a track can be moved in time, and its right edge can be trimmed if you need to change its duration.
• Clicking a clip selects it for precise adjustment on the right in Inspector.

8.4. Right Preview, Properties, and Inspector panel

The right column helps you verify what is currently playing in the engineer's browser and precisely configure the active timeline or selected clip.

• Preview shows the material under the playhead and any overlaid effects.
• The Properties block sets the general timeline parameters: Sync, Layout, Fade in, Fade out, Length, and Auto trim.
• Sync lets you choose internal time or synchronization via Art-Net TimeCode.
• Layout defines which fixture layout the current timeline will work with.
• In the Inspector block for the selected clip, the following fields are available: Kind, Track, File / Effect, Start, Dur, Fade in, and Fade out.
• If an effect is selected, you can also configure Color, Intensity, and Speed Hz here.
• The Delete button removes the selected clip, and Jump quickly moves the pointer to its position on the time scale.

8.5. Recommended workflow in Timeline

1. Open the required timeline or create a new one with the + button.
2. In Properties, select the correct Layout for this scenario.
3. If synchronization with an external time source is needed, configure the Sync field.
4. Upload media files via Media upload if they have not yet been added to the library.
5. Drag files and effects to the required tracks.
6. Check clip positions in time, durations, and fade parameters.
7. After changes, click Bake and wait until all timeline files are baked.
8. Run a test via Play and make sure that both preview and the real light behave as expected.

8.6. What to pay attention to

• If the site must work by external timecode, do not accidentally leave Internal time enabled.
• If the wrong Layout is selected, the playback result may not match the actual layout on the site.
• After noticeable edits to clips, effects, or timeline order, it is better to run Bake again.
• If it seems during verification that nothing is happening, first check which timeline is active and where the time pointer currently is.

9.1. What the top bar shows

The top of the page displays a short summary of the triggers.

• Total shows the total number of triggers.
• Active shows how many triggers are currently enabled.
• If changes are being saved, the Saving... status may appear at the top.

9.2. Left Triggers panel

The list of all created triggers is located on the left.

• The + button adds a new trigger.
• Clicking a list item opens its configuration in the center and on the right.
• Each trigger in the list shows its name, a short event summary, and the number of actions.
• The Run button allows you to manually test the trigger without waiting for an external event.
• You can drag triggers with the mouse to change the list order.

9.3. Central Event block

The central part of the page is responsible for the condition under which the trigger should fire.

Depending on the selected Event Type, additional setup fields appear.

For Sync Play, the Sync key field is used to match controllers that should react to the same synchronized playback event.

• Name sets a clear trigger name.
• Enable turns the trigger on or off.
• Description is convenient for explaining the logic on the site.
• Event Type defines which event should activate the trigger.

Depending on the selected Event Type, additional setup fields appear.

• Soft: manual or software launch without an external input.
• Controller Start: launch when the controller starts.
• Timeline Started and Timeline Finished: react to the start or completion of the selected timeline.
• Sync Play: react to a synchronized playback signal from another controller with the selected Sync key.
• Ethernet Input: react to incoming TCP/UDP data with socket selection and filters.
• RS232 Input: react to a line received on the selected RS232 port.
• Digital Input: react to the state of a digital input with port and level selection.

The easiest way to think about this block is: first you define what should happen, and then on the right you configure what the controller should do in response.

9.4. Right Actions panel

The right column defines which actions are executed after the trigger fires.

• At the top, the type of a new action is selected, and it is added to the chain with the Add action button.
• Each action can be individually enabled or disabled via Enabled.
• The Delay field sets a delay before the action is executed.
• An unnecessary action is removed with the Delete button.

The following actions are available on the page:

• Start Trigger: launch another trigger.
• Start Timeline: launch the selected timeline.
• Start Sync Timeline: launch the selected timeline in synchronized playback mode using the specified Sync key.
• Pause Layout, Resume Layout, Stop Layout: control the selected layout.
• Send Ethernet: send a command via TCP or UDP, specifying the socket, host, port, and string.
• RS232 Output: send a string to the selected RS232 port.
• Digital Output: output a logic level to the selected digital output.

9.5. Recommended workflow in Triggers

1. First prepare what the trigger will refer to: Timeline, Layout, RS232, and network sockets.
2. Create a new trigger with the + button.
3. Set a clear name and, if necessary, a short description.
4. Select the required Event Type and fill in the event parameters.
5. In the right panel, add one or more actions via Add action.
6. For each action, check the type, enabled state, and Delay.
7. Enable the trigger via Enable.
8. Run a test with the Run button and make sure the reaction on the site matches the task.

9.6. What to pay attention to

• If a trigger should react to the network, the required TCP/UDP socket must be configured in Network in advance.
• If a trigger starts a timeline, first make sure the timeline itself is prepared and Bake has been executed if necessary.
• If a trigger works via RS232 or Digital Input, verify the correct port selection and level logic.
• The Run button is convenient for commissioning, but after testing it is still worth checking the real external event separately if the trigger is supposed to work automatically.

10.1. Calendar top bar

The upper part of the page helps you quickly switch between view modes and periods.

• View shows the current view mode.
• The Month, Week, and Year buttons switch the calendar display.
• The <<, Today, and >> buttons let you move to the required period.

10.2. Central calendar area

The center displays the calendar grid for the selected period.

• In Month mode it is convenient to see the general picture by date.
• In Week mode it is easier to verify events by time of day.
• In Year mode it is convenient to jump quickly by month.
• Using the day view and edit windows, you can move an event to the required time.

10.3. Right All Events panel

The full list of events is shown on the right, regardless of the selected period.

• The Add Event button creates a new event.
• Clicking an event card opens it for editing.
• The Run button lets you test the event manually.
• The card shows the name, a short description of recurrence, and related bindings.

10.4. Event Settings window

This is the main working window of the calendar. Here you define the event name, trigger logic, recurrence, exceptions, and bindings to soft triggers and UI buttons.

These screenshots already show the main editor scenarios: a one-time event, standard recurrence, quick recurrence presets, advanced rules, and astronomical mode. Each of them is described separately below.

10.5. Recommended workflow in Calendar

1. First prepare the timelines, triggers, and UI buttons if the event needs them.
2. Click Add Event and set the event name.
3. Select the schedule type and fill in the date, time, and recurrence.
4. If the event should launch something in the system, add the required bindings in the Triggers & UI buttons block.
5. Save the event via Create or Save.
6. Check the result with the Run button and then wait for the real trigger time.

10.6. What to pay attention to

• Scheduling depends on correct time and time-zone settings in Controller.
• If recurrence is used, make sure the RRULE is correct and does not conflict with EXDATE exceptions.
• If the event is linked to a soft trigger or UI button, the corresponding binding must exist and be configured correctly.
• Manual Run is useful for checking logic, but it does not replace verification of a real calendar-based trigger.

11.1. General tab

The General tab is responsible for the overall appearance of the interface.

• In the Theme section, you can quickly apply a ready-made color preset.
• The Branding block sets the Logo Installer, Logo Customer, and Name Customer.
• The Screen Background field selects the image or video used as the interface background.
• The selected background is shown in the Application and in the Preview window.
• Background media is selected from the File Manager media library.
• The Navigation block sets the Home screen, All zones screen and RDM diagnostic screen.
• In the Colors block, the main interface colors are set.
• The Component styles section configures the global look of action, switch, and zone-card buttons.
• The Refresh all buttons button applies the global styles to the buttons.

11.2. Screens & Buttons tab

The Screens & Buttons tab is used for the structure of screens and buttons.

• The screen list and the + Add screen button are on the left.

• A screen can have the special roles Home and All Zones.

• The selected screen and its button list are edited in the center.

• Buttons can be expanded, collapsed, and reordered by dragging.

• The + Add button button adds a new button to the selected screen.

• The selected screen has a Screen name field and a Trigger group field.

• The Trigger group is used to group Action buttons for active button state logic.

• The Apply to Action buttons button applies the selected screen Trigger group to all Action buttons on that screen.

• Buttons can be one of three types: Action, Switch, or Zone card.

• Action buttons can be assigned to a Trigger group and a Trigger, and can be tested with the Test button.

• Switch buttons can be assigned separate On trigger and Off trigger actions, and can be tested with Test ON and Test OFF.

• Zone card buttons are used for navigation and can be linked to a Target screen.

• Each button row shows the button type, binding or destination, and its position in the list.

• Buttons and screens can be deleted with confirmation.

Trigger group defines which Action buttons share the same active state.

When an Action button is pressed in the application, its assigned trigger runs first. If it runs successfully, the button becomes active within its Trigger group.

Only one Action button can be active in the same Trigger group. Pressing another Action button in that group moves the active state to the new button. Buttons from different Trigger groups work independently.

Each screen has a Trigger group field, used as the default group for Action buttons on that screen. Each Action button can also have its own Trigger group. The Apply to Action buttons button copies the screen Trigger group to all Action buttons on the selected screen.

Switch buttons and Zone card buttons do not use Trigger group logic. Switch buttons use separate On trigger and Off trigger actions, and Zone card buttons are used for navigation between screens.

11.3. Button configuration

Each button has a type and a binding.

• Label sets the button caption.
• The Type field switches the button type: Action, Switch, or Zone card.
• For Zone card, the Target screen is selected.
• For Action, one Trigger is selected.
• For Action, the Trigger group field defines which Action buttons share the same active state.
• By default, a new Action button uses the Trigger group from its screen. This value is generated automatically for a new screen and can be changed manually.
• Action buttons with the same Trigger group work as one group: when one button becomes active, the previous active button in that group is no longer active.
• Action buttons from different Trigger groups are independent.
• For Switch, the On trigger and Off trigger are set.
• Switch buttons and Zone card buttons do not use Trigger group logic.
• In the Style block, the button icon and visual design are configured.
• Using the Test, Test ON, and Test OFF buttons, you can immediately verify linked triggers.

11.4. Preview window

On the right, Preview shows the user interface the way operations staff will see it.

• The preview can be switched between different device presets.
• The selected device preset changes the preview size, so you can check how the interface looks on different phone screen types.
• After saving changes, the preview updates, so it is convenient to immediately control the final look and navigation.

11.5. Recommended workflow in User interface

1. First prepare the triggers that will be called by the buttons.
2. In the General tab, set branding, colors, and global styles.
3. In the Screens & Buttons tab, create the required screens.
4. Add buttons and choose their type.
5. Link the required triggers or target screens.
6. Check the result in Preview and run button tests.

11.6. What to pay attention to

• If no trigger is selected for a button, it may not perform the expected action in the user interface.
• For Switch toggles, you need to fill in both On trigger and Off trigger if both states should work.
• If you do not select a Home screen, the initial navigation may be inconvenient for operations staff.
• After major changes, it is useful to check not only the appearance but also the real execution of the buttons using the built-in tests.

12.1. Controller

This is the main tab for the initial controller setup. The engineer usually works here first.

12.2. Users

The Users tab is not directly related to light calibration, but it may be needed during site handover when access has to be passed to operations staff.

12.3. Settings screen: Network

12.4. RGBW Calibration

This is the key tab for setting the correct white for RGBW and RGBCW fixtures. It is best to work with it once the network is already configured, the fixtures are connected, and you understand the addressing scheme.

12.5. Firmware

The Firmware tab is used for service verification of a new firmware version and to start an update or rollback.

12.6. Cloud

• Pairing Code is entered when connecting the controller to a cloud account.
• The Pair button links the local controller with the cloud using the entered pairing code.
• Cloud URL shows the cloud server address.
• Customer UI Sync controls whether the local customer ui configuration can be updated automatically from the cloud.
• Calendar Sync controls whether the local calendar can be updated automatically from the cloud.
• Conflict Rule defines what should happen when the cloud calendar and local controller calendar have different versions.
• Cloud wins automatically uses the cloud calendar version.
• Controller wins automatically keeps the local controller calendar version and sends it to the cloud.
• Ask when versions differ shows a conflict warning and lets the user choose which version to keep.
• Pull cloud to local replaces the local controller calendar with the cloud calendar.
• Push local to cloud replaces the cloud calendar with the local controller calendar.
• Disable pairing disconnects the controller from the cloud and stops cloud synchronization.

13.1. About PWA Technology

The PROMIN customer application is a Progressive Web App (PWA). A PWA is opened through a web browser but can be installed on the phone and used like a regular mobile application.

After installation, the application:

• Appears as a PROMIN icon on the Home Screen.
• Opens in a separate full-screen window.
• Does not require installation from the App Store or Google Play.
• Receives interface updates automatically.
• Provides quick access to the controller’s customer interface.

The phone must have network access to the controller for monitoring and control functions to work.

You can watch a video on how to make it on the Promin youtube channel. https://www.youtube.com/@promincontrol

13.2. Installation on iPhone

1. Connect the iPhone to a network that provides access to the controller.
2. Open Safari.
3. Enter the customer interface address provided by the installer using this format: http://<controller-ip-address>/customer/ (replace <controller-ip-address> with the actual address).
4. Wait until the customer interface opens completely.
5. Tap the Share button in Safari.
6. Scroll down and select Add to Home Screen.
7. Enable Open as Web App, if this option is displayed.
8. Check the application name and tap Add.
9. Return to the Home Screen and tap the PROMIN icon to open the application.

If Add to Home Screen is not displayed, scroll to the bottom of the Share menu, select Edit Actions, and add it to the available actions. These steps follow Apple’s current procedure for installing web apps on iPhone. Apple Support

13.3. Installation on Android

1. Connect the Android phone to a network that provides access to the controller.
2. Open Google Chrome.
3. Enter the customer interface address provided by the installer using this format: http://<controller-ip-address>/customer/ (replace <controller-ip-address> with the actual address).
4. Wait until the customer interface opens completely.
5. Tap the three-dot menu in Chrome.
6. Select Add to Home screen and then tap Install. On some Chrome versions, the command may appear directly as an Install app.
7. Confirm the installation.
8. Return to the Home Screen or application list and tap the PROMIN icon.

The installed PWA can be opened and managed similarly to a regular Android application. Google Chrome Help

13.4. Installation on Windows

The customer application can be installed on a Windows computer using Microsoft Edge or Google Chrome.