@meri-imperiumi/signalk-meshtastic 1.2.3 → 1.3.0

package/.editorconfig

@@ -0,0 +1,5 @@
+[*]
+end_of_line = lf
+insert_final_newline = true
+indent_style = space
+indent_size = 2

package/.eslintrc.json

@@ -2,5 +2,8 @@
   "extends": "airbnb-base",
   "parserOptions": {
     "ecmaVersion": 11
+  },
+  "rules": {
+    "linebreak-style": "warn"
   }
 }

package/.github/workflows/publish.yml

@@ -12,7 +12,7 @@ jobs:
       - uses: actions/checkout@v3.0.2
       - uses: actions/setup-node@v3.1.1
         with:
-          node-version: 22
+          node-version: 24
       - run: npm install
       - run: npm test
 
@@ -23,7 +23,7 @@ jobs:
       - uses: actions/checkout@v3.0.2
       - uses: actions/setup-node@v3.1.1
         with:
-          node-version: 22
+          node-version: 24
           registry-url: https://registry.npmjs.org/
       - run: npm publish
         env:

package/.github/workflows/signalk-ci.yml

@@ -0,0 +1,11 @@
+name: SignalK Plugin CI
+
+on:
+  push:
+    branches: [main, master]
+  pull_request:
+    branches: [main, master]
+
+jobs:
+  test:
+    uses: SignalK/signalk-server/.github/workflows/plugin-ci.yml@master

package/.github/workflows/test.yml

@@ -8,7 +8,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        node-version: [22.x]
+        node-version: [24.x]
     steps:
     - uses: actions/checkout@v3.0.2
     - name: Use Node.js ${{ matrix.node-version }}

package/CHANGELOG.md

@@ -0,0 +1,27 @@
+* 1.3.0 (2026-06-16)
+  - Removed support for serial connections as they require post-install scripts
+* 1.2.4 (2026-02-15)
+  - Corrupted Node DB file should no longer crash the plugin
+* 1.2.3 (2025-10-15)
+  - Nodes that haven't been seen in last two days are no longer registered to Signal K data structure
+  - Added safeties for various non-numeric telemetry and coordinate values
+* 1.2.2 (2025-10-01)
+  - Set "last seen" timestamp of nodes based on packet payloads, not the time they're received
+  - Send timestamp with telemetry
+  - Fixed issue with persising node-to-vessel matches from `DE <callsign>`
+* 1.2.1 (2025-09-28)
+  - Fixed issue with Signal K servers that don't have navigation.position set
+* 1.2.0 (2025-09-28)
+  - Support for Node.js older than 22.x, for example as seen in Venus OS Large
+  - Safety for nodes in DB that don't have a "last seen" timestamp
+  - Made connection status notifications clearer
+* 1.1.2 (2025-09-25)
+  - Added support for the new roles from Meshtastic 2.7 (`ROUTER_LATE` and `CLIENT_BASE`)
+  - Fixed issue with sending a bell with alerts that have sound enabled
+* 1.1.1 (2025-09-18)
+  - Fixed empty response text message to digital switching actions
+  - Added support for the proposed Signal K MOB position specification
+* 1.1.0 (2025-09-11)
+  - Added support for Serial transport with the Meshtastic device
+* 1.0.0 (2025-09-11)
+  - Initial release with HTTP and TCP transports

package/README.md

@@ -29,8 +29,9 @@ In production use on several boats.
 
 ## Features
 
-* Connect to a Meshtastic node via HTTP, TCP, or Serial
+* Connect to a Meshtastic node via HTTP or TCP
   * Keep a persistent database of all seen Meshtastic nodes
+  * Note: Serial transport support was removed in 1.3.0 to comply with [postinstall deprecation](https://demo.signalk.org/documentation/Developing/Plugins/Publishing_to_The_AppStore.html#important-avoid-install-time-scripts)
 * Update Meshtastic node position from Signal K GNSS position
 * Send Signal K alerts as Meshtastic text messages to crew
   * MOB alerts (for example from [signalk-mob-notifier](https://github.com/meri-imperiumi/signalk-mob-notifier)) also send a waypoint to the MOB beacon
@@ -50,8 +51,7 @@ In production use on several boats.
 ## Requirements
 
 * This plugin running inside your Signal K installation
-* One [Meshtastic device](https://meshtastic.org/docs/hardware/devices/) running and connected to the same network (typically boat WiFi) as Signal K. This should be an [ESP32 based](https://meshtastic.org/docs/hardware/devices/heltec-automation/lora32/?heltec=v3) device for WiFi connectivity.<br>
-  If using Serial connection, it can also be a nRF52 device
+* One [Meshtastic device](https://meshtastic.org/docs/hardware/devices/) running and connected to the same network (typically boat WiFi) as Signal K. This should be an [ESP32 based](https://meshtastic.org/docs/hardware/devices/heltec-automation/lora32/?heltec=v3) device for WiFi connectivity.
 * At least one additional Meshtastic device for the crew ashore. [Seeed T1000-e](https://meshtastic.org/docs/hardware/devices/seeed-studio/sensecap/card-tracker/) is a great option, but any battery-powered Meshtastic device will work. Having a device for each crew member is even better. In busy areas these should be set to [`CLIENT_MUTE` role](https://meshtastic.org/blog/choosing-the-right-device-role/)
 * Optionally, a Meshtastic GPS tracker device installed in the dinghy
 * Optionally, a [Meshtastic mast-top repeater](https://www.printables.com/model/1396221-meshtastic-boat-module-masthead) for greatly increased communications range
@@ -91,26 +91,4 @@ Metrics used:
 
 ## Changes
 
-* 1.2.3 (2024-10-15)
-  - Nodes that haven't been seen in last two days are no longer registered to Signal K data structure
-  - Added safeties for various non-numeric telemetry and coordinate values
-* 1.2.2 (2025-10-01)
-  - Set "last seen" timestamp of nodes based on packet payloads, not the time they're received
-  - Send timestamp with telemetry
-  - Fixed issue with persising node-to-vessel matches from `DE <callsign>`
-* 1.2.1 (2025-09-28)
-  - Fixed issue with Signal K servers that don't have navigation.position set
-* 1.2.0 (2025-09-28)
-  - Support for Node.js older than 22.x, for example as seen in Venus OS Large
-  - Safety for nodes in DB that don't have a "last seen" timestamp
-  - Made connection status notifications clearer
-* 1.1.2 (2025-09-25)
-  - Added support for the new roles from Meshtastic 2.7 (`ROUTER_LATE` and `CLIENT_BASE`)
-  - Fixed issue with sending a bell with alerts that have sound enabled
-* 1.1.1 (2025-09-18)
-  - Fixed empty response text message to digital switching actions
-  - Added support for the proposed Signal K MOB position specification
-* 1.1.0 (2025-09-11)
-  - Added support for Serial transport with the Meshtastic device
-* 1.0.0 (2025-09-11)
-  - Initial release with HTTP and TCP transports
+See <CHANGELOG.md>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@meri-imperiumi/signalk-meshtastic",
-  "version": "1.2.3",
+  "version": "1.3.0",
   "description": "Signal K plugin for interfacing with the Meshtastic LoRa mesh network",
   "scripts": {
     "test": "eslint ."
@@ -16,11 +16,20 @@
   "keywords": [
     "meshtastic",
     "signalk-node-server-plugin",
-    "signalk-category-ais",
-    "signalk-category-hardware"
+    "signalk-category-hardware",
+    "signalk-category-notifications"
   ],
   "main": "plugin/index.js",
   "signalk-plugin-enabled-by-default": false,
+  "signalk": {
+    "appIcon": "./doc/mpwrd.png",
+    "displayName": "Meshtastic Integration",
+    "screenshots": [
+      "./doc/meshtastic-bequia.png",
+      "./doc/config-crew-role.png",
+      "./doc/telemetry.png"
+    ]
+  },
   "author": "Henri Bergius <henri.bergius@iki.fi>",
   "license": "GPLV3",
   "publishConfig": {
@@ -30,8 +39,7 @@
     "@bufbuild/protobuf": "^2.6.0",
     "@meshtastic/core": "^2.6.7",
     "@meshtastic/transport-http": "^0.2.5",
-    "@meshtastic/transport-node": "^0.0.2",
-    "@meshtastic/transport-node-serial": "^0.0.2"
+    "@meshtastic/transport-node": "^0.0.2"
   },
   "devDependencies": {
     "eslint": "^8.57.1",

package/plugin/index.js

@@ -16,7 +16,6 @@ if (!global.crypto) {
 let MeshDevice;
 let TransportHTTP;
 let TransportNode;
-let TransportNodeSerial;
 let create;
 let toBinary;
 let Protobuf;
@@ -237,10 +236,6 @@ module.exports = (app) => {
     })
     .then((lib) => {
       TransportNode = lib.TransportNode;
-      return import('@meshtastic/transport-node-serial');
-    })
-    .then((lib) => {
-      TransportNodeSerial = lib.TransportNodeSerial;
       return import('@bufbuild/protobuf');
     })
     .then((lib) => {
@@ -511,7 +506,13 @@ module.exports = (app) => {
     readFile(nodeDbFile, 'utf-8')
       .catch(() => '{}')
       .then((nodeDb) => {
-        const nodeDbData = JSON.parse(nodeDb);
+        let nodeDbData;
+        try {
+          nodeDbData = JSON.parse(nodeDb);
+        } catch (e) {
+          app.debug('Error reading Node DB file', e);
+          nodeDbData = {};
+        }
         Object.keys(nodeDbData)
           .forEach((nodeNum) => {
             nodes[nodeNum] = nodeDbData[nodeNum];
@@ -524,9 +525,6 @@ module.exports = (app) => {
         if (settings.device && settings.device.transport === 'http') {
           return TransportHTTP.create(settings.device.address);
         }
-        if (settings.device && settings.device.transport === 'serial') {
-          return TransportNodeSerial.create(settings.device.address);
-        }
         return TransportNode.create(settings.device.address);
       })
       .then((transport) => {
@@ -986,7 +984,7 @@ module.exports = (app) => {
   plugin.schema = () => {
     function nodeList() {
       if (Object.keys(nodes).length === 0) {
-        return undefined;
+        return [];
       }
       return Object.keys(nodes)
         .filter((nodeId) => {
@@ -1023,10 +1021,6 @@ module.exports = (app) => {
                   const: 'http',
                   title: 'HTTP (nodes connected to same network, typically ESP32)',
                 },
-                {
-                  const: 'serial',
-                  title: 'Serial port (use full path to serial device as "address")',
-                },
               ],
             },
             address: {