Every key can have a meta tag which includes ranges and alarms that apply to them. The server should raise alarms by monitoring the value against the range and placing an entry in the notifications structure.

See http://signalk.org/specification/master/data_model_metadata.html

I can only subscribe to the entire data model but not to parts of it. Is this feature implemented?

as specified here: https://github.com/SignalK/specification/blob/master/schemas/signalk.json#L12, a signalk server shoud publish the self propery containing the uuid of the vessel on which the server is running.

Following log excerpt illustrates the problem:

Jun 11 19:20:32 sophia signalk-server[7438]: signalk-server running at 0.0.0.0:3000
Jun 11 19:20:32 sophia signalk-server[7438]: /opt/signalk-server/providers/serialport.js:38
Jun 11 19:20:32 sophia signalk-server[7438]: this.serial.unpipe(this);
Jun 11 19:20:32 sophia signalk-server[7438]: ^
Jun 11 19:20:32 sophia signalk-server[7438]: TypeError: this.serial.unpipe is not a function
Jun 11 19:20:32 sophia signalk-server[7438]: at SerialStream.start (/opt/signalk-server/providers/serialport.js:38:17)
Jun 11 19:20:32 sophia signalk-server[7438]: at emitOne (events.js:77:13)
Jun 11 19:20:32 sophia signalk-server[7438]: at SerialPort.emit (events.js:169:7)
Jun 11 19:20:32 sophia signalk-server[7438]: at SerialPort.<anonymous> (/opt/signalk-server/node_modules/serialport/lib/serialport.js:103:14)
Jun 11 19:20:32 sophia signalk-server[7438]: at SerialPort._error (/opt/signalk-server/node_modules/serialport/lib/serialport.js:186:5)
Jun 11 19:20:32 sophia signalk-server[7438]: at /opt/signalk-server/node_modules/serialport/lib/serialport.js:210:19
Jun 11 19:20:32 sophia systemd[1]: signalk-server.service: main process exited, code=exited, status=1/FAILURE

is there a simple way to run Signalk using SSL (as in https://localhost:3000/signalk/api/v1/vessels/ instead of http://localhost:3000 ....). Either with self-signed certs or CA-issued ones.

Replace Primus with plain ws.

Hi,

I want to aggregate nmea0183 and possibly n2k data, but also some of my own data. It's all well and good to expand 0183 sentences and n2k sentences, but at some stage people will want to add custom data to the stream. I am looking for a simple way of adding data, type "select category, name the variable, update the data" in order to add the data into the right format and into the server stream. Am I on the right track?

A client should be able to connect with less or zero configuration.

Therefore a Bonjour service should be offered.

The service names could be:
"signalk-tcp" for the tcp service,
"signalk-ws" for the WebSocket.

If you subscribe to a single path like navigation.speedOverGround you will get all the deltas that have that path as a whole, so for example you will get deltas from NMEA0183 VTG containing not just navigation.speedOverGround but also navigation.courseOverGround*.

/signalk should return ws:// urls instead of http:// for ws endpoint. Add the extra s in case we have ssl.

Currently self is not really an alias for "this boat", because you can only retrieve it as a whole, not any paths under it.

Expected Output: server should return FQDN in /signalk response: raspberrypi.domain

Actual Output: server returns short hostname: raspberrypi

the server is correctly configured and the output of hostname -f is raspberrypi.domain

I have a RPI with AP on eth0:0 (openplotter). When enabling mdns, the server advertises the ip address of the AP (192.168.7.7) as well as the LAN IP. All good when I am connected to this AP, but when on LAN, clients (nmearemote) will select this IP address instead of the LAN address (192.168.0.18). This may be a user fault, but if there was some sort of configuration element for mdns where I could tell the server not to advertise on this interface (eth0:0), it would solve my issue.

I found a link that explains some of this, but I don´t understand how to implement it:
http://agnat.github.io/node_mdns/user_guide.html#network_interfaces

not all embedded systems can run bash. the shell scripts including in the distribution directory should be re-written to use sh syntax.

Configuration is quite important, but right now it's not standardised and definitely not easy to use. Not a problem a.t.m., but if there would be a multitude of providers to choose from this would become an issue.

Todo:

• Create a way for Provider authors to register custom CLI flags
• Namespacing of config keys, to prevent collisions between Providers
• Implement a GUI to edit the server config at runtime
• Spin config off into a separate NPM module

All Signal K node code specifies pretty old Node versions. We should upgrade to stable, which at the moment is 5.7.1.

• package.jsons
• installation instructions & other documentation
• travis configs

I don't think there are any code level changes needed. We could also leverage new apis like network stuff to figure out broadcast address for local network.

Raspberry pi 2
Debian mini with lxde, kernel 3.18.8-v7+
node v 0.12.0
bower v1.4.1

3280 error Linux 3.18.8-v7+
3281 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
3282 error node v0.12.0
3283 error npm v2.5.1
3284 error code ELIFECYCLE
3285 error [email protected] install: node-gyp rebuild
3285 error Exit status 1
3286 error Failed at the [email protected] install script 'node-gyp rebuild'.

• Move server initialisation into a constructor function
• Attach all moving parts via require('part')(app), to detach server from global scope

A single misbehaving producer can stop the whole server. The error reported in SignalK/nmea0183-signalk#22 stops the server.

TypeError: Cannot call method 'toUpperCase' of undefined
    at NMEA0183.magneticVariaton (/Users/tkurki/git-workspace/signalk/server-node/node_modules/nmea0183-signalk/lib/NMEA0183.js:116:15)
    at null._decoder (/Users/tkurki/git-workspace/signalk/server-node/node_modules/nmea0183-signalk/codecs/RMC.js:86:48)
    at NMEA0183.decode (/Users/tkurki/git-workspace/signalk/server-node/node_modules/nmea0183-signalk/lib/NMEA0183.js:220:24)
    at Parser._decode (/Users/tkurki/git-workspace/signalk/server-node/node_modules/nmea0183-signalk/lib/index.js:91:44)
    at /Users/tkurki/git-workspace/signalk/server-node/node_modules/nmea0183-signalk/lib/index.js:134:22
    at Function.forEach (/Users/tkurki/git-workspace/signalk/server-node/node_modules/lodash/dist/lodash.js:3297:15)
    at Parser._transform (/Users/tkurki/git-workspace/signalk/server-node/node_modules/nmea0183-signalk/lib/index.js:131:5)
    at Parser.Transform._read (_stream_transform.js:179:10)
    at Parser.Transform._write (_stream_transform.js:167:12)
    at doWrite (_stream_writable.js:226:10)

Node server reports the actual port it is listening on. For situations like at demo.signalk.org, where it is running behind a reverse proxy, the port reported is the internal port, not what is accessible from the outside.

looks like the "provider/execute" pipedProvider may have picked up a problem in one of the latest commits.

For instance, the command

bin/signalk-server -s settings/commandline-provider-settings.json

causes the server to crash after a few seconds with an out of memory error

==== JS stack trace =========================================

Security context: 0x39185c51 <JS Object>
    2: /* anonymous */(aka /* anonymous */) [/home/mauro/signalk-server-node/node_modules/signalk-multiplexer/node_modules/lodash/index.js:~2359] [pc=0x47a1e268] (this=0x391080c9 <undefined>,srcValue=0x391080c9 <undefined>,key=105138106)
    3: arguments adaptor frame: 3->2
    4: arrayEach(aka arrayEach) [/home/mauro/signalk-server-node/node_modules/signalk-multiplexer/node_modules/lodash/index.js...

FATAL ERROR: invalid array length Allocation failed - process out of memory

I also tried with simple Unix commands such as tail -f, which used to work correctly in previous commits.

"As mentioned yesterday, I did a re-install from scratch. It is hard to say where the problems started, but my assumption is, that the issues where cause by strictly following the installation procedure from the signal K website.

$ sudo apt-get update
$ sudo apt-get install curl git build-essential
$ curl -sL https://deb.nodesource.com/setup | sudo bash -
$ sudo apt-get install nodejs

In the first trial, I ran apt-get install nodejs. This time, I stopped after installing the build-essentials and followed the installation procedure for nodejs for RASPI at
https://learn.adafruit.com/node-embedded-development/installing-node-dot-js
Interesting enough, it run through this time. So obviously, the sudo apt-get install nodejs left something irreversible in the system.
I think it would be helpful for other users of RASPI to make a clear comment in the installation description to follow the alternative path."

By supporting Apple Push Notifications an Internet-connected server could send notifications to Apple devices, including iPhones and Apple Watches.

Add page/url that allows traversing the signal k tree and displays current data.

Probably folder-like tree structure with side panel to show values. Start closed, open dynamically as folders are accessed.

Maybe as a separate client app, but probably deployed by default on the server?

The current NMEA0183 over tcp support in the Signal K Node Server is on by default and available on port 10110 (the port registered for NMEA0183 over tcp).

The implementation is currently really naive and doesn't convert anything yet, it just makes any NMEA0183 input processed with providers/nmea0183-signalk available over tcp in addition to converting it to SK.

However the ability to convert other inputs to NMEA0183 would be useful. In my own case I have most instruments on N2K but my Simrad TP32 only accepts NMEA0183.

There should be a shell script that sets up the server as a systemd managed daemon. Systemd can manage the socket, allowing port 80 operation.

Example as ansible script: https://github.com/tkurki/marinepi-provisioning/tree/master/roles/node-app

Providers should only have access to their config namespace and any methods required to register custom functionality (namespaced) - e.g. registering REST routes if that functionality is added.

Todo:

• Clean up Provider.js
• Set up a "redacted" app object which the provider can use to interface with the app without affecting core app functionality or other providers.

The mDNS responses should include a TLS key/value pair if the connection supports it. This is less necessary for HTTP/WS service records as the server should perform a 301 redirect if TLS is configured. However, for future lower-level transports (e.g. directly over UDP/TCP or a PUB/SUB protocol like NATS or MQTT), it will be useful for the client to know that it should initiate the connection with TLS (or upgrade via a mechanism like STARTLS).

Add possibility to get Signalk stream over tcp.

• refers to socket.io
• imho the code should be replaced with a simple html5 consumer (the code on the page being out of date is a good reason why something runnable is better than doc)

To make parsing of updated data easier and to have only model to parse, it would be nice to get the updated data also in the tree model.

Further a nice to have feature would be to receive the whole tree on connection.
This solves the problem to open a connection to the "full tree URL", disconnecting after receiving a full tree and opening a connection to the "update tree URL" to receive only the updates.

The server won't start if it fails to listen on port 10110:

Error: listen EADDRINUSE :::10110

Add http://passportjs.org/ to support authentication.

Minimum viable implementation could be implementing https://github.com/jaredhanson/passport-http-bearer.

As reported by @bobmor99 the server stops outputting messages after about an hour of processing for example gpsd input.

It would be nice if there would be a setting (similar to the config.server.clock.source in the java server) so that the server uses the timestamps from the GPS (if available) rather than the server's own clock.

If one uses a Rapsberry Pi as a platform, it does not have an internal battery to keep the clock updated.

@tkurki: when running the n2k config for a while, I get a memory leak. Have you experienced this as well?

(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at EndIgnoringPassThrough.addListener (events.js:160:15)
    at EndIgnoringPassThrough.Readable.on (_stream_readable.js:707:33)
    at EndIgnoringPassThrough.once (events.js:185:8)
    at ReadStream.Readable.pipe (_stream_readable.js:559:8)
    at FileStream.startStream (/Users/Fabian/Dropbox/Sites/SignalK/signalk-server-node/providers/filestream.js:46:21)
    at ReadStream.emit (events.js:117:20)
    at _stream_readable.js:943:16
    at process._tickCallback (node.js:419:13)

Current example settings files use a hard coded identity (uuid). This will probably lead to cases where people just use the examples and never change the uuid and once they share their data the whole idea of using practically unique uuid's will be wasted.

The server should create a persistent uuid upon first startup. The uuid should be placed someplace where it is available over reinstalls or several different installations on the same computer.

Maybe I'm misunderstanding how sources work but I'm getting strange behaviours...
First of all this is my settings file:

{
    "vessel" : {
        "mmsi" : "000000000",
        "uuid" : "urn:mrn:imo:mmsi:000000000"
    },
    "pipedProviders" : [{
            "pipeElements" : [{
                    "type" : "providers/udp",
                    "options" : {
                        "port" : "55556"
                    }
                }, {
                    "type" : "providers/liner"
                }, {
                    "type" : "providers/from_json"
                }
            ],
            "id" : "I2Csensors"
        }, {
            "pipeElements" : [{
                    "type" : "providers/udp",
                    "options" : {
                        "port" : "55557"
                    }
                }, {
                    "type" : "providers/liner"
                }, {
                    "type" : "providers/from_json"
                }
            ],
            "id" : "1Wsensors"
        }
    ],
    "interfaces" : {}
}

I have connected I2C sensors and 1W sensors to the GPIO of a raspberry 3 and all is working right. I send delta format to the providers with this format:

{
  "context": "vessels.urn:mrn:imo:mmsi:000000000",
  "updates": [
    {
      "source": {
        "type": "1W",
        "src": "0316013faeff"
      },
      "timestamp": "2016-07-28T18:18:46.074Z",
      "values": [
        {
          "path": "propulsion.engine1.temperature",
          "value": 301.837
        }
      ]
    }
  ]
}

This is what I'm getting in full format:

...
{"propulsion": {
  "engine1": {
    "temperature": {
      "value": 301.837,
      "$source": "1Wsensors.0316013faeff",
      "timestamp": "2016-07-28T18:18:46.074Z"
    }
  }
}
}
...
{"environment": {
  "outside": {
    "pressure": {
      "value": 101365.997314,
      "$source": "I2Csensors.BMP180",
      "timestamp": "2016-07-28T18:18:46.297Z"
    },
    "temperature": {
      "value": 302.25,
      "$source": "I2Csensors.BMP180",
      "timestamp": "2016-07-28T18:18:46.297Z"
    }
  },
  "inside": {
    "humidity": {
      "value": 58.1872024536,
      "$source": "I2Csensors.HTU21D",
      "timestamp": "2016-07-28T18:18:46.297Z"
    },
    "temperature": {
      "value": 302.68,
      "$source": "I2Csensors.HTU21D",
      "timestamp": "2016-07-28T18:18:46.297Z"
    }
  }
}
}
...

As you can see, sources have this format:

$source:"<provider id>.<sensor id>"
$source":"1Wsensors.0316013faeff"
$source":"I2Csensors.BMP180"
$source":"I2Csensors.HTU21D"

But I would like to have only one provider in my settings file with "id" : "sensors" and to have this format in all sources:

$source:"<provider id>.<type>.<sensor id>"
$source":"sensors.1W.0316013faeff"
$source":"sensors.I2C.BMP180"
$source":"sensors.I2C.HTU21D"

According to Signal K definition, sources can contain this properties: label, type, src, pgn, sentence, talker, +any string. Being required label and type. And this is my problem, whatever I put in the delta message when I send to signal k server, only the src property affects the $source path. With the rest of properties I only get:

$source:"<provider id>.XX"
$source":"sensors.XX"

Is it possible that signalk-server-node is only working for NMEA 0183/2000 data and not for custom data?

One should be able to add mapping/enrichment/correction layer to the server.

It should be easy to add logic such as sample averaging (to reduce noise), device calibration, or analysis (computing TWS/TWA gives AWS/AWA/Speed/Heading).

Most implementations do all of these calculations per display. The problem with that is that you can have different configurations per display, so one display might show depth from waterline while another shows depth from maximum draft. Averaging and calculations are also done per display. Higher end systems (aimed primarily at race sailboats) often do have an aggregator for this reason.

CORS middleware

Am I right in assuming that there is no provision for MQTT or STOMP in the current version?
I find them in the java server, but nothing in the node server.

(1) The TCP provider doesn't reconnect unless reconnect is explicitly set to true in config, due to a OR issue.

(2) If the TCP server disconnects, stream.prototype.end is called on TCP provider. This sets reconnect to false, causing the provider to never reconnect with the TCP server.

https://github.com/SignalK/specification/wiki/Subscription-based-Streaming

For example a configuration with an NMEA0183 AIS and N2K MFD it would be useful to be able to convert input data (NMEA0183 or generic SK) to N2K and output it via NGT-1.