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 another page.
• Configure toast position, duration, and automatic dismissal in Settings.

These toasts are part of the open dashboard, not a promise of browser push notifications after the tab is closed.

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 host, port, path, username, and password, then test and save the connection.
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.

The dashboard keeps non-secret MQTT metadata in browser-local storage and the password in tab-scoped session storage. Credentials are sent transiently for authenticated connection tests and commands, not stored in the Notificator account database. A new browser session may need the password again. Settings saved in the mobile app are not automatically copied into the browser.

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, and dashboard toast preferences. The email preference belongs to the shared account; dashboard toast preferences belong to the browser experience.

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.