Not sure the WeeWX engine behaviour (backfill only requested during WeeWX startup/restart) will change, you probably have more chance of changing the driver behaviour.
Regarding your loop data question. Unfortunately there is little that can be done if the station does not maintain the same level of ‘precision’ in its stored archive records as it emits in its loop data. For the ws28xx stations in normal operation WeeWX synthesises an archive record from accumulated loop data, so you get all the highs and lows and ‘precision’ of the loop data. When you backfill records from the station you take what the station gives you, if that is one of 16 discrete wind directions that is what you are stuck with, the ‘precision’ of the loop data is not available for that period. In terms of highs and lows some time detail will be lost as highs and lows will now be seen on archive record timestamps rather than loop packet time stamps. The loss or otherwise of high and low values details will depend on how the station constructs the archive record it stores in memory. If it’s any consolation a similar issue exists with the Davis stations, hardware generated archive records provide one of 16 discrete wind directions but loop packets provide wind direction as an integer in the range 1 to 360 degrees. Remember that an archive record value is an average over a period of say 5 minutes so the need for 1 degree precision in the case of wind direction seems somewhat less important. Gary -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/58ccca2b-7024-4d7b-b7e2-a566a0f1c8e1%40googlegroups.com.
