Web Dashboard (Beta)

The Notificator web dashboard is an alternative to the mobile app for everyday account and integration tasks. It uses the same account, notifications, API keys, and device records as the app. It is currently a beta.

Get started

1. Open the dashboard and choose Create an account, or sign in with your existing Notificator credentials.
2. Complete email confirmation or the MFA challenge when requested.
3. Open API keys and create a key matching your integration: WordPress, Strapi, or Public API / Node.js SDK (also used by Astro).
4. Store that key in the integration’s server-side settings or environment.
5. Send a test event from the integration and open Notifications.

You do not need to install the mobile app to complete these steps. For mobile push, install the app, sign in to the same account, and grant notification permission. The dashboard does not replace the app as a mobile push receiver.

Notifications

• Review account activity on Overview, or search and filter the full list.
• Open an alert to read its message, useful fields, and raw payload. Opening an unread notification marks it as read; you can mark it unread again.
• Lock important alerts to protect them from deletion. Delete all leaves locked alerts untouched.
• Visible dashboard pages refresh account data periodically without a full page reload. In-dashboard toasts show new alerts while you use the dashboard.
• Configure toast position, duration, and automatic dismissal in Settings.
• Enable Browser notifications in Settings to receive native alerts when the dashboard is in another tab or window.

Browser notifications

Open Settings → Browser notifications, choose Enable browser notifications, and allow notifications when the browser asks. Use Send test notification to confirm that the browser and operating system allow delivery. If permission is blocked, change the notification setting for the dashboard in the browser or operating-system settings and enable the option again.

Browser notifications are delivered only for new alerts while the dashboard is hidden or unfocused. Existing alerts are not replayed. When the dashboard is active, in-dashboard toasts remain available, and they also remain the fallback when native notifications are unsupported or blocked. Permission and preference data stay in the current browser; no notification subscription is stored in the Notificator account.

API keys

Open API keys to create, inspect, edit, copy, or revoke integration keys. The list includes the last-used timestamp when available and supports filtering active and revoked keys. Use separate keys for each integration and environment.

See Create an API Key for key types and usage. Notificator integration keys are secrets, unlike the public Supabase configuration used to load the dashboard.

Connected devices and MQTT

1. In Settings → Device connection, enter your HiveMQ Cloud hostname, username, password, and topic prefix. Test the connection, choose where to save it as described below, and save. Secure WebSocket port 8884 and path /mqtt are configured automatically.
2. Open Devices to add a supported device using its ID and correct type.
3. With a valid browser MQTT connection, the dashboard automatically refreshes active-device status from the retained broker messages.
4. Open a device to edit supported settings, check its reported firmware, or request a signed OTA update for Base or Touch.

You can pause and resume a device, and remove a paused device from your account. Removing a device record is not a hardware factory reset.

Device commands also need an active compatible account API key. Status can be unknown or stale when the device or broker cannot be reached; an open dashboard is not an independent uptime-monitoring service.

Choose where to save MQTT credentials

Session-only storage is the default. Non-secret metadata stays in browser-local storage and the password stays in the current tab session. Credentials are sent transiently for authenticated tests and commands. Test connection does not save the form; select a save button after a successful test.

Where enabled, Save to my account stores an encrypted copy of the complete configuration in your Notificator account. Select the option and save to use it. When you open the dashboard in another signed-in browser, it can restore the saved connection automatically. An existing session connection takes priority. Restoration does not block the page from loading.

• Save for session keeps the password in this tab session only. Uncheck Save to my account and save to remove an existing account copy and switch back to session-only storage.
• Remove account copy deletes the saved database configuration and leaves the current session connection usable.
• Clear session removes the local connection and prevents automatic restore for the rest of that tab session. A saved account copy remains available for future sessions.
• Signing out clears MQTT session data. Removing an account copy does not erase copies already held by other clients. Change the credentials at HiveMQ to revoke those copies.

Account encryption is managed by trusted Notificator servers, which decrypt the configuration after authorizing access. It is not end-to-end encryption. If account saving is unavailable, session-only saving still works.

The account configuration can be used by the hosted API for authenticated WordPress delivery. When an enabled wordpress_server API key belongs to the same account, the plugin can reuse the saved connection without receiving the broker password. The mobile app continues to use its own secure connection storage. Saving credentials in the mobile app does not automatically save them to your Notificator account.

See MQTT Broker Setup for broker credentials and Firmware Updates for model-specific OTA channels. Live screen-brightness and Touch-volume controls remain mobile-app features.

Account preferences

Use Account for profile and account controls, and Settings for the email delivery preference, browser MQTT connection, dashboard toast preferences, and browser notification preferences. The email preference belongs to the shared account; dashboard toast preferences belong to the browser experience.

Account and security

Open Account to manage the identity shared by the dashboard and mobile app:

• Update your first and last name and review the account email address.
• Request an email change. Supabase sends confirmation links to the existing and new address; the new address becomes active only after confirmation.
• Change the password by entering the current password and confirming the new password. A current password is required before the update is accepted.
• Enable 2FA to enroll a TOTP authenticator. Scan the QR code, or enter the displayed setup key manually, then enter the six-digit code from the app.
• Disable 2FA from the same panel after confirming the action.

The dashboard and mobile app use the same Supabase account and MFA factors. Keep an authenticator available before removing 2FA, and never share the setup key or verification codes.

Local admin activity is different

Local WordPress dashboard alerts and Strapi panel activity require no Notificator account or API key. They remain inside those administration panels. To see an event in the Notificator web inbox, configure connected delivery using an API key.