hmmm - it was right there in front of you if you looked at the list of files there you could have downloaded manually, but I did have a bad wget command. Fixed now (I think).
Reminder - that script won't run as written on a Mac or non-debian(ish) linux so I don't know how applicable it is for you specifically, but it does work fine on a pi or debian/ubuntu box and with a little tweaking has pieces applicable to non-debian(ish) linux os. On Monday, May 18, 2026 at 1:20:39 PM UTC-7 WeatheredScientist wrote: > @Tom, yes, I have thought of that. Envoys are surprisingly pricey on eBay > presently, but I am watching. Not sure what is going on there. > The old console is a less elegant alternative I've also considered. > What would make this super nice is if Davis just let us output from the > WLL console, instead of trying to force us into a subscription model that > still doesn't offer what I want: local logging at 2.5s refresh, plus upload > to services of my choice at my desired refresh rate (or theirs), not > Davis's. > But I like the challenge of the RF dongle for now. The data is there in > the air, just waiting to be plucked, if you can follow it and read it. > > @Vince, I'll keep it here. I found your github repo: > https://github.com/weewx-contrib/weewx-rtldavis > > I can't seem to perform the optional step, it seems to not find a resource: > > % wget > https://raw.githubusercontent.com/weewx-contrib/weewx-rtldavis/refs/heads/main/weewx-pipinstall/install-v5pip.sh > --2026-05-18 16:13:23-- > https://raw.githubusercontent.com/weewx-contrib/weewx-rtldavis/refs/heads/main/weewx-pipinstall/install-v5pip.sh > Resolving raw.githubusercontent.com (raw.githubusercontent.com)... > 185.199.108.133, 185.199.110.133, 185.199.111.133, ... > Connecting to raw.githubusercontent.com > (raw.githubusercontent.com)|185.199.108.133|:443... > connected. > HTTP request sent, awaiting response... 404 Not Found > 2026-05-18 16:13:24 ERROR 404: Not Found. > > > > On Monday, May 18, 2026 at 2:35:47 PM UTC-4 Tom Hogland wrote: > >> The simplest way might be to look at either an older console or a Weather >> Envoy, and add a Datalogger to whichever one you get. That handles >> everything for you and feeds out a stream of packets that Weewx can >> understand. Both are available on eBay for fairly reasonable prices. >> >> On Monday, May 18, 2026 at 9:53:18 AM UTC-8 WeatheredScientist wrote: >> >>> I am trying to get weewx 5.3.1 up and running on my mac. I am not super >>> fluent with github and the like so it is difficult for me to parse my >>> struggles into language that is more easily understood by people >>> well-versed. I haven't had a real reason to work in a terminal setting in >>> over 25 years minus some cmd line programming in an environment that no one >>> here has heard of (shout out to any scientists who have used Igor Pro!), so >>> it is not something I do for my job or hobby. But I am not unfamiliar with >>> terminals. >>> >>> I am using a Davis 6263 system, which means the full set ISS plus their >>> dinky ecosystem-locked console. I hate the console. I want to bypass it so >>> i can have my data. to do that i need to intercept the RF signal. I have an >>> RTL-SDR v3 dongle and a 915MHz antenna to do that. I will need to frequency >>> hop around that center freq b/c I'm in the US and Davis likes to be >>> difficult. >>> >>> The idea is to run weewx in a container on my NAS. But I am setting that >>> aside. Right now, I am just trying to get it running at all on this >>> macbook, which has the nice terminal vs Windows where everything is a >>> problem. Plus I can move right under the ISS to eliminate SNR as a root >>> cause. >>> >>> So far, I have realized I need weewx to read in data from a .json file >>> that rtldavis will generate. The problem I have is getting rtldavis to >>> actually spit out anything meaningful. I am just seeing a bunch of >>> simualtor data. >>> >>> I don't really know where else to start: it's a bit of unknowns unknowns >>> for me. >>> >>> On Sunday, May 17, 2026 at 8:48:11 PM UTC-4 Vince Skahan wrote: >>> >>>> Well not being clairvoyant it is impossible in the absence of any >>>> information for anyone to guess what you actually installed, nor how, nor >>>> what you see... so it is equally impossible for anybody to help. >>>> >>>> I would suggest you start with >>>> https://www.ministryoftesting.com/articles/11b82aee?s_id=15060040 as a >>>> random ‘how to report an issue’ howto… >>>> >>>> On Sunday, May 17, 2026 at 5:34:57 PM UTC-7 WeatheredScientist wrote: >>>> >>>>> I feel like I am getting close but not quite seeing the big picture. >>>>> I'm able to see the transmitter, but am having trouble decoding its >>>>> output, >>>>> let alone parsing it into a database file of some kind. Github is not my >>>>> strength, but I am willing to learn. What's the best way for me to pick >>>>> up >>>>> what I need to know without being too much of a pain on other community >>>>> members? >>>>> >>>>> On Saturday, May 16, 2026 at 8:30:22 PM UTC-4 Vince Skahan wrote: >>>>> >>>>>> Moved a few months ago to >>>>>> https://github.com/weewx-contrib/weewx-rtldavis >>>>>> >>>>>> On Saturday, May 16, 2026 at 3:31:38 PM UTC-7 WeatheredScientist >>>>>> wrote: >>>>>> >>>>>>> The github link above is dead: does anyone know where to find this >>>>>>> today? >>>>>>> >>>>>>> On Monday, February 10, 2025 at 4:29:18 PM UTC-5 Wayne wrote: >>>>>>> >>>>>>>> I think I have answered my own question in that weewx-rtldavis IS >>>>>>>> the correct weewx driver for me to use. Additionally, the following >>>>>>>> install >>>>>>>> script should make the task even easier as it describes how to use an >>>>>>>> earlier golang version which builds a working rtldavis binary (the >>>>>>>> actual >>>>>>>> SDR software for the Davis protocol). >>>>>>>> >>>>>>>> https://github.com/vinceskahan/weewx-rtldavis >>>>>>>> >>>>>>>> My sincere thanks to Vince for the above assist. Thanks for the >>>>>>>> bandwidth... >>>>>>>> >>>>>>>> Wayne >>>>>>>> >>>>>>> -- 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 visit https://groups.google.com/d/msgid/weewx-user/2a161946-2186-4f3d-9133-3d8daed055a2n%40googlegroups.com.
