The monitoring history page (24h) shows correct values, both on the vertical axis as the time stamps. The only outlier is the very last data point. It seems as if the database has one datapoint in the future with values that are a bit off.
So I don’t think the issue is with the plugin side on the boat, or maybe it sent one time wrong values, but rather I think those values remain in the central server database, and keep popping up in the monitoring history page and the monitoring page with a negative “updated since” data field.

ok thanks, just wanted to let you know as the warning was mentioning 2 your plugins. I will happy ignore it now

Hi everyone, 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

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

Looks much nicer, thanks!

This has now been fixed - thank you Saillogger for addressing the issue.

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.

@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

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.

@admin MMSI was missing. Appreciate it!

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.

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.

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.

@admin

Thank you for the magic. I have now activated the Windy reporting option and will monitor the data on Windy to confirm all is as expected.

Cheers, Bill on SV Denali Rose

Thanks for hoping on it and deploying a fix so quickly. Behavior looks correct now. 😉

Thanks! Will do that.

Thank you very much. Sadly we moved since Saillogger went down and I updated it. The .GPX track was to fill in our transit from when it went down and our new location where I brought it back up. Not the end of the world. Glad to have our beloved Saillogger back up and running!

Hi Brian, replied over e-mail but I suspect Venus 3.63 upgrade will not help as Signal K configuration is persisted across upgrades. There is no harm to try though.

Glad to hear you sorted it out! For future reference, it may take up to an hour for new data keys to show up in Saillogger. This is only applicable for the initial configuration, once done data flows in regular one minute intervals.

@admin Thank you for the work!!!

This was resolved in a different thread. Upgrading to the latest Victron firmware and installing Saillogger plugin 4.2.1 or later will work.