sbender9 / signalk-anchoralarm-plugin Goto Github PK

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Feature request :
when retrieving anchor - it would be useful to have a simple “relative bearing to anchor”
(also useful when at anchor without needing to look at mfd chart )

Background ….
i typically anchor single handed - doing it whilst at the bow (with remote control for engine & thruster etc) ..
but a long way from an mfd or tablet that can show chart with boat position & anchor waypoint etc …

im using an “old” smartphone (android) with KIP display - that provides large readout of
depth, anchor rode out, distance to anchor;
and would be useful to add “bearing to anchor” as the final peice of critical info.

I use WilhelmSK (just love it! fantastic!) ….. but dont fancy taking my IPAD to the bow …
and i dont have a suitable “old” iphone that i consider “disposable” for bow anchoring duties ..

i put the smartphone in a waterproof armband pouch … and with its large (KIP) display, at a glance i
can see what i need, whilst having both hands free for remote control .. and “hanging on” .. when needed!

I use an opencpn waypoint to monitor boat position when anchored, it would be very useful to be able to copy the anchor position waypoint lat/lon & paste the position into the anchoralarm plugin in signalk plugin config. Data from opencpn is formatted like this >
"28° 51.6568' N 013° 49.7503' W"
thnx.

(P.S. It would be nice to have the timestanp in the notification like
{
"state": "normal",
"method": [
"visual",
"sound"
],
"message": "Anchor Alarm - Normal"
"timestamp": "2023-10-05T11:11:25.157Z"
}

The reason is that this information is important and is used by another plugin like "simple notification" or "re-notifier"

POST /plugins/anchoralarm/dropAnchor seems to work as expected (though now requires a UI reload in Freeboard to take effect, see SignalK/freeboard-sk#80), however /plugins/anchoralarm/raiseAnchor doesn't clear everything and so Freeboard still thinks we're anchored.

UI after anchor was raised (same also after a reload):

So it seems some anchor state that Freeboard uses is still left lingering.

Request: Add "Bearing to anchor" and "Distance to anchor" fields to the interface to calculate the actual position of the anchor and the exclusion circle.

Rationale:

• Setting the anchor at the boat position is not very practical as you don't have time to interact with openCPN during the manoever.
• Several popular apps use this kind of settings (Anchorwatch, Anchor Alarm, etc...)

Details:
See attached file for an overview of the interface change. Please excuse the poor hand writing.
I guess it would have to be changed in the API as well so the other webapps or pluggin could use it.
If the fields are 0 (default value) there would be no change to the actual calculation of the anchor drop position.
I the fields have values
The actual position (coordinates of the watch circle center) would be
Latitude/Longitude corrected by the bearing to the anchor and the distance to the anchor as depicted in page 2 of the uploaded document.

The bearing I mention should be the true bearing (or magnetic it doesn't matter), not the angle to the bow, as my skecth could be confusing. This is the one you obtain with a handbearing compass that everydbody should have on board.

FeatureEnh.v01.pdf

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

Currently the REST API returns a text response when an operation completes (e.g. "ok").
For consistency, align responses with Signal K HTTP request / response format.
Example:

{
   "state": "COMPLETED",
   "statusCode": 200
}

I set anchor alarm for the first time using the supplied webapp (as opposed to Freeboard that we usually use, but for whatever reason today it failed). I see the maxRadius is set as a string instead of an integer in both that path and the SK alarm threshold. I’m a little worried if this means the anchor alarm won’t actually fire.