we need to see user/pond/pondservice.py also rather than soetemp.py
On Sunday, 6 May 2018 09:40:32 UTC+3, Jens-Jørgen Kjærgaard wrote: > > Here they are: > > Jens-Jørgen Kjærgaard > Tuenvej 818 > 9870 Sindal > +45 21204417 > www.jensjk.dk > > 2018-05-06 8:31 GMT+02:00 gjr80 <gjrod...@gmail.com <javascript:>>: > >> The correction is always applied to loop and only to archive when using >> hardware record generation (otherwise you would correct twice). If the OP >> is using hardware record generation and the pond service is loop based, >> then yes that could cause the problem, but if that was the case I would not >> expect to see any extraTemp1 data in the archive record. >> >> Jens-Jørgen. It might be worth posting your entire weewx.conf (with any >> sensitive info such as passwords/user names removed). Also worth seeing the >> file user/pond.py so we can see exactly what is being done by that service. >> >> Gary >> >> PS. There were some changes to the codebase not too long back to extract >> whatever useful info could be extracted from the accumulators, that could >> be doing something here, maybe not, would need to have a look at the code. >> Tom would know off the top of his head I am sure. >> >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "weewx-user" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/weewx-user/YVAkCwsY2S0/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> weewx-user+...@googlegroups.com <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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
