Expand description
Raising, and standing down, a Signal K notification, on the wire.
notifications.mob is a real, schema-defined path – alongside
fire, sinking, flooding, collision, grounding, listing,
adrift, piracy and abandon, the same generic {method, state, message} shape every one of them takes. Unlike navigation.anchor.*
(see signalk-client::anchor’s own doc), nothing here needs a
registered PUT handler: raising a notification is exactly the same
kind of act as any instrument publishing a reading – confirmed live,
a plain delta sent on an already-open, self-subscribed connection is
accepted and echoed straight back, the server even minting its own
notificationId for it.
§Standing an alarm down is a state transition, not a delete
A Signal K notification has no delete – signalk-anchoralarm-plugin’s
own drag alarm (read directly from its bundled source) clears itself
the identical way: publish a fresh delta on the same path, state: "normal", rather than retracting anything. mob_delta follows the
same convention: a client’s own MOB handling calls it with
"emergency" to raise the alert and "normal" to stand it down,
never anything else.
No path here carries a position – a notification is purely an alert. Where the mark itself lives is a caller’s own decision; see a client’s own MOB handling for why that is deliberately local-first rather than round-tripped through here at all.
Functions§
- mob_
delta - The delta text a caller’s own
signalk_client::stream::Connection::publishsends to raise or stand downnotifications.mob.