App Settings Guide

Use this page as a practical map of mobile settings after onboarding.

Profile and security

Recommended:

Keep profile info up to date.
Enable Two-Factor Authentication (2FA).
Review active sessions/devices when available.

Notifications

Check these first:

Device push enabled for current device.
Notification permissions allowed by OS.
Email notification preference as desired. This is an account-level delivery preference controlled in the app, separate from the mobile push permission granted by iOS or Android.

API keys management

From Profile -> API Keys:

Create separate keys per integration.
Select key type when creating a key:
- WordPress for plugin/server workflow
- Public API for public-notify
- Internal for trusted backend automation
Rename keys with clear environment labels.
Revoke old or unused keys.

Each active key card also shows:

Key type
Last used timestamp
Allowed domains count

Device connection

Notificator does not provide a default MQTT broker. To send commands to a Notificator Base or Touch device:

Open Account → Device connection.
Expand HiveMQ Cloud.
Enter the hostname and mobile publisher credential from your HiveMQ Cloud cluster.
Use the same topic prefix configured in WordPress and on the device. New setups default to notificator-project.
Select Test connection. A successful result confirms the cluster and credentials before anything is saved.
Select Save connection.

The connection is stored only in the operating system’s secure credential store on that phone. It is sent transiently to the API when delivering a command and is never stored in Supabase. Use Remove to delete it, or Clear Data & Sign Out to remove it together with the other local account data.

The connection test uses the values currently shown in the form. It opens a short-lived secure WebSocket connection through the authenticated Notificator API, then disconnects. The test does not save the values, publish an alert, or require an existing device.

See MQTT Broker Setup for HiveMQ Cloud setup and credential permissions.

Device controls

Open a saved device to configure the controls supported by that model:

Notificator Base: idle mode, weather location and timezone, and display brightness.
Notificator Touch: idle mode, weather location and timezone, display brightness, and sound volume.

The app sends these controls through the HiveMQ connection stored on the phone. If a save succeeds but live settings cannot be delivered, verify the device is online and recheck the publisher username and password under Device connection.

For weather, enter a city, area, or postal code and select the intended match. The app fills the coordinates internally so users do not normally need to find or type latitude and longitude. Manual coordinates remain under Advanced location for unusual or ambiguous places. Location search uses Open-Meteo with GeoNames place data and does not request continuous device location.

Home and UI preferences

Common settings include:

Theme selection.
Language selection.
Visibility toggles for home widgets.

Suggested baseline:

Show Active Devices = ON
Show Recent Notifications = ON
Keep only widgets you use frequently.

Diagnostics checklist

If notifications do not arrive:

Confirm app push permission in device settings.
Confirm push toggle for current device.
Confirm user is signed into correct account.
Send a test notification from plugin/API.
For device commands, confirm Account → Device connection is configured and uses the same cluster and topic prefix as the device. Use Test connection to check the unsaved hostname, username, and password first.

Email alerts do not require MQTT. Confirm the email preference is enabled and that the verified address on the account is correct. Mobile push and email can be enabled independently.