DISTRESS SIGNAL BRIDGE

METSUKA

bridge up0 signals today

BUTTONS · FIELD SIDE

where distress signals come from

▶ SEND A TEST SIGNAL

Acts exactly like a real button press. The signal will cross the bridge and appear in the traffic list below.

DEVICES0

Every button that ever sent a signal shows up here automatically.

none yet

SYNCH · OPERATIVE SIDE

where distress events get handled — synchapp.io

Connection to Synch
TEST MODE

No Synch credentials yet. The bridge builds the exact request it would send and logs it — but nothing is really sent. Add SYNCH_API_TOKEN + SYNCH_ORG_ID to .env.local to go live.

last send: nothing sent yet
0
SENT TO SYNCH
0
CONFIRMED
0
FAILED

The exact JSON of the most recent request to Synch — proof of what left the bridge.

BRIDGE CONTROLPOLLER STOPPED - nothing is being forwarded
CHECKING EVERY
-
LAST CHECK
CHECKS RUN
0
SIGNALS SENT
0
POSITION UPDATES
0
FAILURES
0
CHECK EVERY

Faster checking is temporary - a restart returns to -. Stand down SOS clears the red badge on the button in Synch: resolving the incident does not do it, and nothing clears it on its own until the dispatcher-cancel webhook is built.

TRAFFIC — EVERY SIGNAL THAT CROSSED0 total

Each row is one button signal: left = what came in, right = what happened on the Synch side. Click a row for the full details.

no signals yet — press SOS on the left side to watch one cross the bridge