This problem has been seen before <https://groups.google.com/d/msg/weewx-user/KNUZY53oKZ8/TyIYa0JABwAJ>. The workaround solution there was to switch to software record generation. Give that a try and see if that helps. It's not really a solution, but it might get you going.
This driver really needs to be rewritten. It is much more complicated than necessary. Alas, I do not have a WMR200 at hand (nor, at $250 do I want to buy one!). -tk On Wed, Sep 6, 2017 at 4:47 PM, gjr80 <[email protected]> wrote: > And I thought 'reading' the vantage driver was difficult, this one has > really made my head spin. > > When I first read this on my phone last night the log was very difficult > to read and I saw the comment about historical data and was concerned there > was an issue with the interval weighting code introduced in 3.7.0, having > now read the logs on the big screen as well as the rest of the posts it's > clear to me this is not the case and it is a WMR200 driver issue. > > Thinking aloud here as to what is going on. genStartupRecords() is called > on weeWX startup to catch up any archive records. The very first time > through, property _pkt is initialised to None and hence the > _process_packet_complete() method is not called at line 1897 ( > _process_packet_complete() calls self._pkt.packet_process() (ie > PacketArchive.packet_process()) which (would) add the interval field to > the packet). The _sensor_to_fields() method creates the archive record > that is to be yielded, and it would normally add the interval field to > the archive record, but since the interval field was not added to the > packet vide line 1897, no interval field is added to the archive record > that is yielded. The accumulator then chokes when it tries to interval > weight the archive record. > > Solution, something needs to be introduced to add the interval field to > the packet in genStartupRecords() after the _poll_for_data() method is > called at line 1906. I suspect Tom or Matthew will have the elegant code to > do that, besides my head hurts now. > > Gary > > > > On Thursday, 7 September 2017 02:35:19 UTC+10, mwall wrote: >> >> On Wednesday, September 6, 2017 at 11:34:44 AM UTC-4, Tom Keffer wrote: >>> >>> >>> You did commit d4ff72d >>> <https://github.com/weewx/weewx/commit/d4ff72d8dc8775dec72f8cfbc6a17ee8d9a05d96> >>> that was supposed to fix this bug. Are you now saying that you are having >>> doubts it does? >>> >> >> this looks like a different failure mode than what that commit fixed. >> >> >> >>> >> -- > 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. > -- 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.
