where were you able to find that fine offset clone WH25? On Sunday, February 6, 2022 at 2:26:53 AM UTC-5 William Garber wrote:
> rtl_433 spends a lot of time whenever it hops from 433mhz to 915mz > adjusting the minimum detection level based on noise (automatically). > I purchased a fine offset clone WH25 today which is on 433mhz to avoid > this problem. > Perhaps what is happening is a lot of the archived results are getting > nulls because the slower (WH32B) is not done communicating by the end of > the archive_interval. > Note the short archive_interval = 30 or 120 seconds. Is this way too > short especially in my case? > > On Saturday, February 5, 2022 at 11:19:50 PM UTC-8 William Garber wrote: > >> note plots for day are just disconnected points. plots for week and year >> look like continuous curves or lines. >> is this relevant? >> https://groups.google.com/g/weewx-user/c/uGk23BPOPHk >> On Saturday, February 5, 2022 at 11:15:17 PM UTC-8 William Garber wrote: >> >>> Using rtl-sdr; rtl_433; weewx-sdr; weewx. >>> The Acurite Atlas is on 433mhz. The Ambient WH32B is on 915mhz. >>> (1) I am not sure how to configure weewx and rtl_433 for two frequencies >>> both >>> used by weewx; see my config for both. >>> (2) There are a lot of "almost" duplicate packets. >>> (3) The time period between packets is different for WH32B and Atlas. >>> so what, should I use the larger of the two for the archive_interval in >>> weewx.conf ? >>> (4) if you look at the output, especially for the barometer (WH32B), the >>> graph is just a lot of dots. Also a lot of the graphs are just dots. I >>> think they should be connected by lines. So I set line_gap_fraction = >>> 0.99999999 in skin.conf but it didn't make any obvious difference. Also it >>> would be nice if there were no disconnected vertical discontinuities >>> (jumps); weewx should draw a vertical line for a vertical jump (a >>> suggestion). >>> (5) acurite atlas sends three (or more?) different types of packet. >>> WH32B sends one type of packet, but has a much longer period between >>> packets. so how does weewx combine the multiple different packets, >>> eliminate duplicates and form a single archive record? >>> this could be made more obvious in the documentation (a suggestion) >>> otherwise weewx is a wonderful awesome program. >>> >> -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/4333fd4d-5c15-4fbb-a71b-ec130d8b75d2n%40googlegroups.com.
