Velomodo Admin

Help & Guides

How to operate clusters and pods from the admin portal.

Who can do what

Two kinds of administrator can sign in here, and they see different things:

Velomodo admin
Full access to every cluster and every operation, including configuration policies, diagnostics, reservation overrides, gap resets, and picture uploads.
Cluster (device) admin
Can manage the specific clusters they have access to: view live status, view and filter system events, view the reservation list, restart/shutdown the cluster, and set the admin status of the cluster and its pods. Velomodo-only actions (Configuration, Diagnostics, cancelling/completing reservations, picture upload) return a “Velomodo admin access required” message.

If you open a cluster you don’t have access to, the portal shows an Access denied screen rather than a generic error — that means your account isn’t permitted for that cluster, not that something is broken.

Setting admin status

Admin status controls whether a cluster or pod is offered to riders, independent of whether the hardware is online. Open it from the Admin button on the cluster card, or the Admin control on any pod card.

Online
Available for reservations and access. The normal operating state.
Maintenance
Temporarily unavailable for scheduled maintenance. Use when you plan to bring it back soon.
Offline
Disabled and unavailable for use. Use when a unit should not be rented at all.

When you change a status you can add an optional reason — it’s recorded in the system event log so other operators understand why. Cluster-level status applies to the whole station; pod-level status affects just one pod.

Note: a pod also reports its own device health (online / degraded / offline). That’s separate from admin status — admin status is the availability decision you control; device status is what the hardware reports.

Restart & shutdown

The cluster card has two operational commands sent directly to the device:

Restart
Reboots the cluster controller. Use for an unresponsive cluster or after a configuration change that needs a restart. The cluster is briefly unreachable while it comes back.
Shutdown
Powers the cluster down. It will stay offline until it’s physically powered back on, so only use this when you intend to take the station out of service.

Both commands ask for confirmation first. They affect the hardware — they don’t change admin status, so set the cluster to Offline or Maintenance separately if you also want to stop new reservations.

Cluster details & location

The same dialog used for admin status also edits the cluster’s public-facing details: name, description, address, contact phone, and the detail picture shown in the rider app. Leave a field blank to clear it.

Detail picture
Upload a JPEG, PNG, or WebP (max 5 MB). It’s stored and shown on the cluster’s detail screen in the app.
Location override
By default the map position comes from the device’s GPS. Enter a latitude/longitude to pin it manually (useful when GPS drifts indoors). While an override is active you’ll see an “Admin override” badge; click “Reset to device GPS” to go back to the reported position.

Reservations

The reservation list on the cluster page shows every reservation for that cluster across all riders, with status (active, pending, completed, cancelled) and who holds it.

Cancelling or completing a reservation on a rider’s behalf is a Velomodo-admin override. If you’re a cluster admin those buttons will return a permission message — that’s expected.

System event logs

System events are the audit log of everything that happened to a cluster or pod — status changes, door events, connectivity, reservations, and internal sequence events. Open them from System events on the cluster card (whole cluster) or on a pod card (just that pod). Times are shown in your local timezone, newest first.

Date range
Pick a preset (e.g. last hour, last 24 hours) or choose “Custom” to set an exact start and end.
Event types
Use the type filter to narrow to specific events (e.g. only door or only admin events). Selecting none shows all types.
sequence.ready
These high-frequency internal events are hidden by default. Tick them in the type filter if you need to see raw telemetry sequencing.
Cluster-level only
On the cluster view, hides per-pod events so you only see cluster-wide ones.

Use “Load more” to page back further in time.

Reading diagnostics

Diagnostics is a live, read-only snapshot of the three back-end services for a cluster. It has a tab for each. Toggle “Raw JSON” on any tab to see the underlying state verbatim.

Reconciliation
Tracks the data sequence from each device. A gap means some sequence numbers didn’t arrive, so newer records are buffered (held back) until the missing ones come in. “Devices with gaps” and “Buffered records” should normally be zero. If a gap is stale and will never fill, Reset all gaps advances past it and drops the buffered records — this can’t be undone.
State
The current cluster and per-pod state (door, light, occupancy, admin status, last motion). Relearn pod #s clears pod index assignments so the next device report re-numbers them — use it to fix wrong or duplicated pod numbers.
Reservation
The active reservation policy, current reservations, and holds (short-lived locks placed while a rider is booking).

Configuration

Configuration (Velomodo admin only) sets per-cluster policies, grouped into three tabs. Edited fields are highlighted and marked “changed” until you save; each tab can be reset to the system defaults.

Reservations
Booking rules: min/max duration, how far ahead riders can book, holds, early access, slot increments, turnover buffer, and the geo-unlock radius.
State
Battery low/critical thresholds, event retention and archival, aggregation push cadence, and how long without data before a cluster or pod is considered offline.
Reconciliation
How sequence gaps are handled (timeout, check interval, max buffered records, auto-skip) and raw-data archival settings.

Hover the ? next to any field in the Configuration and Diagnostics dialogs for a one-line explanation of that specific setting.