Thanks Thomas, that gives me a place to look. I will follow this up, but it 
may take a while to report back as the dropped sensor data happens 
intermittently. And yes, you are right, it's really a cosmetic issue, but 
it is one of those frustrating things.

S

On Saturday, 15 December 2018 14:00:01 UTC, Thomas Keffer wrote:
>
> The error is in the template index.html.tmpl, not in WeeWX itself. 
> Someplace you are multiplying two numbers together, the first of which, 
> occasionally, has the value of Python "None". The error was probably 
> introduced by some changes you made to the template. 
>
> Because Cheetah gives you so little information, these kinds of errors can 
> be maddening to find. Look through the template at all multiplications, and 
> think about whether the left-hand operand can be "None". If so, test before 
> doing the multiplication.
>
> The good news is that WeeWX is continuing to record data in your database. 
> Nothing is getting lost.
>
> -tk
>
> On Sat, Dec 15, 2018 at 4:46 AM <[email protected] <javascript:>> 
> wrote:
>
>> I've not been able to find the exact issue I have been experiencing, 
>> though it seems some error messages ay be quite generic and therefore not 
>> wildly helpful.
>>
>> I'm running weewx 3.82 on a raspberry Pi against an Irox branded TE923, 
>> using the standard skin though somewhat modified to my taste.  It all works 
>> remarkably well, having taken over years of data from weatherview, probably 
>> similar to many users of weewx. The site is here: 
>> https://www.tinslave.co.uk/weather/
>>
>> All works really well, even if the anemometer does under-read, until the 
>> weather station console drops a connection with one of the sensors, which 
>> happens from time to time, especially in wet weather.  When that happens, 
>> the five minute wee_report run fails, and the weather page is not 
>> refreshed, with the series of error messages as per the truncated weewx.log 
>> file attached.  If I press the little button on the weather station console 
>> to re-establish the sensor connection, after a few minutes the report 
>> generation continues as normal, with a gap in the missing sensor data 
>> showing in the graphs.
>>
>> What I would prefer to happen under weewx is that the graphs continue to 
>> be generated, even with the gaps in the sensor detail.  It "feels" as 
>> though there might be some setting or tweak that could allow wee_report to 
>> run even with missing sensor data, but my python skills are inadequate.  
>> Another option may be to send a command back to the console to start the 
>> process to re-establish the sensor connection, if that is possible, and run 
>> a  watch process for when wee_report fails, but that seems overkill.
>>
>> Does anyone have any suggestions?
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to