Closed marcobergman closed 1 year ago
Wind direction is there, using environment.wind.directionTrue. If you prefer to read it from another Signal K path, we could make this configurable. What’s the path available on your system?
Indeed it is! (apologies; I had not checked the right tick in the derived values plugin).
Still there might be an issue with the momentous value taken, that might differ from a more representative average value. There are plugins available that calculate average values into different paths, and for this a configurable source for these values might be handy. For now I close this issue.
I have made a fork in which I made logSourcePath, headingSourcePath, speedSourcePath, windDirectionSourcePath and windSpeedSourcePath configurable. Please let me know if you would be interested in a pull request.
For sailing, the wind direction is relevant, so the trend can be observed from the log. The momentous value taken from the signalk inventory would not suffice, though, because of the high variance. The latter also applies to COG, SOG and wind strength. See signalk-speed-wind-averaging plugin.