open-index/open-npm huggingface dataset:
npm package: @meri-imperiumi/signalk-autostate
Description: Automatically change navigation.state in Signal K based on vessel movement
Author: Henri Bergius
Latest version: 0.5.1

Signal K auto-state plugin
==========================

This plugin attempts to determine the vessel's state based on sensor values, and updates the `navigation.state` value accordingly.

Currently inputs used are:

* `navigation.anchor.position`: if an anchor is set, the vessed is set as "anchored"
* `navigation.position`: if the vessel moves less than 100 meters in 10 minutes, it is set as "moored", otherwise it is set as "sailing"
* `propulsion.*.revolutions` is used to determine whether the vessel is "sailing" or "motoring" when considered to be moving
* `propulsion.*.state` (value `started` or `stopped`) is used to determine whether the vessel is "sailing" or "motoring" when considered to be moving

The default means of propulsion ("sailing" or "motoring") when moving can be chosen in the plugin settings.

The vessel navigation state can be useful for AIS data, as well as for customizing boat dashboard for the current situation.

## Changes

* 0.5.1 (2025-04-07)
  - Fixed the "fake moored" after hoisting anchor
* 0.5.0 (2025-02-23)
  - Added a five minute extra grace period after deactivating anchor alarm before boat is considered moored
* 0.4.0 (2024-02-16)
  - Speed threshold where stopping the engine will set state to "moored" immediately is now configurable
* 0.3.1 (2023-07-27)
  - Fixed issue with persisted state "sticking"
* 0.3.0 (2023-07-23)
  - Latest state is now persisted on disk to retain state between reboots (like when restarting Signal K while under way)
* 0.2.0 (2023-02-16)
  - Switched "under way" heuristic to use a moving 10min window. This should eliminate some "false moored" situations
  - Made the switch between `sailing` and `motoring` when engine is started/stopped instant when under way
  - Added a special case for when motoring, motor is stopped and speed is zero. This goes directly to `moored`
* 0.1.5 (2020-11-30)
  - Compatibility with the new `setPluginStatus`/`setPluginError` APIs in Signal K
* 0.1.4 (2020-11-25)
  - Compatibility with the upcoming "meta deltas" feature in Signal K
* 0.1.3 (2020-10-13)
  - Simplified dependency chain by only using the `where` library for location calculations at runtime
* 0.1.2 (2020-04-17)
  - Switched status from `not-under-way` to `moored`
  - Switched status from `under-engine` to `motoring`
  - Added propulsion support
* 0.1.1 (2020-01-31)
  - Fixed integration with Signal K
* 0.1.0 (2020-01-31)
  - Initial release. Should work with anchor and position for a sailboat
  - No propulsion support implemented yet
npm package: @meri-imperiumi/signalk-aws-iot
Description: Plugin that sends metrics to AWS IoT
Author: Henri Bergius
Latest version: 1.1.4

SignalK AWS IoT
===============

Plugin that sends a vessel's Signal K data stream to [AWS Iot Core](https://aws.amazon.com/iot-core/). The use case for this plugin is to back up Signal K data on a cloud service, and potentially to enable remote monitoring of the vessel.

## Setup

1. Install and enable this plugin in your Signal K
2. Log into AWS Console and create a "Thing" in IoT Core
3. Create a certificate for the Thing, and copy-paste it and your endpoint details to the plugin settings
4. Ensure the device has an AWS policy allowing it to `iot:Connect` and `iot:Publish`
5. Process or store the data stream from the device in the AWS solution of your choice

If you're only interested in data from particular vessel states (for examples, when vessel is sailing), you can [install a plugin](https://www.npmjs.com/package/@meri-imperiumi/signalk-autostate) that automatically updates vessel state based on telemetry. Then you can choose the states in the configuration of this plugin.

## Changes

* 1.1.3 (2020-11-30)
  - Compatibility with the new `setPluginStatus`/`setPluginError` APIs in Signal K
* 1.1.2 (2020-11-25)
  - Compatibility with the upcoming "meta deltas" feature in Signal K
* 1.1.1 (2020-11-24)
  - Fixed an issue with `navigation.state` filtering when sending messages
* 1.1.0 (2020-10-13)
  - Option for sending all values to a single `signalk` AWS IoT topic instead of topic per Signal K path
  - Ability to control in which vessel navigation states we send data to AWS IoT
npm package: @meri-imperiumi/signalk-infodisplay
Description: Context-aware information display for Signal K
Author: Henri Bergius
Latest version: 1.2.6

Contextual information display for Signal K
===========================================

This is an adaptation of the [c-base infoscreens system](https://github.com/c-base/infoscreens) for Signal K. The idea is to enable HTML-capable viewers (like a kiosk display) to show different dashboards depending on whether the boat is sailing, at anchor, etc. This works well for instance with an onboard [Grafana](https://grafana.com/) installation.

<img width="886" alt="Screenshot 2024-12-09 at 13 37 06" src="https://github.com/user-attachments/assets/bbcfa2ea-19c5-47a0-a90d-e38122fca3d4">

## Usage

Install this plugin and the [signalk-autostate plugin](https://github.com/meri-imperiumi/signalk-autostate#readme).

Configure the plugin and set URLs for the different navigation states:
<img width="735" alt="Screenshot 2024-12-09 at 13 38 00" src="https://github.com/user-attachments/assets/b61fe6d4-e47b-49bb-8a2e-5aeea649b769">

Point your kiosk browser to the webapp URL supplied by this plugin (`/@meri-imperiumi/signalk-infodisplay/`) on your Signal K server.

## Changes

* 1.2.6 (2026-01-26)
  - _Value is within normal range_ notifications are not shown
  - Notifications are cleared when reconnecting to Signal K
* 1.2.5 (2025-11-03)
  - Notification elements take a little bit less space now
* 1.2.4 (2025-10-06)
  - Actually remove the notification elments instead of hiding them
* 1.2.3 (2025-09-30)
  - Hiding all "nominal" notifications until Signal K allows not having "visual" set
  - Added colors for notification types of `warning` and `nominal`
* 1.2.2 (2025-09-25)
  - Added safety for notifications with empty payload
* 1.2.1 (2025-08-31)
  - Hiding non-visual notifications of state "nominal"
* 1.2.0 (2025-03-30)
  - Safety for incorrectly formatted notifications
  - Hiding the persistent but not useful _Anchor Alarm - Normal_ visual notification when anchored
* 1.1.0 (2024-12-10)
  - Show Signal K notifications visually on screen
* 1.0.1 (2024-12-09)
  - Fixed unnecessary reloads when same state message is received again
* 1.0.0 (2024-12-09)
  - Initial release
npm package: @meri-imperiumi/signalk-maidenhead
Description: Generate a Maidenhead Locator System string for vessel position
Author: Henri Bergius
Latest version: 1.0.0

Signal K Maidenhead Locator Plugin
===================================

This plugin produces a [Maidenhead Locator System](https://en.wikipedia.org/wiki/Maidenhead_Locator_System) string for the vessel position. This is useful for communicating position (QTH) in amateur radio communications.
npm package: @meri-imperiumi/signalk-mob-notifier
Description: Create Signal K notifications for discovered AIS MOB, EPIRB, and SART beacons
Author: Henri Bergius
Latest version: 1.1.6

Signal K MOB notifier plugin
============================

This plugin detects if Signal K has seen an AIS MOB (MMSI starting with `972`), EPIRB (MMSI starting with `974`), or SART (MMSI starting with `970`) beacon. If a beacon is detected, a [Signal K notification](https://signalk.org/specification/1.5.0/doc/notifications.html) will be raised. With the notification there are various ways to alert the crew:

* Audio with plugins like [signalk-audio-notifications](https://github.com/meri-imperiumi/signalk-audio-notifications) and an attached speaker
* Meshtastic message with [signalk-meshtastic](https://github.com/meri-imperiumi/signalk-meshtastic)
* Visual with apps like Freeboard

Please note that this plugin aims to aid with noticing and locating crew overboard. It is not a replacement for "proper" alerting mechanisms via dedicated alert buzzers, chartplotters, or a VHF radio.

## Changes

* 1.1.6 (2026-01-20)
  - Round distance to beacon with single decimal
  - Use EPIRB and SART terms for shorter notifications
* 1.1.5 (2025-11-15)
  - Bump release
* 1.1.4 (2025-11-12)
  - Fix reading MOB vessel data structure
* 1.1.3 (2025-11-02)
  - Fix detection of beacon type (MOB/SART/EPIRB)
* 1.1.2 (2025-11-01)
  - Better approach at getting MOB coordinates
* 1.1.1 (2025-09-18)
  - Notifications include position when available
* 1.1.0 (2025-09-04)
  - Notification is not re-published if it already exists
* 1.0.0 (2025-08-25)
  - Initial release
npm package: @meri-imperiumi/signalk-teltonika-rutx11
Description: Signal K plugin that retrieves status from a Teltonika RUT modem via Modbus
Author: Henri Bergius
Latest version: 0.6.1

Teltonika RUT modem plugin for Signal K
=======================================

This plugin makes status information from your Teltonika RUT (for example [RUTX11](https://teltonika-networks.com/product/rutx11/)) boat router available to Signal K.

The data model is roughly equivalent to [signalk-netgear-lte-status](https://www.npmjs.com/package/signalk-netgear-lte-status).

## Supported modems:

* RUT240, RUT360, RUT950, RUT955, RUTX9, RUTX11 and RUTX14 

## Usage

* Install this plugin to Signal K
* [Enable Modbus TCP Server](https://wiki.teltonika-networks.com/view/RUTX11_Monitoring_via_Modbus) in your RUTxxx device
  -   Note: set "connection timeout =  60  and switch OFF "keep persistent connection"
* Enable the plugin and set the Modbus connection details you configured for the router

## Changes

* 0.6.1 (November 28th 2025)
  - Correct error message is now passed out on read errors
* 0.6.0 (January 7th 2024)
  - Make it possible to enable/disable getting GPS position from the RUT
  - GPS data is sent by some RUT devices as big endian, provide a config for that
    (https://github.com/meri-imperiumi/signalk-teltonika-rutx11/issues/90)
* 0.5.0 (April 27th 2023)
  - Improved error handling in case some parts of the ModBus communication fail
  - We no longer try to get GPS position for RUT240 devices
* 0.4.0 (March 4th 2022)
  - Add support for using the Teltonika modem as a GPS source for Signal K
* 0.3.0 (February 4th 2022)
  - Add support for other Teltonika modems apart from X11
npm package: @meri-imperiumi/signalk-triplogger
Description: Log the length of the current trip
Author: Henri Bergius
Latest version: 1.2.0

# signalk-triplogger

This plugin keeps automatic track of the distance traveled on the current trip. The distance tracked is based on vessel GPS positions, so it tracks distance over ground, not distance over water like traditional paddlewheel logs.

The plugin monitors vessel `navigation.state` as set by the [signalk-autostate](https://github.com/meri-imperiumi/signalk-autostate) plugin. Trip recording ends when vessel is detected as anchored or moored, and when vessel again gets under way, the trip log is reset to 0NM. **Install the autostate plugin or ensure your `navigation.state` is correctly set to use this plugin.**

## Changes

* 1.2.0 (April 27th 2023)
  - Added support for populating `navigation.log` for totals
* 1.1.1 (February 28th 2023)
  - Fix issue when `navigation.position` doesn't contain coordinates
* 1.1.0 (March 4th 2022)
  - Persist logs for current day/month/year, also by sailing/motoring
* 1.0.1 (February 18th 2022)
  - Fix issue with reading lat and lon
* 1.0.0 (February 18th 2022)
  - Initial version, logging in-memory only
npm package: @meri-imperiumi/signalk-value-combiner
Description: Combine values from multiple Signal K paths
Author: Henri Bergius
Latest version: 1.1.0

Signal K value combiner
=======================

This plugin combines the values from multiple paths to create a new value. Usage examples include calculating the combined volume of water available in all freshwater tanks, or the combined output of multiple solar charging sources.

## Changes

* 1.1.0 (2026-01-19)
  - Added support for multiplication
* 1.0.0 (2025-08-05)
  - Initial release, addition support