1) What is Volteec?

Volteec is a read-only UPS status viewer for iPhone and iPad. It connects to your self-hosted Volteec Backend to show UPS status and last known state.

2) Do I need an account?

No. Volteec does not require a Volteec account by default. You connect the app to your own backend using a server URL and an API token.

3) Where does my UPS data live?

Your UPS data lives on your backend (self-hosted) and is cached locally on your device for quick viewing. Volteec does not control your backend database.

4) What do I need to connect the app?

You need a reachable backend server URL and the exact API token configured on your backend. Paste the token only (no “Bearer” prefix). The app adds the Authorization header automatically.

5) Is Volteec read-only?

Yes. Volteec is designed as a viewer. It does not control your UPS or perform remote actions on your infrastructure.

6) Does Volteec support push notifications?

Yes, optionally. Push requires Relay credentials configured in the backend. If you do not have Relay credentials, the backend still works, but push is disabled.

Relay credentials are generated in the Volteec app (Settings → Help Center → How to Connect → Resources → Relay Credentials) and cannot be generated locally.

7) What is the difference between “healthy” and “ready”?

Healthy means the backend process is running (/health returns ok). Ready means the backend is ready to serve the API (database available + migrations applied + API token set).

If API_TOKEN is missing, the backend runs in degraded mode: /health still works, but versioned API routes are disabled.

8) /health works in Safari, but the app fails to connect

Common causes include: your phone is not on the same LAN/Wi‑Fi, a firewall blocks the backend port, you used localhost from the phone, or the token is invalid.

9) I get “Something went wrong” when calling the API

This usually means database migrations were not run yet. Run migrations using the backend repo instructions (Docker Compose migration step) and try again.

10) Backend starts, but NUT times out (Docker)

On many NUT installations, upsd listens only on 127.0.0.1:3493, so Docker cannot reach it directly. A common fix is an SSH tunnel to the NUT host, then set NUT_HOST=host.docker.internal and NUT_PORT=3493.

11) How do I find the UPS name(s) for NUT_UPS?

Use the NUT client tool to list UPS names (for example: upsc -l localhost on the NUT host). The UPS names must match what your NUT server reports.

12) Does the backend support SNMP?

Current backend scope is NUT polling. SNMP support is planned but deferred.