Saillogger Community

I have a bluetooth temperature sensor for my refrigerator, and it outputs two SK paths:

environment.refrigerator.humidity
environment.refrigerator.temperature

But I can't put them both in a section, because the section settings only give me a single data type. So I need to use two sections, which is not ideal because "Refrigerator" shows up twice.

I just added a credit card. The other was a debit card.

I just got an email that my subscription is paused, but it shouldn't be.

I see this in the invoice history

INVOICE HISTORY
Sep 9, 2024. Processing. Saillogger Monthly Subscription
Sep 8, 2024. Processing. Saillogger Monthly Subscription
Aug 8, 2024. Paid. Saillogger Monthly Subscription

Thank you!

It seems to be stuck in "processing". Is there anything I need to do to restart/re-enable my subscription?

http://garvinology.com

How to set up remote monitoring of your new Jeanneau Sun Odyssey sailboat

Here is the timeline for the trip:
8/8/2024 8:38:46 AM - boat departed Marina del Rey
8/8/2024 3:53:14 PM - boat lost internet connectivity off the coast of Catalina island
8/11/2024 7:48:21 AM - boat departed Catalina island (without internet service)
8/11/2024 2:59:20 PM - boat arrived Marina del Rey (still without internet service)
8/12/2024 12:31 PM - boat re-connected to the internet, logs sent up

https://saillogger.com/log/020124 - roundtrip, departed 8/8/2024. Showing as arrived 8/8/2024 3:53:15pm but that was when the device lost service. If you look at the timelapse, you can see that the boat flies back to the home port.

https://saillogger.com/log/020125 - one way, departed 8/11/2024, arrived 8/11/2024 at 2:59:20pm. Note that this log was published to saillogger after the device was reconnected to the internet.

Also strange, on the 020125 log, note that the Speed Avg is 9.1 kts, but the Speed Max is 7.3 kts. 7.3 kts is correct for my boat, and the Average should never be higher than the max.

Hi Ilker,

Had an interesting experience today related to this.

A friend took my boat to Catalina Island, and just before entering the harbor at Isthmus Cove on Catalina, T-Mobile lost service. The service stayed offline until they got back to the slip, even though saillogger continued to log. (The modem sim card had to be "manually registered" to get it to connect back to T-Mobile).

After the logs were uploaded, there are two entries in the boat log:

1. The round trip from Marina del Rey back to Marina del Rey
2. The return trip from Isthmus Cove to Marina del Rey

In other words, the return trip was counted twice. So the "stop for more than an hour" didn't actually happen, because the boat lost service for that time.

I think that's what happened, anyway. Feel free to look at my logs if that would be interesting.

Last weekend, we sailed from my home harbor to Catalina Island, stayed overnight, and sailed back the next day.

These really should have been recorded as a single trip, but on the Logs page, they show up as two separate trips.

Is there a way to combine these two trips into one logged trip, which starts from my home harbor, has a 1 night stay at Catalina Island, and then returned to the home harbor?

I know it doesn't make much difference, but I'd prefer to log it as a single round trip instead of two one-way trips.

In signalk, when I choose Plugins, Updates, then click the cloud icon on the Saillogger row. I see "Failed", and when I dig in for more info, I see that the log file name.

I get this in the log:

/home/signalk/.npm/_logs/2024-07-23T00_30_58_675Z-debug-0.log

0 verbose cli /usr/bin/node /usr/local/bin/npm
1 info using [email protected]
2 info using [email protected]
3 silly config:load:file:/usr/local/lib/node_modules/npm/npmrc
4 silly config:load:file:/home/signalk/.signalk/.npmrc
5 silly config:load:file:/home/signalk/.npmrc
6 silly config:load:file:/etc/npmrc
7 verbose title npm install [email protected]
8 verbose argv "--save" "install" "[email protected]"
9 verbose logfile logs-max:10 dir:/home/signalk/.npm/_logs/2024-07-23T00_30_58_675Z-
10 verbose logfile /home/signalk/.npm/_logs/2024-07-23T00_30_58_675Z-debug-0.log
11 silly logfile start cleaning logs, removing 1 files
12 silly logfile done cleaning log files
13 silly idealTree buildDeps
14 silly fetch manifest [email protected]
15 http fetch GET 200 https://registry.npmjs.org/signalk-saillogger 483ms (cache revalidated)
16 silly placeDep ROOT [email protected] REPLACE for: [email protected] want: 3.1.1
17 silly reify mark retired [ '/home/signalk/.signalk/node_modules/signalk-saillogger' ]
18 silly reify moves {
18 silly reify '/home/signalk/.signalk/node_modules/signalk-saillogger': '/home/signalk/.signalk/node_modules/.signalk-saillogger-zUisTaug'
18 silly reify }
19 verbose stack Error: ENOTEMPTY: directory not empty, rename '/home/signalk/.signalk/node_modules/signalk-saillogger' -> '/home/signalk/.signalk/node_modules/.signalk-saillogger-zUisTaug'
20 verbose cwd /home/signalk/.signalk
21 verbose Linux 6.8.0-38-generic
22 verbose node v18.20.4
23 verbose npm v10.7.0
24 error code ENOTEMPTY
25 error syscall rename
26 error path /home/signalk/.signalk/node_modules/signalk-saillogger
27 error dest /home/signalk/.signalk/node_modules/.signalk-saillogger-zUisTaug
28 error errno -39
29 error ENOTEMPTY: directory not empty, rename '/home/signalk/.signalk/node_modules/signalk-saillogger' -> '/home/signalk/.signalk/node_modules/.signalk-saillogger-zUisTaug'
30 verbose exit -39
31 verbose code -39
32 silly unfinished npm timer reify 1721694659065
33 silly unfinished npm timer reify:retireShallow 1721694659975
34 error A complete log of this run can be found in: /home/signalk/.npm/_logs/2024-07-23T00_30_58_675Z-debug-0.log

You're right. https://github.com/inspired-technologies/signalk-fixedstation-plugin doesn't appear to ever refresh the data.

I can still see the use case for monitoring the boat at the slip, and thus not requiring a fresh GPS position. Maybe that could be a user-configurable setting in sail logger?

I turned on the Axiom and signalK is now getting location from that. One thing I noticed is that the lat/Lon fields are in a different order between the Axiom and the Fixed Position plugin. I wonder if the parser in the SignalK client knows how to deal with that?

May 20 10:50:59 2024-05-20T17:50:58.965Z signalk-saillogger Running on Raspberry Pi Zero W Rev 1.1 ARMv6-compatible processor rev 7 (v6l)
May 20 10:50:59 2024-05-20T17:50:59.061Z signalk-saillogger Starting the plugin with collector ID 7649190e-e2a4-4bdd
May 20 10:51:01 2024-05-20T17:51:01.277Z signalk-saillogger Running on Raspberry Pi Zero W Rev 1.1 ARMv6-compatible processor rev 7 (v6l)
May 20 10:51:01 2024-05-20T17:51:01.284Z signalk-saillogger Starting the plugin with collector ID 7649190e-e2a4-4bdd
May 20 10:51:03 2024-05-20T17:51:03.620Z signalk-saillogger Successfully sent metadata to the server
May 20 10:51:03 2024-05-20T17:51:03.635Z signalk-saillogger No position data, not sending monitoring information (Mon May 20 2024 10:51:03 GMT-0700 (Pacific Daylight Time), Sun May 19 2024 19:14:52 GMT-0700 (Pacific Daylight Time))
May 20 10:51:03 2024-05-20T17:51:03.884Z signalk-saillogger Successfully sent metadata to the server
May 20 10:51:03 2024-05-20T17:51:03.889Z signalk-saillogger No position data, not sending monitoring information (Mon May 20 2024 10:51:03 GMT-0700 (Pacific Daylight Time), Sun May 19 2024 19:14:52 GMT-0700 (Pacific Daylight Time))
May 20 10:51:05 2024-05-20T17:51:05.092Z signalk-saillogger Successfully sent 2 record(s) to the server
May 20 10:51:05 2024-05-20T17:51:05.223Z signalk-saillogger Successfully sent 2 record(s) to the server
May 20 10:52:01 2024-05-20T17:52:01.355Z signalk-saillogger No position data, not sending monitoring information (Mon May 20 2024 10:52:01 GMT-0700 (Pacific Daylight Time), Sun May 19 2024 19:14:52 GMT-0700 (Pacific Daylight Time))

1. I'm running (right now) on a raspberry pi zero w. After this message, I got a node kernel panic and I had to restart the pi. I think that the poor thing just ran out of resources (threads or whatever).
2. I don't think I was doing anything in particular that caused this error
3. Yes, the plugin and server stopped working.

Now that I've recovered from this error, I'm not seeing it again.

I am trying to used the Fixed Position plugin instead of a GPS source while at the slip. I mistakenly put in the lat/Lon with a + longitude instead of -, and it put me in Asia. So I fixed that and now the realtime position is putting me in California, but inland.

I tried to fix the longitude again, but now the new longitude isn't getting picked up by the realtime monitor.

Is there something I can do to force the realtime monitor to snap to the location that I'm currently sending? I tried restarting the plugin and restarting signalk but that didn't help.

xMay 18 15:28:32 Error: SQLITE_MISUSE: Database is closed at plugin.stop (/home/pi/.signalk/node_modules/signalk-saillogger/index.js:78:10) at stopPlugin (/usr/local/lib/node_modules/signalk-server/lib/interfaces/plugins.js:239:16) at /usr/local/lib/node_modules/signalk-server/lib/interfaces/plugins.js:445:17 at savePluginOptions (/usr/local/lib/node_modules/signalk-server/lib/interfaces/plugins.js:135:13) at /usr/local/lib/node_modules/signalk-server/lib/interfaces/plugins.js:437:13 at Layer.handle [as handle_request] (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/layer.js:95:5) at next (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/route.js:149:13) at Route.dispatch (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/route.js:119:3) at Layer.handle [as handle_request] (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/layer.js:95:5) at /usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/index.js:284:15 at Function.process_params (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/index.js:346:12) at next (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/index.js:280:10) at Function.handle (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/index.js:175:3) at router (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/index.js:47:12) at Layer.handle [as handle_request] (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/layer.js:95:5) at trim_prefix (/usr/local/lib/node_modules/signalk-server/node_modules/express/lib/router/index.js:328:13) { errno: 21, code: 'SQLITE_MISUSE' }

I want realtime monitoring of my boat at the slip, so I enabled the Fixed Position plugin at a lower priority. I don't know if it's related to this error.

Got it. So it's an hour after we stop moving. Is that documented?

Is there a USB connected GPS I can plug in to my computer?