<?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[Refrigerator history monitoring stopped a week ago]]></title><description><![CDATA[<p dir="auto">My real time monitoring of my refrigerator had stopped but I fixed it yesterday, and now my refrigerator shows up on the realtime monitor.</p>
<p dir="auto">But it hasn't reappeared on the 24 hour or 7 day history monitor.</p>
]]></description><link>https://community.saillogger.com/topic/89/refrigerator-history-monitoring-stopped-a-week-ago</link><generator>RSS for Node</generator><lastBuildDate>Fri, 10 Jul 2026 11:30:46 GMT</lastBuildDate><atom:link href="https://community.saillogger.com/topic/89.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 01 Dec 2024 15:40:14 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Refrigerator history monitoring stopped a week ago on Sun, 09 Feb 2025 22:34:19 GMT]]></title><description><![CDATA[<p dir="auto">Makes sense. I think we just won't recommend that particular sensor, since it's refresh rate is r fast enough for monitoring.</p>
<p dir="auto">I'm really excited to have SailLogger on the boat. That you for making it available.</p>
]]></description><link>https://community.saillogger.com/post/331</link><guid isPermaLink="true">https://community.saillogger.com/post/331</guid><dc:creator><![CDATA[mshulman]]></dc:creator><pubDate>Sun, 09 Feb 2025 22:34:19 GMT</pubDate></item><item><title><![CDATA[Reply to Refrigerator history monitoring stopped a week ago on Sun, 09 Feb 2025 21:56:11 GMT]]></title><description><![CDATA[<p dir="auto">Hi Michael, if the 90 second refresh period is not enough, I am afraid you need to address it in the sensor side or use a different sensor. Using anything more than 90 seconds defeats the purpose of having a minute level granularity for Saillogger.</p>
]]></description><link>https://community.saillogger.com/post/330</link><guid isPermaLink="true">https://community.saillogger.com/post/330</guid><dc:creator><![CDATA[admin]]></dc:creator><pubDate>Sun, 09 Feb 2025 21:56:11 GMT</pubDate></item><item><title><![CDATA[Reply to Refrigerator history monitoring stopped a week ago on Sun, 09 Feb 2025 19:06:06 GMT]]></title><description><![CDATA[<p dir="auto">This is still happening. When I first open the Real Time monitoring page, the refrigerator shows 0F. After sitting on the page for a minute or so, it shows the correct temperature.</p>
<p dir="auto">My other temperature sensors don't have this problem. They show the temperature when I first open the page</p>
]]></description><link>https://community.saillogger.com/post/329</link><guid isPermaLink="true">https://community.saillogger.com/post/329</guid><dc:creator><![CDATA[mshulman]]></dc:creator><pubDate>Sun, 09 Feb 2025 19:06:06 GMT</pubDate></item><item><title><![CDATA[Reply to Refrigerator history monitoring stopped a week ago on Thu, 16 Jan 2025 15:30:10 GMT]]></title><description><![CDATA[<p dir="auto">I have version 4.0.2 and my refrigerator still read 0F when looked this morning. After leaving the realtime monitoring tab open, it now shows 34F.</p>
]]></description><link>https://community.saillogger.com/post/313</link><guid isPermaLink="true">https://community.saillogger.com/post/313</guid><dc:creator><![CDATA[mshulman]]></dc:creator><pubDate>Thu, 16 Jan 2025 15:30:10 GMT</pubDate></item><item><title><![CDATA[Reply to Refrigerator history monitoring stopped a week ago on Tue, 14 Jan 2025 15:54:18 GMT]]></title><description><![CDATA[<p dir="auto">Plugin version is available on Saillogger settings in the boat tab: <a href="https://saillogger.com/settings/?tab=boat" rel="nofollow ugc">https://saillogger.com/settings/?tab=boat</a></p>
]]></description><link>https://community.saillogger.com/post/312</link><guid isPermaLink="true">https://community.saillogger.com/post/312</guid><dc:creator><![CDATA[admin]]></dc:creator><pubDate>Tue, 14 Jan 2025 15:54:18 GMT</pubDate></item><item><title><![CDATA[Reply to Refrigerator history monitoring stopped a week ago on Tue, 14 Jan 2025 15:32:15 GMT]]></title><description><![CDATA[<p dir="auto">I just updated to 4.0.2 and I'll let you know. Thank you.</p>
<p dir="auto">Btw, perhaps the plugin could announce its version number in the server log at startup?</p>
]]></description><link>https://community.saillogger.com/post/311</link><guid isPermaLink="true">https://community.saillogger.com/post/311</guid><dc:creator><![CDATA[mshulman]]></dc:creator><pubDate>Tue, 14 Jan 2025 15:32:15 GMT</pubDate></item><item><title><![CDATA[Reply to Refrigerator history monitoring stopped a week ago on Tue, 14 Jan 2025 12:59:28 GMT]]></title><description><![CDATA[<p dir="auto">Please try plugin version 4.0.2 that we just published. It increases the refreshment timeout to 90 seconds, hopefully it will solve your problem.</p>
]]></description><link>https://community.saillogger.com/post/310</link><guid isPermaLink="true">https://community.saillogger.com/post/310</guid><dc:creator><![CDATA[admin]]></dc:creator><pubDate>Tue, 14 Jan 2025 12:59:28 GMT</pubDate></item><item><title><![CDATA[Reply to Refrigerator history monitoring stopped a week ago on Mon, 13 Jan 2025 18:51:51 GMT]]></title><description><![CDATA[<p dir="auto">This workflow is using the "BT Sensors plugin" (<a href="https://github.com/naugehyde/bt-sensors-plugin-sk" rel="nofollow ugc">https://github.com/naugehyde/bt-sensors-plugin-sk</a>).</p>
<p dir="auto">By default, the sensor broadcasts its data whenever it changes significantly, but at least every 60 seconds by default with the stock firmware.<br />
(link to custom firmware: <a href="https://github.com/atc1441/ATC_MiThermometer" rel="nofollow ugc">https://github.com/atc1441/ATC_MiThermometer</a>)</p>
<p dir="auto">When the "BT Sensor Plugin" sees this reading, it broadcasts it out to SignalK.</p>
<p dir="auto">The bad user behavior is that the sensor broadcasts (or "advertises") its current state every 60 seconds by default, which just matches the obsolete timeout in Saillogger.</p>
<p dir="auto">This leads to the refrigerator reading being missing some or most of the time.</p>
<p dir="auto">We could fix this by increasing the broadcast rate from the sensor, but these sensors use tiny little batteries, so maximizing battery life is important.</p>
<p dir="auto">Perhaps Saillogger could have an override for devices that don't change quickly, like tanks or temperature sensors, and tolerate a 5 minute data refresh interval?</p>
]]></description><link>https://community.saillogger.com/post/308</link><guid isPermaLink="true">https://community.saillogger.com/post/308</guid><dc:creator><![CDATA[mshulman]]></dc:creator><pubDate>Mon, 13 Jan 2025 18:51:51 GMT</pubDate></item><item><title><![CDATA[Reply to Refrigerator history monitoring stopped a week ago on Mon, 13 Jan 2025 18:01:57 GMT]]></title><description><![CDATA[<p dir="auto">I think things are getting a bit confused here. You don't want to rebroadcast data, you want fresh data relatively frequently. Saillogger requests the path every minute and checks the age of the data. If it is more than 60 seconds, it doesn't consider it fresh enough. Otherwise what it displays would be obsolete information (i.e. it is identical to rebroadcasting the stale data into Saillogger).</p>
<p dir="auto">Which plugin is this and how frequently is the data refreshed (like not rebroadcast but actually refreshed)?</p>
]]></description><link>https://community.saillogger.com/post/307</link><guid isPermaLink="true">https://community.saillogger.com/post/307</guid><dc:creator><![CDATA[admin]]></dc:creator><pubDate>Mon, 13 Jan 2025 18:01:57 GMT</pubDate></item><item><title><![CDATA[Reply to Refrigerator history monitoring stopped a week ago on Mon, 13 Jan 2025 17:35:07 GMT]]></title><description><![CDATA[<p dir="auto">I asked if the Bluetooth plugin could rebroadcast data for up to 30 seconds. Here's the reply I got:</p>
<p dir="auto">It'd be bad design to rebroadcast as SK assigns a timestamp for the delta. Rebroadcasting would create spuriously timestamped data and be redundant with existing function -- plugins like SailLogger can ask for the temperature path at any time. If SailLogger is marking infrequently updated paths like temperature missing after 60 seconds that's a SailLogger issue/limitation.</p>
]]></description><link>https://community.saillogger.com/post/306</link><guid isPermaLink="true">https://community.saillogger.com/post/306</guid><dc:creator><![CDATA[mshulman]]></dc:creator><pubDate>Mon, 13 Jan 2025 17:35:07 GMT</pubDate></item><item><title><![CDATA[Reply to Refrigerator history monitoring stopped a week ago on Mon, 13 Jan 2025 16:15:17 GMT]]></title><description><![CDATA[<p dir="auto">The sensor broadcasts it's value infrequently, like once a minute. When the Bluetooth sensor plugin receives the broadcast, it sends it out via SignalK.</p>
<p dir="auto">Let me see if we can make the Bluetooth plugin broadcast every 30 seconds or whenever it receives a broadcast.</p>
]]></description><link>https://community.saillogger.com/post/305</link><guid isPermaLink="true">https://community.saillogger.com/post/305</guid><dc:creator><![CDATA[mshulman]]></dc:creator><pubDate>Mon, 13 Jan 2025 16:15:17 GMT</pubDate></item><item><title><![CDATA[Reply to Refrigerator history monitoring stopped a week ago on Mon, 10 Feb 2025 02:24:59 GMT]]></title><description><![CDATA[<p dir="auto">What do you see in the databrowser for those values and how often do they update? Saillogger normally ignores values that are older than 60 seconds. Almost all instruments report values every couple of seconds in general, so 60 seconds should have a lot of buffer.</p>
]]></description><link>https://community.saillogger.com/post/303</link><guid isPermaLink="true">https://community.saillogger.com/post/303</guid><dc:creator><![CDATA[admin]]></dc:creator><pubDate>Mon, 10 Feb 2025 02:24:59 GMT</pubDate></item><item><title><![CDATA[Reply to Refrigerator history monitoring stopped a week ago on Mon, 13 Jan 2025 05:18:48 GMT]]></title><description><![CDATA[<p dir="auto">Another thought is that maybe the realtime tracker page doesn't do as well with sparse data. The temp sensor only sends data once in a while?</p>
]]></description><link>https://community.saillogger.com/post/302</link><guid isPermaLink="true">https://community.saillogger.com/post/302</guid><dc:creator><![CDATA[mshulman]]></dc:creator><pubDate>Mon, 13 Jan 2025 05:18:48 GMT</pubDate></item><item><title><![CDATA[Reply to Refrigerator history monitoring stopped a week ago on Mon, 13 Jan 2025 05:17:00 GMT]]></title><description><![CDATA[<p dir="auto">I'm still having trouble with this. My refrigerator sensor battery died, I changed it, and I restarted SignalK.</p>
<p dir="auto">I see the refrigerator temperature and humidity in the SignalK data browser, but either temperature or humidity has been reporting 0 since. It seems random which one will show up.</p>
<p dir="auto">On the theory that maybe the monitoring list is too long since these are the last items, I removed refrigerator humidity from the monitoring list.</p>
<p dir="auto">Would it be possible for me to see the data history as a table, just showing the datetime and value for each sensor.</p>
<p dir="auto">I know that the history graph doesn't do well with graphs, and a sensor log would make debugging so much easier.</p>
<p dir="auto">Thank you!</p>
]]></description><link>https://community.saillogger.com/post/301</link><guid isPermaLink="true">https://community.saillogger.com/post/301</guid><dc:creator><![CDATA[mshulman]]></dc:creator><pubDate>Mon, 13 Jan 2025 05:17:00 GMT</pubDate></item><item><title><![CDATA[Reply to Refrigerator history monitoring stopped a week ago on Mon, 02 Dec 2024 15:29:28 GMT]]></title><description><![CDATA[<p dir="auto">Got it, thank you!</p>
]]></description><link>https://community.saillogger.com/post/275</link><guid isPermaLink="true">https://community.saillogger.com/post/275</guid><dc:creator><![CDATA[mshulman]]></dc:creator><pubDate>Mon, 02 Dec 2024 15:29:28 GMT</pubDate></item><item><title><![CDATA[Reply to Refrigerator history monitoring stopped a week ago on Mon, 02 Dec 2024 23:16:24 GMT]]></title><description><![CDATA[<p dir="auto">Hi Michael, I think it is there but since it is missing some data points the X axis is misaligned. It is a bug that we need to address but, but the graph will autocorrect itself when refrigerator sends enough data points.</p>
]]></description><link>https://community.saillogger.com/post/274</link><guid isPermaLink="true">https://community.saillogger.com/post/274</guid><dc:creator><![CDATA[admin]]></dc:creator><pubDate>Mon, 02 Dec 2024 23:16:24 GMT</pubDate></item></channel></rss>