<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[General Discussion]]></title><description><![CDATA[Join the conversation! Dive into questions, share insights, and engage in general discussions about Saillogger and marine monitoring. Connect with the community to exchange tips, ideas, and experiences.]]></description><link>https://community.saillogger.com/category/2</link><generator>RSS for Node</generator><lastBuildDate>Sun, 10 May 2026 17:32:23 GMT</lastBuildDate><atom:link href="https://community.saillogger.com/category/2.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 07 May 2026 07:30:41 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[printing trip details]]></title><description><![CDATA[<p dir="auto">Is there any way of printing the trip details.  The screen shows the route and the left hand bar has a summary.</p>
<p dir="auto">I can do a screen print, and paste into a document , but the summary bar which has some good info is more difficult to capture as it is bigger than the screen.</p>
<p dir="auto">Any ideas welcome please</p>
]]></description><link>https://community.saillogger.com/topic/158/printing-trip-details</link><guid isPermaLink="true">https://community.saillogger.com/topic/158/printing-trip-details</guid><dc:creator><![CDATA[upstart]]></dc:creator><pubDate>Thu, 07 May 2026 07:30:41 GMT</pubDate></item><item><title><![CDATA[Best log book product]]></title><description><![CDATA[<p dir="auto">That's great to hear, thank you for sharing!</p>
]]></description><link>https://community.saillogger.com/topic/157/best-log-book-product</link><guid isPermaLink="true">https://community.saillogger.com/topic/157/best-log-book-product</guid><dc:creator><![CDATA[admin]]></dc:creator><pubDate>Mon, 27 Apr 2026 14:42:47 GMT</pubDate></item><item><title><![CDATA[Problem with SignalK app]]></title><description><![CDATA[<p dir="auto">I actually updated the module better-sqlite3 in the .signalk folder and that did the trick. Working again!</p>
]]></description><link>https://community.saillogger.com/topic/156/problem-with-signalk-app</link><guid isPermaLink="true">https://community.saillogger.com/topic/156/problem-with-signalk-app</guid><dc:creator><![CDATA[Daniel]]></dc:creator><pubDate>Mon, 27 Apr 2026 13:29:52 GMT</pubDate></item><item><title><![CDATA[Status change]]></title><description><![CDATA[<p dir="auto">Thank you, that's brilliant.  i noticed it did record correctly engine hours but I wasn't seeing this reflected when playing back the trip.   have now added a monitoring section to include RPM so hopefully this will show up.<br />
so much great information, its brilliant.</p>
]]></description><link>https://community.saillogger.com/topic/155/status-change</link><guid isPermaLink="true">https://community.saillogger.com/topic/155/status-change</guid><dc:creator><![CDATA[upstart]]></dc:creator><pubDate>Fri, 24 Apr 2026 15:52:16 GMT</pubDate></item><item><title><![CDATA[Printable log book is blank]]></title><description><![CDATA[<p dir="auto">I put in my starting position for Jan 1, but I don't understand the logbook.</p>
<p dir="auto">This year was a few nice trips, but we're not in full-on cruising mode.</p>
<p dir="auto">image.png</p>
]]></description><link>https://community.saillogger.com/topic/154/printable-log-book-is-blank</link><guid isPermaLink="true">https://community.saillogger.com/topic/154/printable-log-book-is-blank</guid><dc:creator><![CDATA[mshulman]]></dc:creator><pubDate>Fri, 27 Mar 2026 05:56:22 GMT</pubDate></item><item><title><![CDATA[Android version on Google play not found]]></title><description><![CDATA[<p dir="auto">Thank you , that's worked.</p>
]]></description><link>https://community.saillogger.com/topic/153/android-version-on-google-play-not-found</link><guid isPermaLink="true">https://community.saillogger.com/topic/153/android-version-on-google-play-not-found</guid><dc:creator><![CDATA[upstart]]></dc:creator><pubDate>Thu, 19 Mar 2026 07:17:02 GMT</pubDate></item><item><title><![CDATA[403r Access Blocked error from Open Street Map]]></title><description><![CDATA[<p dir="auto">Success!<br />
From my limited flipping through zoom levels!</p>
<p dir="auto">Looks good here i will add to this if it starts showing up again</p>
<p dir="auto">Thank you for fixing it</p>
]]></description><link>https://community.saillogger.com/topic/152/403r-access-blocked-error-from-open-street-map</link><guid isPermaLink="true">https://community.saillogger.com/topic/152/403r-access-blocked-error-from-open-street-map</guid><dc:creator><![CDATA[peterahunt]]></dc:creator><pubDate>Mon, 16 Mar 2026 02:40:57 GMT</pubDate></item><item><title><![CDATA[Engine Data not logging correctly]]></title><description><![CDATA[<p dir="auto">I have been watching the new engine logging data and there seems to be an inconsistency of the logged engine data. Here is an example from today.</p>
<p dir="auto">I captured the reported hours on port and starboard engines as we started and ended our journey and confirmed the same data was on the signalK side and the engine side for both.</p>
<p dir="auto">Start Port: 2238.1 Starboard:  2233.8<br />
Stop Port:  2241.5 Starboard:  2237.2</p>
<p dir="auto">However, the log for our journey does not reflect this data. <img src="/assets/uploads/files/1772298219628-screenshot-2026-02-28-at-12.02.51-pm.png" alt="Screenshot 2026-02-28 at 12.02.51 PM.png" class=" img-fluid img-markdown" /></p>
<p dir="auto">Both engines were running the entire journey. Note that the start hours on both are <em>before</em> I started the engines for the trip, while the end hours are very close -- probably because the boat stopped moving before I shut down the engines.</p>
<p dir="auto">Is there something I can do to fix this on my end?</p>
]]></description><link>https://community.saillogger.com/topic/151/engine-data-not-logging-correctly</link><guid isPermaLink="true">https://community.saillogger.com/topic/151/engine-data-not-logging-correctly</guid><dc:creator><![CDATA[jimholthaus]]></dc:creator><pubDate>Sat, 28 Feb 2026 17:06:14 GMT</pubDate></item><item><title><![CDATA[Plugin fails to start - Binding file.]]></title><description><![CDATA[<p dir="auto">I get the following error:<br />
Error: Could not locate the bindings file. Tried: → /home/pi/.signalk/node_modules/better-sqlite3/build/better_sqlite3.node → /home/pi/.signalk/node_modules/better-sqlite3/build/Debug/better_sqlite3.node → /home/pi/.signalk/node_modules/better-sqlite3/build/Release/better_sqlite3.node → /home/pi/.signalk/node_modules/better-sqlite3/out/Debug/better_sqlite3.node → /home/pi/.signalk/node_modules/better-sqlite3/Debug/better_sqlite3.node → /home/pi/.signalk/node_modules/better-sqlite3/out/Release/better_sqlite3.node → /home/pi/.signalk/node_modules/better-sqlite3/Release/better_sqlite3.node → /home/pi/.signalk/node_modules/better-sqlite3/build/default/better_sqlite3.node → /home/pi/.signalk/node_modules/better-sqlite3/compiled/22.22.0/linux/arm64/better_sqlite3.node → /home/pi/.signalk/node_modules/better-sqlite3/addon-build/release/install-root/better_sqlite3.node → /home/pi/.signalk/node_modules/better-sqlite3/addon-build/debug/install-root/better_sqlite3.node → /home/pi/.signalk/node_modules/better-sqlite3/addon-build/default/install-root/better_sqlite3.node → /home/pi/.signalk/node_modules/better-sqlite3/lib/binding/node-v127-linux-arm64/better_sqlite3.node at bindings (/home/pi/.signalk/node_modules/bindings/bindings.js:126:9) <strong>at new Database (/home/pi/.signalk/node_modules/better-sqlite3/lib/database.js</strong>:48:64) at startPlugin (/home/pi/.signalk/node_modules/signalk-saillogger/index.js:124:10) at plugin.start (/home/pi/.signalk/node_modules/signalk-saillogger/index.js:73:5) at doPluginStart (/usr/lib/node_modules/signalk-server/dist/interfaces/plugins.js:362:20) at /usr/lib/node_modules/signalk-server/dist/interfaces/plugins.js:576:25 at process.processTicksAndRejections (node:internal/process/task_queues:105:5)</p>
<p dir="auto">I do have the file<br />
home/pi/.signalk/node_modules/better-sqlite3/lib/database.js</p>
<p dir="auto">My SignalK is running, and has been fine for some time, I am assuming maybe an update has changed something, any ideas?  I am on version 2.20.3, and really do not want to erase my rather significant install unless I really need to.</p>
<p dir="auto">I have not had this plugin running yet on this particular server, but want to get monitoring!</p>
<p dir="auto">Raspberry Pi, everything up to date.  Openplotter install.</p>
<p dir="auto">Thanks for any advice where to look.</p>
]]></description><link>https://community.saillogger.com/topic/150/plugin-fails-to-start-binding-file</link><guid isPermaLink="true">https://community.saillogger.com/topic/150/plugin-fails-to-start-binding-file</guid><dc:creator><![CDATA[peterahunt]]></dc:creator><pubDate>Mon, 16 Feb 2026 06:03:15 GMT</pubDate></item><item><title><![CDATA[Missing all monitoring data]]></title><description><![CDATA[<p dir="auto">Was a change in the name of the boat.</p>
]]></description><link>https://community.saillogger.com/topic/149/missing-all-monitoring-data</link><guid isPermaLink="true">https://community.saillogger.com/topic/149/missing-all-monitoring-data</guid><dc:creator><![CDATA[peterix]]></dc:creator><pubDate>Fri, 06 Feb 2026 18:14:42 GMT</pubDate></item><item><title><![CDATA[signalk-windy no compatible with new Windy API]]></title><description><![CDATA[<p dir="auto">Hi @piotr-pingo yes we will update the plugin.</p>
]]></description><link>https://community.saillogger.com/topic/148/signalk-windy-no-compatible-with-new-windy-api</link><guid isPermaLink="true">https://community.saillogger.com/topic/148/signalk-windy-no-compatible-with-new-windy-api</guid><dc:creator><![CDATA[admin]]></dc:creator><pubDate>Sat, 24 Jan 2026 00:17:58 GMT</pubDate></item><item><title><![CDATA[Cannot login to website or android app]]></title><description><![CDATA[<p dir="auto">Thank you, Ilker, for your fast reply and help outside of the forum!<br />
digger</p>
]]></description><link>https://community.saillogger.com/topic/147/cannot-login-to-website-or-android-app</link><guid isPermaLink="true">https://community.saillogger.com/topic/147/cannot-login-to-website-or-android-app</guid><dc:creator><![CDATA[digger]]></dc:creator><pubDate>Mon, 12 Jan 2026 00:34:56 GMT</pubDate></item><item><title><![CDATA[Boat Offline]]></title><description><![CDATA[<p dir="auto">@admin Now that explains everything. Thanks.</p>
]]></description><link>https://community.saillogger.com/topic/146/boat-offline</link><guid isPermaLink="true">https://community.saillogger.com/topic/146/boat-offline</guid><dc:creator><![CDATA[Andrea]]></dc:creator><pubDate>Mon, 15 Dec 2025 18:31:18 GMT</pubDate></item><item><title><![CDATA[New issue: 0 mile trips]]></title><description><![CDATA[<p dir="auto">Hi @mshulman sorry for the delay in responding. Is there a possibility that there were multiple GPS sources at the time this is happening? If multiple sources report slightly different positions it may trigger a movement. If so, and this is happening frequently you can consider limiting your position reports to a single device. It is explained in FAQs.</p>
]]></description><link>https://community.saillogger.com/topic/145/new-issue-0-mile-trips</link><guid isPermaLink="true">https://community.saillogger.com/topic/145/new-issue-0-mile-trips</guid><dc:creator><![CDATA[admin]]></dc:creator><pubDate>Mon, 08 Dec 2025 18:47:33 GMT</pubDate></item><item><title><![CDATA[npm audit report - issues reported in sailloger and windy plugins dependancies]]></title><description><![CDATA[<p dir="auto">ok thanks, just wanted to let you know as the warning was mentioning 2 your plugins. I will happy ignore it now</p>
]]></description><link>https://community.saillogger.com/topic/144/npm-audit-report-issues-reported-in-sailloger-and-windy-plugins-dependancies</link><guid isPermaLink="true">https://community.saillogger.com/topic/144/npm-audit-report-issues-reported-in-sailloger-and-windy-plugins-dependancies</guid><dc:creator><![CDATA[piotr.pingo]]></dc:creator><pubDate>Tue, 18 Nov 2025 14:47:16 GMT</pubDate></item><item><title><![CDATA[Future log entry?]]></title><description><![CDATA[<p dir="auto">Thanks! It seems ok now, but I don’t have internet connection anymore, so can’t check all.</p>
]]></description><link>https://community.saillogger.com/topic/143/future-log-entry</link><guid isPermaLink="true">https://community.saillogger.com/topic/143/future-log-entry</guid><dc:creator><![CDATA[Daniel]]></dc:creator><pubDate>Fri, 07 Nov 2025 18:01:09 GMT</pubDate></item><item><title><![CDATA[record engine hours on trip logs]]></title><description><![CDATA[<p dir="auto">By the way, we just released native support for engine sensors! They are now logged automatically, along with statistics for your sailing and motoring time. Check out the announcement here: https://community.saillogger.com/topic/142/saillogger-plugin-5-x-native-engine-logging</p>
]]></description><link>https://community.saillogger.com/topic/140/record-engine-hours-on-trip-logs</link><guid isPermaLink="true">https://community.saillogger.com/topic/140/record-engine-hours-on-trip-logs</guid><dc:creator><![CDATA[admin]]></dc:creator><pubDate>Mon, 13 Oct 2025 07:20:05 GMT</pubDate></item><item><title><![CDATA[Depth measurement resolution]]></title><description><![CDATA[<p dir="auto">Looks much nicer, thanks!</p>
]]></description><link>https://community.saillogger.com/topic/139/depth-measurement-resolution</link><guid isPermaLink="true">https://community.saillogger.com/topic/139/depth-measurement-resolution</guid><dc:creator><![CDATA[digger]]></dc:creator><pubDate>Thu, 09 Oct 2025 22:23:38 GMT</pubDate></item><item><title><![CDATA[Suddenly not getting a log entry when arriving at a destination - last entry is “underway]]></title><description><![CDATA[<p dir="auto">This has now been fixed - thank you Saillogger for addressing the issue.</p>
]]></description><link>https://community.saillogger.com/topic/136/suddenly-not-getting-a-log-entry-when-arriving-at-a-destination-last-entry-is-underway</link><guid isPermaLink="true">https://community.saillogger.com/topic/136/suddenly-not-getting-a-log-entry-when-arriving-at-a-destination-last-entry-is-underway</guid><dc:creator><![CDATA[joyride]]></dc:creator><pubDate>Wed, 01 Oct 2025 16:39:20 GMT</pubDate></item><item><title><![CDATA[Privately sharing with friends and family]]></title><description><![CDATA[<p dir="auto">Hi @digger, welcome. You are spot on—if you want to share your position or logs with a select group of people, like your family, you can enable the public profile and set a password. That’s exactly what the password for the public profile is for.</p>
]]></description><link>https://community.saillogger.com/topic/135/privately-sharing-with-friends-and-family</link><guid isPermaLink="true">https://community.saillogger.com/topic/135/privately-sharing-with-friends-and-family</guid><dc:creator><![CDATA[admin]]></dc:creator><pubDate>Fri, 26 Sep 2025 02:38:58 GMT</pubDate></item><item><title><![CDATA[Some Nmea2000 parameters are not shown]]></title><description><![CDATA[<p dir="auto">@admin Hi Admin, today I was able to go out by boat and I was able to verify that in the trip the number of engine hours was not recorded and I don't understand why, the RPMs are recorded as long as the engine is running of course and instead the pre-engines are not</p>
]]></description><link>https://community.saillogger.com/topic/133/some-nmea2000-parameters-are-not-shown</link><guid isPermaLink="true">https://community.saillogger.com/topic/133/some-nmea2000-parameters-are-not-shown</guid><dc:creator><![CDATA[Andrea]]></dc:creator><pubDate>Wed, 10 Sep 2025 14:31:34 GMT</pubDate></item><item><title><![CDATA[starter battery monitor]]></title><description><![CDATA[<p dir="auto">Hi @Andrea unfortunately no, all custom monitoring values are displayed in the same format like the second one. The latter one is specialized for reporting the house/main battery.</p>
]]></description><link>https://community.saillogger.com/topic/131/starter-battery-monitor</link><guid isPermaLink="true">https://community.saillogger.com/topic/131/starter-battery-monitor</guid><dc:creator><![CDATA[admin]]></dc:creator><pubDate>Tue, 26 Aug 2025 12:44:08 GMT</pubDate></item><item><title><![CDATA[Moorage Name]]></title><description><![CDATA[<p dir="auto">Hi @jimholthaus, moorage name lookup in Saillogger is a multi-layer process. It uses four to five different types of logic to identify a moorage name, which can come from GIS sources, community-added moorages, or external references like Wikipedia.</p>
<p dir="auto">Moorages are created automatically, but once they exist, renaming them is straightforward as Kevin mentioned. Please let us know if you’d like any help with that.</p>
]]></description><link>https://community.saillogger.com/topic/130/moorage-name</link><guid isPermaLink="true">https://community.saillogger.com/topic/130/moorage-name</guid><dc:creator><![CDATA[admin]]></dc:creator><pubDate>Tue, 19 Aug 2025 20:31:51 GMT</pubDate></item><item><title><![CDATA[Sort order of Trips for Choose Trips is different]]></title><description><![CDATA[<p dir="auto">Hello John, That’s a good catch, I’m not the developer but I’m assuming that that was the most intuitive direction when he developed it. I’m guessing he’ll comment on this if need be. Thanks, Kevin.</p>
]]></description><link>https://community.saillogger.com/topic/128/sort-order-of-trips-for-choose-trips-is-different</link><guid isPermaLink="true">https://community.saillogger.com/topic/128/sort-order-of-trips-for-choose-trips-is-different</guid><dc:creator><![CDATA[KevinN]]></dc:creator><pubDate>Mon, 11 Aug 2025 03:54:36 GMT</pubDate></item><item><title><![CDATA[Initial Tracking Position issue]]></title><description><![CDATA[<p dir="auto">Thanks for hoping on it and deploying a fix so quickly. Behavior looks correct now. 😉</p>
]]></description><link>https://community.saillogger.com/topic/127/initial-tracking-position-issue</link><guid isPermaLink="true">https://community.saillogger.com/topic/127/initial-tracking-position-issue</guid><dc:creator><![CDATA[TargaDriver]]></dc:creator><pubDate>Mon, 04 Aug 2025 04:15:13 GMT</pubDate></item></channel></rss>