CLOUD email notifications: setup and test
CLOUD email notifications: setup and test
480 × 320 display screens in the selected language. The yellow outline marks where to tap. Illustrated data is for demonstration.
Configure the network first and verify the controller portal/cloud connection. SMTP delivery must be configured in the portal. Use your own Administrator or Service PIN and recipient address; alarm@example.com is only an example. Controller access codes →
If the controller asks for a PIN
Enter your PIN on the display and confirm with OK. Use an account authorised for settings. Email CLOUD requires Administrator or Service access. If already signed in, continue to the next menu screen. Controller access codes →
In METRO, the PIN window retains its original appearance. Controller access codes →
-
1Step 1 / 16
Open MENU and sign in with your PIN
Tap the menu icon in the upper right. If prompted for a PIN, use your own Administrator or Service account. Only these roles can access E-mail CLOUD. Controller access codes →
-
2Step 2 / 16
Open the second menu page
On the first menu page, press the right arrow in the top bar.
-
3Step 3 / 16
Open “Settings”
Tap the Settings tile in the lower left.
-
4Step 4 / 16
Go to the next settings page
Press the right arrow in the top bar. Do not select Network here; the network connection should already be configured.
-
5Step 5 / 16
Open the next settings page
Press the right arrow again. A Service account goes directly to the E-mail CLOUD page. An Administrator first sees the page shown in the next step.
-
6Step 6 / 16
Administrator: press right once more
As Administrator, press the right arrow once more. If E-mail CLOUD is already visible, continue to the next step. Do not activate the other functions on this page.
-
7Step 7 / 16
Open “E-mail CLOUD”
Tap E-mail CLOUD in the lower right. If it is missing, check that the PIN session is active and that you are using an Administrator or Service account. Controller access codes →
-
8Step 8 / 16
Enter the recipient address
Tap the wide address field and enter one recipient mailbox address. This is not a form for the sender SMTP account.
-
9Step 9 / 16
Type the email and confirm with OK
Enter your own recipient address; the example shows alarm@example.com. The symbol key at the bottom provides characters such as @. Finish with OK in the lower right and check the spelling after returning.
-
10Step 10 / 16
Set event notifications to Enabled
The upper-left button should show Enabled, as illustrated. If it shows Disabled, tap it once. This switch controls events; reports after tests have a separate setting.
-
11Step 11 / 16
Choose the notification condition
The upper-right button cycles through conditions. The example uses Faults and emergency. Other choices are luminaire/communication faults, a running test, emergency mode alone or All healthy.
-
12Step 12 / 16
Choose when to notify
Tap the wide button below the address until the desired method appears. The example Activation and recovery reports both the start and end of the condition. On activation reports only its start; Also reminders adds repeat notifications.
-
13Step 13 / 16
Optionally enable reports after tests
Tap Report after test to choose ON or OFF. This setting is independent of the event switch. Enabling it sends new reports; existing archived reports are not sent again.
-
14Step 14 / 16
Save the configuration
Check the recipient and selected options, then press Save. Back does not save changes. Stable condition displays the condition confirmation delay and is not editable on this screen.
-
15Step 15 / 16
Run CLOUD test after saving
After Configuration saved, press CLOUD test. If Save configuration first appears, save the current settings and repeat the test.
-
16Step 16 / 16
Check the recipient inbox
Test queued for portal processing confirms the test request, not email delivery. Check the recipient inbox and spam folder. If no message arrives, check the address, portal connection and the portal mail-sending configuration.
Setup is complete after saving the settings and checking an actual message in the recipient inbox. A CLOUD queue acknowledgment is not a delivery test. Back leaves the screen without saving further edits.