Cloud & Device Connectivity

Central heartbeat, Device availability and Edge synchronization

Sentinel Admin

S

Registered Devices{{ stats.devices }}known Edge nodes

Online{{ stats.online }}heartbeat received

Offline{{ stats.offline }}after {{ heartbeat_grace_seconds }} s grace

Cloud measurements{{ stats.synced_measurements }}synchronized records

Device fleet

Edge nodes and connectivity status

{% if devices %}

{% for d in devices %}{% endfor %}

Status	Equipment	Device	Site	Edge version	Last heartbeat	Interval
{{ 'ONLINE' if d.online else 'OFFLINE' }}	{{ d.equipment_id }}	{{ d.device_id }}	{{ d.site_code or '—' }}	{{ d.edge_version or '—' }}	{{ d.last_heartbeat_at or 'Never' }}	{{ d.heartbeat_interval_seconds }} s

{% else %}

No Cloud Device registered yet. The Edge agent will appear here after its first registration.

{% endif %}

Connectivity event history

DEVICE_REGISTERED · DEVICE_OFFLINE · DEVICE_ONLINE

{% if events %}

{% for e in events %}{% endfor %}

Time	Event	Equipment	Device	Detail
{{ e.occurred_at }}	{{ e.event_type }}	{{ e.equipment_id or '—' }}	{{ e.device_id }}	{{ e.detail }}

{% else %}

No connectivity event yet.

{% endif %}

Power-loss policyNo internal UPS required. Missing heartbeat triggers Device Offline after the grace period. Edge buffering applies only while the Pi remains powered.