Signal K•3w ago

Владимир Калачихин - Signal K Server version 2...

Signal K Server version 2.12.0 Do I understand correctly that the path "navigation.course.nextPoint" no longer exists? Then why is a some point returned when I subscribing to this path?

15 Replies

Scott Bender•3w ago

Do you know where that was coming from before?

Владимир КалачихинOP•3w ago

It's my plugin.

Scott Bender•3w ago

Then I’m not sure I understand your question A path only exists if the source of it sends out data for that path.

Владимир КалачихинOP•3w ago

Yes. But this path was previously specified in the documentation, wasn't it?

Scott Bender•3w ago

I don’t think so Youre referring to the “Keys Reference” in the specification?

Владимир КалачихинOP•3w ago

Yes.

Scott Bender•3w ago

It’s always been courseRhumbline or courseGreatCircle

AdrianP•3w ago

The course API sends out values on the path navigation.course.*

Владимир КалачихинOP•3w ago

O! Thanks. Now it's a "course API". Sends both v.2 and v.1 paths?

AdrianP•3w ago

Yes it sends both V1 and V2 deltas to avoid breaking changes. The rest endpoints are only v2 As per the documentation

Владимир КалачихинOP•3w ago

Ok. I think there is some kind of problem with the v.1 of the course API. I get a some waypoint immediately after subscribing to "navigation.course.nextPoint" by websocket. This can be seen in the e-inkdashboardmodern plugin. I didn't set any waypoints. But maybe it's some old one. But its lifetime must be expire. What can I do to clarify the situation?

AdrianP•3w ago

As of the most recent server release destinations set in NMEA sources will set the value of course.nextpoint.position. You can turn this off in server settings by setting API mode only. The source of course.nextpoint.position will tell you what set it.

Владимир КалачихинOP•2w ago

The source of course.nextpoint.position will tell you what set it.

{
  "context": "vessels.urn:mrn:imo:mmsi:123456789",
  "updates": [
    {
      "$source": "courseApi",
      "timestamp": "2024-12-07T22:56:35.479Z",
      "values": [
        {
          "path": "navigation.course.nextPoint",
          "value": {
            "position": {
              "latitude": 60.1233102676471,
              "longitude": 24.915029422976176
            },
            "type": "Location"
          }
        }
      ]
    }
  ]
}

{
  "context": "vessels.urn:mrn:imo:mmsi:123456789",
  "updates": [
    {
      "$source": "courseApi",
      "timestamp": "2024-12-07T22:56:35.479Z",
      "values": [
        {
          "path": "navigation.course.nextPoint",
          "value": {
            "position": {
              "latitude": 60.1233102676471,
              "longitude": 24.915029422976176
            },
            "type": "Location"
          }
        }
      ]
    }
  ]
}

AdrianP•2w ago

So that indicates it was set via the rest API. This value is persisted between server restart. You need to send a delete request to clear the destination.

Владимир КалачихинOP•2w ago

Ok, but why "timestamp" is the server start time, not a point set time?

Gaming

Programming

Владимир Калачихин - Signal K Server version 2...