Thank you, Gary. That was extremely helpful. That was also my impression from reading about loop packets in the customization guide. I just didn’t want to have to dig into the code to verify if it was not necessary. :-) I think a little note on this would be great to add to the documentation.
On Tue, Oct 20, 2020 at 19:19 gjr80 <gjroder...@gmail.com> wrote: > Hi, > > There are two key events that happen in WeeWX that trigger other events > such as reporting, uploading and archiving etc. These events are the > arrival of loop packets and arrival/creation of archive records. You can > read about them here > <http://weewx.com/docs/customizing.htm#LOOP_packets_vs._archive_records> > in the Customization Guide. In general, loop packets arrive more frequently > than archive records. For your VP2 system they arrive every 2.5 odd > seconds. Without going into a whole pile of detail generation of reports, > standard uploads to services such as PWS Weather, WOW and WU (non-rapid > fire) occur once an archive record is received/generated. In your case that > will be every five minutes. If you change your archive interval to say 10 > minute these things will then occur every 10 minutes. You cannot have > report, standard uploads (except rapid fire) occur more often then the > archive interval, though some things you can set to happen less often (say > every 30 minutes). > > WU rapid fire is tied to the arrival of loop packets, that is how WU rapid > fire uploads more frequently than say PWS. How frequently loop packets > arrive depends on your system, Davis systems are 2.5 odd second, others are > 48 seconds other are dependent on how often you poll a server/interface > etc. So WU rapid fire for you will involve regular 2.5 second updates, but > your neighbour with a different station may have 60 second updates or > updates at irregular intervals. Some (WeeWX) services may let you do things > less frequently than every loop packet (say every 2nd loop packet or on > arrival of the next loop packet once 30 seconds have elapsed) but in > general WeeWX will not do anything more frequently than on arrival of a > loop packet. > > Getting back to your specific questions: > 1. Uploading records via RESTful services happens every archive interval, > you can extend this but you cannot shorten it (WU rapid fire aside) > 2. If they use WeeWX perhaps they run a 60 second archive interval or > perhaps they use other software or publish direct. > > Hope that helps. > > Gary > On Wednesday, 21 October 2020 at 11:40:42 UTC+10 wan...@gmail.com wrote: > >> That doesn't really answer the question though: >> >> 1. weewx is only publishing records every 300 seconds (not every 60 >> seconds as specified in post_interval) >> 2. There are many stations on PWSweather.com (mostly Ambient Weather >> stations) that show 60 second interval updates. >> >> On Tuesday, October 20, 2020 at 5:50:21 PM UTC-7 jo...@johnkline.com >> wrote: >> >>> FYI >>> >>> https://www.pwsweather.com/frequently-asked-questions >>> >>> Why aren't my observations updating more frequently? >>> >>> We utilize a Content Delivery Network for performance purposes across >>> all pages. This ensures fast load times, resulting in a better experience >>> for our users. New observation data is retrieved every 5 minutes regardless >>> of station update intervals. >>> >>> On Oct 20, 2020, at 5:35 PM, wandern <wan...@gmail.com> wrote: >>> >>> >>> >>> It's not clear whether post_interval must be a multiple of >>> archive_interval when sending data to PWSweather.com. >>> >>> Since wunderground support RapidFire updates, weewx is obviously aware >>> of the current conditions more frequently than what's set in the station >>> archive interval (I have my Davis Vantage Pro 2 set to 5 minutes >>> currently), but changing post_interval to less than 300 seconds in the >>> [[PWSweather]] section has no effect. >>> >>> If I want to update PWSweather e.g. every 1 or 2 minutes, does that mean >>> I must set the archive interval on my PWS to 1 minute? >>> >>> >>> Thanks... >>> >>> -- >>> 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+...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/weewx-user/82cb0614-09f6-4480-8e34-7f07775e0c1co%40googlegroups.com >>> <https://groups.google.com/d/msgid/weewx-user/82cb0614-09f6-4480-8e34-7f07775e0c1co%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> -- > 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/9Bnmi9TYZNo/unsubscribe. > To unsubscribe from this group and all its topics, 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/99a60317-19b4-4120-873b-49dbab7353bbn%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/99a60317-19b4-4120-873b-49dbab7353bbn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CALzpO0O%3DU9G4yQ1xz_cqxh7COYoHWf7GjhJBQ-X9Lecu7V5CAw%40mail.gmail.com.
